Alexandre Chapellon created a new topic ' Missing images in Ekos' in the forum. 2 weeks ago

I have installed Kstars from sources and I'm missing some images whenever I open the mount control window.
Other images in Kstar and even other parts of Ekos seem to show up just fine but not this one as shown below:

Does anyone know if I need to manually copy some files to some place orhave some kind of dependency installed?




I'm facing an issue trying to compile the master branch of the indi-3rdparty repo.
Wether I'm trying to use the debian make_deb_pkg script or following the manual build instructions found on the github page I always get that error bellow:

[ 10%] Building CXX object CMakeFiles/indi_azgti_telescope.dir/azgti.cpp.o [40/237] In file included from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:20, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:23, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgtibase.h:21, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgti.cpp:21: /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:62:50: error: ‘INDI::IGeographicCoordinates’ has not been declared 62 | void AddPoint(AlignData aligndata, INDI::IGeographicCoordinates *pos); | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:78:43: error: ‘INDI::IGeographicCoordinates’ has not been declared 78 | INDI::IGeographicCoordinates *position, bool ingoto); | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:80:94: error: ‘INDI::IGeographicCoordinates’ has not been declared 80 | void AltAzFromRaDec(double ra, double dec, double jd, double *alt, double *az, INDI::IGeographicCoordinates *pos); | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:81:103: error: ‘INDI::IGeographicCoordinates’ has not been declared 81 | void AltAzFromRaDecSidereal(double ra, double dec, double lst, double *alt, double *az, INDI::IGeographicCoordinates *pos); | ^~~~~~~~~~~~~~~~~~~~~~ In file included from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:20, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:23, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgtibase.h:21, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgti.cpp:21: /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:82:94: error: ‘INDI::IGeographicCoordinates’ has not been declared 82 | void RaDecFromAltAz(double alt, double az, double jd, double *ra, double *dec, INDI::IGeographicCoordinates *pos); | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/pointset.h:97:15: error: ‘IGeographicCoordinates’ in namespace ‘INDI’ does not name a type 97 | INDI::IGeographicCoordinates *lnalignpos; | ^~~~~~~~~~~~~~~~~~~~~~ In file included from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:23, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgtibase.h:21, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgti.cpp:21: /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:74:77: error: ‘INDI::IGeographicCoordinates’ has not been declared 74 | virtual void GetAlignedCoords(SyncData globalsync, double jd, INDI::IGeographicCoordinates *position, double currentRA, | ^~~~~~~~~~~~~~~~~~~~~~ In file included from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:23, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgtibase.h:21, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgti.cpp:21: /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:76:50: error: ‘INDI::IGeographicCoordinates’ has not been declared 76 | virtual void AlignNStar(double jd, INDI::IGeographicCoordinates *position, double currentRA, double currentDEC, | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:78:52: error: ‘INDI::IGeographicCoordinates’ has not been declared 78 | virtual void AlignNearest(double jd, INDI::IGeographicCoordinates *position, double currentRA, double currentDEC, | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:80:70: error: ‘INDI::IGeographicCoordinates’ has not been declared 80 | virtual void AlignGoto(SyncData globalsync, double jd, INDI::IGeographicCoordinates *position, double *gotoRA, | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/align/align.h:84:87: error: ‘INDI::IGeographicCoordinates’ has not been declared 84 | virtual void AlignStandardSync(SyncData globalsync, SyncData *thissync, INDI::IGeographicCoordinates *position); | ^~~~~~~~~~~~~~~~~~~~~~ In file included from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgtibase.h:21, from /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/azgti.cpp:21: /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:78:15: error: ‘IEquatorialCoordinates’ in namespace ‘INDI’ does not name a type 78 | INDI::IEquatorialCoordinates lnradec; | ^~~~~~~~~~~~~~~~~~~~~~ /home/alxgomz/workspace/libindi/indi-3rdparty/indi-eqmod/eqmodbase.h:79:15: error: ‘IHorizontalCoordinates’ in namespace ‘INDI’ does not name a type 79 | INDI::IHorizontalCoordinates lnaltaz; | ^~~~~~~~~~~~~~~~~~~~~~ make[2]: *** [CMakeFiles/indi_azgti_telescope.dir/build.make:108 : CMakeFiles/indi_azgti_telescope.dir/azgti.cpp.o] Erreur 1 make[1]: *** [CMakeFiles/Makefile2:97 : CMakeFiles/indi_azgti_telescope.dir/all] Erreur 2 make: *** [Makefile:149 : all] Erreur 2

I have compiled previous versions without errors and managed to build & install indi-core without problem. I have all requirements installed (even installed libindi-dev).
Some info about my compilation env:
$ cmake --version
cmake version 3.18.4
$ gcc --version
gcc (Debian 10.2.1-6) 10.2.1 20210110
$ dpkg -l | egrep '^ii\s+(lib)?indi'
ii indi-bin 1.9.2 amd64 INDI server, drivers and tools
ii libindi-data 1.9.2 all Instrument-Neutral Device Interface library -- shared data
ii libindi-dev 1.9.2 amd64 Instrument-Neutral Device Interface library -- development files
ii libindi1:amd64 1.9.2 amd64 Instrument-Neutral Device Interface library -- shared library

Anyone facing that same issue or knowing how to fix it?


Thank you Magnus! That's exactly the kind of feedback i was joping for :)
Jasem, thanks for you reply too, I guess by best in class you mean from a driver's features perspective? 
It's actually quite funny people come back to me now as yerterday for the first time in more than 2 months (!) I managed to get a really good guiding session with my old heq5! I bought it second hand from someone I didn't knew and i found clues which made me believe i hemihht have have taken great care of it. It. So in the end it took 10 weeks to fot together and correctly tune the new bearings, belt and worm gear! I'm still looking quite avidly at g11g losmandy but don't feel trapped anymore:)

BTW, Jasem thanks for the amazing work and for releasing indi under a free license!


Thank you Nou!
I think my heq5's behaviour makes me very reluctant to buy skywatcher again... I know plenty of people use those but mine has been only nightmares recently, to the point I'm even wondering if I will keep spending that much time and money in astronomy... That makes me sad to say it but that how I feel right now.


No one using either of these drivers (celestron cge, ioptronv3 or losmandy)?
Getting a feedback from someone who uses on of those and clarify wether he/she needs to do an alignment with the hand controler before using the mount with the indiserver would really help me.




I'm looking into getting a new mount to replace my old heq5.
one of the important criteria is a good (read conveniente) indi driver support.
reading the different mount driver documentation i have several states "mount must be firdt aligned" before connecting to the driver. That's the case for the celedtron CGE, Losmandy or ioptronv3 driver (and maybe others...)
Does that mean one needs to proceed to star alignment with the hand controler EVERYTIME the mount is put in place and turned on or just the very first time the mount is turned on?
Such a requirement doesn't exists with the eqmod driver and given i udually only shoot a single target each night i never proceed to star alignment and only rely on polar align + plate solving. Having to start align xith the HC would be a kind of regression if I had to do that for each session, even more problematic in nomad.
Any feedback from users of these drivers or clarification from knowledgeable people would be helpful



So this is a reply just in case someone find it useful one day, given this topic didn't exactly get much traction...
So eventually managed to get indi_v4l2_ccd working again with the SPC900NC modified for long exposure controlled by LED.

In addition to the modification documented here , I had to also patch the indi_v4l2_ccd in order to avoid reaching a part of the code which - according to the comment should anyway not be reached - where the capture was failing.
The patch is attached bellow, but BEWARE: I'M NO INDI DEVELOPER AND I DONT COMMIT TO ANYTHING, DON'T BLAME IT ON ME if it breaks your device, insult your mother or reelect Georges Bush (<- a geek reference is hidden here!)

Thanks to @geehalel for his help and for updating his driver for recent kernels (5.4)


Taking a look at the code I saw the error occurs in an "else" part of an "if" statement:

if ( PrimaryCCD.isExposing() )
        non_capture_frames = 0;

        if( non_capture_frames > 10 ) {
            /* If we arrive here, PrimaryCCD is not exposing anymore, we can't forward the frame and we can't be aborted neither, thus abort the exposure right now.
            * That issue can be reproduced when clicking the "Set" button on the "Main Control" tab while an exposure is running.
            * Note that the patch in StartExposure returning busy instead of error prevents the flow from coming here, so now it's only a safeguard. */
            IDLog("%s: frame received while not exposing, force-aborting capture\n", __FUNCTION__);

So it confirms the CCD should be exposing but indi reports it is not, although I can see the LED is on for the time of exposure and the error message says it's receiving frames in the error message...

I'm lost here, if anyone can shed a light on how frames should be grabbed and what can lead to this error? Is it the capture which doesn't happen at the right time? could it be indi v4l2 driver which do not talk to the device appropriately? Or could it be my mod which is just not right? (BTW, here is the mod I used: spc900 LED mod LX


Whenever I try to do long exposure frames with my spc900 and the v4l2_ccd driver, the driver goes unresponsive and spits the error message bellow repeatedly:

2021-01-31T20:20:23: Driver indi_v4l2_ccd: newFrame: frame received while not exposing, force-aborting capture

I have a webcam Phillips SPC900NC which I modified using the long exposure mod.
I have compiled the pwc-lxled driver for my led, which loads successfully and both normal capture (bellow 0.025 seconds or stacked) and streaming works ok in the indi client UI.
On the other hand, long exposure pictures gives me the error above, though I can see the LED turns on or the duration of the exposure and turns off after exposure time. Only then the error starts to appear in the logs.
I have checked the verbose logs but couldn't find anything obvious (see attached file

File Attachment:

File Name: indi_log.gz
File Size: 50 KB
I'm using a fairly recent version of libindi:
INDI Library: 1.8.7
Code v1.8.6-11-g92c1e617. Protocol 1.7.

The error message seem to suggest the driver didn't really notice it is actually exposing but that doesn't help me much.

Any help is mush appreciated as I have spent a fair amount of time moding this cam and would really like to get this working at some point :)


After a first successful test guiding my setup with an Orion 80x400 and the Phillips SPC900 (non modified), I wanted to try real guiding, not just test and shooting of objects in the sky.
Unfortunately I have tried many different settings but never managed to find a guiding star in the area I was shooting whatsoever!

I have tried fiddling with the V4L2 settings, to make it more sensitive by:
* decreasing fps to 5/s
* raising gain & exposure
* playing with contrast and autogain

Nothing worked... and I just ended up wasting a night :huh:

I'm wondering if I'm missing something, is there any settings or magic trick that's known to work and make the SPC900 sensitive enough for guiding in most areas of the sky?

I suspect that webcam is just not sensitive enough and I would need to mod it. So I have searched for ways to do that but what I found is very partial, talk about different cameras, or is full of broken links...
In particular I'm interested in the LXLED mod as it allows minimal modification and avoids having more cables.

Anyone knows where to find proper doc on how to complete this mod? The software part is already OK as I "ported" the pwc driver patch from @geehalel to the kernel I'm using (4.19) and the LED flashes according to the settings sent using the INDI driver!

Also, everytime the INDI client first connect to the INDI server, the V4L2_CCD driver connects to /dev/video0, while my cam is /dev/video2. So I have to manually disconnect, change the char device manually, reconnect and set the various properties I want... That's rather tedious. Is there a way to have those presets saved somewhere so my client knows which device to use , with which config at connect time?


Alexandre Chapellon replied to the topic 'SPC900 LX without mod' in the forum. 2 years ago

OK thank you very much for the answer.
It indeed seems I missunderstood the purpose of the LXLED feature. I guess I was trying to convince myself it was not necessary to go the hard way... :)



Alexandre Chapellon created a new topic ' SPC900 LX without mod' in the forum. 2 years ago

I just got a Phillips SPC900 I hoped I could use for guiding.
Most things on the setup are working but I can't seem to get the long exposure working on this cam.

It's not moded but my understanding was that it was not 100% necessary.
In particular I was under the impression one could use the LED ioctl in order to transmit long exposure commands.
In particular this thread bellow filled my heart with hope:

@gaetan mentioned his driver can work without moding the cam (at least that's my understanding), so I ported his changes to the current driver and recompiled but despite I can load the new module with appropriate settings (flashled=1) I still get an error when clicking on the "SPC900 LED" button in the "Long Exposure" tab of the indi_v4l2_ccd panel:

2020-08-05T14:24:30: Can not set Lx Mode to SPC900 LED 
2020-08-05T14:24:30: ERROR: device does not support PWC ioctl

Anyone know how to shoot long exposure frames with the SPC900? Is there any solution which doesn't involve soldering and buying more electronic parts?