LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

[QUES] Provided LabVIEW Suite pointing at wrong DLL...

Solved!
Go to solution

I have a commercial product that contains an API as a DLL.  The company has also provided LabVIEW API VI’s for each of the DLL function calls.  These VI’s drill down to use “Call Function Library Mode” to access the DLL.  Problem is the company has placed the version details in the DLL’s file name.  They have updated the DLL and rolled the number but the VI’s have not been updated and all point at a DLL that now does not exist.  There are around 30 VI’s, is there a quick way I can rename the “Call Function Library Mode” DLL path in all of them, or will I have to open every one manually.

Christopher Povey

Principle Test Systems Engineer for BAE Systems.
0 Kudos
Message 1 of 7
(2,513 Views)

Just for 30 VIs you can do this manually, or you can use VI scripting for this, something like that:

 

RenDLL.png

0 Kudos
Message 2 of 7
(2,506 Views)

@Andrey Dmitriev wrote:

Just for 30 VIs you can do this manually, or you can use VI scripting for this, something like that:

 

RenDLL.png


Could you possibly attach the above as a VI?

 

Thanks.

Christopher Povey

Principle Test Systems Engineer for BAE Systems.
0 Kudos
Message 3 of 7
(2,500 Views)

Sure. Downsaved to LabVIEW 8.0

 

 

0 Kudos
Message 4 of 7
(2,495 Views)

It seems to only process one file in the folder and then stops.  I have attacted one of the problem VI's.  It seems not to be changing anyhting.

 

The VI has Call Library function in it, which calls "C:\Program Files\FireDiagnostics Suite 4.3\bin\FireSuiteAPIv4_3_4.dll"  It needs to call C:\Program Files\FireDiagnostics Suite 4.3\bin\FireSuiteAPIv4_3_6.dll

 

Thanks.

Christopher Povey

Principle Test Systems Engineer for BAE Systems.
0 Kudos
Message 5 of 7
(2,490 Views)

@ChristopherPovey wrote:

It seems to only process one file in the folder and then stops.  I have attacted one of the problem VI's.  It seems not to be changing anyhting.

 

The VI has Call Library function in it, which calls "C:\Program Files\FireDiagnostics Suite 4.3\bin\FireSuiteAPIv4_3_4.dll"  It needs to call C:\Program Files\FireDiagnostics Suite 4.3\bin\FireSuiteAPIv4_3_6.dll

 

Thanks.


The attached code shows just the idea. You may need to modify this code according to your needs.

 

For exampls, add cycle for all VIs in directory, etc:

 

RenDLL2.png

Message 6 of 7
(2,485 Views)
Solution
Accepted by topic author ChristopherPovey

Sometimes the most obvious solution is over looked! Smiley Sad  There are actuall more like 327 VI's.  However you can do "Find and Replace" from the Edit Menu.  It does open every VI though!

Christopher Povey

Principle Test Systems Engineer for BAE Systems.
0 Kudos
Message 7 of 7
(2,482 Views)