FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

I have lost communications with the cRIO controller

HELP - HELP

I just updated my LabVIEW with the Update 2 download.

That went fine and I tested some programs ok.

Then, I tried to install the new image for the cRIO.  Somewhere I made a mistake and now I cannot communicate with the cRIO.

I tried moving ethernet cables which did not help.

I have them back to:

The cable from the laptop goes to the Driver Station, ETH1

The cable from the DS ETH2 port goes to the Ethernet 1 port on the Linksys for the DS

No changes were made to the cables on the cRIO.

Now, when I start the CompactRIO Imaging tool it finds a MAC address with an IP address of: 0.0.0.0

I select LabVIEW

Check the format Controller

Select the new image

Enter FRC-cRIO-1918

Enter team 1918

Click on "Apply"

The Reconfiguring Device window pops up with:

Extracting CompactRIO ...

Connecting ...

Formating...

Then it puts up a box with:

Unable to complete operation because of unexpected error 60:

UDP Open in repFPC open

connection.vi-SetTargetConfig.vi->Set IP Address.vi->

ConfigUtility.lvlib:SetIPAddrAndGetInfo.vi->

ConfigUtility.lvlib:ReImageTarget.vi->

ConfigUtility.lvlib:Dialog.vi

PLEASE, what do I do now?

Thanks

0 Kudos
Message 1 of 3
(7,251 Views)

All I did was turn everything off.

Pray for 1/2 hour.

Turn it on and repeat the steps required.

My system is now back up and working fine.

0 Kudos
Message 2 of 3
(2,864 Views)

RobotMan,

My first guess was your cRIO was in IP Reset when you were formatting the controller.  IP reset is controlled by dip switch 3 being in the "On" position during boot up; this forces the controller to take the IP address of 0.0.0.0.  Unfortunately when I attempted to format a cRIO-FRC with IP reset enabled I received a different (and more descriptive) error message.  It is also possible this error is due to a firewall or another setting we are over looking. 

Since waiting (and praying ) seems to have fixed the problem it might have been simply a fluke problem, but if the behavior occurs again please post back and we will continue to investigate. 

Cheers,

Mark

Mark
NI App Software R&D
0 Kudos
Message 3 of 3
(2,864 Views)