|
|
|
 If people really want to see "better" refereeing, they should see what they can do to help FIRST make better. - petek [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| If people really want to see "better" refereeing, they should see what they can do to help FIRST make better. - petek [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
27-01-2010, 22:28
|
|||
|
|||
|
Re: cRIO output problem
We found the problem. Remember the enable switch from last year? Turns out the stop button didn't replace it. They just hid the switch inside the DS code. Turns out the robot was disabled. We didn't notice since we had no reason to run the DS program in the Developer account.
Although theoretically, inputs should have worked all along. Apparently there was another problem. 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| cRio problem | specs101kid | Programming | 4 | 21-01-2010 16:19 |
| Problem receiving console output from cRIO | Arborama | Programming | 7 | 15-02-2009 03:30 |
| cRIO output files | aoconnor | Programming | 2 | 09-02-2009 17:59 |
| cRIO Problem | Pneumaticsman | NI LabVIEW | 8 | 10-01-2009 11:59 |
| cRIO/Driver Station output to laptop | smcmahon | FRC Control System | 3 | 14-12-2008 13:51 |
Threaded Mode