[Greg McKaskle]

The long build times will definitely be reduced. It was in work just before Atlanta, but too risky to release at that point.

The file solution has two flavors. Number one downloads a description file, could be XML or lines of text or binary. Choose your own location, /tmp is a reasonable location I think, and then ftp the file using an ftp client. You can write tools to put a nicer UI on the ftp operations if you like.

The second downloads code that is dynamically called. For LV that would mean downloading a VI and then changing either the framework or the autonomous VI to dynamically call the VI by reference. Again, you ftp the file to the cRIO to a known location, and the dynamic call code will use an Open VI Reference with a path to your VI, and will then invoke the run method on the VI.

For the C++ users, this is equivalent of downloading a different .out. I haven't done this yet, but it should be possible.

Greg McKaskle