Upgraded to 1.5.1
Ran a 60x240s sequence. All on RPI4 (as quoted below). Not a single problem. Really nice!
Well, there was one issue which is not RPI4 or 1.5 specific and has been there for quite a while.
Bias frames. (this was reported before).
Often, Ekos takes bias frames but they are completely empty (no signal whatsoever).
Usually this happens on the first run, when switching from Lights or Darks to Bias.
Switching back to Lights and taking a few exposures makes Bias to behave normally.
Couldn't quite figure out the exact pattern.
At least I know now that the issue exists and sort of know how to get around it.
RPI 4 B (4Gb) with SMate
Askar FRA400, TPO RC6, Nikon D5500 full spectrum (with IDAS D1 clip-in filter).
ZWO ASI120MM Mini on ZWO 30F4
ZWO ASI224MC-S on Orion 50 mm f/3.2
ZWO EAF x 2
Last night I had to position my mount slightly further away from the house which meant that my wifi connection from my laptop running Kstars and INDI on the Pi was not strong.
I lost connection a few times and focussing was impossible (too long required for the download).
I had an old Airport Express (mini router/Access point) which I have now connected directly to the Pi with a cable. Seems to have solved my wireless woes.
I think the Pi wireless access point is very weak and only really seems to work if you are within a couple of metres.
WO ZS 61
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
294 mc pro
224 planetary cam
174 guide cam
Sesto Senso focusser
QHY5II-Mono guide camera
EOS6D - not modified
That honestly baffles me. I imaged again last night and my rig is ~60ft away from the WiFi extender I am using for coverage in my backyard. So definitely not ideal conditions, with distance, extender and all.
Nonetheless, the INTERNAL 5GHz WiFi of the Pi4 never had any trouble whatsoever with that constellation.
I get consistent connection speeds of ~ 390 Mbs, which makes for a very snappy response via VNC. I am running KStars on the Pi4 directly.
I can only wonder whether the poor connection many people here are describing is the result of either a subpar power supply that cannot pull the Amps the Pi4 needs to run at full speed, or whether it is somehow related to the OS. I am using Ubuntu 18.04 as my OS on the Pi4.
Maybe the key is the power supply. I am using the one that came with the Canakit when I originally ordered the Pi4. Rated to 3.5 Amps.
@rishigarrod: Just popping prior post on issues between USB3 and Wifi at 2.4Ghz. It's not clear whether you're using the Pi4's USB3 ports, and you didn't say whether your wireless is using 2.4Ghz. If yes to both, it's most likely that you are experiencing RF interference. This has nothing to do with SM 1.5. It's solely a function of Pi4's USB3 close proximity to the internal wifi antenna. See this prior post for details and workable solutions: www.indilib.org/forum/general/6576-pi4-u...erference.html#50509
FWIW, after adding a direct ethernet cable from laptop to Pi4 (lured by speed improvement), I'd never go back to wireless now unless it was an absolute emergency ! Clear skies...
p.s. For Jo, I'll note that although power supply can be a problem (lots of prior posts on poor power issues), when it's Pi4, USB3, and wifi at 2.4Ghz, it's almost certain to be RF interference (and NOT power). Similar symptoms though, so it can be very confusing. Folks need to take note as they migrate to Pi4 with USB3 since 2.4Ghz wireless is everywhere, and people don't necessarily think to take action to switch over to 5Ghz.
Thanks, Doug! I had forgotten about the WiFi interference problem. Never had it, since it felt natural to connect via 5 GHz only. 2.4 GHz WiFi is just too slow. About 6 times slower.
Anyway, just to let everyone know not to give up on the internal WiFi of the Pi4. It works great on 5 GHz and it is not weak at all.
Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set
- Raspberry Pi 4, Model B, 4GB
- Official Raspberry Pi 4 Power Supply / 5.1V / 3A / USB-C
- FLIRC Raspberry Pi Heatsink Case
- Adafruit PiRTC DS3231 RealTime C
- Ethernet cable to home LAN
- USB-HEQ5 PA Interface (USB to serial cable)
- HEQ5 PRO Mount (connected via EQMod Mount)
- ZWO ASI294MC Pro
- ZWO ASI120MM-S (as guiding cam)
I tried KStars 3.4.3 for MacOS (recommended by Stellarmate) but when connected to Stellarmate via Ekos it was quite unstable. If I left the computer for a couple of minutes it seemed it kind of lost the connection for a while and then sometimes managed to reconnect again when I did something like trying to click another tab in Ekos or so. I could not really be sure if an ongoing capture sequence was working properly or not. Sometimes it never reconnected an I had to restart everything. When I tried looping captures or running video it crashed immediately.
It's a pity since the user interface felt better in MacOS KStars than directly in Stellarmate (via VNC). It was somewhat more stable when connected via Ethernet (cable) but not entirely stable.
Anyone else has the same experience?
The only stable setup so far is as below:
- The Rapberry Pi connected by ethernet cable to my home LAN.
- Running VNC from my MacBook (connected on my home WiFi) to run Stellamate's local KStars and Ekos.
- The ASI294 connected directly to the RPi's USB 3.0.
- The ASI120 guiding cam connected to the ASI294's "USB2.0 Out" connector.
- The ASI120's ST4 cable connected to the mount.
- The mount connected (via USB-HEQ5 USB/Serial cable) directly to one of the RPi's USB 2.0 connectors.
This setup has been really stable. When I try to use the RPi on WiFi it randomly freezes. I have only tried on 2.4GHz though since I though that should be more stable, but I now read in this thread that 5GHz might be more stable? I'll definitely try that, since using the extra ethernet cable is a bit of a hassle.
EDIT: I can confirm that after about 24 hours of testing it seems really stable over 5GHz WiFi as well!
I've also tested using a couple of USB 3.0 hubs (with external 2A power) since I thought that was causing instability, but it seems equally stable to connect the ASI294 directly to the RPi's USB 3.0.