From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

(My Labview built executable) has encountered a problem and needs to close.

Solved!
Go to solution

I'm looking into the Call Library function.  When I put the dll that I'm using in the activeX invoke node into the call library function, I get less than half of the available function calls.  What gives?

--

Ro ma wa ichi ni chi ni shi te na ra zu
0 Kudos
Message 11 of 19
(2,520 Views)

Incidentally, here is the VI that's causing the problem.

--

Ro ma wa ichi ni chi ni shi te na ra zu
0 Kudos
Message 12 of 19
(2,516 Views)

The error message I get from the Visual C++ debugger I have installed on the target machine is

 

"Unhandled exception in your_vi.exe (BQ80XRW.ICX): 0C0000005: Access Violation."

 

There is no problem with this object when it's invoked by other software.  I have VB6 code that runs perfectly well without issue.

--

Ro ma wa ichi ni chi ni shi te na ra zu
0 Kudos
Message 13 of 19
(2,510 Views)

Here is a bunch of posts with the same or simmilar error message...

 

http://forums.ni.com/t5/forums/searchpage/tab/message?filter=location&location=forum-board%3A170&q=0...

 

Maybe there is a soution in there someplace

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 14 of 19
(2,506 Views)
Solution
Accepted by gdecker

Okay, problem solved.

 

The issue was the fact that the activeX object (BQ80XRW.OCX) and dynamic link library (BQ80XUSB.dll) that I was invoking in my VI did not have the permissions set correctly in the destination computer.  Basically, since I did not have Labview installed on the target machine, those objects denied access to programs developed in labview.  I never had a problem with VB6 executables because VB6 is installed on the target computer.

 

Texas Instruments provided me with an executable that puts the DLL into developer mode, and after updating IVI and the device drivers to account for some GPIB errors, the program now opens and runs as expected.

--

Ro ma wa ichi ni chi ni shi te na ra zu
0 Kudos
Message 15 of 19
(2,492 Views)

Hello Gdecker

 

   I am trying to control EV2300 in LabVIEW via dll but do not know how to start.  May you share the code of how to control to me if possible ?   Many thanks

 

Sincerely

 

Jesse

0 Kudos
Message 16 of 19
(2,192 Views)

I am trying to control EV2300 in LabVIEW but do not know how to start.
can you help me?

 

thank you

0 Kudos
Message 17 of 19
(2,127 Views)

Hi there.

 

Can you share the Vi you used on communicating your EV2300 thru USB. I'm currently on a project with the same purpose but I'm having a hard time to do so...

Thanks in advance.

0 Kudos
Message 18 of 19
(1,853 Views)

Rctrigger,

 

Given the fact that the EV2300 is third-party hardware, if you have specific questions regarding that hardware you should contact the manufacturer directly.

 

In general, however, when interfacing with third-party hardware the Call Library Function Node can be used to call shared libraries in LabVIEW. Please reference the following pages from LabVIEW 2015 help:

 

Calling Shared Libraries

http://zone.ni.com/reference/en-XX/help/371361M-01/lvexcodeconcepts/shared_libraries_dlls/

 

Configuring the Call Library Function Node

http://zone.ni.com/reference/en-XX/help/371361M-01/lvexcodeconcepts/configuring_the_clf_node/

 

Call Library Function Node

http://zone.ni.com/reference/en-XX/help/371361M-01/glang/call_library_function/

 

*NOTE: If you are not using LabVIEW 2015 then reference the help page for your specific version of LabVIEW.

 

If you have already implemented the Call Library Function Node and you are having trouble debugging calls to shared libraries the following help page outlines troubleshooting steps:

 

Debugging Shared Libraries and Calls to Shared Libraries

http://zone.ni.com/reference/en-XX/help/371361M-01/lvexcodeconcepts/debug_dlls_and_dll_calls/

 

Regards,

 

Kyle S.
Applications Engineer
National Instruments
ni.com/support

0 Kudos
Message 19 of 19
(1,825 Views)