digital inputs: some bad?

[Trav-O]

ok, so I heard a rumor a long time ago that the higher number rc digital inputs have questionable functionality... is this true?

the reason this concerns me is that i'm trying to get signals from my IR board... The board does give signals when you press the corresponding buttons on the remote controller (i've checked with a multimeter) BUT the code doesn't seem to want to register the signals... (btw, there are no code errors. I'VE CHECKED! trust me on this) when we replugged the pwms into digita inputs 1 2 and 3, the switch 1 2 and 3 leds came on, binking when we pressed the remote controller buttons:ahh: so yea...

[ComradeNikolai]

Yes, I believe this is an issue; our team was using digital 15 - 18, and we were only able to utilize three of our commands, and linked it to pin 16 or 17, but thanks to my poor coding, we couldn't figure out which one specifically. However, it did work splendidly for us using pins 1 - 4; see if switching it to different pins, and changing your code, can resolve it.

[Stvn]

The pins need to be defined as digital inputs or digital outputs. I believe that by default pins 9-18 are defined as outputs, and you need to change that in the code.

I don't know what you're programming with, but for WPILib, you can use: #define IN 1
#define OUT 0

void Initialize (void)
{
DefineControllerIO(IN,IN,IN,IN,IN,IN,IN,IN,IN,IN,I N,IN,IN,IN,IN,IN,IN,OUT);
}//end Initialize

[jgannon]

I haven't looked into this all that much, but we plugged the IR board into 15-18, and could not seem to get the buttons associated with 17 or 18 to register in code. We moved the signal connector to 13-16, and it worked just fine. I was busy with a lot of other things, so I chalked it up to either subtle user error or gremlins in the system, but I'm a little surprised to hear that this may be a common occurrence.

EDIT: We definitely set the pins to be inputs. Also, if I remember correctly, the RobotC debugger window wouldn't even display a value for those pins. Bizarre.