Hi Kemal,
first thanks for feedback, this is the way to improvement
I tested on Raspberry with the daily snapshot of Indi and could not reproduce this behavior.
I suppose you have indi running on your raspberry and the OnStep controller connected via USB and /dev/ttyACM0 on the raspberry.
Then you connect to Indi with Kstars to your raspberry via Ethernet / WiFi.
OnStep <=> USB on Raspberry <=> Ethernet / WiFi <=> Your PC - Kstars remote Indi
I did this and connect without any issue, the connection sometimes take a second or two but no error message.
Are you sure of your communication?
I would spy the comm to see the trafic
I give you hereunder a brief description on how to do this under linux
============================= Serial Spy under Linux =============================
Debugging serial communication:
First Install jpnevulator
apt-get install jpnevulator
once done you can run it to spy the serial line:
Let's assume:
/dev/ttyACM0 is the serial device where is connected your device
then issue the following command:
jpnevulator --ascii --print --tty /dev/ttyACM0 --pty /tmp/serial --pass --read
jpnevulatro returns
jpnevulator: slave pts device is /dev/pts/4 (or whatever /dev/pts/x)
To show graphically what is going on
/dev/ttyACM0 <==> /tmp/serial <==> /dev/pts/4
which means you can connect with your client (kstars for example) to /dev/pts/4
all the communication between your serial port /dev/ttyACM0 and your virtual port /dev/pts/4
will go through the file /tmp/serial
you can then do a tail -f /tmp/serial
and observe all the trafic between your serial port /dev/ttyACM0 and your virtual port /dev/pts/4
Screenshot: jpnevulator
alain@alain:~$ jpnevulator --ascii --print --tty /dev/ttyACM0 --pty /tmp/serial --pass --read
jpnevulator: slave pts device is /dev/pts/4.
Screenshot: tail /tmp/serial where I dis send ack (^F) and OnsTep returns P for polar
alain@alain:~$ tail -f /tmp/serial
06 .
/dev/ttyACM0
50
P
/dev/pts/4
3A :
47 G
52 R
23 #
/dev/ttyACM0
30 35 3A 30 38 3A 34 35 23
=============================
To debug the communication you may use minicom connected to /dev/pts/4 and with a macro set to send
ack (^F)
don't forget to set minicom serial to 9600 bauds ....