Downloading exe to FP-2000 doesn't seem to replace existing exe

[Brett_Percy]

When updating an executable version of a LabVIEW RT program on a client's FP-2000, it appears that the new executable doesn't replace the old one. The only way to get the new exe to work is to delete the old one via FTP first

[JeffBoettcher]

In general, you do not have permission to delete the existing startup.exe. Because of this, attempting to overwrite the existing startup.exe would fail. In fact, attempting to delete the existing startup.exe also should fail as a measure to prevent the accidental deletion of this file. However, you do have permission to rename the "startup.exe" to something else, such as "startup2.exe". You can then delete the startup2.exe, and FTP transfer your new startup.exe into the ni-rt/startup folder.

[Carl L.]

If you are using Application Builder then the executable will not be updated if the old application is still running. Stop the application first and then use Application Builder to update the startup.exe.

[Brett_Percy]

Hi Jeff, thanks for your response.

I'm concerned that the normal way of installing an exe onto the FP unit (build application w/FP unit as the target) appears to silently fail some of the time. I was messing about trying to delete the file first to see if that would help.

[Brett_Percy]

OK, that sounds reasonable - but App Builder doesn't tell you that the app didn't download succesfully.

Is there an easier way to stop the exe than setting the 'don't run at statup' dipswitch and rebooting the FP unit?

[JeffBoettcher]

If physical access to the hardware is what is causing the difficulty, then yes.

Simply target the FP-2000 from the LabVIEW RT development system. Doing so should prompt you for the front panel of the VI already running (your existing startup.exe). You can at this point close the running VI, and then from the Tools - Network Options selection, go to RT Target: Miscellaneous. Un-check the box that specifies to start the application at boot. Reboot the FP-2000 and your startup.exe file will still be there, but it will not run.