Created attachment 155713 [details] Log file from Ekos SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** As I have 3 ZWO ASI Cameras, I refer to my ASI1600MC-S as a ZWO CCD, my ASI120MM-S as ZWO 2 and my ASI120MC-SS as ZWO 3. I only use one of the ASI120's for guiding at any time, and that may be with a QSI 683 CCD or the ASI 1600MC-S as imaging cameras. The problem is that I get multiple ASI 120's showing up as selected cameras, 1 as an ZWO CCD 120xxx and the other as ZWO 120xxx STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 155714 [details] Shows 2x ZWO120MM_S Cameras
Another issue is that I cannot find a backup procedure for my settings (Backup does not return any results in a search of the manual) as I have spent hours entering my settings for every new version and often when I reopen the program. Although I press save in each of the Indi Control Panels, the next time it starts I have to re-enter my settings e.g. Observer name and optical train details etc Please note: My location is always showing correctly. Would you like a list of those I regularly reset? And I just love the reworking of the Optical Train format. It suits the smaller screens. Thanks for all you do, I'm in Australia and have been with KStars since 2017. I now have a tripple boot PC with your beta version on Kubuntu, and your stable version on Ubuntu.
Which drivers did you select in your profile exactly?
This will not work. You cannot mix and match "ZWO CCD" driver with "ZWO Camera X" ..etc drivers. These are two separate drivers. You either use "ZWO CCD" once in the profile and it will connect to any number of cameras you have. Or you select "ZWO Camera 1" , "ZWO Camera 2"..etc.
Thank you Jasem, Camera driver issues resolved. My startup issues have been resolved with all cameras playing nicely together on one driver. Setup time last night was about 25 minutes compared to a usual 2 to 3 hours. Information only. Last night I got to observe our dark skies with binoculars while capturing with Ekos. I also saw the brightening of the sky in a Unihedron SQM graph as the milky way went over. My aligned mount with motors is in a fixed position in my backyard where I setup and strip the scope and electronics for each session. Controlling is done by an Ethernet cable from the house. Other projects are all portable. I went into our winter cloud period last May and nearly gave up astronomy over guiding camera connection issues. You have been very helpful.