Labview Deployment Issues

[nez51]

Throughout the season our team has had lots of issues when deploying code to the roborio. The building process of the code is completely fine however when we deploy code to the robot it will fail multiple times in a row before we achieve a successful deploy. This process takes around 20 min. Is anyone else experiencing these issues and if so have you found a solution?

[Ari423]

We have used LabVIEW with the RoboRIO all season and haven't had a problem with it. When we go to deploy code it just asks if we want to overwrite the existing code then deploys.

Some things to try might be reflashing the RoboRIO, reinstalling LabVIEW and the FRC add-ons, or deploying a new project to see if the problem is within the project. Knowing your team's quality, I would assume you checked that you aren't using a bad Ethernet cable, but I'm going to suggest it just in case you didn't. I really don't know anything about the problem for sure, but that is where I would start if I were in your shoes. Perhaps if you posted more detailed error codes, logs, or descriptions someone could better help you fix your problem.

[Greg McKaskle]

Before reflashing things, I'd try other network options and see if that is the root of the problem.

First, I'd connect roboRIO and computer via USB cable and see if the deploy behaves the same or better. Then try ethernet, and then try wifi. The deploy code may not like having lots of interruptions or having to restart the connection mid-deploy, and this may happen sometimes, especially with wifi in a school environment.

Greg McKaskle

[Ari423]

Originally Posted by Greg McKaskle

Before reflashing things, I'd try other network options and see if that is the root of the problem.

It didn't even cross my mind that they might not be using Ethernet. We always deploy over Ethernet because once a few years ago something got messed up when deploying over WiFi and it messed up the cRIO. Eventually it was fixed, but it was a pain and we vowed to always tether when deploying.

Actually, you probably shouldn't reflash the RoboRIO while you are having this problem because if a flash is interrupted it can cause serious problems with the RoboRIO (we've only experienced this with the cRIO but I assume it is the same).

[nez51]

Thanks for some of the assistance everyone however the issue still continues to happen that whenever code is deployed we get the error message cannot deploy target settings and that connection has been lost. This issue persists on all of our programmer's computers and we have already re imaged some of our spare robo rios as well as have made sure that all connections and the way that we are deploying code is correct. Even if a blank project is being deployed the deploy will still most likely fail. However, after I turned off the ni real time startup app through the browser interface I was able to get a successful deploy every single time however the ni real time startup app needs to be enabled considering it is pretty much the bread and butter of being able to run the code. If anyone is familiar with this issue we would greatly appreciate help. Thanks.

[Joe Ross]

If you disable the RT startup app and then deploy a blank project, can you successfully deploy again? If so, I suspect in your robot code, you have the problem described here (or something similar): http://wpilib.screenstepslive.com/s/...from-bad-loops

[nez51]

We have tried all of the things recommended in this discussion and still are not able to successfully deploy to the robot every time we try. (Code deploys correctly occasionally). Even after imaging the roborio as well as restarting the RT startup app this issue still exists. I know this is something that is very unheard of however if any of you have any other ideas it would be greatly appreciated. We also believe this is not a connection issue such as Ethernet,usb, or wifi although the issue states that it is waiting for a response from the target.