LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Possible 8.5 Problem... There are foward slashes in NI-Motion files? Adding forward slash to destination?

I am attempting to make an LVOOP app build in 8.5.  I added a custom destination called Classes and am targetting all my class vi's to that folder so it doesn't stick them all at the top level.  But since the default on dependencies is set to "same as caller" and one of the classes is using NI motion, it is sticking a .flx file from the NI directory inside the custom classes destination.  OK - Thats fine and all, but its putting a forward slash in the destination path! 
 
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Motion\FlexMotion\FunctionsVIs\Trajectory.llb\Load Acceleration/Deceleration.flx

Destination: C:\850 Software\MfgTest\Galvo Test Station (GTS)\App\Classes\Load Acceleration/Deceleration.flx
 
Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>
 
 
Is there really an NI file name that contains a forward slash?  (Load Acceleration/Deceleration.flx)  That would mean the app builder can't build anything that puts this file anywhere onther than in the exe itself.


Message Edited by billings11 on 02-05-2008 09:56 AM
-Devin
I got 99 problems but 8.6 ain't one.
0 Kudos
Message 1 of 5
(3,342 Views)
Hi Billings11,
 
So, the Load Acceleration/Deceleration.flx is an NI file. Do you have a library that includes the class vis that you are then including in your executable? This procedure is detailed in this KnowledgeBase.
 
Additionally, you could rename the file (without the /) and use it as you would a normal subvi.
 
If you're not using the Load Acceleration/Deceleration.flx in your project you could also try the following steps:
1. Right-click on your EXE Build Specification in your Project Window
2. Click on Properties
3. Navigate to the Additional Exclusions section
4. Make sure that the "Remove unused members of project libraries" checkbox is checked.
 
Let us know how it goes.
 
Regards,

Hillary E
National Instruments
0 Kudos
Message 2 of 5
(3,307 Views)

Yes, I'm using the file in my project. 

Renaming the file is a pain because I have to also copy rename the hierarchy of NI-Motion vi's that call it, to differentiate them from the NI directory vi's that will be called when I open the project on another computer.

I will find a workaround.  I just wanted to verify that the NI filename really does have a forward slash.

-Devin
I got 99 problems but 8.6 ain't one.
0 Kudos
Message 3 of 5
(3,301 Views)
Yes it does have forward slash in the file name and yes you are right by changing the file name it'll be one big mess. They couldn't simply use _ instead of / in the file??
0 Kudos
Message 4 of 5
(2,949 Views)

Here is the fix for LV 2009 Build issue with forward slash in .llb vi file name.

 

Step 1) In project explorer -> Build Specifications -> Right click your executable build and go to properties.

Step 2) Go to Advanced tab and check "Use Labview 8.x File layout"

 

Now you can build your project without the forward slash issue.

 

Cheers,

 

Farhoud

0 Kudos
Message 5 of 5
(2,947 Views)