PS2 connection problems

I’m experiencing difficulties with my ps2 controller. My set up is ah3-r. As prescribed in previous forums the controller doesn’t connect to the receiver. The left light on the receiver blinks at one second intervals as does the left light on the controller. The right light on the controller remains inactive. I have spent much time looking at posts similar to this and have tried all of the remedies that lynxmotion has put in the open. None of then changed anything except the one where somebody gave an idea to unplug blue/orange/yellow/brown cable to see if the controller would then connect. When I did this the right light on the ps2 light up and the left receiver light began to blink rapidly.

I have recently purchased a new pelican ps2 controller but the robot doesn’t acknowledge its connection to the cable. Could the cable be the problem or maybe it’s the controller/receiver?

Thanks for any help…

Hi Kevin,

It would help to have additional information. You have an AHR-3. Does this include a Atom Bot Board 2 with an Basic Atom Pro28? Are you using a tutorial and if so which one and what step are you up to? Is this a Lynxmotion PS2 controller? What Program are you trying to run? As this was your first post you probably won’t be able to post a picture, but if you could that always helps.

As you mentioned you have checked out all of the posts, but some things to double check:

  1. You have fresh batteries in the PS2 controller, likewise your robot has a fresh charge
  2. Make sure the controller wire is plugged into the right pins on the BB2 (12-15) and the IO pins not power or ground
  3. Make sure the power jumper for pins 12-15 are set to +5v not VS
  4. Make sure the PS2 receiver is plugged in correctly into the cable.
  5. Try running the PS2 test program that you can download from the Lynxmotion tutorials.

Good Luck
Kurt

Yes the set up is an atom pro on a bs2.

I have followed the tutorial to the end and the robot is programed.

The controller is a lynxmotion.

I don’t know how to post a picture.

  1. The batteries have been sitting in the controller for maybe a month or two.
  2. The wires are connected correctly.
  3. The power for pins 12-15 is set to +5V
  4. The receiver is connected properly.
  5. I am in the process of running the test…

The results of the test gave me a repeating sequence of:

79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000
79 255 255 128 128 128 128 000 000 000 000 000 000 000 000 000 000 000 000

In the tutorial at the link; lynxmotion.com/images/html/build034.htm, the sequence was exactly the same.

Does this mean that the controller works?

Maybe, maybe not…

it implies that receiver is communicating properly with the BAP. Are the lights still blinking like before? If the batteries have been sitting in the controller for a couple of months, you might try fresh ones (long shot). If you move the joysticks or press buttons, does the output from the program change?
Another long shot: If you take the tutorial code for the PS2 and at the end insert a command: Pause 20
Before the goto Main

Does that change anything? I have had programs that did a query too fast and the controller and remote did not have time to talk to each other…

Other than that I think you may have to wait until tomorrow for others to join in…

Kurt

The lights still blink as before although sometimes the left light on the controller blinks about three times a second.

When I was running the test I tried that and nothing seemed to happen.

The sequence repeats too rapidly to type anything in the space. I had to disconnect from the board so I could copy the code it was spitting out.

Thanks for your ideas and quick response.

I have had no luck with the potential solutions. I tried reprogramming the robot on a different computer because mine now has viruses.

Moving the controller buttons had no effect on the code that was reading out.

Any more suggestions?

I’m not sure how I missed this thread. :frowning:

Here’s the bottom line on our wireless PS2 controller…

]Remove the Atom from the Bot Board completely. /:m]
]Connect power to the receiver. Make sure you are providing 5vdc not VS which could be much higher. /:m]
]Install batteries in the hand held controller and turn it on. /:m]

If you turn on the receiver by itself the left green LED is on steady and the right red LED is blinking about 3 blinks per second.

If you turn on the transmitter by itself the left LED blinks and the right LED is off.

Turning on both should result in the blinking LED on the receiver going on steady, and the transmitter LED going out.

The Atom is not required for the two parts to communicate. However if there is a problem with the code, the two may not sync up. By removing the Atom completely you are not relying on code for the sync.

If the two will not get along then their is likely a defective unit involved. If this is the case we need to replace the controller. This process requires you to contact us in email with the date and order number. If less than 30 days have elapsed you will receive a new controller. We will need to get the defective unit back before we will send a replacement though.

How can I remove the atom chip without bending the terminals?

If you don’t think you can do it, then by all means leave the Atom in the Bot Board. Just pull the 4 ganged PS2 cable connector from the Bot Board. Leave the one that is supplying power to the receiver. :wink: Same thing…

I had previously seen this solution in another forum post and decided it wouldn’t hurt to try it. There was no change in the blinking of either led’s on the controller or receiver. Since reprogramming I have tried this again and the results were the same. No difference in the controller or receiver.

I also purchased a Pelican controller and it didn’t work either. Any help with that would be useful…

My mom should be emailing me the order forms so it could be a while. By the way I’m fifteen just to make that last part not sound strange. I used her account to order parts and I’m using my dad’s account to talk on the forum. The only reason I’m not using mine is because it’s saved on my laptop that has many viruses at the time.

Thank you so much for your help.

The order number is:

Subject: Your Lynxmotion Order Number is: 26585
Date: Sun, 8 Mar 2009 16:45:35 -0700

Lynxmotion Online Order Placed 3/8/2009 11:45:35 PM UTC
Your Order Number: 26585
[snip]
Item:
Description: PS2 Robot Controller
Item #: RC-01
Qty: 1
Unit Price: $19.95
Extended Price: $19.95

Unfortunately there is no way we can support other brands of PS2 controllers like the Pelican controller. It would mean we would have to have one of every brand available in house. This is not practical.

Kevin, this order is over a year old… :open_mouth: :unamused:

Yes this project has been going on for a while. So what you’re saying is that I just have to order another controller?

I did say " If less than 30 days have elapsed you will receive a new controller." above, right? :wink:

Ok. Well I’ll see to it that I order another sometime in the near future.

Thank you for the help.

Hi,

I was reading this topic, cause I cant get any communication going as well… Im trying now with a Atompro 28, Bot board II and a lynxmotioncontroller with receiver.

While im reading this topic, I notice several problems… :open_mouth: :confused:
There is a green led suppose to light up when you turn the controller on ?? Mine doesn’t and never has… only the red led starts to blink
I’m trying it right now, with new batteries.

If I only place 5V on the receiver then both leds starts to burn… (green and red)
when i connect the communication wires (Braun, orange, yellow and blue) then the the red led start to blink weak with irregular a bright blink :confused:

I bought my controller a few months ago trough a dutch retailer, hoping to get it going with a basic stamp… that never worked… Im getting the feeling now that it wasn’t the stamp but that the controller/receiver is not working…

I’m getting now the feeling that I trow my money away… that always sucks! :wink:

Hope someone can help me out here…

So if you only plug in the power/ground to the receiver you have both LEDS on the receiver light up. That usually implies that it has made a connection between the sender and the receiver.

You say you plug in the communication wires, that you only get a faint irregular blink. Questions are:
a) where do you have the cable plugged in? Pins 12-15 on the BAP? on the IO pins? (the row toward the inside of the board)
b) What is the power jumper set to for pins 12-15? (should be +5v NOT VS)
c) What power do you have going to the BB2?
d) What program are you trying to run on the Basic Atom Pro? Have you downloaded something? If so what? Also what version of the Basic Micro software are you running?

Kurt

"So if you only plug in the power/ground to the receiver you have both LEDS on the receiver light up. That usually implies that it has made a connection between the sender and the receiver.

You say you plug in the communication wires, that you only get a faint irregular blink. Questions are:
a) where do you have the cable plugged in? Pins 12-15 on the BAP? on the IO pins? (the row toward the inside of the board)
b) What is the power jumper set to for pins 12-15? (should be +5v NOT VS)
c) What power do you have going to the BB2?
d) What program are you trying to run on the Basic Atom Pro? Have you downloaded something? If so what? Also what version of the Basic Micro software are you running?"

sorry for my incomplete background info;

a: Pins 12 - 15 on the botboard II
b: the power is set to 5V, I have measured it as well, 4,99V
c: think that b answers c; ( a nine volt adapter connected to VL)
d: trying with the Basic Micro Pro IDE <= 08.0.1.7 and the standard test program found on lynxmotion website

But I still think that the main problem is that there is not a green led on my controller. But I will be happy proved otherwise :slight_smile:
Ill ad a picture, not very clear… but you can see the connecting.

Thanks for all the help

I can not tell for sure from your picture, but it almost looks like the yellow wire from the PS2 connector is going to ground and the Black/red combination is going to power which is backwords…

Here is a diagram of the different PS2 cable connectors: lynxmotion.com/images/html/b … tm#aglance

Kurt

Hi,

The picture is kinda bad, but I guess that you talk about the yellow/black cable, thats the communication cable between the BotBoardII and the SSC-32 board. The receiver is connected as follow: black/white to ground, red to 5V… P12=brown, P13=orange, P14=yellow and P15=blue

I’m pretty sure that all the wires are correct, the green led on the receiver burns, and the red one flashes.

Think that If I would find someone with a PlayStation, it would be easy to tell if the receiver/controller is working at all…
only stupid that none of my friends has a Playstation :confused: what are the chances :open_mouth:

but this is the code I’m reading now.

41 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
FF 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
41 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
FF 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
41 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
FF 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
41 255 255 255 255 255 255 255

And this code keeps generating with my controller on or of.
My program is the test program from Lynxmotion website::
;PS2 Controller / BotBoard II
DAT con P12
CMD con P13
SEL con P14
CLK con P15
;-----------------------------

index var byte
temp var byte(19)
mode var byte
Small_Motor var byte
Large_Motor var byte

;PS2Init
high CLK

low SEL
shiftout CMD,CLK,FASTLSBPRE,$1\8,$43\8,$0\8,$1\8,$0\8] ;CONFIG_MODE_ENTER
high SEL
pause 1

low SEL
shiftout CMD,CLK,FASTLSBPRE,$01\8,$44\8,$00\8,$01\8,$03\8,$00\8,$00\8,$00\8,$00\8] ;SET_MODE_AND_LOCK
high SEL
pause 100

low SEL
shiftout CMD,CLK,FASTLSBPRE,$01\8,$4F\8,$00\8,$FF\8,$FF\8,$03\8,$00\8,$00\8,$00\8] ;SET_DS2_NATIVE_MODE
high SEL
pause 1

low SEL
shiftout CMD,CLK,FASTLSBPRE,$01\8,$4D\8,$00\8,$00\8,$01\8,$FF\8,$FF\8,$FF\8,$FF\8] ;VIBRATION_ENABLE
high SEL
pause 1

low SEL
shiftout CMD,CLK,FASTLSBPRE,$01\8,$43\8,$00\8,$00\8,$5A\8,$5A\8,$5A\8,$5A\8,$5A\8] ;CONFIG_MODE_EXIT_DS2_NATIVE
high SEL
pause 1

low SEL
shiftout CMD,CLK,FASTLSBPRE,$01\8,$43\8,$00\8,$00\8,$00\8,$00\8,$00\8,$00\8,$00\8] ;CONFIG_MODE_EXIT
high SEL
pause 1

main

;-----------PS2 Mode----------
low SEL
; asking “mode” to PS2 controller
shiftout CMD,CLK,FASTLSBPRE,$1\8]
; reading “mode” from PS2 controller
; 73(hex) is dualshock1 (digital buttons)
; 79(hex) is dualshock2 (analog buttons)
shiftin DAT,CLK,FASTLSBPOST,[mode\8]
high SEL
;-----------------------------

pause 1

;-----------PS2 Data----------
low SEL
; asking data to PS2 controller
shiftout CMD,CLK,FASTLSBPRE,$1\8,$42\8]
; reading data from controller
; (don’t use a “for-next” loop, it’s too slow to read PS2 data)
shiftin DAT,CLK,FASTLSBPOST,[temp(0)\8,temp(1)\8,temp(2)\8,temp(3)\8,temp(4)\8,temp(5)\8,temp(6)\8,temp(7)\8,temp(8)\8, |
temp(9)\8,temp(10)\8,temp(11)\8,temp(12)\8,temp(13)\8,temp(14)\8,temp(15)\8,temp(16)\8,temp(17)\8,temp(18)\8]
high SEL
;-----------------------------

pause 1

;-----------------------------

;-----------Basic Micro IDE terminal----------

serout S_OUT,i57600,[13, hex2 mode\2] ; Basic Micro Pro IDE <= 08.0.1.7

for index = 1 to 18 ; temp(0) contains a dummy variable so we don’t send it to the PC

serout S_OUT,i57600," ", dec3 temp(index)\3] ; Basic Micro Pro IDE <= 08.0.1.7
next
;-----------------------------

goto main

Hope someone can help me out here. Maybe its a simple stupid mistake I make, but I don’t see it anymore…

THX