fischertechnik community forum

Hi,

After successfully using Python for quite some time, today it started going wrong. Not constantly, but often. In this video I made you can see what happens on screen and on the TXT: https://youtu.be/nlXpsAMvl2g. For clarity, this is the error I get on screen:
Connected to TX2013 version 0x4020300
WARNING: ResponseID 0x0 of startOnline command does not match
WARNING: ResponseID 0x0 of updateConfig command does not match
Received data size does not match length of format string
WARNING: ResponseID 0x0 of updateConfig command does not match
WARNING: ResponseID 0x0 of updateConfig command does not match
WARNING: ResponseID 0x0 of updateConfig command does not match
WARNING: ResponseID 0x0 of updateConfig command does not match
WARNING: ResponseID 0x0 of updateConfig command does not match
Traceback (most recent call last):
File "DiscoveryPython.py", line 8, in <module>
Motor_fan = txt.motor(4)
File "/opt/knobloch/ftrobopy.py", line 1256, in motor
return mot(self, output)
File "/opt/knobloch/ftrobopy.py", line 1222, in __init__
self._outer.updateConfig()
File "/opt/knobloch/ftrobopy.py", line 353, in updateConfig
res = self._sock.send(buf)
socket.error: [Errno 32] Broken pipe

What is happening here ? is ftrobopy failing against the new firmware ?

hvn

Hi,

the problem could be related to timing issues, that can occur when Python communicates with the TXT control libraries. I have not yet tested ftrobopy with the new TXT firmware version 4.2.3 but I could well imagine that due to the new I2C support, which presumably needed an additional thread on the TXT, the timing is different now. I will check this as soon as I have upgraded to 4.2.3. In any case I wanted to upload a new ftrobopy version with better camera support and a better communication-timing control to the download area soon.

Best,
Torsten

Hi,

Thank you. I'll wait for your follow up and look forward to camera support.

hvn