|
Re: Using a separate thread for driving motors?
You could lengthen the timeout from the default of 0.10 seconds to something less touchy... like 0.21 seconds. A lot of teams just disable it altogether; safety is such a pesky thing.
Are you sure you're setting the motor values in every iterative pass?
Are your iterations taking more than 0.02 seconds to execute? Are you having to do a lot of computations (camera processing)?
Are you sending too much data to the dashboard (or too often) and having the communications jam up on you?
|