suvowner wrote: www.amazon.com/gp/product/B0794RL6JT/ref...n_title?ie=UTF8&th=1
Pick one of those for the usb c cable
Very interesting. I'm currently using a USB-A type supply (only 2.4 A), simply because I was worried that if I bought a USB-C supply it might not like the Pi and supply no power or limit to low current mode.
I have had a couple of times where the Pi has stopped responding then found the red power led is off which seems to suggest low power supply.
I've only been able to test it indoors as well but so far it seems much faster than 1.4.4 and 1.4.5, both in starting up and general use. I'm running everything on the Pi at 1920x1080 and VNC in from a laptop.
Kajetan wrote: So why I was getting different PA error every time I was doing this (without correcting PA, just to see if it show the same PA error every time which it doesn't)?
I think its a known bug in polar alignment. If your PA error gets bigger after polar alignment then you have to put the circle on the star, not the end of the line (opposite of what you are supposed to do) I always do it this way and 9 times out of 10 it works.
Tried again last night using indi camera instead of asi camera in PHD2 configuration. It was maybe a bit quicker but still slower than in 1.4.4.
I started using 1.4.5 and found it slow. I was blaming the update but now I've worked out it's being caused by PHD2. When PHD2 is not running everything runs smoothly but after PHD2 is started everything slows down. When I click on a tab to change apps there is a big delay, the tracking graph on PHD2 updates only very 3 or 4 seconds even with the exposure time set to 1 second. Everything is slow including Kstars and the desktop not just PHD2 itself.
I was using PHD2 in 1.4.4 with no problems and I have the same equipment configured (asi camera, indi eqmod mount) so I don't know.whats changed. The only thing different I have done is that 1.4.5 for some reason didn't like my exfat formatted usb stick so I installed exfat support.
Anyone else having problems. Any suggestions?
AstroNerd wrote: Hi, sorry to hear of your issues, I know for a fact that 1.4.4 was reported as very slow with the same symptoms that you have, but the 1.4.5 version, which I have, is much much faster
So not sure why you are still seeing the old issues....but I would certainly check it direct with monitor and mouse and keyboard connected...just to rule out VNC as the issue, I run mine at 2560 x 1600 resolution and all good....
I connected the RPi4 to a monitor and keyboard and it was quite quick. I also used VNC from my laptop at the same time and it was also quick from there. I don't know why it was so slow the first time I used it after updating. Does it do something in the background after the SD card image is written and then used for the first time?
I tried again last night and found the cause of the slow down when imaging - it seems to be PHD2. Before starting PHD2 everything is fine then after starting PHD2 things slow down. I dont think it's a WIFI issue so I'll start a new thread.
When I installed 1.4.5 yesterday I could not connect via Wifi at all. I connected via ethernet and the hotspot was turned off. After fiddling around finally got it connected to my home wifi network. Once running I found the desktop painfully slow. Click on a menu and wait a few seconds for a reaction, or start typing and wait a few seconds for the text to appear. I turned off Compositor which seemed to help speed up 1.4.4 and that improved things. Once using it in the field last night though it slowed down again, and while watching the countdown on a sub in the capture module, the time would only update every 5 seconds or so. I had PHD2 running and that was also slow to update the chart. I only had Kstars and PHD2 running so I don't know why it was so slow. The only changes I made from the stock 1.4.5 image was to set the screen resolution to 1920x1080 through raspi-config, and as I mentioned turn off compositor. What else can cause it to run so slow?
File Attachment:File Name: Light_L_1_secs_2019-11-14T22-24-55_001_2019-11-14.txt
File Size: 4,151 KBYes that will be interesting for me. Focal length of 190 mm hasn't been tested. Try to save a series and drop it somewhere in the web so I can have a look.
File Attachment:File Name: NGC7293_Light_L_1_secs_2019-11-14T20-30-42_001.txt
File Size: 4,151 KB
To avoid saturation, short or very short exposure times will be beneficial for solving.
I've attached 2 images. They are actually fits files but the forum software does not allow fits files for some reason.
han.k wrote: Carneb,
Can you share an image made by the setup you try to solve?
I didn't save any of the images, but I will try to get some tonight and share them here.
knro wrote: Update KStars. That was resolved and Linux/Mac/Windows version all got re-uploaded.
OK thanks I'll try that tonight.
I got the ASTAP solver working last night. It would not solve using my guide scope and camera (what I usually use for polar align assistant) but when I used my primary scope and camera it crashed Kstars, the same result as when using the astronomy.net offline solver. So for me the polar align assistant is not working at all.
I had some success using ASTAP in Kstars on my Rpi4 running stellarmate last night. Using my primary scope and camera it solved very quickly and every time. However using my guide scope and camera (190 x 50mm and asi290mm) it would not solve at all. A small rectangular window would pop up in the top left of the screen and count up in degrees (e.g. 5(30) then 6(30)...) but then eventually say solver failed. The image size was also displayed in the window and that was the correct image size.
I installed ASTAP, The 64bit version wouldn't install but the 32bit version did. It was cloudy last night so could only test from Kstars just using simulators and loading a previous image. It solved the image very quickly so it looks like its working. Hopefully tonight I can test it outside and also see if it works with the polar align assistant.