Long deployment time.

[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.