I followed the advice in this thread but no success so far: When indiserver is manually started with indi_asi_wheel and the client connects from remote everything works fine. But if it's Ekos to start the server it doesn't work.
I then tried to:
- Replace the config file name from 'ASI' to 'ZWO'
- Delete the config file and the default config. It then doesn't get recreated by Ekos because the driver is not connected.
- Reset all the tables in the sqlite database
- Upgrade to nightly
In all cases it seems to be Ekos failing to start the driver.
The log only reports a generic failure where the device is referred as 'ASI EFW' by the server but then the client cannot find 'ZWO EFW':
[2024-02-06T14:30:04.785 CET DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_asi_wheel"
....
[2024-02-06T14:30:05.005 CET DEBG ][ org.kde.kstars.indi] - Received new device ASI EFW
[2024-02-06T14:30:05.019 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < CONNECTION >
[2024-02-06T14:30:05.019 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < DRIVER_INFO >
[2024-02-06T14:30:05.019 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < DEBUG >
[2024-02-06T14:30:05.019 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < SIMULATION >
[2024-02-06T14:30:05.046 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < CONFIG_PROCESS >
[2024-02-06T14:30:05.046 CET DEBG ][ org.kde.kstars.indi] - < ASI EFW >: < POLLING_PERIOD >
[2024-02-06T14:30:05.111 CET INFO ][ org.kde.kstars.ekos] - Connecting to "Telescope Simulator"
....
[2024-02-06T14:55:10.898 CET INFO ][ org.kde.kstars.ekos] - "Unable to establish:\n+ ZWO EFW\nPlease ensure the device is connected and powered on."Attached the full log.
Any idea?
Ferrante
Read More...
© 2003-2022 by INDI Library. All rights reserved.