Update on PS2, ABB1, and Pro?

[mspurk]

I’m trying to establish communication with the Lynxmotion wireless PS2 controller using my ABB1 and Atom Pro. I tried to use the example as outlined here lynxmotion.com/images/html/build034.htm . I downloaded everything and modified the code for the 8.0.1.7 IDE. The code compiled properly, but when I view the terminal I see this:

*FF 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
FF 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
FF 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
FF 255 255 255 255 255 255 255 255 255 255 255 *

and it just repeats that. The little vibration motors do nothing. Now, I haven’t installed a 1k pull-up resistor yet as outlined here: lynxmotion.com/images/html/build026.htm

Now my question is do we still need to install the pull-up resistor on the data and clock lines for the lynx controller? Do we install the controller on pins 4-7 and the pull-up on 4 & 7, or do we install the PS2 controller on 12-15 and the pull-ups on 12 & 15? The information on the site seems to contradict the forum, but the forum posts are old, so who knows which one is correct. Before I start soldering I want to make certain I’m doing it right.

-Matt-

Note: if a pull-up needs to be added to the board to make it work that should be included in the example. I spent countless hours late into the evening trying to get this and other example codes to work, only to find it may be a hardware issue when I searched the forum.

[kurte]

On my Hex Robot, I also have a ABB and an Atom Pro. I know that there are problems with one or more pins on the Pro having a lower voltage in the pins 4-7 so you need to move the PS2 controller to a different set of 4 pins. Originally I moved mine to 12-15, but later to 8-11 as to free up IO pins 14-15 which are used for a hardware serial port…

The new board BB2 has pull-ups built-in for pins 12 and 15, but if you are using an older ABB you will need to add one at least for the DAT line (pin 12).

Good Luck
Kurt

[mspurk]

Cool, so I can move it to any set of 4 pins I choose as long as it isn’t 4-7.

Originally I moved mine to 12-15, but later to 8-11 as to free up IO pins 14-15 which are used for a hardware serial port…

Is 14-15 dedicated on the board for serial IO. Sorry for the newb questions, I’m just learning. If yours is working on 8-11 I may move mine to the same, that way I know it will work there.

-Matt-

[kurte]

Yes, you can move them to any 4 pins… The new standard that the BB2 has for it is pins 12-15 which should work fine. That is where I started off.

My first answer maybe had too much information in it for a NEWB , but I don’t know how to rectify except to add more info .

Many Input/Output pins on the underlying Renesis H8/3694 Microprocessor have possible other uses. If you look at Mudule Pinouts on page 187 of the Basic Atom Pro manual (P197 in the PDF), you will see what functions are available. Note many of these pins have multiple possible other uses. For example IO pin 3 can be used as a normal IO pin or it can be used as an Analog Input (ADIN) or it can be used as Interrupt input (WKPINT_3) as it is used on the TV Brat robot (BIPED forum).

Now IO pins P14 and P15 are also TXD/RXD which is the hardware serial port. In basic you can access this using HSERIAL commands. You can use any IO pins for serial IO using the normal serin/serout commands. This uses software routines to “Bit Bang” out each of the bits in the serial communication. This works fine for most circumstances. However one big advantage for the hardware port is for receiving serial input from an external device. Using serin on standard IO pins will only properly work if your program is sitting in the serin command when the serial input arrives. So if your program is off doing something else and the serial input happens it will be lost. If instead you were using HSERIN, the underlying hardware will receive the input regardless of what your program is doing and you can process it when it is conveniant. Note: there are limits on how much input it will buffer before your program must process it…

Sorry again I know this way too much information!
Kurt

[mspurk]

No that was fine. I’ve done some basic PIC microcontroller programming. I understand the basics, but using the “features” on the Pro and ABB are something I’m muddling through.

I used pins 8 through 11. I installed the 1k on pin 8 and it didn’t change anything. I tried a 1k on 8 and 11 and still nothing. I then tried the 500k on pin 8 and still no changes. I’m not certain if I’m missing something. I checked all my batteries and they’re fine.

Here is the code I modifed from the Lnyx web-site.

;-----------Bot Board Selection----------
;PS2 Controller / BotBoard I
DAT con P8
CMD con P9
SEL con P10
CLK con P11

;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

;-----------PS2 Vibration motors----------
Small_Motor = 1 - Temp(1).bit5 ; Numeric right arrow button (Small Motor on/off)
Large_Motor = Temp(8) ; Analog left arrow button (Large Motor speed)

low SEL
; asking data to PS2 controller (again)
; sending at the same time the vibration motors speed to perform
; (using the previously read analog buttons position ( <- : large motor, -> : small motor )
; the more you press on these buttons, the more the corresponding motor vibrates fast
; some wireless PS2 controllers react only to the large motor command and some have no motor at all.
shiftout CMD,CLK,FASTLSBPRE,$1\8,$42\8,$0\8,Small_Motor\8,Large_Motor\8]
; we don’t care about reading the data from the controller here.
; so, why not use this to read PS2 data the first time? because it’s not working:
; as the PS2 controller is starting to send data just after receiving the
; “shiftout CMD,CLK,FASTLSBPRE,$1\8,$42\8…”<------here
; and as we are sending after that some data for motors “… ,$0\8,temp(7)\8,temp(8)\8]”
; it’s now too late to read all the data from the PS2 controller
; because there’s already some bytes sent by it and lost (no buffer here).
high SEL
;-----------------------------

;-----------Basic Micro IDE terminal----------
; sending carriage return (CR = 13) and the PS2 mode(hex) to the PC
;serout S_OUT,i57600,[13, hex2 mode\2] ; Basic Micro IDE <= 02.2.1.1
;serout S_OUT,I8N1_57600,[13, hex2 mode\2] ; Basic Micro IDE <= 05.3.0.0
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
; sending all the data to the PC
;serout S_OUT,i57600," “, dec3 temp(index)\3] ; Basic Micro IDE <= 02.2.1.1
;serout S_OUT,I8N1_57600,” “, dec3 temp(index)\3] ; Basic Micro IDE <= 05.3.0.0
serout S_OUT,i57600,” ", dec3 temp(index)\3] ; Basic Micro Pro IDE <= 08.0.1.7
next
;-----------------------------

goto main

I’m sure I’m missing something stupid, but for the life of me I can’t find it.

Thanks for your help.
-Matt-

[kurte]

Sorry, I don’t see anything obvious here. Obviously make sure your pull-up resistor is wired properly to the +5v. I believe that it should only be necessary on the DAT bin as the Pro will be driving the CLK pin. But I could be wrong.

I have been playing with making this pS2 controller work with a Propeller Microcontroller and have it somewhat working. I found this site informative about what these commands are:curiousinventor.com/guides/ps2

So far I have not had luck with getting the initialization code to work properly. However I have been able to make the controller work. What I sometimes have to do is to start the program, then turn off the PS2 controller and turn it back on (the lock function worked, but not the switch to analog). Then I press the analog button on the joystick and it switches to mode 73 and I am able to get the joystick information… You might try this as well to see if you can start to get valid input.

I believe that you said you have the Lynxmotion PS2 controller. If not you might try running the green wire to a VS pin. Some controllers (like the one that I have from Sector 7 require this connection to work).

Other than that I am not sure what to tell you…

Kurt

[robotdude]

@mspurk

Now my question is do we still need to install the pull-up resistor on the data and clock lines for the lynx controller? Do we install the controller on pins 4-7 and the pull-up on 4 & 7, or do we install the PS2 controller on 12-15 and the pull-ups on 12 & 15? The information on the site seems to contradict the forum, but the forum posts are old, so who knows which one is correct. Before I start soldering I want to make certain I’m doing it right.

-Matt-

Note: if a pull-up needs to be added to the board to make it work that should be included in the example. I spent countless hours late into the evening trying to get this and other example codes to work, only to find it may be a hardware issue when I searched the forum.

The most up do date PS2 code will be found in the A4WD1 tutorial. It’s working with the Atom Pro and the Bot Board II.
lynxmotion.com/images/html/build134.htm

Because you are using the Next Step board you will need to install a 1k pullup resistor added to the data line only. You can look at the users manual for the Bot Board II to see the schematic.

Unfortunately we do not have the ability to make sure all programs and tutorials work for very old boards that we have not sold for over 7 years.

The only other potential for problems is if you are trying to make your own cable to connect the PS2 receiver to the Carrier board. Our published color code may not match your cut extender cable.

[mspurk]

Unfortunately we do not have the ability to make sure all programs and tutorials work for very old boards that we have not sold for over 7 years.

Ummm I’m using a Mini-Atom Bot Board, which I bought in December 2007.

The PS2 controller is the lynxmotion controller.

Edit: I purchased the cable from lynxmotion as well.

[robotdude]

Ahhh I see. I had it in my head you were using a Next Step carrier. Sorry…

Ok, so the ABB came before the Atom Pro. We chose pins 4,5,6 and 7 for the PS2 connections. When the Atom Pro was made they put 3.3vdc I/O pins for pin 6 and 7. So for that reason we had to make the changes in the Bot Board II. It has the PS2 connections moved to 12,13,14 and 15. The only line that requires a pullup is the data line, which is P12. The pullup must be 1k or lower. One end goes to 5vdc and the other end goes to the I/O pin.

If you are able to add the pullup then you should be able to use the A4WD1 tutorials to get your PS2 controller working.

[mspurk]

Nope. Didn’t work. I dowloaded the very bottom code here lynxmotion.com/images/html/build134.htm

I configured it for the Botboard 1.

DAT con P12
CMD con P13
SEL con P14
CLK con P15
GRIP_UD con p4
GRIP_Rot con p5
GRIP_OC con p6

I moved the 1k resistor to pin 12. I quadruple checked the resistor is tied from 5V to signal. I also tied pin 10 signal to LED A. I connected 2 servos to pin 2 and 3. I also tried them on 4, 5, and 6 with no change.

Here’s what happens when I run the code:

Ascending notes from speaker - Good
LED A comes on - Okay I suppose
left LED on PS2 controller (next to left analog stick) flashes
right LED on PS2 controller stays off
right LED on PS2 receiver goes solid
left LED on PS2 receiver stays off

I cannot cycle LED A with triangle (or any other button for that matter). No combination of buttons causes the servos to move. I double-checked the batteries in the remote, still reading 1.6V each. I check my source battery, still reading 7.6V. Made certain I had the jumper on VS-VL. I have the jumper on the PS2 cables set to 5V. I have the green wire connected to VS.

Here is my code straight from IDE:

'Program name: PS2ROV4.BAS
'Author: Jim Frye / Nathan Scherdin (PS2 stuff)
'Modified by Laurent Gay : speed limit control with L1/L2
'Modified by Brian Nave : Normalized analog joysticks, named button variables, positive boolean logic, audio feedback on speed limit
'Modified by Laurent Gay : New PS2 Controller code (more compatible)
'Modified by James Frye : Configured for Atom Pro

’ This program allows the remote control of a differentially steered robot
’ from the Sony Play Station 2 game controller.

’ The Scorpion has two modes of operation. The default is the mixer mode. This
’ is where you have a Throttle for forward and reverse speed control, and a
’ Steering control for turning. In this mode the left input is throttle and
’ the right input is steering. The other mode is a differential style control.
’ This is where the left and right channels are controled indepentantly to
’ steer like a tank. This program uses the mixing mode. It also requires the
’ BEC (battery eliminator circuit to be dissabled. See the Scorpion manual.

'Connections
'Pin 0 Left Scorpion channel.
'Pin 1 Right Scorpion channel.
'Pin 2 Pan servo.
'Pin 3 Tilt servo.
'Pin 8 NA
'Pin 9 Speaker
'Pin 10 1/0 Controlled from Triangel Button
'Pin 11 1/0 Controlled from “X” button
'---------------
'BotBoard I :
'Pin 4 PS2 Data
'Pin 5 PS2 Command
'Pin 6 PS2 Select
'Pin 7 PS2 Clock
'Pin 12 Gripper up/down servo.
'Pin 13 Gripper rotate servo.
'Pin 14 Gripper open/close servo.
'Pin 15 NA
'---------------
'BotBoard II :
'Pin 7 NA
'Pin 12 PS2 Data
'Pin 13 PS2 Command
'Pin 14 PS2 Select
'Pin 15 PS2 Clock
'Pin 4 Gripper up/down servo.
'Pin 5 Gripper rotate servo.
'Pin 6 Gripper open/close servo.
'---------------

'PlayStation game controller connections.

'PS2 Controller / BotBoard I
DAT con P12
CMD con P13
SEL con P14
CLK con P15
GRIP_UD con p4
GRIP_Rot con p5
GRIP_OC con p6
'PS2 Controller / BotBoard II
'DAT con P12
'CMD con P13
'SEL con P14
'CLK con P15
'GRIP_UD con p4
'GRIP_Rot con p5
'GRIP_OC con p6

temp var byte ’ Variable definitions.
buttons var word
Lastbuttons var word

bpress1 var bit
bpress2 var bit

rhori var byte
rvert var byte
lhori var byte
lvert var byte

rhori_null var byte
rvert_null var byte
lhori_null var byte
lvert_null var byte

NormalizeValue var byte
NormalizeNull var byte
DeadBand con 2

ldrive var word
rdrive var word
PanPosition var word
TiltPosition var word

GripperVertPosition var word
GripperTurnPosition var word
GripperGripPosition var word
servo5 var word

GEAR var byte

Button_START var bit
Button_SELECT var bit

Button_L1 var bit
Button_L2 var bit
Button_R1 var bit
Button_R2 var bit

Button_A var bit
Button_O var bit
Button_X var bit
Button_S var bit

Dpad_UP var bit
Dpad_RIGHT var bit
Dpad_LEFT var bit
Dpad_DOWN var bit

GEAR = 3 ’ Start at Gear 3 (from 1 to 4)
PanPosition = 1500 ’ Start the servos at mid position.
TiltPosition = 1500
GripperVertPosition = 1500
GripperTurnPosition = 1500
GripperGripPosition = 1500

low p0 ’ Ensure pulsout commands are positive going.
low p1
low p2
low p3
low GRIP_UD
low GRIP_Rot
low GRIP_OC

low P10 ’ Ensure device connected to pin 10 and 11 is off on startup
low P11

high CLK ’ Ensure CLK is negative going.

sound 9, [100\880, 100\988, 100\1046, 100\1175] 'four quick ascending notes.

pause 1000

setup ’ This section sets the PSX Controller to Analog Mode. (red LED should light)
’ This will work with Sony and Madcatz wired, but not with Medcatz wireless.
’ You must press the analog button on the controller to set to analog mode.
low SEL
shiftout CMD,CLK,FASTLSBPRE,$1\8]
shiftin DAT,CLK,FASTLSBPOST,[temp\8]
high SEL
pause 1

if (temp <> $73) and (temp <> $79) then
	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

	goto setup
endif

gosub get_PSX_data
gosub NullJoysticks

main
gosub get_PSX_data

if Button_START then : gosub NullJoysticks : endif

'SET LINEARIZED JOYSTICK DISPLACEMENT BASED ON JOYSTICK CENTER POSITION
NormalizeValue = lhori : NormalizeNull = lhori_null : Gosub Normalize : lhori = NormalizeValue
NormalizeValue = lvert : NormalizeNull = lvert_null : Gosub Normalize : lvert = NormalizeValue
NormalizeValue = rhori : NormalizeNull = rhori_null : Gosub Normalize : rhori = NormalizeValue
NormalizeValue = rvert : NormalizeNull = rvert_null : Gosub Normalize : rvert = NormalizeValue

'   remove the rems (') to see the NORMALIZED joystick values in terminal 1.
'	serout S_OUT,i57600,[dec3 lhori\3," ",dec3 lvert\3," ",dec3 rhori\3," ",dec3 rvert\3," ", 13]

'SET MAX MOVEMENT SPEED TO ONE OF FOUR CHOICES AND GIVE AUDIO FEEDBACK
if Button_L1 and (Lastbuttons.bit10 = 0) then
GEAR = (GEAR + 1) MAX 4
for temp = 1 to GEAR: sound 9, [100\880]:pause 10:next
elseif BUTTON_L2 and (Lastbuttons.bit8 = 0)
GEAR = (GEAR - 1) MIN 1
for temp = 1 to GEAR: sound 9, [100\880]:pause 10:next
endif

’ lvert=255-lvert ’ Changes vertical up from 0 to 255 and vertical down from 255 to 0.
lhori=255-lhori

'CALCULATE DRIVE SPEEDS FROM JOYSTICK POSITIONS AND SPEED LIMIT
ldrive=((lvert*GEAR) + 1500 - (GEAR 128)) ’ Forward / backward
rdrive=((lhori3) + 1500 - (3 *128)) ’ steering

'   remove the rems (') to see the calculated drive motor speeds in terminal 1.
'	serout S_OUT,i57600,[dec5 ldrive\5," ",dec5 rdrive\5," ",13]


PanPosition  = (PanPosition  + (rhori-127)/5) MAX 2250 MIN 750
TiltPosition = (TiltPosition + (rvert-127)/5) MAX 2250 MIN 750

GripperVertPosition = (GripperVertPosition - Dpad_UP*25    + Dpad_DOWN*25) 	MAX 2250 MIN 750 	'Move Gripper Vertically.
GripperTurnPosition = (GripperTurnPosition - Dpad_RIGHT*25 + Dpad_LEFT*25) 	MAX 2250 MIN 750 	'Rotate Gripper.
GripperGripPosition = (GripperGripPosition - Button_R2*25  + Button_R1*25) 	MAX 2250 MIN 750 	'Grip Gripper.

'   remove the rems (') to see the gripper and pan positions in terminal 1.
'	serout S_OUT,i57600,[dec4 GripperVertPosition\4," ",dec4 GripperTurnPosition\4," ",dec4 GripperGripPosition\4," ",dec4 PanPosition\4," ",dec4 TiltPosition\4, 13]

’ I/O on/off

if Button_A and (bpress1=0) then	' This makes a latching output pin that responds to button presses.
	bpress1=1
	toggle p10
endif
if (Button_A=0) and bpress1 then
	bpress1=0
endif 

if Button_X and (bpress2=0) then	' This makes a latching output pin that responds to button presses.
	bpress2=1
	toggle p11
endif
if (Button_X=0) and bpress2 then
	bpress2=0
endif 

’ Send out the servo pulses
pulsout 0,(ldrive2) ’ Left Scorpion channel.
pulsout 1,(rdrive2) ’ Right Scorpion channel.
pulsout 2,(PanPosition2) ’ Pan servo.
pulsout 3,(TiltPosition2) ’ Tilt servo.
pulsout GRIP_UD,(GripperVertPosition2) ’ Gripper up/down servo.
pulsout GRIP_Rot,(GripperTurnPosition2) ’ Gripper rotate servo.
pulsout GRIP_OC,(GripperGripPosition*2) ’ Gripper open/close servo.
’ pulsout 15,servo5
pause 20
goto main

get_PSX_data ’ This section gets the data from the PSX controller.
’ The first byte is the mode (Temp)
’ The 2 next bytes are the pushbutton data (button1, button2).
’ The 4 next bytes are the analog joystick data (rhori,rvert,lhori,lvert).
Lastbuttons = buttons
low SEL
’ Initiate request for data from PSX controller.
shiftout CMD,CLK,FASTLSBPRE,$1\8,$42\8]
’ Temp is the Mode value, it will be dumped. Then it puts the button data into two byte variables.
shiftin DAT,CLK,FASTLSBPOST,[temp\8,buttons.LOWBYTE\8,buttons.HIGHBYTE\8,rhori\8,rvert\8,lhori\8,lvert\8]
high SEL
pause 1

buttons = buttons ^ $FFFF	' SO WE CAN USE POSITIVE BOOLEAN LOGIC WHEN EVALUATING BUTTONS

Button_SELECT 	= Buttons.bit0
Button_START 	= Buttons.bit3

Dpad_UP 		= Buttons.bit4
Dpad_RIGHT 		= Buttons.bit5
Dpad_DOWN 		= buttons.bit6
Dpad_LEFT 		= Buttons.bit7

Button_L2 		= Buttons.bit8
Button_R2 		= Buttons.bit9
Button_L1 		= Buttons.bit10
Button_R1 		= Buttons.bit11

Button_A 		= Buttons.bit12
Button_O 		= Buttons.bit13
Button_X 		= Buttons.bit14
Button_S 		= Buttons.bit15	

’ remove the rems (’) to see the RAW joystick and Button values in terminal 1.
’ serout S_OUT,i57600,[bin buttons\16," “]
’ serout S_OUT,i57600,[dec3 rhori\3,” “,dec3 rvert\3,” “,dec3 lhori\3,” “,dec3 lvert\3,” "]
’ serout S_OUT,i57600,[13]
return

Normalize
if NormalizeValue < (NormalizeNull-DeadBand) then
NormalizeValue = (127NormalizeValue)/(NormalizeNull-DeadBand) MAX 127
elseif NormalizeValue > (NormalizeNull+DeadBand)
NormalizeValue = (127(NormalizeValue-NormalizeNull)/(255-DeadBand-NormalizeNull) + 127) MAX 255
else
NormalizeValue = 127
endif
return

NullJoysticks 'READ ANALOG JOYSTICKS TO NULL OFF-CENTER VALUES
rhori_null = rhori
rvert_null = rvert
lhori_null = lhori
lvert_null = lvert
return

I really don’t even know what to try next to make it work. Totally out of ideas.

[robotdude]

Do you have or know anyone who has a PS2 game console? You can test the controller on it. If it doesn’t work on the game console it’s a bad controller. It has happened before. If it does work on the game console then we can dig deeper. FYI the controller will link up with the atom chip removed.

Turn bot board (receiver) on, left LED on steady, right LED blinking.

Turn hand held controller on, left LED blinks once, then both LEDs blink twice, then go out. On the receiver both LEDs light and stay on steady.

This will happen even if the only thing connected to the PS2C is the 5vdc power…

Basically what I’m trying to say is it’s probably not a program issue. Another thing I noticed a couple times, but not every time, is that the robot / receiver should be powered on first, then the hand held controller should be powered on second. I’m sure this is due to me testing it with the 4 position DAT, CMD, ATT, CLK connector removed.

[mspurk]

Ding Ding Ding. You got the prize Jim. It’s a bad PS2 controller. I plugged my wired PS2 controller in and it worked fine. servos moved, lights flashed, horns buzzed. Everything worked. It was an amazing relief. I sent you an e-mail as well.

Thanks,
-Matt-

[robotdude]

@mspurk

Ding Ding Ding. You got the prize Jim. It’s a bad PS2 controller. I plugged my wired PS2 controller in and it worked fine. servos moved, lights flashed, horns buzzed. Everything worked. It was an amazing relief. I sent you an e-mail as well.

Thanks,
-Matt-

The quality of the controllers is generally very good, but I have had to replace a couple bad right out of the box. We will take care of it for you. Sorry for the trouble…

[mspurk]

Not a problem. I appreciate you fixing the issue and helping me troubleshoot everything.

So in summaray:
if you stumbled onto this thread and you need help troubleshooting your setup. Try these things first:

*Install a 1K pullup resistor on the Data pin (power to signal)
*Download the 4WD rover PS2 code found here: lynxmotion.com/images/html/build134.htm
*double check all your batteries, resistor installation, and PS2 controller
*also make certain your jumper is set to VL not VS.

Hopefully that solves the problem for you.
Thanks again Jim,
-Matt-