BasicMicro

Same issue on a 2x30A, did not manage to resold it. How long would it take to ship and back from europe?

I would like to have reliable current readings at the same rate as my control loop (30Hz). The goal is to monitor the torques of my robot and to compare it to a semi-empirical model in order to detect potential problems (i.e. higher wheel friction due to tearing or dust, collision detection, etc...)...

Just updated to last versions, only one motor is responding when using SpeedAccelDistanceM1M2.

The following mixed commands from the python library seems to be not working: SpeedAccelDistanceM1M2(address, accel, speed1, distance1, speed2, distance2, buffer) SpeedAccelM1M2(address, accel, speed1, speed2) Whereas the unmixed SpeedAccelDistanceM1(address, accel, speed, distance, buffer) and Spee...

Thanks for your answer.
So if i understand well, there is no way of getting an estimate of the current consumed by the motors if not pulling the readings at minimum 1250Hz?
Would it be possible in a next firmware version to set the number of samples on which the current value is averaged?

I have now something which is working more or less okay. Anyone is welcome to test and try. Made the following improvements today:

Split max speed in max linear and angular
Added custom msg. Needed to modify name of script
Publish commanded wheels speeds and motors currents readings

Hello, Two questions about motor currents. What exactly is send back by the "49 - Read Motor Currents" command? I am guessing this is the currents readings averaged over a time period ? In that case what is this time period? I am trying to get an estimate of the torque outputed by the moto...

Precisely, two threads were trying to read/write to the serial port at the same time. Still need to check in depth the robustness of the com implementation. I am new in python, and while when using C++ with ROS, callbacks are handling thread conflict, it has to be done manually in python. I have mad...

Forked here: https://github.com/doisyg/roboclaw_ros
for now, just corrected the com issues and increased loop to 30hz

Hi, Thanks for your answer. No communications issue with the Ion Motion software. I assumed the ROS driver was working well but it is very buggy. The problem was that the encoder values could not be read while sending motors commands (both were trying to communicate in the same time). I am going to ...