Problems Imaging the cRIO

[rhoads2234]

Hi everybody,

We are unable to image the cRIO. When we try to, it says "The specified IP address is unreachable. Ensure that the IP address is on the correct subnet."

We've tried to reformat, but that ran for over half an hour. We can ping the port on the cRio, and the Computer we are downloading from has the IP address of 10.22.34.6 with a subnet mask of 255.0.0.0

We are trying to reimage with v19, and are coding in Java(And checking that box on the Reimage tool.)

Thank you in advance!
Team 2234

EDIT: We were able to download and reimage with another computer, but we don't get voltage readings on the Driver Station. When we try to run the code, the jaguars continue blinking, as if they have not been initialized.

Any ideas?

[apalrd]

Similar problem.
We are using LabVIEW and tried two computers, both got the same error.
We tried puting the cRio in Safe Mode, running the imaging tool and formatting it, turning safe mode off and imaging it, and that worked... better. It failed while uploading the configuration file.


We have not yet found a solution

[Jon236]

Hmmmmmm.....an epidemic? Same issue here....had to leave school before the reformatting was done. Will try again tomorrow.

[timytamy]

Try reimaging the Crio with the classmate (should have an ip of 10.XX.YY.5) but make sure you have the latest update installed.

Thanks,
timytamy

[apalrd]

We tried first on the Classmate after installing the updates and rebooting. Then we tried another laptop.

[Greg McKaskle]

Generally, my advice is to simplify the network as much as possible. Eliminate switches, other network connections, turn off firewall (completely off), turn off wireless network and any other types of IP. Just for grins, stop apps that don't need to be running.

Greg McKaskle

[apalrd]

No other networking. Direct connection.
After we turned on safe mode and formatted the cRio, it progressed further in the imaging process and then when uploading the configuration files it got an error... forgot the number but it involved timeout on reboot

[gvarndell]

Not that there's a real answer in the other thread, just a happy ending, but I think this thread is the same problem as this other thread, isn't it?

http://www.chiefdelphi.com/forums/sh...threadid=80441

[BLProgram2010]

We're use Labview. Every time we develop new code and try to deploy it or connect to the cRIO, there a error that says the vi's in the start up application will not open and will remain closed if you continue to apply and deploy. I found out the by using the 'cRIO Imaging Tool' and hitting 'Format controler', the pproblem is removed and we can deploy the code and run a drive test. But when we switch users back into the developer the same problem occurs and the cRIO needs to be re-imaged again. Running the 'cRIO imaging tool' with the format controler takes about seven minutes to finish; and ontop of that we still need to deploy and build the code which take another five to seven minutes. We seem to be spending a lot of time re-reimaging the cRIO to fix our problem. How do we fix it?

[Alan Anderson]

Originally Posted by BLProgram2010

We're use Labview. Every time we develop new code and try to deploy it or connect to the cRIO, there a error that says the vi's in the start up application will not open and will remain closed if you continue to apply and deploy....

Can you copy and paste the exact error message you're getting? What you're describing sounds very similar to an informational message that isn't an error, but before I give any advice I'd like to see what you see.

[PriyankP]

Originally Posted by rhoads2234

we don't get voltage readings on the Driver Station.
Any ideas?

To receive the battery voltage readings, you need to power up the Analog Breakout attached to one of the cRio modules. + and - from the Analog Breakout go to the Power distribution board and use a 20 amps breaker.


THere is no additional code required to get the battery power readings.

~ Priyank

[Mark McLeod]

Originally Posted by BLProgram2010

We're use Labview. Every time we develop new code and try to deploy it or connect to the cRIO, there a error that says the vi's in the start up application will not open and will remain closed if you continue to apply and deploy. I found out the by using the 'cRIO Imaging Tool' and hitting 'Format controler', the pproblem is removed and we can deploy the code and run a drive test. But when we switch users back into the developer the same problem occurs and the cRIO needs to be re-imaged again. Running the 'cRIO imaging tool' with the format controler takes about seven minutes to finish; and ontop of that we still need to deploy and build the code which take another five to seven minutes. We seem to be spending a lot of time re-reimaging the cRIO to fix our problem. How do we fix it?

Next time that happens just click okay and let it continue to see what happens.

[BLProgram2010]

When we try to connect/deploy to the cRIO in developer labview we get this message:
'This VI is part of a Real-Time Startup Application. All VIs on the target will be closed if you choose to apply and continue with deployment.'

The message also highlight the VIs- Auto. Independent; Robot Main; Send Image to PC; Async VI Agent; Acquire Image; HandleRuntimeErrors.

How Do we fix it and stop re-reimaging with the imaging tool with formatting controller everytime?

[Mark McLeod]

That's just a message you can safely ignore.
We all do.

It's just warning you that you're replacing the code that's already on the cRIO, but isn't that what you want to do?

[BLProgram2010]

It was an 'ID 10 T-Error'
Thank you so much