What's the quickest way to update a LabVIEW executable on a FieldPoint module?

[bmihura]

I'm developing a complicated LabVIEW 7.0 standalone executable that runs on a FieldPoint FP-2010 module. I believe I'm going through too many steps whenever I change this software; could somebody tell me a faster way to change the code?

Here's the insanely tedious way I'm doing it now:

1. First, it seems I have to �clear� the existing VI from the FieldPoint module by setting its �Disable VI� jumper to ON, then rebooting the FieldPoint module, waiting for it to boot, then setting its �Disable VI� jumper back to OFF, then rebooting the FieldPoint module, and waiting for it to reboot again. If I don�t do this tedious step, the new LabVIEW .exe won�t load later on.

2. In LabVIEW, change t
he execution target to the FieldPoint module ("Operate >> Switch Execution Target >> RT Target ...").

3. Make the RT application launch at boot up (�Tools >> RT Target � Options >> RT Target: Miscellaneous >> Launch Application at Boot-up�).

4. �Tools >> Build Application or Shared Library (DLL) >> Applications Settings >> Set Target to Launch at Boot-up >> Build�

5. Reboot the FieldPoint module yet a third time to get the new .exe code running.

6. Finally, my code will be running on the FieldPoint module.

[Matthew_Williams]

I think you are pretty much stuck with steps 2, 4 and 5 if you are changing the code each time.

As far as clearing the existing .exe, you can delete it with an ftp program. You will probably have to rename it first to something other than startup.exe. This should save two reboots. Make sure you do not rename it something with a 'space' character. The module should accept the new .exe without a reboot at this point.

If you make a build script (one of the options on the Application Builder screen) you can avoid step 3 by setting launch at boot in the saved script.

Lastly, I have a little .vi that will do the rename, delete, upload and reboot if you are installing a pre-compiled startup.exe but it is at the shop right now. Let me know if that wo
uld be useful to you.

Matt

[bmihura]

That little .vi of yours would indeed be useful. Would you post it?

[bmihura]

ftp, eh? I logged in to my FieldPoint module as

Username: anonymous
Password:

and I saw these files:

ftp> ls
200 Data Connection OK
150 Opening data connection for listing of /
NI-RT
NI-RT.INI
TEMP
HDMON.BIN
PH_EXEC.EXE
tempEMBLVIEW_7.0__cur.txt
226 Closing data connection
ftp: 75 bytes received in 0.01Seconds 5.00Kbytes/sec.
ftp>

I don't see any startup.exe there. Is PH_EXEC.EXE the right file, or do I need to log in as something else?

Also, I can't find where any of this is documented. Is it?

[Matthew_Williams]

The startup.exe file is locate in the \NI-RT\STARTUP directory. 'cd NI-RT' then 'cd STARTUP' should get you to the right place after making the connection with ftp. I don't recognize PH_EXEC.EXE. Logging in as anonymous is fine. I don't recall seeing documentation on the file structure and locations on the module but I'm sure there is some. I just wandered around w/ftp.

The program to update the node should be below. Enter the IP address, the green light will confirm the node is found.

The version function scans the existing startup.exe for a string beginning and ending with " RU Version " and prints everything in between as the version.

The autostart function will copy the existing ni-rt.ini file to your computer, mod
ify the autostart as requested, then put the file back. Leaves the copy on the PC, which can be handy.

Send file will request a file of the format startup*.dat which will be renamed startup.exe and ftp'd to the module. Lets you keep version numbers in the filename on the PC side. Your directory structure probably won't match mine so you'll have to browse for your file.

Reboot module reboots the module.

Hope this is useful, let me know if anything doesn't make sense. Thanks.

Matt