this is something i forgot. thanks. 
anyway the SSC still flashes.
im in the middle of a renovation in my home.
a few walls to knock out,
new kitchen to install, + built-in wardrobe in bed room,
Rear extention single story
and infill porch area,
then make good the decorating! … (a busy one man band)!!!
so i may not be as active here for a while. 
i may get time to work on this problem soon as i really need to get it working again!
thanks.
OK…
All power good,
SSC pins good,
ABB pins good,
PC Serial connection good,
PS2 controller good,
PS2 receiver good,
code good,
one more thing…
i know iv been here but i think im missing all the info on baud rate.
baud rates:
do i need to change this for IDE, CODE and SSC?
what baud rates wouldnt be recommended? or are all ok.
i understand what modulation rates are but “Really” what would i expect by changing them?
thanks.
The SSC-32 can chat with a device at 115.2k, but the Atom (and other micro’s) can’t talk so fast. So we slow the SSC-32 down to 38.4k for the Atom. Usually the faster it is the easier it is to write communication intensive code for. The firmware can not be done at slower rates though. That’s primarily why it is the way it is.
this is why i ask:
?
i have narrowed all the posible problems down to the baud rate.
shall i try 115.2k?
The reason I asked this is for troubleshooting purposes. It’s possible that the baud rate jumpers were not making connection, were defective, or the traces that go to them were open. You must use 38.4 for Atom programs.
Going back to your statement of a beeping every two seconds or so, as Kurt (I think) observed, the Atom could be resetting. I just ran into a brand new 9V battery connector that was sensitive, and gave me a similar problem. The fix, of course, is to just bend the terminals to grip a little better.
Just thought I’d throw that in.
How’s the 'bot coming along?
Alan KM6VV
yeah i got the beeping to stop last week. it was due to wire connection as you mentioned.
the SSC is still Flashing and so i added a sound command to the (main) section of the code and it was beeping like mad in time with the flashing. iv got it down to this problem:
Wire connections for communication between both boards = ill be sorting this out when i get some time. ill change the wire and also the pins.
i kinda did this already but when i replaced the wire i was still connecting them to the original pins but now ill try a new wire on new pins. i think ill try pin 6-7, 6-8, or 6-10,
iv tried 8-11 and i think the problem lies with pin 11.* ill confirm this.*
iv now disconnected all the leg servos and only have PS2, communication wire, batterys and one servo connected.
im doing the standard stuff to find the problem but its just finding time at the mo.
cheers.
ok been changing the data connection pins and on change!
SSC works fine with lynxterm… 
The Atom code (sounds) work fine when buttons pushed, and ABB pins seem to be ok…
…but SSC is still flashing and servos move on their own!
when using the remote while everything is turned on it seens like i have some influence to the servos but this is only sporadically.
im thinking of buying another ATOM but do you think it will be worth it?
I’d send it in to Jim to test it out. It would be a bummer to get a new one and still have the same problem.
I’m still thinking you’ve got a baud rate problem. The SSC32 is flashing, so it’s receiving data. Might be wrong, but it’s receiveing!
If you don’t mind, verify the jumpers on the SSC32 again. Make sure it matches the baud rate you’re sending commands at!
Simplify the setup, do a simple one-servo move?
If you’re sending data, the Atom is probably fine!
You could use a TTL to RS-232 converter, and send the data to a COM port on your PC, read what you’re sending. Verify sending baud rate.
The jumpers on the SSC32 can be confusing!
Alan KM6VV
That’s funny, how did I quote myself?
Alan KM6VV
Without knowing the basic code is sound there is no way to know anything really. I’m not even sure he’s able to program the atom currently.
What needs to happen here is a major step backwards. write a program for the atom to send a simple ascii command string. We need to drop back and punt so to speak…
i replaced my controller and now all is ok. i had been turning up the deadzone for the controller as i thought it might be the controller.
it was a Micro Madcatz PS2. lasted three years!!!
guess it was sticking, resulting in signal being sent to boards.
thanks again for everyones help. 
Doh!!! All this trouble caused by a cheap PS2 controller clone! 
lol I’m glad you got it figured out!!! 8)
