Cannot image cRIO. Error message 56

[gustavo.goretkin]

When imaging the cRIO from the FRC Imaging utility, we receive error:

Unable to complete operation because of unexpected error 56:
UDP Read in repFPC read packet.vi->SendRebootCmd.vi->RebootSystem.vi->Format Target.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlib:Dialog.vi

We have version 7 of the image. The tool does recognize the cRIO and after the unsucesful imaging, the cRIO's IP address is 0.0.0.0 .

We have tried with the cRIO directly connected to the computer via a crossover cable, or connected to a switch (with no other devices). In all instances, the utility sees the cRIO and we can ping it too. But we always get the above error message.

We will be trying the tool on a new laptop, and hopefully that will resolve the issues. Until then, could anyone provide clarification on what error 56 means? I don't have access to the system right now, but is there anything that would help diagnose the problem? If the serial port output would provide useful information, I can log it to a text file.

We haven't yet tried formating it from MAX. Should we follow the instructions in this post: http://decibel.ni.com/content/message/3360#3360 ?

Thank you,

Gustavo

[Nate.H]

Dear Gustavo,

I do recommend following the instructions in the post that you linked to reformat your controller from MAX. You can find more information about error 56 here:

AE KB 3YTEBIJ8: MAX Error 56 When Communicating With a LabVIEW Real-Time Controller

Please let me know if you can successfully image the cRIO from another computer, or if reformatting from MAX and setting the IP address before imaging works.

Best Regards,

~Nate

NI FIRST Support

[Now_With_Underscores]

If Nate's suggestion does not resolve this issue, try the following steps:

1. Temporarily set your computer's IP configuration to obtain automatically using DHCP.

2. Unplug your cRIO's power and Ethernet

3. Use the orange crossover cable to plug Ethernet port 1 on the cRIO directly into your computer's Ethernet port

4. Look on the front of the cRIO and set the IP Reset and Safe Mode switches to true

5. Plug in the cRIO's power supply

6. Open Measurement and Automation (MAX)

7. On the left side under the 'Configuration' Tab, expand 'Remote Systems'

8. You should see your cRIO.  If your cRIO has two arrows pointing towards an X, your cRIO was not found.

9. Right click on your cRIO and select Format Disk.  This will erase everything on the cRIO

10. Turn off the Safe Mode and IP Reset switches and restart the cRIO by holding the reset button for several seconds

Now follow the normal instructions to update the cRIO-FRC using the updater utility (including configuring IP address and hardware setup).

If you still aren't able to get the cRIO up and running post back with your results.

[nathand]

We had the same problem; switching to a different laptop, running a different version of Windows, fixed the problem.  It seems like under some conditions Windows networking doesn't like to do UDP communications with the IP address 0.0.0.0.  I don't know if this is a firewall issue (disabling the Windows firewall didn't seem to help), or a routing issue (not seeing 0.0.0.0 on the local subnet?), or perhaps I'm completely mistaken about the cause of the problem.

[Jeremy_B]

Hi,

0.0.0.0 is an invalid IP address, the Windows networking stack probably won't even send any packets, and no router (which follows the standards correctly anyway) will route such packets.  You must have an IP address on the 10.x.x.x subnet for it to work, on both your PC and the cRIO.

Regards,

JeremyB
Applications Engineer
National Instruments

[gustavo.goretkin]

Thank you all for the response.

We tried imaging the cRIO from a laptop with a crossover cable and it worked without any hassles. We don't understand clearly what was the issue with the first computer, but we possibly attribute our troubles to a firewall installed on the company computer.

Thanks again.

[nathand]

Unfortunately we don't have a choice in the 0.0.0.0 IP address - when the imaging tool formats the drive, it sets the RIO's IP to 0.0.0.0.

[Jeremy_B]

When the cRIO is formatted, the IP address will be 0.0.0.0.  However, the imaging tool will then set the IP address to the given address.  It does this by sending a broadcast (255.255.255.255), containing the IP address the cRIO should assign.  The cRIO also communicates via broadcast until it receives an IP address.  This is the reason why you have to be on the same subnet as the cRIO to configure it, routers usually don't forward broadcast packets (otherwise you could flood the entire internet).  Make sure you configure it with a crossover cable, and it should work fine.

Regards,

JeremyB
Applications Engineer
National Instruments

[Nick_Luther]

Hello all,

We have a cRIO-FRC, PN 192172F-03L.  It's from either the 2009 or 2010 FRC season.  We tried to use the FRC cRIO Imaging Tool to program it but received error 56. We were able to successfully ping the controller, so the network configuration looked good, but we were still getting the error.

We tried to follow NI KB 3YTEBIJ8 but could not see the controller in MAX.  We also tried the IP Reset / Safe Mode procedure hoping that MAX would see the controller, but it still didn't.  We have also tried programming from safe mode with the FRC cRIO Imaging Tool.  In all cases, we either can't see the controller or get error 56.

We are using a crossover cable, but have also tried straight through.  We see the power LED come on and the status LED blink.  The status LED is currently on a single blink, though that may have changed during our troubleshooting process.

Does anyone have any ideas for this situation?

Thanks,

Nick

[MegaHertz]

Hi Nick,

Sorry to see you're having trouble with this. As seen in the "Why is the Status Light on My CompactRIO Controller Flashing?" KB, the single flash of the status LED just indicates that the controller is unconfigured. This shouldn't be cause for concern.

If the controller isn't even appearing in MAX, I'd have to suspect there's something odd with the network or firewall settings on the computer you're using. This "Why Does My CompactRIO Controller Not Show Up in MAX?" KB is a fantastic checklist you can go through to try and troubleshoot this problem. Please let us know if you have any luck.

Andy H.

Applications Engineer

National Instruments