I am building the AL5D to work with a PS2 controller. There is a new tutorial up ( lynxmotion.com/images/html/build091.htm ) but the Schematic that shows both micro controllers has a black/red/yellow connection, but the red wire is in a different port (11 instead of 10) than the rest. I don’t have the part, and when I saw the page a few days ago, it showed it using a black/yellow only connection, which I do have.
Why’d it change?
What’s the best way to go about doing it? If there was a way to see the black/yellow older schematic… that might be helpful?
the other connection is like this:
To connect the Bot Board II to the SSC-32, you will need to modify a 6" servo extender cable. Remove the header pins from the cable so you have two female ends. Then use an exacto knife to gently pry the tab up to pull the red wire free on one end. Cover the exposed female connector with heat shrink to avoid accidental shorts.
Remove the TX and RX jumpers from the lower-right corner of the SSC-32, and plug the unmodified end of the cable in. Yellow on TX, red on RX, and black on ground.
Thanks! I did that, but the servos are still not working.
I coded the BAP28 with Basic Micro Studio to be controlled with the PS2. When I turn on the PS2 there is a connection (solid red light on the controller, solid green and red on the receiver). When I hit “Start” it makes the three tones, but then when I push the buttons/d-pad/joysticks, nothing happens.
Quick check. Check your baud rate jumpers on the SSC32. Sould have both installed for a baud rate of115200. Also when you do stuff do you notice the led on the ssc32 flashing at all?
hmm… looks like one line of the code was accidentally commented out was the problem. Now, when I turn it on I get some, but very slow movement. I have control of the robot for about 30seconds, but it’s almost like there’s a delay. After about 30 seconds, I can’t control the robot anymore. It seems almost as if the batteries need charging, but they are fresh.
I’m pretty sure that in the Schematic above, that Red wire goes into the 11 pin. Thats how i have mine, and it works, but its very insubordinate. Description of that is here: lynxmotion.net/viewtopic.php?f=6&t=7923
Yep that’s what I have. Robot is still very slow and unresponsive at times. Also, certain directions on the joystick move more than one motor at a time…
It probably is a software issue… here, read what kurte posted. Middle post with the program attachment: lynxmotion.net/viewtopic.php?f=6&t=7923
I get the same thing, and it was like that with the old program, so i assume, that a solid red means its connected to the wireless reciever.
You mentioned that you have the Red on P11, what about the black and yellow? Normally I plug them into P10. We are not currently using the input coming back from the SSC-32, but you do need a ground wire between cards, which is what the Black will do…
As you mentioned, I did find some issues with the original program that was part of the tutorial and I posted an updated version in the thread you mentioned. Again need to mention that I moved the SSC-32 connection from P8 to P11 and updated the baud rate to 115200 as the basic atom pro serial output function was fixed a few builds ago that allowed the higher baud rates to work. In the other thread I mentioned that you can easily revert back to the older configuration, by changing the values of two constants…
Thanks, I cant wait to try your updated orginal program. I do have the yellow and black wires on P10 and I also like the original program alot better…other than the fact that there was a bug. I will try your updated program when I get back work with the arm on Tuesday.
