|
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.
|