Quote:
Originally Posted by Alan Anderson
I got a balky 8-slot cRIO to accept code today by turning on the NO APP switch before rebooting it. I'm not sure what's keeping it from responding properly otherwise, but I'm confident I'll figure it out soon, and I expect it'll be something simple.
|
We turned on the NO APP switch and found out that we could no longer download or run code on the robot. We recieved the following error:
NI-system configuration(hex 0x80004003) required ponter parameter was null
No other switches on the CRIO are on, save for the Console Out switch, which has been on for as long as I can remember. Should we set that to off and try again?
Quote:
Originally Posted by Doug Norman
Is this also true if you build and deploy the basic robot code before you make any edits? I'm wondering if a loop with no time delay could be starving other loops?
|
We edited the Begin VI in the basic robot code to accomodate a 4-motor drivetrain. Other than that, no edits were made.