LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Weird LV 7.0 File names on Macintosh

When opening a VI, from the Basics 1 course, a screen appears that it cannot find a VI named "AI Sample Channel (scaled value).vi"

The required file is found in the 1EASYIO folder, on the computer's hard drive" but LV shows the file name as "AI Sample Channel (scaled va.vi"

In view of this inability to associate the truncated file name as being the same the file "AI Sample Channel (scaled va.vi" is duplicated and the name of the copy is changed to "AI Sample Channel (scaled value).vi" .  It appears with the new name when the folder is reopened.

However LV 7.0 will not recognize the new name, which always appears normal in the OS directory.  LV, when Open is used shows the file name as "AI Sample Channel (scal #C7E2.vi"  This hex looking addition still does not open because LV does not recognize it as the "AI Sample Channel (scaled value).vi" which appears in the Finder Directory.

How have others got around this limitation?

Raymond
0 Kudos
Message 1 of 6
(3,033 Views)
RL,

I am trying to duplicate this on my Mac.  Which OS are you using and which version of the Basics 1 course?  Looks like you are using the traditional DAQ driver, which version?  My test iBook G4 is running LabVIEW on OSX with DAQmxBase, but we have other test machines I can use to try to duplicate this issue.

Cheers,
Spex
National Instruments

To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be has a 2x safety factor...
0 Kudos
Message 2 of 6
(3,004 Views)
Raymond,

I think I recall seeing something like this. I think some versions of the Mac OS had 32 character limits on filenames, including the extension.

A possible workaround: Make a copy of the VI. Change the name on the copy to something shorter. Open the main VI. When you get the dialog, tell it to ignore the missing VI. Once the main is opened, replace the missing VI with the renamed one. Then save the main VI with a new name.

It would be nice if the search dialog would allow the replacement of a missing or miss-named VI, but that probably introduces a whole new set of problems.

Lynn
0 Kudos
Message 3 of 6
(2,992 Views)
"Which OS are you using and which version of the Basics 1 course?  Looks like you are using the traditional DAQ driver, which version? "
The Basics I course version is 6.1 but I think this is more related to LV 7.0  The file name changes I did had to be done on the hard drive.

The operating system is OS 9 Classic.  I don't think that OS X can communicate with the DAQ boards unless using Real Time.

I am not at the computer in question therefore I do not know if or which DAQ drivers are installed (actually there are no boards in that computer).  I am mostly trying out the demo VIs.

Raymond
0 Kudos
Message 4 of 6
(2,984 Views)
Spex,
"Looks like you are using the traditional DAQ driver, which version?"

I am using 6.6.1

Aside:  I have not used the DAQmx because my preferred 4452 board uses only traditional acquisition.

Raymond
0 Kudos
Message 5 of 6
(2,967 Views)
Raymond,

I found an archived copy of the LabVIEW Basics course manual and CD for LV 6.1.  You said you are mostly trying the demo vi's.  I looked at these vi's but it doesn't look like they use the Traditional DAQ VI's.  Those demo vi's are actually used to simulate the DAQ VI's without HW.  I can see though if you opened one of the VI's that actually uses the driver, the filenames are longer than 32 char.

I think Lynn is on the right track for a workaround.  Are the Traditional DAQ VI's in your LabVIEW palette?  If so, you should easily be able to open the VI, ignore the missing subVI's, and replace them with the VI's in the palette, and resave.  Let us know if reopening the VI after you have saved it with the changes results in any similar behavior. 

Good Luck!
Spex
National Instruments

To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be has a 2x safety factor...
0 Kudos
Message 6 of 6
(2,943 Views)