Help On Coding 2K1 Controller

[GregTheGreat]

Originally Posted by Sachiel7

You might have bad joysticks. Unplug the connector to ensure all the pins are lined up right, and make sure it's plugged in all the way. If it is, then hook it up to a PC and setup a 3axis 2-button (I'm guessing you're using the joysticks from the kit) joystick. Test it's buttons. That *may* solve your problem. If it works on your PC, a few quick questions/points:
-Your OI connection might be bad...
- Which version of PBasic are you using?
- Are you using a y-cord?

Just to name a few. A list of your control setup might help. But as stated before, I think it's a problem with your inputs, not the programming.

Oh, how I wish it was something easy like bad joysticks.... (Then i could just get new ones)

I will give you the 411 on what I know....

The joysticks all work on port 2 and 4.... I ran button checks on the computer and through the dashboard viewer and all the axies work. The problem is just in my buttons on OI port 1 and 3.... I find it somewhat odd that the number on which the problem I am having trouble on are both odd ports.... Now heres the real kicker..... I am using the 2.0 software as well as the 2.0 default program.... I was tempted to run the 2003 default software but I didn't know if it was compadable. It is not hardware and I dought their is a problem in the OI someware... Remember if their is a problem at a match the first thing that is looked at in detail is the programming.... I still think their is a problem in my coding.... seeing as it is just the button on the odd # ports.... and since thats how in the end the ports are split up for the relay's.

If you have in more ideas they would greatly help....

Thanks For The Help All,

-Greg The Great

[Dave Flowerday]

Originally Posted by GregTheGreat

The joysticks all work on port 2 and 4.... I ran button checks on the computer and through the dashboard viewer and all the axies work. The problem is just in my buttons on OI port 1 and 3.... I find it somewhat odd that the number on which the problem I am having trouble on are both odd ports....

Are the "disable" DIP switches set correctly on your OI? See page 17 of this document. Quote: "The DISABLE dipswitch is used to disable buttons on joysticks connected to PORT 1 and PORT 3."

[GregTheGreat]

Originally Posted by Dave Flowerday

Are the "disable" DIP switches set correctly on your OI? See page 17 of this document. Quote: "The DISABLE dipswitch is used to disable buttons on joysticks connected to PORT 1 and PORT 3."

Thank You VERY MUCH! This was the problem... Thanks Again...

-Greg The Great

[Steve Shade]

Greg:

Check the OI to make sure the Disable Dipswitches are not enabled. These switches disable the switch inputs on ports 1 and 3 and reassign these inputs to ports 2 and 4. See page 17 of the old Operator Interface Reference Guide for more information. If you can't find the guide online send me an e-mail or pm with your e-mail and I'll send it your way.

Steve

[Mike Soukup]

Originally Posted by GregTheGreat

Now heres the real kicker..... I am using the 2.0 software as well as the 2.0 default program.... I was tempted to run the 2003 default software but I didn't know if it was compadable.

Yes, you can use the new editor / tokernizer and the new code with an older controller. We used either the 2002 or 2001 controller with our prototype robot and the exact same code as our real robot this year and we did not have any problems with it. It worked exactly like the 2003 controller.

As you mentioned, it's odd that the problem is only on ports 1 & 3. Both of those are read in and stored in 'oi_swA' so that's the first place to look. I've fogotten some of the common coding problems in the old controller, but the ones I remember - telling the controller you want to grab the byte from the stream, and actually including the byte in the stream - look good. Try printing out 'oi_swA' immediately after it's read in from the data stream.

[GregTheGreat]

Allright I will try all of this fun stuff tonight, seeing as I am at school right now... I believe you might be right about the disable dip-switches seeing as my # is on 000 right now...

Thanks,

-Greg The Great