cRIO v20 Update Problems

[PaulRevere]

Today we had an interesting issue crop up with our cRIO. While attempting to get our camera working, I realized that out Driver Station and Development machines were out of date. So I updated our DS with the 1.1 update. Then I upgraded our development machine with the LabVIEW for FRC 2.1 Update. Once that was completed, I updated WPILibJ in NetBeans. (We are using Java for FRC.) Next, using our development machine, I formatted and imaged our cRIO with v20. (It was on v19). I then went into NetBeans and did a Clean and Compile of our robot’s code. It compiled, but when I tried to deploy it, Ant threw an exception stating that the file update.xml claimed there was a mismatch between our cRIO’s OS Version, and the one it wanted. I was unsure of the cause of this, but after looking at the file in question with Notepad, there indeed was a line that claimed v19 was needed. So I said “what the heck, let’s try changing it to v20 and see if it works.” So I changed v19 to v20, saved, and attempted a deploy in NetBeans. Sure enough, it worked fine, camera code included!

On a side note, during the 3+ hours of troubleshooting this issue, I downgraded our cRIO from v20 to v19 without editing the XML file. It would compile, and begin to deploy, but would get the stage just before the cRIO was to be rebooted. Just before it reached there, the cRIO’s FTP server crashed out for no apparent reason. I used a program called WireShark to capture the raw network packets going over our robot’s network, and everything appeared fine until that step, where the FTP server just stopped responding to my machine. (My machine was literally spamming the cRIO with FTP packets, and the cRIO just sat there, not even replying.) Oddly enough, I could still mount the FTP share MS-DOS (Even after it said the server had crashed. As soon as I pinged the cRIO, or did an FTP mount is DOS, the traffic in WireShark would resume, but NetBeans was still throwing, “Waiting for OTA Server…”)

If someone could let the WPILibJ team know of this issue, it’d be good. Hopefully if anyone else has this issue, this post will offer some insight. If anyone would find the packet capture dumps useful, I can post a ZIP Archive of them.

[JasonStern]

This information was very helpful. Thank you for sharing it!

[PaulRevere]

yea, no problem. I also noticed while going though the packet captures that a lot of the different components love to announce random UPnP events. I'd say roughly 25% of what I captured was not even robot traffic, but useless stuff like Windows SMB File sharing announcements from the DS and Dev. machine. There was also random DNS traffic that was either broadcast on the entire subnet (as in sent to 10.31.83.255)or was directed at some random machine that had an Internet IP address (I don't remember the address, and the machine is back at our shop.)

[Daniel Jones]

There is a new java update available which should fix this issue. Make sure that the update site in NetBeans is set to http://first.wpi.edu/FRC/java/netbea...te/updates.xml
This update also includes support for the KOP I2C Accelerometer.
Note that this will not work with previous images, so you must image the CRio with the v20 image to use this update.

[Twisted eric]

I am having that problem i have read what you guys have posted but I can't figure out what to do pleas put into simple terms because we did not have this problem last year.

[BradAMiller]

Originally Posted by Twisted eric

I am having that problem i have read what you guys have posted but I can't figure out what to do pleas put into simple terms because we did not have this problem last year.

You can keep your copy of NetBeans current in one of two ways:
1. The easiest and best works if your development system is connected to the Internet. You should follow the directions in the "Getting Started with Java" document. But basically, start NetBeans, select Tools -> Plugins. In the "Settings" tab be sure that there is an Update Center listed (left pane) that has a URL of "http://first.wpi.edu/FRC/java/netbeans/update/updates.xml". In my case, it's called "FRC Tools" in the left window - you can call it anything you'd like. If you just added the WPILib update center for the first time, look at the "Available Plugins" tab and check everything starting with FRC (there will be 5 plugins). Then click install. If you are just updating, look in the "Updates" tab, check, and install all the FRC plugins that are listed.

2. If you are not connected to the Internet, you must go to a machine that is on the Internet and go to the URL:
http://first.wpi.edu/FRC/java/netbeans/update
and copy all the .NBM files onto some removable storage, like a USB flash drive. Plug the flash drive into your development computer. In NetBeans, go to the "Tools->Plugins" window and select the "Downloaded" tab. Click "Add Plugins..." and select the location where the .NBM files are located. Select all the files and click "Install".

Either of these techniques will update your system to the current version of the NetBeans plugins. The current version requires the V20 image file that installs with the most recent NI LabVIEW update.

[Twisted eric]

Thanks it helped a lot.

good luck everybody

[1168Programmer]

We are having the exact same problem. We are updating from the correct address and have done everything previously posted and still nothing works. Has anyone gotten the cRIO to work? Does anyone have any other suggestions?

[1168Programmer]

We have the same exact problem. We are updating from the correct address and have done all the steps posted above and our cRIO still doesn't work. Has anyone gotten their cRIO to work? If so, how? Is there anything that can be done that hasn't already been posted?

Thanks in advance

[1168Programmer]

As an addition, the output that we are seeing when we try to upload the code to the cRIO is as follows:

...
Connecting FTP @10.11.68.2
upgrade:
Sending local file image.suite
flashapp:
deploy:
init:
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 11s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 12s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 13s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 14s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 15s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 16s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 17s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 18s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 19s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 20s
...

and it will continue to print the "waiting to connect to OTA command server" line until we halt it.

Any help is appreciated.

[urg8rb8]

Originally Posted by 1168Programmer

As an addition, the output that we are seeing when we try to upload the code to the cRIO is as follows:

...
Connecting FTP @10.11.68.2
upgrade:
Sending local file image.suite
flashapp:
deploy:
init:
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 11s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 12s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 13s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 14s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 15s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 16s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 17s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 18s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 19s
Waiting to connect to OTA command server of 10.11.68.2:8001 for past 20s
...

and it will continue to print the "waiting to connect to OTA command server" line until we halt it.

Any help is appreciated.

I had this exact same problem today after I reformatted and programmed the crio with v20. The only thing I did was reboot the crio to "fix" the problem. I have not seen that problem again since.

[1168Programmer]

Originally Posted by urg8rb8

I had this exact same problem today after I reformatted and programmed the crio with v20. The only thing I did was reboot the crio to "fix" the problem. I have not seen that problem again since.

Thanks for the response.

I have tried power cycling the cRIO and using the reset button - neither of those actions solved the problem. Is there anything else that we can try?

Thank you.

[urg8rb8]

Originally Posted by 1168Programmer

Thanks for the response.

I have tried power cycling the cRIO and using the reset button - neither of those actions solved the problem. Is there anything else that we can try?

Thank you.

Try reformatting the crio and programming it with v20. Are you using 802.11 to program the crio? Or are you using an ethernet cable?

[1168Programmer]

Originally Posted by urg8rb8

Try reformatting the crio and programming it with v20. Are you using 802.11 to program the crio? Or are you using an either cable?

We are using an ethernet crossover cable for programming. We have already reimaged the cRIO twice with v20, but I suppose it can't hurt to try again. I don't have access to the robot until tomorrow though.

Thanks again.

EDIT: Any other ideas on what could be causing this or how to fix it?

[urg8rb8]

Originally Posted by 1168Programmer

We are using an ethernet crossover cable for programming. We have already reimaged the cRIO twice with v20, but I suppose it can't hurt to try again. I don't have access to the robot until tomorrow though.

Thanks again.

EDIT: Any other ideas on what could be causing this or how to fix it?

Did you also reformat the crio when you reimaged it? I'm also assuming that you ran the latest updates for the DS and LabView? I can't think of anything else at the moment. Try reformatting/reimaging of the crio and tell us what happens.