My equipment works on Stellarmate's latest Build: 2021-04-23T17:00:52Z Stable release.
but the Nikon DSLR driver doesn't connect on either the stable or nightly builds on Unbuntumate 20.0.4 on an Odroid-N2
although it seems like there is a service running
"2021-04-27T15:42:59: Driver indi_nikon_ccd: pid=196435 rfd=5 wfd=10 efd=11"
A log file showing this from the last run is attached
How do I determine the current indilib version and gphoto2 version?
120 MM Skywatcher Esprit on Celestron CGX, ZWO ASI 224MC guiding, Pegasus FocusCube v2
Nikon Z7 8256 x 5504, 35.9 x 23.9mm 4.34 um. Triad Ultra Quad NB Filter
1) Odroid-N2 Ubuntu-mate 20.04 2) StellarMate on RPI4 8G
The good, the bad, the ugly at sciencedowneast.no-ip.ca/zenphoto/
I finally made it (still don't know what exactly solved the problem). I purged everything from the system,kstars-bleeding,indi-bin,indi-full everything. Then I built indi from source following the directions here: indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html . I successfully built indi and indi 3rd party drivers from source but a problem occurred when I tried to build Kstars from source and couldn't solve it. Then I installed kstars-bleeding from PPA following the directions and everything is working fine now. Kstars 3.5.3 stable.
Hope I helped you a bit with that but still don't know what exactly was the solution. I think the proper installation of 3rd party drivers was the solution.
Clear skies to everyone.
AAVSO/SILSO - Sun Observer - Sunspot Counting
ESA ARIEL Exoclock Project & NASA Exoplanet Watch Project - Exoplanet Observer
Sky-Watcher Black Heavy Duty EQ6 mount
Sky-Watcher 254/1200 mm Newtonian
Bresser Skylux 70/700 mm
ATIK 320E Mono
QHY 6 Mono
I did not purge the previous 3.5.3 but went to the ppa and installed Kstars-bleeding and it left me with Kstars 3.5.4 Beta instead of 3.5.3 Stable? I am trying to purge the nightly build ppa and try again. Could you explicitly show the commands you used to install Kstars 3.5.3 Stable. The Kstars 3.5.4 Beta was still not showing my SX CCD in the Indi Control Panel, so I am still trying to get a stable working Kstars for my equipment.
I got my QHY camera working by purging/reinstalling kstars and indi-full as recommended above, and then rebuilding and installing just libqhy from the 3rd party drivers from github. Now I seem to have everything working. I tried (and failed) to rebuild indi_qhy_ccd, but that wasn't needed in the end.
I had an indication from Jasem that the PPA had resolved the issue (a day or so ago). When I use the ppa and install Kstars-bleeding I ended up with Kstars 3.5.4 Beta and my SX CCD still did not show up in the Indi Control Panel. So I was trying to find a way to get to 3.5.3 stable. I found this info on one of the download pages:
"If you would like to stop using Nightly PPA builds and instead return to using stable PPA builds then run the following commands:
sudo apt-get install ppa-purge
sudo ppa-purge ppa:mutlaqja/indinightly "
So I did that and I ended up with Kstars 3.5.3 Stable, but my SX CCD is still not connecting. However now I get a message from Indi(?) that the SX CCD is not connecting and I should check if it is connected and powered up. It is connected, it shows up in lsusb as the Starlight Express Lodestar and it runs fine in PHD2.
I seem to be making progress as at least now I get a warning about the SX CCD but I don't know how else to debug the connection to Kstars/EKOS
If I go to the Device Manager in Kstars and select the SX CCD and hit Run Service it says:
"Driver Indi_sx_ccd pid=2074 rfd=4 wfd=11 efd=12
Client 5: new arrival from 127.0.0.1:46726 - welcome!"
so somewhere it seems to be recognized, but not in Ekos?
the log does not tell me much more than it is not connecting.
Having run the ppa:purge above will I now only get 'stable' versions of Kstars rather than nightly builds? Yet installing kstars-bleeding seems to imply that you will get the latest (nightly) build. I have not tried it but can you just run:
sudo apt-get install kstars (instead of kstars bleeding)
Not sure any of this has to do with the SX CCD issue. It does seem that this update of release of 3.5.3 stable has a lot fewer issues than a few days ago. I am just trying to let the developers know that there are still some issues.