I have the ASI462MC. I have not tried it on Astroberry. I have it working in Windows 10. But at first I could not get it to work in Firecapture 2.6 in Windows 10. It turns new Firecapture 2.7 beta has the latest ZWO drivers integrated into the program. An alternate solution listed in another forum is to replace the driver in the Firecapture 2.6 folder with the newest one from ZWO.
I don’t know if this new 2.7 version is available for the pi. I don’t know if the pi version has the drivers integrated into the program where you could swap in the latest INDI version. But it is something you might want to look into.
That fixed it. Thank you.
Decided to give StellarMate another try on Rpi 4 with a fresh install of 1.5.1.
Using the iPad app, I get an error when attempting to access the desktop. The iPad app is version 1.9.13. I think I heard there is a newer iOS app, but my version is the latest on the App Store. The error occurs both when I am connected to the hotspot and when connected to my home WiFi.
Attached is a screen shot of the error. I had the same issue that prevented me from using 1.4.6. I have cleared the browser cache on my iPad, as suggested on the Facebook group.
I was just working with the Astroberry, taking a screen shot to show you the NO FIX in the INDI Control Panel. The GPS dongle was blinking green, and Control Panel/Main Control of GPSD showed NO FIX.
Just for kicks, I hit the Disconnect button and then the Connect button and the info updated to reflect my current position, time and a 2D fix, next to my office window.
I have a U-blox7 USB GPS. I have successfully used it on StellarMate on an Rpi3 using GPSD. It just worked out of the box. Now I am trying to use it on Astroberry Server 2.0 on a Pi4. Ekos says the device is connected, but NO FIX. The light on the dongle is blinking green, indicating that is has determined its position.
I tried playing with the GPSD configuration file in /etc/default/ to change the DEVICE = to “/dev/ttyUSB0” as suggested in another thread, but I get a permissions error when trying to save the changes to the file.
So I am stuck.
Hope someone here has had success they can pass along. Thanks.
Fresh install of the RPi 4 version. Hotspot showed up quickly. No problems switching to my home network.
In the app, hit connect in NoVNC and this pops up. Same message whether connected to hotspot or my wifi, just different addresses.
I can't help with the log files, but I have had similar behavior from my EQ6-R Pro with it starting to flip and then just stopping. A subsequent GoTo command put it on target on the wrong side of the pier.
So, after reading some other forum posts, I now have the meridian flip set to trigger at + 0.2 hours instead of the default of 0. At that hour angle, the mount has no doubt that it is past the meridian, so it completes the flip.
In the guiding tab, select your guide camera as the camera and as the mount. That will tell Stellarmate to send guiding commands back through the guide camera, which will route them to your ST4 port.
SSAG now capturing and looping images on the Pi3. I will try the Pi4 later. Thank you so much.
I am still getting this error on the latest 1.4.4 Rpi3 and Rpi4 versions. I ran software updater today, Sept. 29, on both machines and the rules file in lib\udev\rules.d was updated with the 9/28/2019 85-QHYCCD.rules. I have rebooted both machines a number of times.
My camera is the Orion SSAG. It has worked well in the past connected as a QHY. On Stellarmate, the camera is listed as QHY-M-. In the rules file, under SSAG, it says stuff like idproduct "0011" and QHY5Loader.hex.
It connects with no problems, but will not take a picture. In the camera module it says capture aborted and in another place it says GetQHYCCDSingleFrame error (-1)
Do I need to run a firmware update or downgrade on the camera somehow?
What else should I be doing to make this work?
Thank you. Apparently, the first time I ran software updater, it did not update the indi library. The camera is connected and capturing frames now.
I am having the same problem with the QHY driver crashing on Stellarmate. Using an SSAG that worked before the latest update.