Long deployment time.

[EvanA]

Whenever we deploy code from robot main it takes an excessively long time. We're talking like 10 to 15 minutes do finish deployment. This never happened with last year's code and we don't have near as much in our current project. Obviously, this is a huge inconvenience when testing new code and our mentor gets inpatient. Is there something we can do to speed this up?

[Alan Anderson]

Suffer through it once, and the subsequent deployments are much faster. It only needs to copy over any vi that has changed since the last deployment. It's annoying, but it's a one-time annoyance when you start a programming session.

I do agree that it's taking a lot longer to run Robot Main this year than it did last year.

[fawkes32]

We had the same problem, but the difference is that we didn't know about last year deploy time, so we thought it was normal...

[jhellr13]

I'm having the same problem as well. On our robot for this year, the deployment is a decent speed, but is terribly slow on our robot from 2 years ago. It's absolutely terrible at moments. Sometimes even when the code does load, the robot main is so laggy that it's hard to test new programs at times.

[Greg McKaskle]

If Robot Main seems slow, please test the Diagnostics tab. Error reporting takes quite a bit of CPU, so if your code on the older robot has an issue casing it to report messages, fix that before being concerned about performance.

Greg McKaskle

[Wildcats1378]

Yeah, we've also noticed that Labview 2012 is much, much slower then Labview 2011... I just wrote it off as our computer being old, but I guess that isn't the case. Last year, when we'd try and run any sort of code, it would load up in like 30 seconds to a minute, whereas now we are waiting 8+ minutes every time, even with code deployed on startup already!

[Greg McKaskle]

I haven't experienced 2012 slow builds. Can you describe exactly when these occur, and can you open the Task manager to see if there is a hint at what is running and taking CPU?

Greg McKaskle

[fawkes32]

where are you running the program (vi) on the classmate PC on a personal computer, please specify your hardware and if the cRIO shows connection on the dashboard.

also, review the robot main.vi for waits or watchdogs, because if watchdog finds something wrong, it will stop the whole thing or make it slow.

[tcjinaz]

We saw 20+ minute deploy times off of our 2011 ClassMate
Using a Core i7 (late 2011-ish) laptop, it went down to 5.

[blackflame2996]

We have a very interesting issue on top of slow deploy time. Whenever deploying code after a build has been run as startup, it gets stuck on "waiting for target" line, which is printed twice. The only way to get around this that we have found is to re-image the cRIO. any suggestions?

[Alan Anderson]

Originally Posted by blackflame2996

We have a very interesting issue on top of slow deploy time. Whenever deploying code after a build has been run as startup, it gets stuck on "waiting for target" line, which is printed twice. The only way to get around this that we have found is to re-image the cRIO. any suggestions?

It's a bug. It's been explained on the Chief Delphi forums many times. Until the next LabVIEW update is released, the workaround is to close the Dashboard before trying to load new code into the cRIO.

[Wildcats1378]

Originally Posted by Greg McKaskle

I haven't experienced 2012 slow builds. Can you describe exactly when these occur, and can you open the Task manager to see if there is a hint at what is running and taking CPU?

Greg McKaskle

We aren't using the classmate, and I don't have the specs on hand, but we are running Wndows 7 on a school computer. We only have Labview and the driver station open. Labview seems to be taking 100% of the CPU. it happens whenever we try to run code, unless we had already ran code previously without restarting the cRIO.
Our computer isn't amazing, but it could run Labview / driver station / dashboard and any Internet browsers without any lag in speed. The code would download fairly fast, like under a minute.