Yep I was going to mention that the connection between the two boards is wrong as well.
Note: The black wire should be connected to a ground pin, which is the pins closest to the outside of the board. The Red and Yellow lines should connect to signal pins which are the ones that are the most inside of the board.
Have you been able to program the Basic Atom Pro with the IDE? Also were you successful earlier in talking to the SSC-32 from your PC using Lynxterm to set up the servo zero point offsets? If the above is yes, than we know that you at least have a serial port that is working.
"Does the LED come on when power is applied to the bot board? "
yes.
“Does the speaker emit a clicking sound?”
Yes. sounds like a heart beat. Its very soothing.
“Have you been able to program the Basic Atom Pro with the IDE?”
Nope.
"…were you successful earlier in talking to the SSC-32 from your PC using Lynxterm to set up the servo zero point offsets?
Never been able to get that far.
Start the tutorial and do each step at a time. all steps are very important and if missed or skipped will make problems later.
Clicking chip:
i feel you may not have push your Atom chip in far enough. to confirm this can you post an END view of the Atom chip so we can see both rows of the pins.
Ok the first step in the tutorial is the talk to the SSC-32 with your PC using LynxTerm.
make sure no other program that uses the serial port are already open.
make sure the LED on the SSC-32 comes on, then connect the serial cable, then type VER then enter. The LED on the SSC-32 should go out then blink with every character. The SSC-32 should reply with it’s version number.
The problem: You cannot have the SSC-32 set up to both talk to the Bot Board II AND a PC. In order to communicate with a PC, remove the cable from the SSC-32 and replace the two jumpers that were on the TX/RX pins.
its hard to tell from that. we can work on your photography later, maybe pull the camera away abit. distant focused images are easier to see than close ups with no focus.
The SSC-32 should be configured for 115.2 kbaud and DB9 communication, with the VS2=VS1 jumper installed. Remove the VL=VS jumper. Consult the SSC-32 manual if needed. Attach the wiring harness to VS1. Connect 8" of 24awg wire (not included) AND the 9v battery clip to VL; this will provide power for the electronics. Make sure that the red wires go to (+) and the black wires go to (-).
Fish, did as you said. no dice.
heres a better shot of my chip. i pushed and pushed on it just now. not going in any deeper (or at least i fear im gunna break it)
if this still isnt clear enough I can use a different camera (just gotta dig it out of who knows where), using an iphone.
Gotta take a break, a friend of mine needs help ‘Wrangling his kids’ what ever that means.
thank you guys. ill be back in a few hours if youre still here.
OK, ill face my fears squeeze the hell of that chip. I can always buy a new one if i break it I guess. When power is applied the SSC LED does come on. it remains on until i start lynxterm, then it goes out perminantly. it does blink when i enter data. when i type VER nothing happens. or more accurately, the curser moves to the next line and stays there blinking.
I totally understand about wanting to not hurt the chip. But it should go in most all of the way. That is there should be very little gap between the top of the pins and the socket.
But now back to the problem at hand. That is communicating with the SSC-32.
OK first lets verify some of the settings/jumpers on the SSC-32.
You have power to both the logic side and servo side. Could have just one power going into it if you have the VL=VS jumper jumper-ed. If you have separate power sources going in for VS and VL make sure the VL=VS jumper is removed.
On the area near the DB9 connector, you have the two jumpers in place for RX and TX
Toward the middle of the board you have the two jumpers set for BAUD. This would set up the SSC-32 to communicate at 115200.
It sounds like you have maybe the right Com port selected on the PC, as when you start up the LED on the SSC-32 goes out. The light on the SSC-32 blinks when it receives data, but not necessarily valid data…
Now make sure you have the serial port connection from your PC plugged into the 9 pin connector on the SSC-32. Is this a real serial port or are you using an USB to serial adapter. If an adapter, which one?
Now on the PC side. If you are running Lynxterm, Make sure the comm port that is shown at the top shows the right. Click on the setup button and make sure the baud rate is set to 115200. Also does the button at the right of the comm port say connect or disconnect. If it says connect, then click on it…
I’m sorry I don’t mean to butt in, but as far as I can tell he still has the SSC-32 setup to talk to the BotBoard… James noticed it and posted yesterday…
Yep, I was wondering that as well, but then mentions led on SSC-32 turns off when he starts lynxterm, so then I was not so sure. That is why I tried to detail what I would expect the SSC-32 to be configured like.
In particular, I would suggest getting back to the configuration shown in Step 10 of the T-Hex body assembly guide (lynxmotion.com/images/html/build170.htm).
Success! Thank you guys. I can FINALY move to the next steps.
It still isnt working on my primary computer (Win7) but is on my secondary (Vista).
Did every single thing you guys said to do (thanx again) but it still didnt work. But there was a profound difference between today and yesterday. This time i knew i had it all correct, cuz you told me I did. soo … i tried my other machine. works. Dont know why it doesnt work on my Win7 machine. But whatever. The Vista machine litterally has lynxterm and nothing else installed. i guess ill keep it that way for now.
