I think I might (possibly) be experiencing the same type of problem with my ASI294MC-Pro. In my case, when capturing darks the first 300 second dark downloads OK, but subsequent dark downloads are corrupt/incomplete (either with a filesize of 0MB, or ~5MB - expected filesize would be ~23MB).
I also built from source.
Can you guide me on how to apply the rule you posted above? Are these commands to be entered from bash?
Pardon me if this is a silly question - I am running Raspbian on Raspberry Pi4 and used your script to set everything up. I configured the Field Wifi to turn on after 3 minutes if the default 'home WiFi' is not found in range. Can you tell me if there is a simple way to VNC in via the Field Wifi access point (I can do this fine) and then switch the network on the Pi back to the 'home WiFi' (assuming it is in range), without having to reboot the Pi?
The reason I ask is I have found that sometimes when I boot up, even if the Pi is close to my router, it is not detecting the home WiFi and is switching to Field WiFi mode.
Thanks a million, I ran the systemUpdater script first and am now re-running the setupAstroRaspbian script to do the git pull and rebuild of kstars & indi which seems to be doing its thing just fine
Thank you so much for the continued work on the AstroPi3 script. I used it flawlessly last week to install everything on my new Raspberry Pi 4 (4GB) and it went off without a hitch.
I noticed that a new version of indi library was released yesterday, and was wondering what the process is for updating kstars / indi libraries etc. as new versions are rolled out? Is it possible to rerun the script to get the system to download latest code and then it will automagically rebuild indi library / kstars etc?
Hi, I invested in a Pegasus Pocket Powerbox recently when I heard they had implemented a Indi driver for the device. I finally managed to get the driver installed on my Raspberry Pi 3 last night, but can't find much documentation on how to use all the setting within the Device Control. I was wondering if it might be possible to create a Wiki page which is similar to that for the Ultimate Powerbox (
), but specifically for the Pocket Powerbox?
Thanks Jasem, I used that update command it appears to have resolved by issues accessing the libqhyccd.so.2 library, happy days
Hello, last night I fired up Ekos & Indi for the first time in a few months. I did an update of kstars-bleeding and indi-full on my Raspberry Pi 3 Model B, running Ubuntu Mate 16.04.
After trying to start indiserver for my QHY 5L II (Mono) using indi_qhy_ccd I get the following exception on the console:
2018-09-12T21:27:56: startup: indiserver -v indi_qhy_ccd
2018-09-12T21:27:56: Driver indi_qhy_ccd: pid=2114 rfd=3 wfd=6 efd=7
2018-09-12T21:27:56: listening to port 7624 on fd 4
2018-09-12T21:27:56: Driver indi_qhy_ccd: indi_qhy_ccd: error while loading shared libraries: libqhyccd.so.2: cannot open shared object file: No such file or directory
2018-09-12T21:27:56: Driver indi_qhy_ccd: stderr EOF
Child process 2114 died
Can anyone advise if there is a workaround for this issue with QHY cameras on the latest driver? Am I missing something from my update process?
Just a quick update on this - I did not succeed to boot up Ubuntu Mate 16.04.2 on the new Raspberry Pi 3 B+ as it appears to need an update of bootloader / kernel. There is a thread discussion here:
The official download from Ubuntu Mate website for RPi has not yet been updated to support the new Pi 3 B+. I guess there is some way of updating on top of my current Mate install but I have not yet figured out how.
I noted today that a new version of the Raspberry Pi (Model B+) has just been released and couldn't help but purchase one as an upgrade to the original Raspberry Pi 3 that I have been using. It boasts 5GHz Wifi (which should give a nice speed increase in downloading of FITS files, when connecting to Indi from another client machine) as well as higher processor spec etc.
I was wondering do you know / expect if the script you have worked on here should work out of the box with the new Raspberry Pi version? In any case, when I receive it I can try it out and let you know if anything unusual turns up.
I was just looking at the GIT history for indi_qhy, I don't suppose this recent fix could possibly be related to / provide a resolution for the issue I am describing in this thread? If so I could try to build the driver from source on my Raspberry Pi 3:
Sorry, yes I should have said in my previous post - the issue is still the same (QHY getting stuck at capture after dither applied, and 'Lost Track of Guide Star' appearing in console) as with the previous version of KStars / Ekos.
Hi Jasem, just a quick note that the dithering issue remains the same in version 2.93. I was wondering if you might have any ideas of how I could resolve this, or a possible workaround that would achieve the same end result as the automated dither? Not having the dither option is really killing me with the colour mottle in final stacked DSLR image