loss of comm at deployment of lvproj

[Integral]

This system has been working fine through out build season. Last night (this morning !) we began to encounter this loss of comm error. We get the error with our current code, with a fresh project, wireless and wired as well as from our laptop or the driver station. Attempts to format the Crio resulted in a error 56. Help!

[Doug_Norman]

In case you aren't getting the message from this error - here is an easy way in LabVIEW.  On the front panel of a blank VI, right-click and go to the Array, Matrix & Cluster palette and choose Error In 3D.ctl and drop it on the front panel.  Type in your error number "56", then right-click on the number and choose "Explain Warning" (or "Explain Error" if the Status is a red X).  Your error message is "The network operation exceeded the user-specified or system time limit."  Basically you have a network problem.  Here are things I can think to try:

1. Replace, or check all your network cables.  Swap them around, giggle them etc.

2. Make sure you are using crossover network cables where needed - if connecting directly to the cRIO etc.

3. On the classmate you may need to disable the wireless network - some teams have had trouble with this.

4. On the Driver Station, make sure you have entered your team number, and that it shows in the DS.

5. On the classmate, go into the network settings and make sure your network is set to what you expect (team number as part of the IP)

6. Make sure evrything has power - I've had this trouble when my gaming adapter lost power.

[nathand]

When does this error occur - when you're first attempting to connect/deploy code, or after you've already started running the code?  Do you have a startup application deployed on the cRIO?  If you're seeing the error when you try to download code, and you do have a startup application deployed, it is possible that the startup application is taking too much CPU time on your cRIO, preventing LabVIEW from establishing a connection.  This could also lead to a failure to connect, and an error 56, from the cRIO Imaging Tool.  If this is the case, try setting the "Disable App" DIP switch on the cRIO, reboot, then attempt to connect.  Be careful - the DIP switches need only a gentle push, they do not slide.

[jonathan_b]

Thank for the info.  I hope this works.  Our CRIO doesn't have a "Disable APP" sw but rather "No APP" switch which I think is equivalent.  What say you?

[jonathan_b]

Thank you nathand.  We followed your advise and set the CRIO dip sw to "No APP".   We were then able to deploy our code from our Laptop wirelessly on the first attempt.

Thanks again.  This problem was a big time waster, but now it's behind us.

[Integral]

Thank you very much. You nailed our proplem exactly. We are now up and running and a bit more aware of what we d/l to the the cRio.