I have the Phoenix hexapod with the BAP2 28, Bot Board II and SSC32.
Via Lynxterm got the servos aligned ok.
Had all kinds of issues with programming the BAP2, first serial communications (same computer with native serial port as I used to upload firmware to ssc) and compiling code at line 1071. Fixed those by a) switching computers and b) adding the ASM{} as instructed in another post.
So, I have a good PS2 connection, appropriate on-off beeps when pushing the Start button, all LEDs on BAP2/PS2 link appropriate. BUT, the legs do not “snap” into position when I hit the Start. They have “tone”, aren’t flaccid as when powered down, but no movement.
So I hooked the SSC back to Lynxterm, and now it can’t find the SSC card. Won’t work on either computer (both running XP). I noticed the SSC LED is rapidly blinking. It’s telling me something, but I don’t know what.
To summarize, I think the Bot Board II/BAP2?PS2 are working ok, now the SSC is not responding. Thoughts?
If the SSC-32’s LED is blinking then it’s still connected to the Bot Board, not the PC and that’s why you can’t see the SSC-32 from a PC.Remove the data cable and reinstall the two DB9 enable jumpers.
You press start to get the servos powered up. Is that working?
After you press start the legs hold position, but nothing ofter that? You say you have a good PS2 connection, but what brand PS2 controller? Are you sure it is going into analog mode? This would prevent the program from being able to read the joysticks… Thereby preventing motion, but still working for the pushbutton operations.
make sure you have changed the control file in the phoenix project for the ps2 one. iv made this mistack before thinking it was for the ps2 when really i had the DIY file uploaded.
make sure you are using the correct baud rate on the SSC when connecting back to serial. vice verser.
I press Start (on my Lynxmotion PS2) and get three tones. No servo motion.
When I power up the servos they have resistance, that’s what I meant by tone (I’m a doctor not an engineer), when I toggle power off they are flaccid and easy to move. So I presume they are getting power. But upon hitting Start, they do not move at all–no snapping into position as the tutorial instructions mention.
Pressing some of the PS2 remote buttons elicits a beep. So I assume there is a connection. All my gear is through LM (via trossen).
Baud is still 115.2k. Programming file check for PS2.
Note on Bot Board I made all my wiring and jumpers to match Figure Schematic 14-3. If I can remember how to post an image I will get it on here.
Ah… I see. If you power the servos on before pressing the start button they may jump a bit, but they should still be slack, not holding position. Then pressing start will cause them to snap into position. Try it.
So after that nothing will coax it to walk… Is the LED on the SSC-32 blinking when when you press start, and or when you move the joysticks?
What brand of PS2 controller is it, and does it have an analog button on it? I suspect the controller is not going into analog mode, preventing the software from reading the joysticks.
When I power up the servos the legs don’t even twitch.
I replaced the DB9 jumpers and checked the firmware, it was fine. The legs moved once when I did that, Curling up, then stopped moving. I couldn’t recalibrate them. So I don’t even have it back to where I was when I first calibrated the servos.
People wonder why we ask for pictures… I never suspected you were using digital servos. They will hold position when powered on. They will hold whatever position they are in when power is applied. Thus skewing the interpretation of the replies to my questions.
Because the servo controller is receiving data, the LED is blinking, but the servo are not moving, I suspect the baud rate has not been changed or is just wrong on the SSC-32.
again this was my first point… check the baud rate. i did notice that since the t-hex tutorials were put up, some of the other tutorials have been changed to 115.
just refer to the Table 14-1
edit. yes thats correct but now remove one so its at 38.4k when connected to the ABB.
