[Greg McKaskle]

A comment on the difference between Run as Startup and pressing the run button using LV.

Running LV with only the run button is quite similar to running as startup, but because the panel(s) are open, the cRIO and development computer are both working a bit harder communicating info back and forth about panel values.

This protocol is typically lightweight, just sending binary values, usually from robot to dev computer. If you change a panel value such as a PID gain, the dev sends a small packet to the robot. Obviously, the more windows you have open, the more traffic. The more probes you add to your VI, the more traffic. Vision is a case that is not lightweight. It is extremely useful to be able to probe and view panels with camera data on them, but to get the data to the laptop, the image has to be compressed by the cRIO and transmitted as part of the protocol. This only happens if the image is visible on a probe or panel. Scrolling the image offscreen won't help, and I doubt that minimizing helps. To lighten the load, you close the panel with images when you aren't using them.

I develop with the run button all the time, but then again, I like debuggers. Also, I usually don't run the dev stuff and DS on the same computer, and almost never run both on a Classmate. Hopefully this helps explain why panels can indeed cause dropouts, but it doesn't have to force the Startup approach too early.

Greg McKaskle