1.4.6 release - impressions, problems, etc. Please post.
knro wrote: It could be 64bit Kernel, by January we will have the stable release for RPI4 ready.
Just in time for clear weather! (dang clouds)
I checked today and a lot of problems in RPI4 with wifi when connect a usb 3 device. The 1.4.6 very slow compared with Astroberry 2.0.0, that works very fine, estable and fast than stellarmet, at lest for RPI4.
maxthebuilder wrote: Installed today. All is good so far.
Only tried indoors. Bad weather.
I was on 1.4.3 for some time. 1.4.4 and 1.4.5 didn't work well for me.
Enviado desde mi SM-T813 mediante Tapatalk
Skywatcher Quattro 250 with f4 coma corrector
Skywatcher Evostar 80ED with 0.85 reducer/flattener
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser
Carneb wrote: I tried it for the first time last night in the field. It seems to run OK except for when running PHD2. When running PHD2 everything slows down, the same problem I had in 1.4.5.
Yes me too, but to be honest mine slows right down as soon as Kstars has been open for a few minutes.....
Skywatcher EQ8 pro
Meade series 5000 80mm triplet Apo & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar Guide Camera
Pegasus Ultimate Hub for all USB & Power
Pegasus focus motors on both scopes
Anyways, I had one lockup after a bunch of imaging (I almost got all the way through my Blue images).
Restarting I was event free all night.
One thing, my network (I use an ethernet connection for the speed) worked from a boot after I removed my powered USB hub. I no longer needed it because of the 2 extra on the camera. First time I didn't need to unplug all my USB3.0 cables before trying to connect. I suspect my wireless would be working if I tried. I'm not because of the +10x speed on my hardwire.
The ASTAP worked beautifully and quickly. Astro.net still did have the correct FOV . I use a focal reducer and must not think of that when it auto calculates my FOV. ASTAP seems to.
when using the internal guider, after a dither the guider would then constantly try to guide the dither back to the baseline. I tried 5 and 10 second settle times and no improvement.
I still don't understand why the histogram in the fits viewer looks so much different than other programs like nebulosity or astroimager.
is kstars compatible with macOS Catalina ?
I noticed the qhy polemaster app built into 1.4.6 which is really cool thank you for this.
based on this I decided to use an old apple airport express as an access point and connect it to the pi4 ethernet plug and the pi4 seemed very responsive when using safari browser on my iMac inside to vnc to the pi4 at my telescope outside, otherwise the pi4 5ghz wifi signal strength was only 1 bar. the pi4 automatically recognized and used the ethernet connection .
suvowner wrote: also, this was an interesting read regarding wifi and the pi4.
Good article. I even feel better using my Ethernet hard wire.
It happens after there is a high CPU load, such as plate solving or using the mount control while doing live video from my DSLR camera.
Additionally it won't switch out of Hotspot mode and recognize any nearby wifi signals to connect. KStars no longer locks up when closing the live video or loop of the Nikon DSLR.
Equipment is: ioptron ieq45 pro, sky safari, qhy 168C, pole master and qhy5L-IIc
- Wifi Hotspot comes up automatically but it takes 1Min 57Sec for the hotspot to show up from power on. Must have rebooted over 50 times and every time it is exactly the same time to the second. Bootup time only is 30 secs
- If I leave it on Auto, the Wifi always uses the 2.4Ghz band so I manually set to to the 5Ghz band to get the faster speed.
- I initially had the same issues with the WiFi dropping out but that disappeared after I did a reset of the network configuration with the manual configuration to lock it on the 5GHz band.
- VNC over 4K is very laggy but at 1920x1080 is it very fast.
Now for my issues (haven't done an update, just downloaded the image)
- There seems to an issue with my mount and sky safari - If I just plug in my 3 cameras, all the cameras work.
- If I then add my mount, I need to plug everything in a certain order, otherwise the Polemaster will crash kstars when taking a drak frame or the 5L occasionally does not show up in the indi panel, or all three cameras are unable to take an image and no messages in the indi panel. It is like ekos has lost communications with the cameras. The order is the three cameras first and then my mount before starting the indi server. Mount has to be on the first USB port but the last device to be plugged in
- If I then add in Sky Safari as an aux device, I see it connecting to the server but when I press connect in Sky Safari on my ipad, I see a message in the indi panel saying the client cannot connect so my ipad is communicating with the Pi but cannot connect to kstars. This occurs in both the Pi3 and Pi4. Works on 1.4.4
- When I add in Sky Safari and take a dark frame with the Polemaster, kstars crashes, doesn't occur when it is a light frame!!!! Not too much of an issue as I probably would never take a dark frame with my polemaster.
Wifi Hotspot comes up automatically but it takes 1Min 57Sec for the hotspot to show up from power on. Must have rebooted over 50 times and every time it is exactly the same time to the second. Bootup time only is 30 secs
That's too long. Can you run this command?
What's the output?