Desabling the VS engine to run a LV RT vi

[LDBM]

According to this Knowledge bases note, to run a LV-RT vi on a target that has the VS engine installed, one must disable the VS engine.

The note states at the bottom:

"Before you deploy non-NI VeriStand VI's to RT systems that have the NI VeriStand RT engine installed, disable the startup application NI VeriStand.rtexe in BIOS and reboot the RT machine".

What does it mean by " .. in BIOS" , going into the RT target BIOS only show boot devices, nothing relating to the Startup folder... Thx.

thx.

L.

[Jarrod_S.]

Maybe someone else can chime in, but I see no need whatsoever to explicitly disable the NI VeriStand startup executable before deploying a LV VI to the target.

When you deploy a LV VI to the target that is running the VeriStand Engine, LabVIEW will first prompt you that deploying the VI will disable the current startup executable. Just click OK on this warning and continue with deployment.

To re-enable the VeriStand Engine after you're done running your LV VI and want to run VeriStand again, the easiest thing to do is to reinstall the VeriStand support for your target from MAX.

[LDBM]

THat is exactly what I want to avoid.  Doing so leads to the issue mentioned here. We use a system with cards that are part of the recommended models from NI.

L.

[Jarrod_S.]

Luckily, you can avoid using MAX to enable support for the VeriStand Engine. Using MAX is just the most straightforward way to do it. When you deploy a LabVIEW VI, it unsets VeriStand as the startup executable. However, the executable and its dependent files are still located on the target. The ni-rt.ini file at the root level of the target is simply modified to disable it from running.

So to restart the VeriStand Engine, you just need to edit the ni-rt INI file to set the VeriStand Engine as startup, then reboot the target. You can edit this text file manually to set up the proper keys, but the easiest way to do it is probably just to make a copy of the INI file while VeriStand is deployed and active. Then whenever you want to start it back up, simply overwrite the version on the target with that copy.

You can manually access the file system on your RT target using FTP. An easy FTP client to use is the standard Windows Explorer shell. Just open Windows Explorer and type ftp://<Target IP Address> into the address bar. Then you can navigate around just like your local file system.

[LDBM]

Thx Jarrod. Will try this and post back on Monday.

L.

[LDBM · Accepted solution]

To be more precise, the items to change are in the ni-rt.ini: 

• Run a LV-Rt VI: 

RTTarget.LaunchAppAtBoot=False--> so that a RT_VI can be run from the Windows side

• To revert to VS:

RTTarget.ApplicationPath=c:\ni-rt\startup\NI Veristand.rtexe

        ...

        RTTarget.LaunchAppAtBoot=True

Laurent.