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
Just to add a note, I finally tried out version 2.93 yesterday and the issue I reported with strange ADU value now appears to be resolved for me. The maximum ADU also now appears more to be what I would expect for a 14-bit DSLR (verison 2.93 reports around 15900 for a 20second exposure, whereas the previous version was reporting a value of around 8000 for the same exposure length / target brightness).
Thanks for the update
Thanks Jasem, I will try version 2.93 when it is released and report back here.
It is 14-bit, but when I shoot a really long (eg. 30s) flat exposure @ ISO200 it tells me that the ADU is around 4800 or so?
I have been trying to use the calibration section for capturing flats for my Canon 450D. I set a target of an ADU of around 2750, and put in an initial exposure of 0.25 seconds. Whenever I do this (even with other initial exposure lengths), on the 3rd exposure during calibration, Ekos reports a really weird ADU value in the console which is a massive number. I have attached a log, see line #170, the number calculated for ADU is of the order of 10^120.
I ended up just using manual exposure length as I could not get the calibration setup to work because of the above issue. Has anyone else come across this strange ADU value being shown?
Thanks Jasem, by capture - do you mean capture of the guiding camera? I think the dither operation used to work for me with the same hardware about 9 months ago or so, I recently came back to Ekos/Indi and did a full update about 3 weeks ago or so.
On a slightly related question: when capturing a dark frame from within the Guide Module, it appears to only be possible to capture a single dark. Is this the case, or is it possible to capture multiple which are stacked to improve the picture quality when guiding?