How to manage versions of RT program?

[CoastalMaineBird]

My client has 20-30 HOST computers, each with a corresponding PXI RT box.I am developing the software for both ends and need to consider deployment strategies. I currently do all communications with PXI, via TCP/IP, I am comfortable doing that. The PXI is on a local network with its own host and other instruments, there is not one network that can reach all PXI boxes. One host can talk to another host via a 2nd net, but it can talk to only one PXI box, its own. I want the users to be able to :1... Maintain uniform versions of both the host and the RT software.  If we update either, we need to spread it around, so they all are operating the same version. 2... Use a minimal number of LabVIEW copies.  IOW, i want to spread the binaries around, on host machines that do not have the full LV dev. system. #2 is the important part - only the software maintainers will have LV dev. systems, the users will have only the runtime.  Basically, I would like to do this in the host program:1... Connect to my RT program on PXI and obtain its version number.
2... If the PXI responds with the latest version number, then all is well, and we're off and running.3... If the PXI doesn't respond, or if its version number is old, then I download the latest RT program to it, and re-boot it. This would let them download the latest HOST program from a central server, and embedded in that is the latest RT program.I already have the version number query running and displayed.  But what I don't know is how to download to the RT and how to reboot it. Do I FTP the program to the STARTUP.RTEXE file?  Can I do that to a box that has never had my software on it (new box)?How do I do the reboot? All this is easy when LabVIEW is on the host, but what do I do if it's not? Suggestions for other approaches welcome, as well. 

[Matthew Williams]

Check out:&nbsp;&nbsp;<a href="http://zone.ni.com/devzone/cda/tut/p/id/3937" target="_blank">http://zone.ni.com/devzone/cda/tut/p/id/3937 </a> &nbsp;From the write up there may be some issues with PXI, but we have had good luck building our owntools for FieldPoint based on the toolset (we don't use PXI).&nbsp; We had done the ftp route, includingdisk formatting and OS installation, but if there is any way to get the toolkit to work with PXI, I&nbsp;expect it would be much easier.&nbsp;edits:If you go the ftp route, you may have to rename the existing startup file before it can be deleted;this is necessary on FieldPoint.&nbsp;For LOGOS rebooting: <a href="http://digital.ni.com/public.nsf/allkb/383D4113BACF175486256F2C00493BB5" target="_blank">http://digital.ni.com/public.nsf/allkb/383D4113BACF175486256F2C00493BB5</a> again, I know this works on FieldPoint, might work, or something similar, on PXI. &nbsp; Matt Message Edited by Matthew Williams on 08-14-2008 04:01 PMMessage Edited by Matthew Williams on 08-14-2008 04:05 PM

[TonP]

I have heard that the LabVIEW Stop function reboots the PXI chassis. I have never tested it.&nbsp;Currently you have an upload routine (from host to PXI via FTP), what about a download routine?The PXI software could ask for the executable via TCP as a bytestream and writes the data over it's own executable, then stop itself (rebooting) and loading with the new software.&nbsp;Ton

[CoastalMaineBird]

The PXI software could ask for the executable via TCP as a bytestream and writes the data over it's own executable, then stop itself (rebooting) and loading with the new software.Maybe, but when a new box comes online, they would have to load it initially.&nbsp;I want something where the host &quot;pushes&quot; the version onto the PXI, even if the PXI is fresh out of the box. &nbsp;I understand they might have to use MAX to set the IP number, but they shouldn't have to use LV at all.&nbsp;Message Edited by CoastalMaineBird on 08-15-2008 05:20 AM

[dan_u]

You don't even need MAX to set the IP. If you get the PXI with LV RT installed but unconfigured, RT ping will be able to find it. Using the <a href="http://zone.ni.com/devzone/cda/tut/p/id/3937" target="_blank">replication toolkit</a> functions you can set the IP address using the MAC address (which you get from RT ping). Anyway, it's a good idea to look into RT replication toolkit, also for updating your system.&nbsp;To update the software I would recommend (as mentioned before) renaming the startup.rtexe using FTP, upload the new startup.rtexe (also using FTP) and reboot the PXI. To reboot, there's a function in RT Utilities (RT Reboot Controller).&nbsp;All that's mentioned above can be compiled into an executable, so you don't need LabVIEW dev. version on the host PC.&nbsp;&nbsp;Hope this helps,Daniel&nbsp;Message Edited by dan_u on 08-15-2008 01:38 PM

[CoastalMaineBird]

Yes, I haven't waded thru the whole replication toolkit, but it looks like the answers are in there somewhere.&nbsp;Thanks,&nbsp;

[StevenA]

the nice thing about the system replication tools&nbsp;is that you can do a complete disk image (drivers and all) you can also do things like set the ip addresses etc.