-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random transmission errors #1
Comments
Packet frames have been captured with a digital oscilloscope while executing the example:
The issue seems to come from the time.sleep(0.01)
num_bytes_available = self.serial_connection.inWaiting()
status_packet_bytes = self.serial_connection.read(num_bytes_available) |
Increasing the "time.sleep()" argument to e.g. "0.1" (100ms) fix this issue. Despite the short 1ms delay response (of Dynamixel units) measured on the oscilloscope (i.e. the time between the Instruction packet and the Status packet), the operating system actually needs more than 10ms to fill its buffer... To avoid this error, the "time.sleep()" delay between Instruction and Status packets can now be configured by a class member. |
The following snippet is sometimes executed correctly (i.e. returns "True" when the dynamixel #1 is connected) but fails otherwise, either by returning "False" (i.e. the input buffer is empty) or by returning a
ValueError
("Incomplete packet"). This failures seems to occur randomly, even on successive executions.These transmission errors have never been encountered on Gnu/Linux test platform so far.
The text was updated successfully, but these errors were encountered: