Glad that your system is now ok.
In my case it seems to be dithering still. Disabling it the scheduler runs all night.

Ferrante

Read More...

Glad that your system is now ok.
In my case it seems to be dithering still. Disabling it the scheduler runs all night.

Ferrante

Read More...

hi Chris,
it seems you dither every 5 frames. Dithering is the last line in your log, and, even though dithering is successful, it fails to capture the next frame.
As a test, try to disable dithering.

I'm experiencing the same issue, we both use 10micron lx200 driver.
Here's my log:

[2024-02-25T22:35:31.252 CET INFO ][   org.kde.kstars.ekos.capture] - Dithering...
[2024-02-25T22:35:31.252 CET INFO ][   org.kde.kstars.ekos.capture] - "Dithering..."
[2024-02-25T22:35:31.252 CET INFO ][   org.kde.kstars.ekos.capture] - "Dithering..."
[2024-02-25T22:35:31.252 CET INFO ][     org.kde.kstars.ekos.guide] - Starting non-guiding dither...
[2024-02-25T22:35:31.253 CET WARN ][     org.kde.kstars.ekos.guide] - Non-guiding dither failed.
[2024-02-25T22:35:31.253 CET INFO ][   org.kde.kstars.ekos.capture] - Dithering failed, capture state "Dithering"
[2024-02-25T22:35:31.253 CET INFO ][   org.kde.kstars.ekos.capture] - "Warning: Dithering failed."
[2024-02-25T22:35:31.253 CET INFO ][   org.kde.kstars.ekos.capture] - "Warning: Dithering failed."
[2024-02-25T22:35:47.600 CET INFO ][ org.kde.kstars.ekos.scheduler] - Scheduler is stopping...
[2024-02-25T22:35:47.601 CET INFO ][   org.kde.kstars.ekos.capture] - "CCD capture aborted"

Ferrante

Read More...

hi Nick,
I'll keep trying. thanks,

I doubt it is cable issue: It works fine if I start it as standalone server. Plus, it's 10.000km from home...although I can ask people there.
ferrante

Read More...

hi Nick,
thanks for your help.
I followed step by step what you described above. Unfortunately I get the same error: after starting Ekos and before the USB selector pops up I get the 'unable to connect' error.
I downgraded to 3.6.9 stable for this test, did you use nightly?

Ferrante

Read More...

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...

Luigi is friends with Ferrante Enriques

Teseo is friends with Ferrante Enriques