Society of Robots - Robot Forum
Software => Software => Topic started by: Ricardo Gómez on May 31, 2012, 05:34:04 PM
-
Greetings, I have an axonII and a Dynamixel ax18a, I am using interface indicated by webbotlib and using version 2.09 webotlib, I already set the ID in each servomotor. Position the servomotors with
ax12_set_GOAL_POSITION(&_servo_, X);
and
servo.setSpeed(X);
functions perfectly.
The configurations are generated WebbotLib dynaixel Project Designer with 1M in theUART0. The problem is that when I try to feedback to the command servo.dumpAll() or servo.read() throws me the error 0x400 "we received an invalid header". Any ideas or help?
-
I've used the AX-12 (identical to the AX-18 in software of course) successfully with Webbotlib 2.0x. I've been using C, rather than C++ though; I think you're using C++?
I can successfully do
ax12DumpAll(&UART3toAX12_driver);
Which is for all of my servos... but I'm not sure I've ever done data fetching from single servos.
I don't want to make you redo your code in C, if possible... I'm sure Webbot will have better ideas :)
-
Haven't tried, or got, th ax18a. But I guess it should work ok.
The dumpAll command Gertlex mentions just does a read/dump of each servo in turn.
Only thing I can suggest is try a lower baud rate. Also try with just one servo connected - to make sure you've got your wiring correct
-
Oohh, and idea that just occurred is to double check that the tristate buffer is working/hooked up right? Make sure the signal wire is connected too... I had mine wired to the wrong pin for a few months and so it just floated. Most of the time I could send commands to the servos, but it was flaky... and getting info back just didn't work, if I recall correctly.
-
Thanks for your support. the problem was with the source, I was using a laboratory power supply and replace it with a lipo battery I worked right all ...
-
Good to hear... they take a lot of current, aye. Make sure to get a battery monitor, e.g. these (http://www.hobbyking.com/hobbyking/store/__7223__Hobby_King_Battery_Monitor_3S.html).
-
ok you're right! the problem was that the source was generating a magnetic field that corrupted packets
-
ok you're right! the problem was that the source was generating a magnetic field that corrupted packets
wha?
-
the power supply generated a magnetic field that corrupted packets
-
the power supply generated a magnetic field that corrupted packets
How'd you determine that? Are you sure it wasn't noise, or insufficient current? (if a power supply can't supply enough current, the voltage drops, and that would interfere with binary)
-
Not that we're diagnosing something right now, but out of curiosity, what was the Axon II's power supply?