gordonbrander
commented
7 years ago Perhaps this is related... from @rwdavis513:
After much debugging this weekend, the pfcs with the new software wouldn't be able to access the serial port anymore after 30-45minutes. Perhaps there was something that needs to change in the cmake or it needs to be run again. Here's a post with the error: http://answers.ros.org/question/233355/rosserial-running-please/
The error:
Traceback (most recent call last):
File "/home/pi/catkin_ws/install/lib/rosserial_python/serial_node.py", line 80, in <module>
client = SerialClient(port_name, baud)
File "/home/pi/catkin_ws/install/lib/python2.7/dist-packages/rosserial_python/SerialClient.py", line 382, in __init__
self.requestTopics()
File "/home/pi/catkin_ws/install/lib/python2.7/dist-packages/rosserial_python/SerialClient.py", line 389, in requestTopics
self.port.flushInput()
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 500, in flushInput
termios.tcflush(self.fd, TERMIOS.TCIFLUSH)
termios.error: (5, 'Input/output error')
rwdavis513
ghost
Summary
The pi loses sync with the arduino very frequently. It seems to break when a lot of setpoints get commanded at the same time. Maybe rosserial or something in our handling of it breaks when there are a lot of messages? Maybe a serial buffer overflow? Possible fix could be to move the relay board to usb with:
Docker logs
If you look at the time stamps below they happen very frequently.