i.e. running VIs on the target from within the IDE and seeing front panels of VIs being opened on the host (Windows) computer

LabVIEW bug no. 1876112 describes a behaviour where during deployment to RT targets, LabVIEW will open the front panel of any VI containing an event structure. The reason for this behaviour is a LV-internal warning (“VI containing Event Structure will not receive front panel events in LabVIEW Real-Time”), which is not actually displayed or anyhow visible to the user.

Specifically, this bug has been found, documented, investigated and resolved by working with a DQMH module. It also turned out that the behaviour would show if the module .lvlib was added to the project, and would not show if the .lvlib was removed from the project and only showed up in Dependencies.

This bug was fixed in LabVIEW 2022.

After deployment == when running the code

For targets without UI (all Vxworks and Phar Lap targets and NI Linux RT with Embedded UI disabled), this might be related to executing VIs that contain front panel related nodes. These nodes will throw error 53 (Manager Call not supported) when being executed, and will trigger the IDE to open the front panel of the containing VI.

• After updating an RT system with a new startup.rtexe, it is not executed, although the build was successful.
• When deploying (not when building) from the development environment, LabVIEW reports for arbitrary VIs (mostly those from the LabVIEW basic functions) that they cannot be deployed. The error message, for example, as shown in the screenshot.

The problem is most likely because several targets (mostly Windows and Real-Time) are created in the project file and are also filled with VIs, and LabVIEW then gets into a conflict as to which platform such a VI is then compiled for should (or the other way around, LV seems to compile VIs for Windows and then of course they don't run in real-time)

• Stick to our Best Practices for LV Project files