Closed npol closed 8 years ago
Occurs when motors are active and reading from encoders. Possibly corrupted packets causing issues
Two possible sources:
Seems to be resolved through fixing concurrency. Warning WARN_RC_RXBUF_NOT_EMPTY occurs 0x8113 when get pid is executed, however
Bug source: wrong command used for getting PID. Position PID command was used instead of velocity PID command.
'A' was printed indicating roboclaw rx buffer not empty before sending new data, but no warning was triggered. after rc gs1. Other issues seem to be fixed
Issue not replicated during system test
FW reports warnings 0x8101 and 0x8002 when using m1 command