Sounds like something is disrupting your serial communications somehow. At least ModemManager and GPSD might cause that when they probe for devices causing the device to react in unexpected ways when INDI driver tries to talk to them. Having the full driver debug log might show the issue, but you can also try uninstalling ModemManager especially if you don't need it. For GPSD you might need to somehow force it to ignore the ScopeDome port as from your log in the EQMod thread it seems you have a GPS device using another ttyACM port or you can try to rule that out by uninstalling or stopping GPSD temporarily too. And you should use the /dev/serial/by-id/ names for device ports avoid the ttyACM and ttyUSB names as the the order they are assigned numbers change randomly if there are multiple devices of same type, ie. a device that is ttyACM0 in one boot might be ttyACM1 the next and the device previously ttyACM1 becomes ttyACM0 depending on the order kernel discovers them. But the names in /dev/serial/by-id/ don't change and always point to the correct actual (ttyACM or ttyUSB) device.

Hello,
Thank uou very much for your answer.
I remove the GPS and ModemManager AND I have always the same error with the scope dome
You'll find the latest log of EKOS
The scopedome crashed
Thank you

Hello again,
I connected only mount simulator and CCD simulator ANDthe scopedome
You'll find the log attached, the scopedome crashed

Hello,
Now after some tweaks I am connectind the scopedome
But it is unusable because as I display a what ever command, I get the error below :


: [ERROR] Error writing command: Write Error: Input/output error. Cmd: moveDome=CCW:6
: [ERROR] Error writing command: Write Error: Input/output error. Cmd: getStatus

That Input/output error is a generic one that means the serial port has disappeared from under the driver for some reason when it's trying to communicate with the device. Kernel log from that time might show if the device has reset itself for some reason (there is a watchdog in the ScopeDome controller that might be overly eager) or something else. Also having driver debug enabled in Ekos logging configuration before connecting to the device would show all serial port traffic the driver sends and responses it gets from the device.

Hello,
Yes you were right :
At the beginning, before the scopedome is connected I listed the ports and I found this for the scopedome :
lrwxrwxrwx 1 root root 13 janv. 4 18:26 usb-Arduino__www.arduino.cc__0042_95032303837351D04142-if00 -> ../../ttyACM1
I launch a command
While it is correct, I am looking at the ports and it does not change.

As soon as I get the error, i look at the port and I see it has changed :
lrwxrwxrwx 1 root root 13 janv. 4 18:36 usb-Arduino__www.arduino.cc__0042_95032303837351D04142-if00 -> ../../ttyACM0
How can I do to unchange the ports ?

to resume :
the ports before the error :
rwxrwxrwx 1 root root 13 janv. 4 18:26 usb-Arduino__www.arduino.cc__0042_95032303837351D04142-if00 -> ../../ttyACM1
lrwxrwxrwx 1 root root 13 janv. 4 18:26 usb-FTDI_FT232R_USB_UART_A10K713T-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 janv. 4 18:18 usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 janv. 4 18:26 usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 -> ../../ttyACM2

the ports after the error:
lrwxrwxrwx 1 root root 13 janv. 4 18:36 usb-Arduino__www.arduino.cc__0042_95032303837351D04142-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 janv. 4 18:36 usb-FTDI_FT232R_USB_UART_A10K713T-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 janv. 4 18:18 usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 janv. 4 18:36 usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 -> ../../ttyACM2

the other ports do not change.

,

Here are the logs before the error and after the error

the second file

Hello again !
I reinstalled UBUNTU 22.04 and right after I reinstall INDI EKOS without anything else.
It's always very hard to connect the scopedome and while it is connected it finishes to change its port number ACM1 to ACM0
I can lauch some commands but it finishes to give errors ( getState etc....)
Yet I made udev
So I have /dev/scopedome witch points to /dev/ttyACM1 as a symbolic link
But after a while, it changes its ports to /dev/ACM0 and its finishes by errors And I cannot launch other command while there are errors.
I don't know what to do now.

Hello,
Now the port is changing in :
ls - l /dev
lrwxrwxrwx 1 root root 15 janv. 6 16:12 scopedome -> bus/usb/003/084

Cordialement
Sylvie

Please find the logs :
1- after not connected,
2- afterconnected
3- and error and the new ports

There is definitely something weird in your USB connections as all the USB-serial devices seem to get the same error for some reason. Are they connected to the same hub? Is the hub powered? Does kernel log (run command "sudo dmesg" on command line for example) show anything interesting when the error happens?

For ScopeDome there is also the possibility to use ethernet connection, I'm running out of ideas why the USB serials behave like that for you.