Afetr two minuts
osservatorio@raspberrypi:~/onstep-python $ ./examples/test-timeouts.py
0.040 GR 14:22:17#
0.021 GD +89*59:02#
0.019 Gc 24#
0.021 GM GPS#
0.021 GT 0.00000#
0.020 Gt +46*10#
0.030 Gg -013*32#
0.022 GG +02#
0.046 GL 13:57:07#
0.035 GC 02/12/23#
0.027 GVD Jan 5 2023#
0.020 GVT 18:13:00#
0.024 GVN 4.24r#
0.031 GVP On-Step#
0.037 FA 0
120.036 F1A
0.000 F2A
0.000 F3A
Traceback (most recent call last):
File "/home/osservatorio/onstep-python/./examples/test-timeouts.py", line 45, in <module>
r = scope.send_str(':' + cmd + '#')
File "/home/osservatorio/onstep-python/lx200/onstep.py", line 83, in send_str
self.scope.send(string)
File "/home/osservatorio/onstep-python/lx200/sock.py", line 41, in send
self.sock.sendall(msg.encode('utf-8'))
BrokenPipeError: [Errno 32] Broken pipe

I see that F1A times out.
Alain, is this the 1st focuser?
If so, does Ettore indeed have focusers on his controller at all?

The issue is the broken pipe message. It looks like the connection is lost.

Ettore,
Are you sure the connection is stable?
Things like distance between devices and AP, signal strength, other neighbours on the same channel, ...etc.?

In wifi is not stable in USB is perfect.
Yes i have a focuser but i not use,
Ettore

@Khalid, Ettore,

Yes F1A is asking for the first Focuser but it is never called in real situation , only in the Python test (if so configured).

@ Ettore good to see you managed doing the Python test but you'd better customize examples/test-timeouts.py to match your real liofe (commands used by your particular set-up).

@Khalid According to Ettore's screen shot he is using port 9998.

I see nothing else than pinging the OnStep address during test to see if there are lags in the connection. I see no other explanation than bad WiFi here but sure it needs to be proven.
I would issue a ping with this command

ping -D 192.168.0.40 > pings
to have a history of the network latency during tests with OnStep

My thinking is the same as Alain,

It looks like the WiFi connection is unstable or weak for some reason.
If the underlying connection is unstable, then errors will happen like what you see.

Ettore,
Start with the ping command to see if the connection is stable or not.

Yes I have same values ... when not communication with OnStep, but when I run the communication tests it goes higher anyhow on my side never more 30ms .
What I suggested was to run the test over a long period and in parallel run the ping sot than you can see what's happening at network level.
Anyhow when the timeout arrives with the test scripts you can (with good probability) deduce it is a network problem.

If you use the ESP8266 without external antenna it is more likely to limit good connection to some 10 to 20 meters outdoors .
Example in my observatory despite the wooden structure I have no good connection between Observatory and Home (Observatory to home WiFi is 40 meters strait line without obstacles) After that I installed a WiFi antenna outside without success.
Do you use the WiFi of your Raspberry?

Yes i use wifi of raspberry

OK.

So I suppose Raspberry is running Indiserver and Kstars!
OnStep is connected to Raspberry over WiFi.
Do you also connect remotely to Raspberry via WiFi with VNC?

Yes running Indi e kstars but now i'm trying indiweb manager.
Onstep is connected to raspberry over wifi.
For connection remotely i use vnc 64 bit.
Ettore

This is most probably one of the cause of your network issue.
The Raspberry pi must route OnStep and VNC traffic which is not huge I agree, theoretically should be largely enough but by experience Raspberry Pi WiFi is not one of the best for that.
This is the reason Why I decide to go over Optical fiber finally.

I got this kind of problems in two scenarii:
Raspberry running IdI/Kstars and VNC for remote connection
and later
I tried Raspberry as a USB over IP server so taht I could remotely connect all devices as if they are connected to my remote machine.

In both case I got this WiFi Bottleneck .

Di you ever try wit an Ethernet cable for the remote VNC connection?

I know it is not a solution to your WiFi but a test to see if the problem remains

I've never tried with a network cable, I'll try next week and see what happens.
Thanks.
Ettore