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

Ferrante Enriques replied to the topic 'Scheduler and pause' in the forum. 2 months ago

Why not adding in the scheduler a fake sequence 1s exposure and 599s delay?
It's not elegant nor smart but should do the work.

Read More...

Ferrante Enriques replied to the topic 'Python driver package' in the forum. 7 months ago

hi Bernard,
you were right about the connection standard property.
I added this switch to the Thermostat:

# create a switchvector so client can turn on/off connection
    connectionswitchmember = SwitchMember(name="CONNECT", label="Connection",
                                   membervalue=thermalcontrol.connectionswitch)
    connectionswitchvector = SwitchVector( name="CONNECTION",
                                    label="Connection Control",
                                    group="Control",
                                    perm="rw",
                                    rule = "AtMostOne",
                                    state="Ok",
                                    switchmembers=[connectionswitchmember] )

And the error message is gone. But I know that managing connection properly is more than that: some property like connection itself and connection parameters should be available before connecting, while the others are visible only upon successful connection; more or less what updateparams() function does in the INDI protocl convention.

@Jasem, if I got this right, by expanding this code to fully manage interaction with a client (connection, standard properties etc as Bernard wrote) and feeding the xml directly into indiserver via stdin/stdout (to avoid chaining) would allow the community of python developers to write drivers that interoperates with standard INDI drivers and client like Ekos to connect both drivers.

Read More...

Ferrante Enriques replied to the topic 'Python driver package' in the forum. 7 months ago

Hi Bernard,
As you said, I'd like to mix standard drivers on Ekos client with custom drivers in python.
I followed a different approach by chaining the python to the ekos server so that I don't have to write an executable driver just for communication.
Here are the easy steps if someone wants to give it a try:

1) Started Example 1 with pyServer on port 7625. Name of the device is Thermostat as in the example.

driver.listen("localhost", 7625)

2) chained this python server with the Ekos one, like in the picture below:


3) Start Ekos.


Still I get an error in the log: Failed to connect to Thermostat. Please ensure device is connected and powered on.
But the temperature updates just fine.

Ferrante

Read More...