After carefully following all instructions in the setup tutorial (08/21/08) I am getting a loud noise from the botboardII speaker.
I am using the Basic Atom Pro IDE 08.0.18 (beta) and loaded the Phoenix 1.3 into the AtomPro, by clicking ‘program’ (no errors detected).
Maybe I’ll have to change some (com) settings in the program before uploading to the AtomPro?
The Lynxmotion PS2 controller is showing a flashing left red led and does not give any reaction on the Hexapod.
When powering up (9V and 6 V NIMH) the Phoenix is giving a loud noise, a blinking green light on the SSC-32 board, a green light on the botboard and no other lights, the legs go into the callibrated settings (I did before) and then move downwards… and still that terrifying (spider?) noise…
What am I doing wrong??
Jim, Is the pinconnection on the coreldraw diagram OK?, or do I have to connect to the lower pins( TX and RX)??
Thank you for your mail.
I have checked the connection of the modified servo extender wire a few times.
After downloading the software and powering up, the annoying loud beep keeps on going.
The legs are holding the callibrated position now, so that is OK.
The green light of Botboard and SSC-32 are lit continuously, but no A, B and C lights on the Botboard.
I have checked all the jumpers according the schematic.
The PS2 controller’s left red light is blinking… nothing else…maybe he is dead javascript:emoticon(’’)
I think tomorrow I try to get another PS2 controller, maybe a board or processor is dammaged??
It’s midnight now here in the Netherlands and go to sleep…
The sound is caused by the PS2 controller like Jim already said. The BAP can’t see the PS2 receiver, it’s got nothing to do with the controller – receiver connection.
One led on the receiver turns on when power is on. The other (blinking) led tells that the controller is not connected. Turn on and off the remote to let it connect again.
You need to check this:
Are the leds on at the controller (did this already but just in case )
Are the jumpers near buttons A, B and C removed
Check the receiver wires.
If you can’t find anything wrong in the above tests it could be the receiver. Can you try to connect another PS2 controller?
Hi Jim,
V1.2 used bidirectional communication to synchronize both BAP and SSC. V1.3 uses a internal timer for synchronisation. So the bidirectional communication isn’t really necessary at this point.
The PS2 controller has the part you hold (transmitter) and the part on the robot (receiver). You didn’t answer my question. Are the LEDs on the PS2 receiver lit up? This will tell me if the receiver is getting power.
Yes both receiver lights are lit on.
I have checked and double checked all wires, jumpers, where they have to be and not…according to the schematic.
Now I’ll have to recharge my NIMH batteries and try again in an hour.
Do I need other wiring because of version 1.3, as Xan said?
The tutorial never mentions the LED’s on the Bot Board being lit up, so why are you worried about them? In fact the schematic clearly shows the LED / switch enable jumpers not installed. So there is no way the LED’s will ever light.
As far as everything you have reported your robot should be working. The controller is working, no blinking LED’s, no beeping speaker, and the legs do move when turned on, so the Bot Board is talking to the SSC-32. As far as I can tell, all you have to do is press the START button on the remote control to activate the robot. Have you done this?
’)
)
Wheeeeew!!! 