Thanks Kurte, I connected the wires as you suggested. I downloaded the test for the PS2 interface and these are the results I got when I ran the program. Looking at my results I am getting 255 rather than 000. Is this the problem I am having and how can I correct it?
picture of test.doc (139 KB)
picture of test.doc (39.5 KB)
73 first byte says you are in analog mode (the 7 part, the 3 part says there are 3 words of data…)
255 for the next two bytes is correct. It says there are no buttons pressed. (A button pressed will set it’s corresponding bit to 0
The next 4 bytes - are the values for the 2 joysticks, where something around 128 says they are at their default center location.
So it looked reasonable to me.
Kurt
We recently updated the diagrams and apparently goofed it up. 
Thanks for pointing it out. It will be corrected in a few minutes.
Totally my fault, sorry! Got my numbers mixed up during editing.
Here’s the updated, CORRECT, diagram:
? Looks the same?
Kurt
It may take a while to get the new image due to caching, but it IS different.
DAT P12
CMD P13
ATT P14
CLK P15
I had these numbers reversed in the original file.
the update is the three columns of colors?
Shows up here!
Alan KM6VV
Thanks, I did a refresh and it loaded the proper pin numbers.
Kurt
I am glad my problem identified an error. But I still have my problem. I think the last 12 columns which read 255 should read 000. If this is so then what is the problem? Columns 2 to 7 change numbers appropriately when I press the buttons on my PS2 (its the Sony one Jim) so the PS2 is communicating with the Bot Board II but the next 12 columns should be 000 according to the test manual.
The sony brand controller, sorry, was found to be the worst performer concerning the sticks returning to center. All after market ones work better. Our software puts the PS2 controller into analog mode. Make sure yours is in analog mode as well. We have basically covered all the bases. Do you have a different PS2 controller to try?
OOPs Snailkeeper: Looking at the new diagram, I think it still has issues.
That is, the bottom brown wire is DAT which you hook up to the IO pin 12… You have the right pin numbers, but I think you need to update the diagram with DAT at the bottom connected to the first pin which is brown…
Amoquith1: Because in your run you had a 73 versus a 79 as the first byte per row, this says you are in analog mode, but you are only receiving valid data for 3 words or 6 bytes of extra data, which gives you the 2 bytes for keypad and 4 bytes for the 2 joysticks. When in mode 79, you are getting 18 bytes of data, which includes the above information plus pressure data on how hard you pressing different buttons. Note: very few if any of our programs up here use this extra data. Not sure why your PS2 did not get into the extra data mode. Are you using a Lynxmotion PS2 controller?
EDIT: I see it is a sonly, so timings may be different to get into some control mode…
Kurt
Oh man, so close… Should be fixed properly this time. Sorry again!
From your output, maybe the timings for your PS2 is not getting the PS2 into command mode and maybe the program is hanging in the PS2 configure code.
But for the most part the program does not care if it is in 0x73 or 0x79 mode…
So you might try changing the one line of code:
if DS2Mode <> PadMode thento
if (DS2Mode & 0xf0)<> 0x70 thenNote: Several of our programs have sound statements within the PS2 init code to let us know if there is a problem (lots of noise). So you might try adding a line like:
sound 9, [100\4000, 100\4500, 100\5000]
Maybe as the next line after the one I mentioned above.
Kurt
Yeaaaaaaaah. It finally worked. You are a genius Kurt. I cannot thank everyone enough who have helped. But kurt, I will get a statue put up in your honour at my school. I cannot thank you enough. You are more than welcome to visit my school (St Paul’s Way Trust school, Mile End, London) and you will be the guest of honour. We have other gadgets we have been working on such as the Robonova and remote control cars, helicopters and planes. Take care everyone
Congratulations! I’m sorry we had an error in the documentation. It certainly didn’t help matters. Thanks for bringing it to our attention so we could fix it.
Kurt, thanks for testing the PowerPod code with Studio. Although the tutorials still point to the older IDE’s, it’s good to know the current Studio will work as well. We will update the tutorial in time.
I’m glad everything worked out ok!
Thanks Jim. Perhaps the tutorials can be updated and a mention made of the problems I had in some sort of trouble shooting section. There is no way I could have sorted out this problem without everyones, particularly Kurt’s help. Look forward to some other project involving Lynx Motion
I am glad it is working for you. If I ever get to London, I may take you up on that 
Kurt
The first problem was you installed the processor backwards. We include a clear image showing the proper way to install it. The second problem was when we updated the tutorial recently we goofed the pin numbers. That has been corrected. The third problem is you were not using our controller. So if a customer does not have the exact equipment we used in our tutorial it has to be dealt with on a case by case basis. If we were to create a troubleshooting guide to cover everything a customer has done wrong in the last 16 years, it would be larger than the tutorial and no one would bother to read it anyway. lol
We do have a troubleshooting guide for serial coms, which is sometimes a pain.
Again I’m glad you got it going. Thanks!
Hiya Jim
I assumed the Bot Board came with the chip installed when I was using it but it transpired that my Science Technician installed the chip without my knowledge when he was working on it first so sorry for any confusion there. I simply meant the problem with the PS2 controller. We all assumed that a Sony PS2 would work fine. A liitle mention that this may cause problems for future customers would save them alot of time but it is only a suggestion. Take care Jim
Well the clarification concerning the PS2 controller was mentioned in the introductory portion of the tutorial. Even before step 1. 