Greetings,

My ATIK & QHY cameras are not recognized by Ekos after upgrading to 3.5.3 stable running on Ubuntu 20.04 desktop. Cameras are connected on the laptop and powered on. Both drivers are at the newest version:
ATIK - 2.6~202104252346~ubuntu20.04.1
QHY - 2.7~202104260035~ubuntu20.04.1

Photo and logs file attached.
Any thoughts on this?
Thank you very much for your time in advance.

Best regards,
George.

 

I'm seeing the same on Ubuntu with ASI cameras and EAF - 3.5.3 Stable

Same problem with QHY and ZWO cameras on Ubuntu 20.04 after 3.5.3 upgrade.  The drivers are running, though, because I can connect to them with PhD2, and capture images.

again same for me (Ubuntu 20.04 LTS) 
QHY_CCD and Altair no connection but a ZWO 178mm is up and running

CS Heiner

Same issue for me with SX and ATIK drivers www.indilib.org/forum/general/9581-sx-an...r-recent-update.html

I have the same problem.
QHYCCD is not recognized by the updated new INDI (1.9.0).
This has also happened in Nightly Build for some time.
The following message is output.

Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.

Of course, the device is connected and powered on.
It is recognized normally in INDI version 1.8.9.
I have stopped updating to the new version.

 

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?

Greetings again guys, 

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.

Best regards,
George.

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.

thanks,

Greetings Ronald. You can purge the nighty build following the commands here with ppa-purge command: www.indilib.org/download.html . Also you can purge everything with sudo apt purge (what you want) for example sudo apt purge indi-full. After purging everything you start all over following the commands here: indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html . You can give it a try and build from source.

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.

The kstars and indi-full installs were from the repository.  That wasn't clear in my previous message. The only thing I had to build and install was lbqhy.