FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Recieve error 60 when imaging

This is the message I get when I try to image:

"Unable to complete operation because of unexpected error 60:

UDP Open in repFPC open connection.vi->SendRebootCmd.vi->RebootSystem.vi->Format Target.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlib:Dialog.vi"

Not sure exactly what the hang up is, but it appears to effect my ability to communicate with the cRIO.

0 Kudos
Message 1 of 12
(11,204 Views)

Also, the device name keeps being changed to temp rather that the name provided.

0 Kudos
Message 2 of 12
(3,799 Views)

Hi k4molo,

Are any of the white dip switches on the cRIO flipped?

Are any of the LED flashing?

At what point in the imaging process does this error pop up at? That is, what was the last step being shown in the Reconfiguring cRIO window before you get the error?

0 Kudos
Message 3 of 12
(3,799 Views)

This type of error usually occurs when there is in fact some type of networking hiccup.  If your configuration is wireless to the cRIO, you may want to try directly wiring it.  It is normal for the device to get named "temp" during the imaging process.  The "temp" name will change if it completes successfully.

0 Kudos
Message 4 of 12
(3,799 Views)

1. All dips are in off position.  I have reset ip and gone safe a few time to try imaging again.  All dips returned to off prior.

2. Port 1 leds show steady green, flashing amber.  power steady green. status shows amber two-blinks, pause, two-blink...

3. The error occurs after formating.  When accessed next the IP address is updated appropriately, but the device name is set to 'temp."

It appears there's a comm failure after changing the IP address...something to do with UDP?

I have downloaded the update again, in case it was corrupted in transfer and have turned off firewall and virus protection..

0 Kudos
Message 5 of 12
(3,799 Views)

I'm connected hardline w/ a crossover cable, no other net connection active.

0 Kudos
Message 6 of 12
(3,799 Views)

Hi k4molo,

Have you installed the LabVIEW update?

Can you check the ends of the crossover cable and make sure the wire colours are not in the same order on either end?

What is the IP address of your computer?

0 Kudos
Message 7 of 12
(3,799 Views)

update was downloaded, installed...no luck...uninstalled, reinstalled...no luck...downloaded (again), installed...no luck (yes, I used the latest serial number)

crossover end 1:OW-O-BlW-Bl-GW-G-BrW-B   end 2: GW-G-OW-Bl-BlW-O-BrW-B

static ip: 10.6.53.6 subnet 255.0.0.0

0 Kudos
Message 8 of 12
(3,799 Views)

Hi k4molo,

The wiring configuration that I am familiar with for crossover cables is the following,

crossover cable.JPG

where side A is the normal configuration for the T-568B standard and side B being the crossover end. I've had success using crossover cables with this configuration. Is there any chance of you getting a crossover cable with this configuration and giving it another shot? I'm not sure if this will make a huge difference, but it's worth a shot. Let me know how it goes.

Aaron

0 Kudos
Message 9 of 12
(3,799 Views)

cable configuration diagram matches what I'm using.  Continuity check ok.  Have been working on possible issues associated with trusted network settings for 10.xx.yy.1 thru 6, but so far, unsuccessful.

0 Kudos
Message 10 of 12
(3,799 Views)