It might be that the serial port assignments have changed, Linux seems to assign /dev/ttyUSB devices randomly every reboot so it's better to bind them to unique names either with udev rules or by using the Ekos serial port assistant. In my case my EQDir adapter and ScopeDome controller both use the same FTDI USB-serial chip and have to be identified by their serial numbers. For example I have in /etc/udev/rules.d/99-indi.rules file lines such as this for my EQDir adapter:

SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A700Q6JZ", SYMLINK+="mount"

which creates a symlink /dev/mount which I then use as port in EQMod driver. You can get the correct values for your devices with "lsusb -v" command and create separate rules for your mount, cloudwatcher and scopedome and they don't get mixed up.

Thank you, I will look at this and I will inform you .
I hope this will function
Thank you very much for your answers

Sorry but EDMOD does not connect, it disappears as soon as it is connected

I have these ports :
ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 janv. 1 20:05 usb-Arduino__www.arduino.cc__0042_95032303837351D04142-if00 -> ../../ttyACM1 : SCOPEDOME
lrwxrwxrwx 1 root root 13 janv. 1 20:05 usb-FTDI_FT232R_USB_UART_A10K713T-if00-port0 -> ../../ttyUSB0 : EQMOD
lrwxrwxrwx 1 root root 13 janv. 1 20:05 usb-Pegasus_Astro_UPBv2_revD_UPB277HPKB-if00-port0 -> ../../ttyUSB1 PEGASUS UPB
lrwxrwxrwx 1 root root 13 janv. 1 20:05 usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 -> ../../ttyUSB2 : AAG CloudWatcher
lrwxrwxrwx 1 root root 13 janv. 1 20:05 usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 -> ../../ttyACM0 : GPSD
So I am trying to connect the EQMOD with ttyUSB0 as it is noted above
I am always verifing these ports when connecting the items

Plea se find in attachment the log file of EQMOD

Hello ,
I reinstall KUBUNTU 22.04 and indi, etc...on the laptop and now the EQMOD is connected but the scopedome 2m is very hard to connect
So everything is connected on the first attempt except the scope dome and after 4 or 5 attempts (sometimes more !) finely it is connecting.
but very often I have the errors :
: [ERROR] Error writing command: Write Error: Input/output error. Cmd: moveDome=CCW:6
: [ERROR] Error writing command: Write Error: Input/output error. Cmd: getStatus
So I have to disconnect and reconnect the scopedome and often I don't arrive to reconnect it.

Thank you

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