i just got my CH3-R working with the remote PS2 controller for about 20min, then all servos on the VS2 side went dead. I un-pluged the Bot Board II and set the jumpers to for PC communication and checked the response of all the servos with PowerPod and LynxTem. I un-installed/re-installed jumpers for VS1=VS2 but that didn’t make a difference. My battery (6.0 Volt Ni-MH 2800mAh) seems to have a good charge so i don’t think its that. I haven’t tried but, could i disconnect my battery and connect it to VS2 to see if its something to do with the jumpers?
Electronics i’m using:
SSC-32
bot board II
BASIC Atom pro 28 pin
PS2 and controller
6.0 Volt Ni-MH 2800mAh
18 x HS-645
DB9 serial cable
I’m new to all of this to but i have a bad feeling that the board is now dead.
Are you powering the VL from the VS battery? If so try removing the jumper VS1=VL and power the VL from a 9vdc battery to see if it helps. Note, all of the jumpers on the SSC-32 are vertical (when you can read SSC-32 on the board). We have just recently updated the hexapod guides, so you might want to look them over.
I tried powering VL from a 9vdc battery just now with the jumper removed and same thing. I tried compleatly different jumpers on VS2=VS1 removing the old ones but still didn’t work. BUT I then tried powering VS2 directly with the 6.0 Volt Ni-MH, removed the VS2=VS1 jumpers, VL powered with the 9v, and it worked! So whatever is connected before the jumpers on VS2 seems to have given out (assuming that the jumpers are connected to the VS2 power input). Other then no power being able to get to VS2 the board seems to be working normally. Before i disconnected all the servos and the bot board II, the basic atom pro was driving the bot fine. Then without any intervention the hexapod suffered a stroke and half the body went limp.
Image’s of the Bot Board II and the SSC-32 with serial cable.
I don’t know what would cause this. I will replace the board for you if you return that one to us for evaluation. For now it appears that you could add a wire from the VS1 to the VS2 terminal to get the bot operational.
