I’ve been working the Phoenix hexapod. got it built and working with the SSC32, using sequencer files and playing around with the PEP spreadsheet. I’ve gone on to add the Botboard II/AtomPro but can’t get past a hookup problem. When I power up I get a continuous beeping (sounds like a clicking really). The instructions on the tutorial say “If you hear a continuous beeping, the PS2 controller is not connected to the Atom properly or is not functioning.” but I am not sure what I have wrong or what troubleshooting step to try. and while I’m here - what baud rate does the serial port on the BBII use and is it settable?
Have you downloaded and installed Xan’s Phoenix code?
It will set the Baud from within the program…checkout the thread for the Phoenix it is near perfect for all the ps2 stuff and everything else you will need to know.
Dave
The clicking noise that you hear is a program that is uploaded to Atom/Atom Pro chips used to test their functionality. The continuous beeping is three consecutive beeps, each higher in pitch than the last. As Putt Putt stated, you’ll need to download and program your chip with Xan’s Phoenix code.
For the program, you will need to set your SSC-32 to 38400 baud.
Hope this helps.
Thanks for the pointer to the new code. I haven’t been looking at new posts lately so I didn’t know about it and am eager to get going.
My current problem is just getting connected and running, I am not yet to getting a program downloaded.
I turn on the wireless PS2 controller and the left LED begins blinking so I have power. I turn on the BBII and I get one beep. On the controller both LEDs blink twice then it returns to the left LED blinking slowly. The BBII then goes into a continuous rapid series of beeps. WRT the PS2 recevier LEDs, during the board initialization, the right LED (as I face the receiver) is steady on and the left LED is slowly blinking; once the continuous series of beeps starts, the left LED on the receiver blinks rapidly in time with the series of beeps.
In Basic Micro Studio - if I disconnect and re-connect Terminal 4 (connected through a serial cable and COM port), then, regardless of the baud rate (and I have tried a number) when I re-connect the board seems to reset and I see the behavior I have described above.
Summing up - I don’t seem to have things connected right yet, but I am not sure what to troubleshoot; I don;t know what is correct and incorrect behavior as I am new to it. So any help is appreciated.
Thanks
Thanks
I just posted right on top of you so I hadn’t read your reply. I was trying to describe my bot’s behavior in gory detail. i’ll download Xan’s program and work with it.
and I had missed the SSC32 baud jumper setting
try that next
thanks
Making progress of a sort. I loaded up Xan’s code. Built it and hit ‘Program’ to upload it to the bot. The clicking stops (I get that now). I get an error saying ‘A BasicATOMPro processor must be connected to program’. I tried using Tools->Preferences->[GeneralTab]{Find Processor} button and that checks com ports and fails to ‘find’ the processor. Still not sure what baud rate to set the port to or whether thats’s an issue. I did set the SSC32 baud jumper. Feel like I am almost there but missing something in the setup (or maybe something between the ears).
build159 - is the one I have been following. I am at the 'Program the AtomPro." baby step in step 16. Seems innocuous enough. Thanks for the help so far.
You’re programming the Atom, so I’m assuming you have the serial port cable connected to the Bot Board, not the SSC-32. 
Please review this Basic Atom Pro programming tutorial.
Yes
So the clicking at powerup is actually a good thing, right? a self test program that says that the AtomPRO chip is OK?
OK - Success. A combination of RTFM - the programming tutorial which I hadn’t gone through - to make some adjustments in the advanced dialog in the IDE - and then I stopped using the USB->Serial cable and went back to using my dedicated serial port (my computer is old enough to have one) and between the two the IDE can now ‘see’ the AtomPro.
Thanks for your help. hopefully that’s my ‘hump’ for awhile.
Yes, it’s a good thing. I asked about the serial cable cause you mentioned SSC-32 settings when asking about programming issues. Moving on…
I’m poking in the middle of this. If I ask a question that you have already answered don’t be offended.
Are you using a serial port or a USB to serial cable?
If USB what brand?
What settings for port? com1, com7 etc.
Which editor are you using? Studio or older version.
Have you looked at the tutorial for programming? If so are any of the steps working?
Sigh… you got it while I was typing. 
Appreciate it anyway. I had added the USB-Serial cable when I thought I was having trouble with a conflict on the COM1 port. I had got the USB-Serial cable working with the SSC32 back a bit so I didn’t think about it with the BBII. When kept not working I figured take away a variable. Anyway. On to the next issue (viz Xan’s code - left side and right side legs are at totally different heights - I’ll go looking in the Phoenix forums - or the code - for someone else who’s had that problem)
Thanks again.
Did you build all left legs, or are there right and left legs? Can you post an image of the beast?