Unzip files within labview

[rolfk]

Thanks Devin. I was always looking for such a resource since it can be a bit cumbersome to find out what OS is used by a certain RT target. Pharlap ETS has never really been a problem here, since it uses the Windows binary object format and the DLL format therefore doesn't change at all between versions.

The only problem with your answer is that this does not solve the question why the VxWorks OS can't load the lvzip shared library.

Unfortunately I have no cRIO chassis available to do my own tests and most of the lvzip work for VxWork has been a theoretical exercise for me so far. If an AE could take the latest lvzip library and try to load it in debug mode onto a LabVIEW RT 2009 target to see the possible debug failure messages that are generated that would help a lot.

Rolf Kalbermatter

Message Edited by rolfk on 09-12-2009 10:26 AM

[Devin_K]

No problem Rolf.  Sorry for the delayed response...other job duties have been keeping me busy.

Anyway, I had a chance to test things in LabVIEW 2009, and I was able to get things working correctly on my cRIO.  The problem I found was that after installing lvzip 2.5.1 with vipm, the <LabVIEW>\user.lib\_OpenG.lib\lvzip folder did not contain lvzlib.out.  As far as I can tell, all the other files were there (readme.txt, .mnu files, lvzlib.dll, and the two .llb folders), but the .out file was missing.

I tried downgrading lvzip to go back to a different version (to see if I could get the .out file in an older version), but it gave me an error trying to uninstall the latest version.  I totally uninstalled and reinstalled vipm and manually deleted the lvzip folder (probably not good practice, but I'm not overly familiar with using vipm).  I then installed lvzip 2.4 in LabVIEW 2009, and I still didn't see an .out file, so I upgraded back to 2.5.1.

Anyway, I got a copy of the lvzlib.out file from a colleage who still had 2.4 installed in LabVIEW 8.6, and put it in the LabVIEW 2009\user.lib\_OpenG.lib\lvzip folder.  Then I manually FTP'd the .out folder over to c:\ni-rt\system on the controller.  After that, I was able to successfully deploy my VI and .zip a file on the cRIO using"ZLIB Compress Files_ogtk.vi".

Unfortunately I just upgraded my system to Windows 7 and I only installed LabVIEW 2009, so I can't check to see whether the missing .out file is specific to 2009 or something with the package/vipm.  Any ideas as to what the problem might be Rolf?

[rolfk]

That explains everything. The VxWorks 6.3 version of the out file is in the package but since we did not know if that would be the right version for the 2009 version of LabVIEW we did not update the package meta data to install it.

You can get at the file yourself though. The OpenG package is simply a ZIP file with a specific internal structure. It should be in the File Group 7 folder inside that archive.

We will try to get a 2.5.1-2 package with that metadata update.

Rolf Kalbermatter

[Jim_Kring]

I've just released 2.5.1-2 which should work in LabVIEW Real-Time 2009.

[Devin_K]

Great!  Thanks a lot Rolf & Jim

[Jim_Kring]

---

Devin_K wrote:
Great!  Thanks a lot Rolf & Jim

---

And, thank you, Devin, for testing to confirm that the *.out file works in LabVIEW Real-Time 2009.

Cheers, 

[rex1030]

I downloaded and installed the new package. I am still having problems when I try to deploy a VI that uses the LVzip "zip files.vi".

When I try to deploy it I get this error message:

Initializing...
Calculating dependencies...
Checking items for conflicts. This operation could take a while...
Preparing items for download. This operation could take a while...
Deploying NI_FileType.lvlib
Deploying Belle Glade 2009.lvproj
Deploying BelleGlade(successfully deployed target settings)
Deploying List Directory and LLBs.vi (13.75 K)
Deploying Recursive File List.vi (27.98 K)
Deploying ZLIB CRC32__ogtk.viZLIB CRC32__ogtk.vi loaded with errors on the target and was closed.
LabVIEW:  Failed to load shared library lvzlib.*:lvzip_crc32:C on RT target device.
Deploying BelleGlade Container
Deployment completed with errors

I even tried uninstalling and reinstalling the package. I have attached the VI I am attempting to deploy to the crio. As you can see, it is pretty simple. I don't know what I did different than Devin_K.

I appreciate the work you guys have done so far. I really do. I would love to get this working. It would be so useful. 

[rolfk]

Maybe a stupid question but did you read the release notes that come with the package? LabVIEW RT for VxWorks targets will NOT deploy shared libraries automatically. You do have to copy the according *.out file yourself through some means (FTP for instance) to the c:\ni-rt\system directory, in order for your VIs to be able to link to them.

Rolf Kalbermatter

[rex1030]

Not a stupid question at all. 🙂 How do i do that? Where can I find the appropriate .out file to ftp over? Where are the release notes. Thanks for your patience.

Message Edited by rex1030 on 09-21-2009 02:32 PM

[rex1030]

You mean "For VxWorks support, after installing the lvzip package, you should ftp "<LabVIEW>\user.lib\_OpenG.lib\lvzip\lvzlib.out" to the RT controller into ni-rt\system." right? Trying that now...

The wiki is for a previous version, I thought something had changed that I might not have to do that.

Message Edited by rex1030 on 09-21-2009 02:34 PM