https://bugs.kde.org/show_bug.cgi?id=523212
Bug ID: 523212
Summary: macOS 26.5.2: ZWO EFW 8×1.25" detected but cannot be
initialized (Failed to get filter wheel info)
Classification: Applications
Product: kstars
Version First 3.8.3
Reported In:
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Environment
-----------
KStars: 3.8.3 (official macOS bundle)
macOS: 26.5.2 (25F84)
Hardware: Apple Silicon MacBook Pro
Device: ZWO EFW 8×1.25"
Problem
-------
The filter wheel cannot be connected from Ekos.
Ekos reports:
Unable to establish the following devices:
+ ZWO EFW
The device never appears in the INDI Control Panel.
Expected behaviour
------------------
The filter wheel should be initialized and appear as an INDI device.
Actual behaviour
----------------
The driver starts, detects the wheel, but fails while retrieving its properties
and never creates the INDI device.
Diagnostics
-----------
macOS detects the device correctly:
Vendor ID: 0x03c3
Product ID: 0x1f01
The bundled driver exists:
indi_asi_wheel
The bundled SDK libraries exist:
libEFWFilter.dylib
libASICamera2.dylib
Running the driver manually:
./indiserver -vvv ./indi_asi_wheel
produces:
HotPlugManager: Discovered ASI EFW with ID: 0
HotPlugManager: New device connected: 0
HotPlugManager: Failed to get filter wheel info for ID: 0
HotPlugManager: Failed to create device for identifier: 0
The above messages repeat every second.
Additional information
----------------------
ASIStudio (installed on the same Mac) detects and operates the same EFW
correctly.
Therefore:
- USB communication is working.
- The hardware is functioning correctly.
- The issue appears to be specific to the INDI ZWO EFW driver and/or the SDK
bundled with the KStars macOS package.
Additional observations
-----------------------
The SDK libraries bundled with KStars differ from those bundled with ASIStudio
(different MD5 hashes), suggesting they are different SDK versions.
No crashes occur. The failure happens after device discovery, during retrieval
of the filter wheel information.
--
You are receiving this mail because:
You are watching all bug changes.
