Java to Crio Downloading Issues

[Patrick Chiang]

Originally Posted by matthysen2

I have had this same problem aswell. When you say restart do you mean pressing the button on the or cutting the power off and then turning it back on? And should this be done while the code is trying to run?

It's a known bug since last year.

SOP for flashing/updating the crio:
1. Flash it
2. Upload code
3. Reboot the crio
4. Pretend nothing happened and upload code
5. Success.

[bdbayes]

Glad to hear it works. You should try some of the examples.

[leeboy1312]

We are having a similiar problem when we try to deploy the code onto the CRio the program stops without a build error at

[cRIO] Default disabled() method running, consider providing your own
[cRIO] task 0x25c7a58 (System Web Services Load Thread) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2869f70 (mDNS resolve) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2bff0d0 (mDNS resolve) deleted: errno=0 (0) status=0 (0)


I have tried almost everything i can think of so any help would be strongly appreciated.

Thanks,
F.I.R.S.T. Team #4021

[bdbayes]

That is displayed whenever you finish deploying the code.

[touchdownjesus4]

Originally Posted by leeboy1312

We are having a similiar problem when we try to deploy the code onto the CRio the program stops without a build error at

[cRIO] Default disabled() method running, consider providing your own
[cRIO] task 0x25c7a58 (System Web Services Load Thread) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2869f70 (mDNS resolve) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2bff0d0 (mDNS resolve) deleted: errno=0 (0) status=0 (0)


I have tried almost everything i can think of so any help would be strongly appreciated.

Thanks,
F.I.R.S.T. Team #4021

This same thing happens when I deploy code to our cRIO. It gets to the mDNS resolve and hangs. I've found that if you just stop the process it deploys the code correctly, it just seems to get hung up after its finished deploying for some reason. It says that there is robot code when we switch to the driver station and any changes we make work even though it hangs.

[derekwhite]

The deploy process is not supposed to "finish". It stays connected to your robot in order to display any output that your robot or the cRIO prints out.

This message is printed by WPILibJ if you haven't overridden the disabled() method (which isn't a requirement by the way):

[cRIO] Default disabled() method running, consider providing your own

If you see that message, then it's very likely that your robot code is running fine.

This message is printed by the cRIO for some reason. I think it is an ordinary status message though, not any real problem:

[cRIO] task 0x25c7a58 (System Web Services Load Thread) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2869f70 (mDNS resolve) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2bff0d0 (mDNS resolve) deleted: errno=0 (0) status=0 (0)

For your own sanity and/or peace of mind, you might want to print a message at the beginning and end of your disabled(), autonomous() and operatorControl() methods - something like "entering autonomous mode", "exiting autonomous mode", etc.

[jesusrambo]

Correct, reimaging the cRIO should solve the versioning error.

[austin1743]

thanks, i will do this first thing before we do anything else.

i will keep you guys informed more tomorrow. Time for some sleep in this robotics season before crunch time.

[jesusrambo]

Originally Posted by austin1743

Time for some sleep in this robotics season before crunch time.

You kidding? That's what the Mountain Dew is for

[austin1743]

no im not kidding, hehe stocking up on mountain dew now... hehe crunch time starts in the final week

how long does this cRio imaging process take? before it only took us a couple minutes...

[Patrick Chiang]

Originally Posted by austin1743

how long does this cRio imaging process take? before it only took us a couple minutes...

Up to 5 minutes. Shouldn't take any longer than that.

[austin1743]

we have been imaging for 2 hours now.... continues to say formating cRio...

i dont think this is normal...

[Patrick Chiang]

Something is definitely wrong if it's taking more than an hour. Try connecting back to the cRio. If you can't connect back to it, then it's somewhat likely that it's bricked. If you can connect back to it, try the re-image thing again.

My only three guesses for what possibly happened is:
1. You were flashing it thru a wireless connection?
2. The cRio lost power midway through formatting?
3. The cRio was faulty?

[austin1743]

well i got it to the right image... (by doing what you said)

our next problem is no robot communication... for this is i:


cycled power
reimaged it 2 times
checked to make sure ip addresss set-up correctly (they are)
made sure ethernet cord is properly attached (wired connection entire time)

any other suggestions?

[jesusrambo]

Both IP addresses? Are you able to ping it?

Did you image it with the right IP address?

Are it and your computer on the same IP range (10.xx.yy.zz where xx and yy make your team number), with the computer's subnet set to 255.255.255.0?