Gah, I don’t know why I seem to have so much trouble keeping this diagram up-to-date and also accurate. Have to do a couple of edits every time I touch it, haha.
This time I accidentally opened up an old version of the file, and worked off of that. Should be fixed now! crosses fingers
I took off the jumpers and put them in a little bag, to make my BB2 look like the schematic.
Errr, I dont know what you mean by wash. I saw the little tag, but didnt know what it was referring to, so I left it.
Ok cool - I will swap the PS2 cable around, then try it to see if that works.
Thank you very much for the replys!!
Ok, an update:
After changing around the Pins so the blue is on the other side, now what happens is:
PS2 reciever on the robot: Red and Green lights are both on continously
PS2 controller: the only thing thats changed is instead of the red light flashing, now the red light flashes once for a few seconds when i press analog, and then the red and green flash together twice when i press analog again. Apart from that, no lights flash and no response from the robot.
EDIT: when i turn off power to the robot, the PS2 controller red light flashes continously again.
I just re-read this post - The two tripods do not lift and lower. Should they do this every time it is powered up? In fact, they have never done so. I believe i must have made another mistake somewhere 
EDIT:
This step here in the assembly guide is where it stops doing what it is supposed to do:
“If all is well, you should hear a few short beeps, the legs should snap to position, and slowly lift the body up. Then the two tripods will lift and lower once. At this point, if you properly calibrated the servo offsets, the legs should be perfectly aligned. Remove power to the robot.”
It does not make a few short beeps, it beeps once, the legs DO snap to position (but dont lift the body up? is that the perfectly aligned position? or higher?) and the tripods do not lift and lower. The legs are aligned however.
Can you get it to walk?
the initial alternating tripod can be turned off and on with in the powerpod program.
the drop down list titled “Auto legs down” can change the time taken before performing the initial tripod. it should be set to 3 sec’s by default.
Did you turn the whole connector around, or did you pull wires from the connector and rearrange the order?
All of that sounds right except the no response part. Please make sure the SSC-32 baud rate jumpers are set to 38.4kbaud. If this is wrong the SSC-32 will not get the commands right. Also check to see if when you push the joystick the LED on the SSC-32 blinks. If that doesn’t help it sounds like it’s time to send us some images of the SSC-32 as well. Do you have an old PS2 console to test the controller? You can send it to us for testing.
Nope, at the moment the only thing I can get it to do is to beep twice (with 20secs in between) when i click the “program” button on the Basic Micro Studio.
I re-did the steps from setting the Powerpod offsets and building the .bas program, and set the auto-legs down to 1sec, however it still does not do the initial alternating tripod lowering and raising.
Is there some way of making it move from Basic Micro Studio? without using the PS2 controller?
First question - i turned the whole connector around, I did not rearrange the order, since it was the original order that it came in.
Second question - the SSC-32 baud rate is correct, at 38.4k (i triple checked this when i first did it, and made sure it was correct by reading the SSC32 manual). Also, the LED on the SSC32 did not blink, it was constantly off. I have now gone back a few steps, and I am going to attempt to start from where I began getting lost.
So, to start again, the current status is:
I have installed the SSC32 and all the servos are plugged into it.
The power to the servos and also to the logic is on, and the baud rate is currently 115.2k, with the DB9 port enabled for PC communication.
In Powerpod, I have calibrated the offsets for each servo, till they are correctly aligned.
The green LED flashes when I click “ALL=1500” and also “ALL=OFF”.
I have entered the following information from the master.pmp:
From here, I have then “Build Basic Program” and named it zeus.bas
I will also attach a photo of the SSC32 tonight, when I get my good camera back.
Could I just have clarification that, up to this point, everything is correct and should be working?
Also, Robot Dude, I dont have a PS2 unfortunately, it would probably take weeks for me to send the PS2 controller to you guys for testing (from New Zealand), so ill leave that option for a last resort at this point. 
Hi,
I’ve no exp with Powerpod, but looking at the last page of the manual you can control it using a “PC serial port control panel”.
Btw, don’t you have to hit the “Start” button on the PS2 remote to turn the hex on?
No this program is ready to move without pressing anything as an enable.
I have taken some pictures of the SSC32, a before pic of when I got it to connect and talk to Powerpod:
(Baud= 115.2k and the DB9 Enable jumpers)
And after I completed the next step:
(Baud= 38.4k and the DC-01 connector)
One thing I noticed was, on the build99c (instructions on setting up BB2 and SSC32) I saw this image:
And it appears that the powercables going into the left side of the SSC are different to the schematic. Can anyone say why its not going into VL+ on this picture? But the schematic has it going into a different area?
EDIT: Got all the pic’s the right way.
Before I get on to the next step, I have a question regarding the Basic Atom Pro - when plugged into the BB2, is it supposed to look like this?
Next step:
Unscrewed the hex screws attaching the SSC32, and screwed the BB2 on top of it. Picture of screwed on BB2:
Then plugged the DC01 into I/O port 8, black wire closest to the edge of the board.
Then plugged the PS2 controller connections (as per the correct instructions on the previous page of this topic, Blue wire on Pin15 and the black and red cables on Pin15 also, black wire closest to the edge of the board.
I then plugged the power cables from the SSC32 into the BB2. (red positive, black negative, obviously)
Picture of plugged in BB2:
Can someone tell me if i have done everything correctly in this step?
Thanks
Next step:
I plug in the Serial port -> USB cable into the Botboard.
I then apply power to the entire robot, the 6V to the servos and the 9V to the logic.
what happens is:
The next instruction is to “Program the ATOM”.
I open the zeus.bas program from powerpod in “Basic Micro Studio”, and then click the “Program” button.
The robots legs go down and up, and then beeps
Micro studio says: “Writing” which it does for a while, then “Verifying” for a small bit, then the legs go down and up, and then beep again.
Micro studio then says: “no errors detected, programing…, finished programing.”
The robot now stands in the “aligned” position, green light ON on botboard II, and green light OFF on SSC32.
The next instruction is: “Install the PS2 controller receiver into the PS2 cable on the robot, and apply power.”
I plug the PS2 controller reciever into the PS2 cable, which then flashes a red light and has a constant green light. The instructions then say to apply power, which i find strange - power is already applied to the robot, in order to program the ATOM.
The next thing that is supposed to happen is:
“If all is well, you should hear a few short beeps, the legs should snap to position, and slowly lift the body up. Then the two tripods will lift and lower once.”
Which doesnt happen. This is where I am stuck. I will now turn the robot off, and then on again, and report what happens:
Unsure of what is wrong, I then put batteries into the PS2 controller. The red light on the PS2 reciever stops flashing (implying that it has now connected with the controller) The green light is still on on the BB2, and still off on the SSC32. I then attempt to press the buttons on the controller, but no response - also the SSC32 light does not turn on at any point during this time. (pressing analog on and off does nothing either)
Now, I am at a loss as to what is going wrong here, so can anyone suggest something I can do to troubleshoot the problem? Or does anyone see why it is not working? 
The program may be getting hung some place.
When you first turn on the robot do you hear any sounds being played? There should be a couple of notes played. Then when it tries to configure the PS2 there should play 3 notes probably once if everything is working or a constant annoying sound if it can not properly setup the PS2…
In cases like this, where it looks like you are getting some communications between the BB2 and SSC-32, but not sure about PS2, I would probably try checking out your PS2 workings. You might try using the tutorial: lynxmotion.com/images/html/build034.htm
That would show that the PS2 is working good.
The mystery picture, would probably not work, as there is now power going to the VL terminal and VL=VS1 jumper is not set.
Kurt
Not exactly. The pins on the BAP must be pressed further down to the DIP28 socket.
I was worried about breaking the BAP - i didnt want to push too hard. How far down should the pins be? Could this be the source of my problem?
Kurte - there is only ever one beep, when the robot is first turned on. Thanks for the link for the PS2, i will run through that and see if i can get it to work.
Thanks for the replys
Yes not having the pins in far enough could imply that not all pins are making contact. Should be in something like:
Just be careful and make sure all of the pins are in the appropriate holes and press in.
Kurt
P.S. - The green tape is to keep the sound down 
Let’s see what happens when the chip is plugged in all the way! 
If that doesn’t work, I’ll chime in with more troubleshooting steps for you. 
Unfortunately, still no change even with the chip plugged in firmly
My deduction skills seem to think that it is the bot board II that is not communicating with the SSC-32… is there any way that i confirm that the bot board II is working correctly? and if it is, that it is communicating with the SSC-32?
Im thinking, some kind of test where the robot will move its legs around, to prove connections are there.
