im all out.
if this doesn’t result in it being concluded as a power issue then ill head my hat. [size=85]i dont have a hat[/size]… ill buy one… and ill eat it.
sorry if i go over things again or ask the same questions…
ok. so the hexapod works perfectly fine before and after connecting it all back up.
But going back and simply connecting up the SSC cause the Y read outs…
baud set to 115k?
and connected properly the first time you “calibrated” the servos?
what about connecting it up with no servos attached?
That confuses things further.
something is not right here, as you have already figured. but im really not sure im going to be much more help to you, without pointing out anything i havent already covered.
did you follow a tutorial when you first set your robot up? if so what one?
that one, I would like to mention that we are not using the default servos, we are instead using very powerful ones and we also have 2 relay modules connected to the SSC
We got 24 of those very powerful servos, and they are all connected to the robot, they draw a bunch of current, so much that we usually use a motorcycle battery for real testing. And we burnt an SSC-32 once and had to install a fuse.
Oh and I don’t think the relay module is the issue.
ok ok, I could have only assumed the conditions were normal…
Current Drain (6.0V): 300mA/idle is pretty ok and wouldnt be an issue, if you have the appropriate battery. SO, What battery have you been using when you get the Y error?
So the motorcycle battery is a 6V battery, so that’s fine. It just draws a lot of current, one cable from the power terminal got caught on something, touched the other cable, and they melted together shorted and boom. Very fast.
Anyway, the problem is still the calibration thing, I havent tried connecting the SSC-32 with the computer with the motorcycle battery though
The 7950 is optimized for 7.4V LiPo batteries. The 6V 2800mAh NiMh battery could never power a 24DoF+ hex made p of these servos. Each motor draws about 300mA at no load idle and up to 4.8A at stall at 6V (higher at 7.4V). The 6V, 2800mAh battery can provide a maximum of 2.8A for short periods of time. You’ll need a 7.4V, 5Ah+ LiPo battery capable of 20C discharge or more. Try one servo connected to the SSC-32, ensure the serial to USB cable is working properly (many of them don’t) and double check the baud rate and COM port (and of course power).
Hi CBenson. Even with the motorcycle battery we are having a lot of power issues. We had to switch from a 15 AMP fuse to a 20 AMP fuse, because the 15 amp was getting fried from the amount of current flowing through it. We are evaluating the possibility of powering each side of the hex with 2 different batteries of the type you mention.
Could you give me a hint on exactly what brand of that 7.4 LiPo should I use?
Hello, I’ve been troubleshooting this issue today, it has become frustrating, because I have to calibrate this thing before June 1st.
While I was waiting for the new lipo batteries I unplugged every servo from the SSC-32, and I removed the Bot Board. connected a 6V battery to VS1, applied power to the SSC, and opened lynxterminal, clicked on all=1500 and plugged in a small HS-422 servo on pin 0. The servo moved, so I went and I typed VER, got no response, clicked on Reg. and I got a message “Can’t find SSC-32”.
I proceeded to repeat the same process by connecting one leg (with the powerful servos) and connected a far more power 6V lipo battery, the leg moved like crazy, didn’t go into neutral position at all, I typed VER, no output, click on reg “Can’t find SSC-32”.
I am either doing something wrong or this SSC-32 is defective.
No, I am in the US. The first thing I tried to do when I got this SSC-32 a few days ago was to try to connect it to the computer, and I never could. Burlington, Vermont
The Low Dropout regulator is defective, it is not making the right contact. That’s why I’ve been having power issues since the beginning with this board!!!. I checked EVERYTHING but that, today it just clicked my mind that maybe this part came in defective, since all of the problem were related to power issues. How frustrating and silly… I’ll see if I can get the board replaced, I don’t want to mess up with it as it might kill the warranty.
