where did the behind-the-scenes code go?

[Mark McLeod]

These attachments show the differences between the two versions.

Did you start with a Blank vi (PC target) and add Motor Set to it before drilling down?
(left picture is what you'd see with the PC as a target)

The right picture is what you'll get opening Motor Set in an FRC framework project (defaulting to cRIO as a target).

[tilky]

Originally Posted by Mark McLeod

Did you start with a Blank vi (PC target) and add Motor Set to it before drilling down?

This is the problem. I would have never guessed that what appears to be just a subvi would actually have the code change depending on if you are in a cRio project or not.

Thanks!

[Greg McKaskle]

LabVIEW supports many types of platforms.

It is necessary to compile your VI code for each platform, and it is often useful to swap out vi.lib subVIs that are written differently, perhaps taking advantage of OS or architectural specializations. Other languages do this too. C runtime libraries are standardized at their interface, but pre-built for platform details.

In this case, since the Wintel platform doesn't have an FPGA and can't really be the robot, we used it as a simulate-flag. If the code is PC, it links to the simulator.

Greg McKaskle