But trying out the rc_test_servo command with many different options, has
not revealed any movements at all.
You haven't stated which Beagle or cape is in use, nor to which pins
you have connected the servo leads. I'm guessing at the use of the
"Robotics Cape" on the basis of the documentation for rc_test_servos ( http://www.strawsondesign.com/content/manual-servos ).
I have tried "rc_test_servos -v -s 1.5" as best guess but not sure though.
I have checked that polarity is ok.
Have you tried specifying frequency? Possibly this servo has slow
response to pulses.
Have you even confirmed you have pulses? [An {analog} VOM should show a
non-zero voltage between signal lead and ground -- exact voltage would vary
with pulse width and frequency and sensitivity of the meter; a DVM probably
won't respond in time -- an oscilloscope would be the most precise as you'd
get an indication of both pulse width and voltage height... Even an LED
with suitable dropping resistor should vary in brightness as you sweep the
pulse width]
If you've got pulses, you may just have a bad servo. Forgive me, but
based on the specifications/price, I'm not sure I'd trust the quality of
that servo... The closest match (4.8V 3.9kg-cm 0.22 sec/60deg; 6.0V
5.2kg-cm 0.18 sec/60deg) from a quality company (Futaba) is 10 times the
cost -- $40. S9001/FUTM0075 Aircraft http://www.futabarc.com/servos/analog.html
But trying out the rc_test_servo command with many different options, has
not revealed any movements at all.
You haven’t stated which Beagle or cape is in use, nor to which pins
you have connected the servo leads. I’m guessing at the use of the
“Robotics Cape” on the basis of the documentation for rc_test_servos ( http://www.strawsondesign.com/content/manual-servos ).
I am sorry…I am running on the Beaglebone Blue, and I have attached the servo to the plug farthest away from the sd-button, with the white wire closest to the CPU.
uname -a: Linux beaglebone 4.4.54-ti-r93 #1 SMP Fri Mar 17 13:08:22 UTC 2017 armv7l GNU/Linux
I have tried “rc_test_servos -v -s 1.5” as best guess but not sure though.
I have checked that polarity is ok.
Have you tried specifying frequency? Possibly this servo has slow
response to pulses.
I have tried frequencies from 5 to 500 with no change…
Have you even confirmed you have pulses? [An {analog} VOM should show a
non-zero voltage between signal lead and ground – exact voltage would vary
with pulse width and frequency and sensitivity of the meter; a DVM probably
won’t respond in time – an oscilloscope would be the most precise as you’d
get an indication of both pulse width and voltage height… Even an LED
with suitable dropping resistor should vary in brightness as you sweep the
pulse width]
I will check this in the lab later with a scope…
If you’ve got pulses, you may just have a bad servo. Forgive me, but
based on the specifications/price, I’m not sure I’d trust the quality of
that servo… The closest match (4.8V 3.9kg-cm 0.22 sec/60deg; 6.0V
5.2kg-cm 0.18 sec/60deg) from a quality company (Futaba) is 10 times the
cost – $40. S9001/FUTM0075 Aircraft http://www.futabarc.com/servos/analog.html
You are right, I might have bought this one too cheap…
The output when running the command confirms that the 6V rail is switched
on using software.
Obvious next step?
Well... Tracing backwards to where the 6V rail is supplied power might
be next -- as long as the scope is available and you can try each 6V point
all the way back to the regulator.
Does the Blue use the same control pin as the Robotics Cape? If it uses
a different control pin, then the software you are using to test with may
not be actually enabling the 6V.
You can power the servo from an external 6V source, but you’d have to connect the ground of the power source to your BBBlue or the servo will not work right. ie. The ground going to the servo, still needs to connect to the ground pin on the BBBlue servo output header.