vitalyartemiev / experiment-automation Goto Github PK

Similar to the Framing error issue, this message ('The I/O operation has been aborted because of either a thread exit or an application request') sometimes appears when connecting to that same SR844 detector. I have yet to locate where it is reported, as every time (out of 3) it appeared so far, i didn't have the debugger avaliable. The only cure I found is to reboot the computer.
Another program, which is not using synaser does not seem to have this problem, and also doesn't check for errors.

When transmitting commands, Win XP adds a delay of 200 ms by default to avoid transmitting small TCP packets. This severely limits speed of interactions with devices over TelNet.
Workaround:
create 2 registry keys in [HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Services \Tcpip \Parameters \Interfaces {Adapter-id}],
DWORD TcpAckFrequency = 1, and DWORD TcpDelAckTicks = 0.
Adapter-id can be found by looking at properties of the network which represents the connection to the device.
Sometimes one also needs to reboot the PC and/or to disconnect/reconnect the Ethernet cable before the changes take effect.

Sometimes, when connecting to a serial device, an exception is raised: 'Error 9999: Receive framing error'. It seems that the stop-bit is not received. Only encountered when connecting to SR844, mostly for the first time after its power-on, but in one instance, had to reboot the computer to restoe normal work. Maybe some kind of interference when powering on? Faulty connector?