It is a problem with the CPU that is on the boards, as in it is an error in the silicone. IFI knows about the problem, as several others and myself have emailed them about this problem. The new libraries are supposed to fix this, but yet we got the same problem at the NJ regionals. Since we did not have a joystick on port 4, I added the following code to Process_Data_From_Master_uP, and to User_Autonomous:
Code:
if (p4_y != 127 || p4_x != 127 || p4_sw_top || p4_sw_trig) {
while (1) { ; }
}
What this will do is cause a code error if there is any data on Joystick 4, as that means the data is all wrong. This helped us catch it one time when it happened again, before the match started
