Guys, I've just made the swap to the INDI/KStars world from the ASCOM world. I got tired of using my dinky old windows laptop with a tiny screen and slow processor and wanted to make use of my shiny, still-new MacbookPro. So far, everything has been good, with the sole and important exception that my guide cam is not recognized by EKOS, and by association, INDI. Therefor, I have been unable to plate solve, autoguide, etc. Though, it is of note that I can still attempt to autoguide via PHD2 (I have other, unrelated issues on that front, but not from the camera).
I know that the problem is not with the camera and/or USB cable as it loads up fine and functions normally in ASI Studio and in FireCapture. I am also taking care that no other application is using it when I load up KStars and try to connect to it. EKOS does connect fine to my other gear (AZ-GTe in EQ mode, Sony A7RII via the libgphoto2 stuff). I have tried to connect it as both a guide cam and as main CCD with no discernable difference in error message. Any guidance would be greatly appreciated as I would like to ditch ASCOM and am considering grabbing a ready-made Stellarmate, just need to iron out this one major kink first. Thanks in advance!
Pertinent Details
Machine: 2019 Macbook Pro 16", 6-core Intel, 32GB RAM, 2TB SSD
OS: Mac OS Big Sur 11.1
KStars Version: 3.5.1 Stable
Build: 2021-01-08T04:07:42Z
Connection to Machine: ZWO-supplied USB 3.0 B to A cable + Apple Brand USB A to C adapter (this combination works fine with PHD2, FireCapture, ASI Studio)
Log Info from Ekos' bottom area for attempt at connecting to my ZWO:
2021-02-03T17:58:20 Unable to establish:
+ ZWO CCD
Please ensure the device is connected and powered on. [It definitely is]
2021-02-03T17:58:14 INDI services started on port 7624.
2021-02-03T17:58:12 Starting INDI services...
Full verbose log info:
[2021-02-03T18:08:43.039 JST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_ccd" crashed!
[2021-02-03T18:08:54.040 JST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_ccd" crashed!
[2021-02-03T18:09:05.056 JST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_ccd" crashed!
[2021-02-03T18:09:14.988 JST DEBG ][ org.kde.kstars.indi] - Removing managed driver "ZWO CCD"
[2021-02-03T18:09:14.988 JST DEBG ][ org.kde.kstars.indi] - Stopping INDI Driver "indi_asi_ccd"
[2021-02-03T18:09:15.004 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: stop indi_asi_ccd"
[2021-02-03T18:09:15.005 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_asi_ccd - tDriver: indi_asi_ccd"
[2021-02-03T18:09:15.006 JST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2021-02-03T18:09:15.990 JST DEBG ][ org.kde.kstars.indi] - Adding managed driver "ZWO CCD"
[2021-02-03T18:09:16.002 JST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_asi_ccd"
[2021-02-03T18:09:16.003 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_asi_ccd"
[2021-02-03T18:09:16.004 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_asi_ccd"
[2021-02-03T18:09:16.005 JST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2021-02-03T18:09:16.006 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: pid=1521 rfd=5 wfd=8 efd=9"
[2021-02-03T18:09:16.007 JST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2021-02-03T18:09:16.051 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: dyld: Library not loaded: @rpath/libASICamera2.dylib"
[2021-02-03T18:09:16.053 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: Referenced from: /Applications/KStars.app/Contents/MacOS/indi/indi_asi_ccd"
[2021-02-03T18:09:16.053 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: Reason: image not found"
[2021-02-03T18:09:16.054 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 1521 died"
[2021-02-03T18:09:16.055 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: stderr EOF"
[2021-02-03T18:09:16.056 JST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2021-02-03T18:09:16.057 JST DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-02-03T09:09:16: Driver indi_asi_ccd: Terminated after #0 restarts."
[2021-02-03T18:09:16.057 JST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2021-02-03T18:09:16.069 JST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_ccd" crashed!
Read More...
Guys, I've just made the swap to the INDI/KStars world from the ASCOM world. I got tired of using my dinky old windows laptop with a tiny screen and slow processor and wanted to make use of my shiny, still-new MacbookPro. So far, everything has been good, with the sole and important exception that my guide cam is not recognized by EKOS, and by association, INDI. Therefor, I have been unable to plate solve, autoguide, etc. Though, it is of note that I can still attempt to autoguide via PHD2 (I have other, unrelated issues on that front, but not from the camera).
I know that the problem is not with the camera and/or USB cable as it loads up fine and functions normally in ASI Studio and in FireCapture. I am also taking care that no other application is using it when I load up KStars and try to connect to it. EKOS does connect fine to my other gear (AZ-GTe in EQ mode, Sony A7RII via the libgphoto2 stuff). I have tried to connect it as both a guide cam and as main CCD with no discernable difference in error message. Any guidance would be greatly appreciated as I would like to ditch ASCOM and am considering grabbing a ready-made Stellarmate, just need to iron out this one major kink first. Thanks in advance!
Pertinent Details
Machine: 2019 Macbook Pro 16", 6-core Intel, 32GB RAM, 2TB SSD
OS: Mac OS Big Sur 11.1
KStars Version: 3.5.1 Stable
Build: 2021-01-08T04:07:42Z
Connection to Machine: ZWO-supplied USB 3.0 B to A cable + Apple Brand USB A to C adapter (this combination works fine with PHD2, FireCapture, ASI Studio)
Log Info from Ekos' attempt at connecting to my ZWO:
2021-02-03T17:58:20 Unable to establish:
+ ZWO CCD
Please ensure the device is connected and powered on. [It definitely is]
2021-02-03T17:58:14 INDI services started on port 7624.
2021-02-03T17:58:12 Starting INDI services...
Read More...