Quote:
Originally Posted by Mark McLeod
Your description sounds like the NO APP switch isn't getting set properly.
To use the NO APP switch: - flip it to ON
- reset the cRIO (3 equivalent ways)
- cRIO panel black reset button
- DS Diagnostics->Robot reboot...
- cycle power
- After the DS Comm light comes back on, then you can flip the NO APP switch back OFF. You don't have to though until you want the user code to startup automatically.
If you get the NO APP switch working, then you can move on to discovering why you have to use it in the first place.
Usually, it's only necessary if your code is running too fast and hard. There are ways to check on that. |
I have read in other threads about the System Manager. While the NO APP switch has been ON (and I have cycled power), I have attempted to deploy. I have run the System Manager and observed that the CPU is occupied approximately 10-15% while data is being transferred between my laptop and the cRIO target. The VIs are still being uploaded to the CRIO at its crawling rate.
My friend has deployed the exact same code I have been trying to deploy the whole time with his laptop to the same cRIO, with the "NO APP" dip switch OFF. I believe the problem resides with my laptop hardware (or software on my computer, perhaps LabVIEW), not with the cRIO or with my code.
I have read through a few CD threads on deployment issues, and I believe this is a unique issue, as it hasn't been resolved (as far as I can tell) with the "NO APP" dip switch.