LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Programmically detecting software versions on RT Devices

Does anyone know if there is a way to programmically detect software versions installed on real-time devices.  Specifically the PXI-8145RT.

We have stumbled across an issue where we can not use System Replication unless LabVIEW is already installed on the device.  Basically what happens is that when we build the RT executable, we are forced to create a .rtexe file.  Not necessary a problem, but if you format the compact flash on the 8145, confiure the IP address and then try to re-image it using an image created from the same device, it fails when it tries to FTP the .rtexe file to the controller. 

The problem seems to be with the ftp program that resides on the ROM of the device.  With no software installed on the device, you can only ftp files to it that are in the 8.3 format. 

If I could programically detect that LabVIEW is not installed, then I could display an error message to install LabVIEW first.

0 Kudos
Message 1 of 4
(2,826 Views)
The way I do it is, I Ping the RT. If it doesn't ping back, I assume there's a problem. I'm pretty sure if LV isn't installed, it isn't going to Ping.


Message Edited by Broken Arrow on 08-06-2008 10:44 AM
Richard






0 Kudos
Message 2 of 4
(2,824 Views)
You are probably correct that the issue is due to 8.3 filename limitations. When the controller boots and the disk has been formatted it loads a safemode from an EEPROM. Due to backwards compatibility issues, this safemode is limited to 8.3 filenames and your .rtexe would not be allowed. There is not a VI or a parameter returned by the Get Target Info VIs in the System Replication VIs which would tell you if and what version of the software is installed. And since it loads safemode from the EEPROM, it would still reply to RT Pings.

I'd recommend putting a marker file in your image that you are deploying. For example just an empty text file whose name reflects the version of the image that you are applying. Then you can check to see a version marker file exists and if not you apply an image of just LabVIEW RT, reboot, and then apply the full image. Once LabVIEW is installed and boot from disk it would support long filenames.

Regards,

JRA
0 Kudos
Message 3 of 4
(2,799 Views)

Thanks for the input.  Just thought I would throw it out there and see how people responded.  It makes sense that it is a backward-compatibility issue.

 

As for an empty file, I have had very bad luck with using FTP or Replication with empty files.  It does not always cause an issue, but sometimes it does and causes the a failure in the replication process so I try to stay away from them..

 

How about is there a way to detect the mode of the controller like it shows in MAX?  Running, Safe-Mode(User Defined), No Software Installed, etc...

 

 

0 Kudos
Message 4 of 4
(2,755 Views)