Errors on LabVIEW

[FRC2476]

We are also getting error 44085--it appeared seemingly spontaneously and we can no longer run any programs.

We have version 3.0A of Crio and v11 of the controller. Any ideas as to what we can do specifically??

any response would be much appreciated.

[Alan Anderson]

Originally Posted by FRC2476

We have version 3.0A of Crio and v11 of the controller. Any ideas as to what we can do specifically??

Specifically, you can help us figure out what you're referring to. I'd usually consider the cRIO and "the controller" to be the same thing.

There are three or four things that you need to keep updated properly. First is the LabVIEW environment on your programming computer (that should be Update 3.0a). Second is the cRIO image (v11), which gets installed along with the LabVIEW update. Third is the Driver Station firmware (2009-01-22c1). I'm not keeping track of the the WindRiver libraries myself, since I'm focusing on LabVIEW, but you need to keep it up-to-date as well if you intend to use C++ for programming.

[Jon236]

When re-imaging with 3.0a and ver 11, I keep getting an 'error 56'. Any idea of what that is?

It had been running well up to this point.

[Greg McKaskle]

56 is a timeout on a network operation. Simplify the network connection and see if that helps.

To get quick explanation of errors, you can use Help>>Explain Error, or you can usually right click on an error control and Explain...

Greg McKaskle

[Jon236]

Originally Posted by Greg McKaskle

56 is a timeout on a network operation. Simplify the network connection and see if that helps.


Greg McKaskle

All I had was a crossover cable from the laptop to the cRio

[Mark McLeod]

Try running through the DS, using it as a switch. e.g., PC to DS to cRIO wired directly. Sometimes using a switch as an intermediary smooths communications.

[Greg McKaskle]

Make sure to disable firewalls, and perhaps try on a different computer.

Greg McKaskle

[Alan Anderson]

Originally Posted by Greg McKaskle

56 is a timeout on a network operation.

One thing that might point to is a mismatch in the network addressing. Make sure your computer's IP address and mask are what they should be (10.2.36.6/255.255.255.0), and that the cRIO Imaging Tool is being told the correct team number (236). You could also get away with using 255.0.0.0 for the network mask.