Running a .dll in a .VI

Hi, i have some issues running a dll in a .VI.
to be more specific...
I am running a main VI, and that main VI calls for a .dll when it is running labview crashes. after that y tried another way, I made the main VI a .dll then when i ran it everything went good.
so the question is, does labview have to run everything in .dll when something is in .dll or i can mix a .dll in a vi or viceversa
hope i explained myself

LabVIEW can call DLLs just fine, so you do not need to run everything in a DLL. Your most likely issue is incorrect configuration of the Call Library Function Node, or you are not managing memory properly. There have been many threads posted in the forum on calling DLLs with various parameters. There's a very extensive example that ships with LabVIEW called "Call DLL". I would suggest searching the forum for message related to the error that you are seeing and/or the kinds of datatypes you are trying pass into/out of the DLL. If you cannot find the answer, then post back. Please provide details, such as the DLL header file, or at the very least the prototype for the function, as well as your LabVIEW code for how you are calling the DLL.

Similar Messages

"Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'"

Hi!
As you can see from here :
http://www.fabiocavallo.it/sap/maxdb.jpg
MaxDB seems to work fine, but after starting application server i have got an error :
SAPGUI Logon Error Message:
http://www.fabiocavallo.it/sap/sapguilog.jpg
...here comes dev_w0 :
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Thu May 22 19:58:50 2008
B create_con (con_name=R/3)
B Loading DB library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib: LoadLibrary(C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll) Error 126 http://dlnt.c 237
M Error 126 = "Impossibile trovare il modulo specificato."
B *** ERROR => Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'
http://dbcon.c 4726
M sysno 00
M sid NSP
M systemid 560 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 95
M intno 20050900
M make: multithreaded, ASCII, optimized
M pid 3376
M
M kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
M length of sys_adm_ext is 360 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3376) http://dpxxdisp.c 1301
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M
M Thu May 22 19:58:51 2008
M DpShMCreate: sizeof(wp_adm) 6328 (904)
M DpShMCreate: sizeof(tm_adm) 3605136 (17936)
M DpShMCreate: sizeof(wp_ca_adm) 1200 (60)
M DpShMCreate: sizeof(appc_ca_adm) 1200 (60)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
M DpShMCreate: sizeof(comm_adm) 528048 (1048)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (96)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1280)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 06420040, size: 4205552)
M DpShMCreate: allocated sys_adm at 06420040
M DpShMCreate: allocated wp_adm at 06421A28
M DpShMCreate: allocated tm_adm_list at 064232E0
M DpShMCreate: allocated tm_adm at 06423310
M DpShMCreate: allocated wp_ca_adm at 067935A0
M DpShMCreate: allocated appc_ca_adm at 06793A50
M DpShMCreate: allocated comm_adm at 06793F00
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 06814DB0
M DpShMCreate: allocated gw_adm at 06814DF0
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 06814E20
M DpShMCreate: allocated wall_adm at 06814E28
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host PCFABIO
M
M Thu May 22 19:58:52 2008
M calling db_connect ...
B create_con (con_name=R/3)
B Loading DB library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib: LoadLibrary(C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll) Error 126 http://dlnt.c 237
M Error 126 = "Impossibile trovare il modulo specificato."
B *** ERROR => Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'
http://dbcon.c 4726
M ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) http://thxxhead.c 1426
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) http://thxxhead.c 10240
M
M Info for wp 0
M
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M vm = no VM
M
M *****************************************************************************
M *
M * LOCATION SAP-Server PCFABIO_NSP_00 on host PCFABIO (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Thu May 22 19:58:52 2008
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10439
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm http://thxxrun1.c 720
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed http://thxxtool3.c 260
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3376) http://dpnttool.c 327
File dbsdbslib.dll' is 'there' (in 'C:\SAP\NSP\SYS\exe\run\), maybe i have to set environment variable in windows for SAP.
Could you help me, please ?
I don't know how to set these variables.......
Many thanks.
Regards.
Fabio

Hello Fabio,
-> You wrote:
"File dbsdbslib.dll' is 'there' (in 'C:\SAP\NSP\SYS\exe\run\)"
=> Please check the version of this file.
< Go to file properties ->Version && update with 'file version', Platform,
   Product Name, Product Version information >
-> What version of the SAP system did you install?
     "I suppose that i can download this patch from Sap MaketPlace, but i can't register there, because i have no
      Customer or   Installation Number! (i can't Logon in SAP....) "
     From were did you get the SAP software installation or CD?
-> Could you upgrade the database client software on the application server to the version 7.7.04.08 or higher.
    You pointed "As you can see from here : http://www.fabiocavallo.it/sap/maxdb.jpg u2026 "
   => If the database and application were running on the same server, you installed the database
Software version 7.6.02.17. Please run 'sdbregview -l' to review the list of all installed packages
on the server.
-> "MaxDB seems to work fine, but after starting application server i have got an error"
     Was the system working fine before? What was changed?
     Or you was not able to start the application server after installation. ?
Thank you and best regards, Natalia Khlopina

I would like to convert a matlab file into a .dll and use it in LabVIEW. However, when I run the .dll in LabVIEW I get an error stating "... Procedure not found". What could this be? Can anyone help me...

I wish to convert my Matlab files into .dll's so that I can use them in LabVIEW. I am using 'mcc' and 'mbuild' of Matlab to convert my .m files into .c and .dll.
When I try to run the .dll's in LabVIEW, I get an error message in a modal window stating some required .dll or procedure is not found.
How should I resolve this issue. Should I add any other Matlab .dll's in course of making my .dll?
Please help in solving this issue... Thankyou very much.

KJV wrote in message news:<[email protected]>...
> When I run the matlab generated dll, it is stating 'matllb.dll not
> found'. Is it that I should set the path for matlab\bin to include
> all the dll's before I compile? When I make dll from C, it works fine
> in LabVIEW. The problem is from .m to .dll. The problem also arises
> when I convert my .m to .exe. The same error of 'matllb.dll not
> found' comes over. Should I change my matlab compiler options or
> something else? Please help me?
I have the same question,I don't know how to use the matlab DLL file in labview,
I hope someone can descripe the procedure in detail.

When opening a PDF in IE 10 with Enhanced Protection Mode it displays "This website wants to run acropdf.dll"

I am running my application which requires JRE on Internet Explorer 10. Since the IE need to run in 64 bit mode, we have enabled the "Enhanced Protection Mode" in Security option of Internet Options in Advanced tab. But my application also opens
up PDF in the browser, when the page with PDF is invoked it displays "The webpage wants to run 'AcroPDF.dll'. If you trust this site, you can disable Enhanced Protection Mode for this site to run the control.(Disable)(Always Ignore)". And on
clicking any option the PDF is not displayed.
We would not be able to disable the Enhanced Protection Mode as the 64 Bit JRE would not be invoked for other part of the application.
Please let me know how to resolve this issue.
Regards
Navin

... and/or
Configure Adobe Reader to not use a Web Browser to open PDF documents... (see the Adobe.com for admx files to apply this setting by group policy) (
http://forums.adobe.com/thread/392489 )
Start>Adobe Reader>Edit>Preferences>Internet>uncheck "Display PDF in browser"
It seems that Adobe have recently changed the location of that setting in Adobe Reader (at least on 11.0.4). They've now hidden it under Edit > Accessibility > Setup Assistant > Then on page 5 of 5, there's a tick box to toggle 'Display PDF
documents in the Web Browser'.
However, it doesn't work like it used to though, as it won't just open a PDF in Adobe Reader instead of the browser. It will instead ask to disable Enhanced Protected Mode to run acroPDF.dll.
And if you try disabling the Adobe PDF reader add-on in Manage Add-ons to try and force it to open in Reader, then when you visit a PDF link, you just get the same blank page (shown below) with the black crossed out circle in the top left, but without the
message bar at the bottom of the window. The only way to open the PDF is to either turn off Enhanced Protected Mode and allow acroPDF.dll to run or if there's an original link to the PDF, right click and select 'save-as'.
I think it's about time Adobe released an x64 PDF viewer... Or at least there should be an open/save dialogue box in IE.
If you've got Reader 11.0.4 installed, you can try it for yourself with this PDF link:
http://helpx.adobe.com/pdf/adobe_reader_reference.pdf
(The below screenshot is with 'Display PDF documents in the Web Browser' UN-ticked in Adobe Reader settings, so it should open in Reader instead. But it doesn't. And with the Reader add-on disabled you get the same page, but without the
message at the bottom.)

FSCT - Having Error "There were errors during running WordFileClose.dll scenario" when running the FSCT in controller & non-windows file server

I encounter 2 errors in the controller when running FSCT.
- "There were errors during running WordFileClose.dll scenario"
- "There were errors during running WordFileClose.dll scenario"
Does anyone has any ideas for this errors?
I am using the following server to run the FSCT:
- AD Server: Windows 2008 R2 SP1 x64
- FSCT Controller: Windows 2008 R2 SP1 x64
- Client: Windows 7 x64
- File Server: Non-Windows Server (EMC Isilon)
And the commands are as follows:
> fsct prepare dc /users 10 /clients testing /password password
> fsct prepare controller
> fsct prepare client /server ofscluster /password password /users 10 /domain abc.local /server_ip 192.168.2.16
> fsct prepare server /clients testing /password password /users 10 /domain abc.local /volumes \\ofscluster\fsroot1 /workload HomeFolders /create_only_fileset
> fsct run client /controller fsctcon /server ofscluster /password password /domain abc.local
fsct run controller /server ofscluster /password password /volumes \\ofscluster\fsroot1 /clients testing /min_users 2 /max_users 10 /step 2 /duration 360 /workload HomeFolders

Dear all,
The errors were:
<Error>1264 DeviceIoControl 1{WINERR}</Error>
<Error>Error executing scenario: WordFileOpen.dll</Error>
<Error>943 DeviceIoControl 50{WINERR}</Error>
<Error>Error executing scenario: WordFileClose.dll</Error>
Do you have any idea about what the errors mean?
Thanks,
Rayson

Trouble with TestStand running VB DLLs compiles in separate threads

I have an application that uses DLLs written in VB 6 to manipulate hardware. The hardware is Stepper Motors controlled via the NI CAN bus card, and two instruments controlled via the GPIB PCI card. I have written the two DLLs to use the same NI PCI GPIB and the same NI CAN BUS card. (One instrument per DLL and One Motor per DLL)
Test stand is then creating the DLLs and running them in separate threads. I have the one DLL Call in a subsequence running as a separate thread, and the other DLL is in the main sequence. I have a GOTO step with preconditions set so that the main sequence only continues after the separate thread in the subsequence is finished.
The problem I am having is that these D
LLs work OK when I run them both in the VB debugger. The program even works when I run the main thread in the debugger, and the subsequence is run compiled.
The problem is, that if I try to run both of these DLLs compiled It seems as if the subsequence DLL never executes.

To Tuxamation -
Nothing comes to mind as to why this would happen. VB 6 automation DLLs are used all the time for code modules.
Note that when MSVB debugs a DLL, it is actually running the DLL as an EXE server within the MSVB process and not in TestStand's process that is using it. I typically found that there is typically a subtle difference in behavior between running the server as an EXE or DLL server.
A simple way to determine if the TestStand call is reaching your DLL is to place a MsgBox function call in the DLL entry point and immediately return, ie. bybassing your existing code.
So, if the call is being made to your DLL, you could then enable the Visual Basic project option on the Compile tab, "Create Symbol Debug Info" and recreate your VB DLL.
You can then attach Microsoft Visual Studio (C++ debugger) to the TestStand process, open the file that contains the entry point in to DLL that TestStand calls, set a breakpoint, and see if the breakpoint is reached.
Scott Richardson
Scott Richardson
National Instruments

How to run a .DLL(created in VB & VC++) in client machine through Java?

Hi Guys,
When i run the .DLL in the server machine through servlets, it opens a
login screen created by .DLL.But I want to run the same .DLL (which inturn
opens login screen) in the client machine in the distributed architecture.Let
me know if u guys are having any suggestions at the earliest.
Thanks in advance ,
Venkat.

Catch up some information on JNI, read the tutorial on
http://java.sun.com/docs/books/tutorial/native1.1/concepts/index.html
Very straight forward, you could make a decision and be on your way to achieve it within about an hour.
Cheers and have a great year.

How to run windows dll files and driver loaded in remote system?

Dear Friends,
I need some valuable info regd how to run a remote windows dll files and the drivers of the system using java
reply regd thanking you

Please don't make duplicate posts like this.

Required Windows updates to run/load dlls created with Visual C++ 2013

I have dlls created with VS2013 C++. Dlls are statically linked with runtime libraries and therefore do not require the redistributable to run on a machine that does not have VS2013 installed.
I have a test machine with Win7 SP1 64-bit without any windows updates. When I try to load a dll created with VS2013 in an executable on that machine, the code dies. Another test machine with windows 7 SP1 fully updated using windows updates loads the same
dll without a problem and the code runs fine.
My question is which windows updates for Win 7 and Win 8 are necessary for dll created with VS2013 to load and run?
Thanks.

I did use dependency walker. In my post above (third post in the thread) I actually state that:
"The code crashes(=dies) on the machine without windows updates. I used dependency walker and there are no missing dlls.
Even if there were missing dlls, which there are none, those would be system dlls, because a machine with fully up to date Win7 loads and executes the code without a problem."
The dll is statically linked (/Mt flag was used). For a good measure I installed redistributable which did not solve the problem. Besides static linking applies to runtime dlls, not the system dlls.

How to run a dll in background

I'm using a dll to control and read data from a camera. The dll is in a loop, in which it reads data from the CCD and moves the data to a memory location passed by labview (an array of uns_16). I want to have this dll running in the background while monitoring the contents with an intensity graph.
the problem is that the data is only displayed on the graph after the dll has quitted (-> all sequences completed).
What is the way ?
Thanx

Sory, I wasnt clear enough. The dll call isnt inside a labview loop. The dll itself calls a loop, i mean a while (...) { read_data_from_ccd(buffer_from_labview); ... }
I want to start my labview VI with a call to this dll, which then goes to background, and then i want the labview program to go on displaying the contents of the "buffer_from_labview" memory area continously, as fast as possible, in an intensity graph.
There is no point in posting the VI, it consist of an initialise array, a call library function node and an intensity graph.
thx !

Cannot run Simulink dll at the same time as running real-time target VI

Hello
What I am trying to do is run a model dll created in Simulink to control some servo's through a CompactRio 9014.
At the moment I have managed to create three VIs
1) In the FPGA target that performs the PWM on a desired channel
2) That takes the value of a network variable which contains the position required and feeds that to the 1st VI
3) A VI that runs on the host computer that modifies the value of the network variable to change the position
I can get these three VIs working and the servo controlled, but when I try to update the value of the network variable using the simulation, by deploying the simulation to the RT target and running it, it says
'Access denied: This target is already in use by another project or host computer.'
I assume as this is because the project is already connected to the cRio, so I disconnect and am able to deploy the model files.
However when I try to run one of the VIs in the RT Targer along with the simulation I get the error:
'This VI is downloaded on the target but is not present in the project you are attempting to deploy. All VIs on the target will be closed unless you choose to add the missing VI to the project.'
With a large number of missing VIs...
Would I be doing this wrong, i.e. is there a much simplier way to control the FPGA inputs using the simulation, or is there something I could have missed?
Thanks
Geoff
Solved!
Go to Solution.

Hi Geoff,
It seems that you are on the right track except for some concepts that I
want to review:
A CompactRIO or cRIO has 3 different components:
1)
Real-Time controller (in your case a 9014)
2)
FPGA backplane (this could be a 9102, or a 9103, 910x,
etc)
3)
I/O modules (like a 9401, 9263, etc)
When you write an application for cRIO you usually have three different VIs:
1)
Host VI – This VI is used as a user interface and runs in
Windows (under “My Computer” in the LabVIEW project) This VI is optional because
you might want to run the cRIO headless.
2)
RT VI – This is the VI that runs in the cRIO controller
(in your case the 9014). This VI lives
under the cRIO target in your LabVIEW project.
3)
FPGA VI – This is the VI that runs in the cRIO
backplane like a 9102. This lives under
the cRIO >> FPGA target in the LabVIEW project.
The ONE application that I was talking about in my last post is for the RT
VI. There can only be one RT VI that
gets deployed. If you want to run
multiple VIs in the cRIO RT, then you need to run those VIs as subVIs of one
top level VI.
LabVIEW Simulation Interface Toolkit (SIT) has a tool called the SIT
Connection Manager that creates two of these three VIs for you (the RT and the
Host VIs).
Please refer to the following link about the SIT Help. Go to the How To section. It is organized in a kind of step by step
tutorial.
http://zone.ni.com/reference/en-XX/help/371504D-01/
In your case it is going to be a bit more difficult because of two things:
One, you are using a VxWorks target.
Two, you want to use your own FPGA VI.
Let’s address each one of them:
1)
VxWorks target- To use the SIT Connection Manager you
need to use a DLL not an OUT file, even though you need the OUT file for the cRIO VxWorks target. The reason is
that this tool needs to read the compiled model to know what the
parameters, signals, inports and outports of your model are. Because the tool runs in Windows you cannot
open an OUT file (meant for a different OS) so you need to give it a DLL.
For this reason you will need to compile your model file into an OUT
file and a DLL. Once you give a DLL to
the Connection Manager and you select your cRIO as the execution target, keep
doing the rest of the steps as the help says.
LabVIEW will identify that you are using a VxWorks target and will
download the OUT file to the cRIO.
2)
Custom FPGA VI – LabVIEW SIT has some FPGA bitfiles
(compiled FPGA VIs) that it can use.
When you open the SIT connection manager and go to the Hardware IO
mapping section it asks you to select the bitfile. If you want, you can select one of the
shipping bitfiles but iIf you
want to use your own, then you will need to do some changes to your FPGA VI , recompile it and
save the bitfile in a specific location with a specific name.
Please refer to the following link for
instructions on how to create your custom FPGA VI:
http://zone.ni.com/reference/en-XX/help/371504D-01/lvsithowto/sit_h_custfpga/
What I would suggest is that you start with a very simple example and using
one of the shipping bitfiles. Look into
the following path for a very simple Sine wave generation example:
C:\Program Files\National Instruments\LabVIEW 8.6\examples\Simulation
Interface\Sine Wave
Because you are running a VxWorks target you will need to recompile this
example model sinewave.mdl to an OUT file.
To get a better understanding of what SIT does you might
want to check some quick videos. Go to
http://sine.ni.com/nips/cds/view/p/lang/en/nid/11763 and under the
resources tab there are two videos called Demo - <something>...
Hope this helps and let me know if you have more questions.
Ricardo
National InstrumentsSystems Engineering

Folder of application builder(*.exe) with run-time DLL

My application consists of main.vi, subvi folder, and example folder.
In addition, I have to add the run-time libraries for add-on tool kit (advanced signal processing, lvwa.dll) which should be located in the root folder.
(For exe application, can I set the location of DLLs to not the root folder but "DLL folder"?)
In my several trials, I can't maintain the hierachy of "example folder".
Instead of my intension, the NI application builder copied the files in the folder to the support directory.
Can I locate the "example folder" to the root folder by using NI application builder?
In summary, I want to get the folder structure by application builder.
main.exe, DLL folder, Example Folder.
메시지가 08-08-2008 01:30 AM에 labmaster에 의해 편집되었음

Hey Labmaster,
What version of LabVIEW are you using?
I am not too clear as to what you are trying to do. You can create folders and add anything from your project when creating an installer under the Source Files section in its properties.
It might be easier if you'd attach a screen shot of what you are doing or trying to do.
Aashish M
Applications Engineer
National Instruments
http://www.ni.com/support/

DW won't run - mfc110u.dll missing on PC - What should I try next?

I've just tried installing and uninstalling DW CC 3 times. Once even on the actual Admin User Login account.
I keep getting the message "The program can't start because mfc110u.dll is missing from your computer. Try reinstalling the program to fix this problem".
I am running Windows 8.1 64-bit.
Any ideas what I could try to fix this issue?

Hi Jon and others,
Thanks and others who tried to help. The problem has been solved, before you responded, as I was so keen to get Dreamweaver to load I kept trying and trying and finally I managed to get it to load.
What didn't work:
Simply installing the Microsoft C++ re-distributable Upgrade 2013 by Microsoft - over a completed Dreamweaver installation.
When trying to run Dreamweaver, even though initially the Dreamweaver application reported a successful install that error message kept popping up
What did work:
Uninstalling all my old Redistributable Upgrades in the Microsoft Remove Programs Uninstaller
Then uninstalling Dreamweaver with all my saved settings removed as well. I had no saved settings btw.
Then installing Microsoft C++ re-distributable upgrades for both, 32-bit and 64-bit.
Then restarting the machine.
Then reinstalling Dreamweaver via the Cloud installer interface.
After that Dreamweaver loaded up. Hooray!
Maybe some of the things in the list above was unnecessary, but the combination of all did fix my problem.
Hope this will help others as well, should they get the same issue.
Happy computing.

Running external *.dll's on NI CVS-1450

I have yet to install and use the NI CVS-1450. The hardware is available, but the VI's and code have yet to be fully developed. Before I seek permission from the network security guys to install hardware and software, I'd like to know if my end goal is feasible.
I believe in Labview on my desktop I can call externall code libraries written in C, *.dll's, and use them in an integrated way with the rest of my VI.
Is it possible to do the same exact thing with the CVS-1450? Having no experience with the 1450, my question may not be worded correctly. Is it possible to upload the C *.dll's on the 1450 and have the Labview routine running on the 1450 call those *.dll's?
All feedback appreciated.

Apologies, I believe this post answers my question:Can I use external code on CVS 1450 with LabView RT 7.1?
http://forums.ni.com/ni/board/message?board.id=170&message.id=88311&query.id=91090#M88311

VI on LabVIEW real-time is loading and running a DLL which has been deleted from the machine

OK, this is a weird one (at least, to me :-) )
I have a small real-time demo application VI that I am writing, using some new VIs I just created. My new VIs are wrapper functions for a DLL, using Call Library Function Nodes.
In the process of debugging, I decided to delete the DLL and run without it, to confirm that I am actually loading and using the DLL (since it seemed to have stopped doing something it had successfully done just a little while earlier).
The VIs that use that DLL still run, and at least some of them actually do what they are supposed to do. But the DLL does not exist on the real time machine! Not only did I delete it, reboot the machine, and check that it was gone, but through my ftp program I searched the whole hard drive for that DLL and did not find it (the search succeeded in finding a different DLL which did exist on the system, so the search-via-ftp is working).
How could this happen? What am I missing? Could this somehow be the result of a corrupted VI or is there some more logical explanation for the phenomenon?
Thank you.
Batya

Nathan is right at least for the Phrlap ETS based RT systems. For VxWorks you have to (or maybe used to have) to download the shared library to the controller before you could deploy an executable that makes use of them. For Pharlap ETS systems if you deploy a VI library dynamically to a machine it will download everything including shared libraries to the the RT target memory and run it from there. Only if you create an executabel and "install" it to the target and run it from there will it use whatever VIs are in the executable and also use the shared libraries that have been installed onto that system (at least for Pharlap ETS RT targets. As mentioned before for VxWorks targets, the deploy process even for executable installation did for some reasons not take care about moving the according *.out library to the target together with the rtexe).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Running a .dll in a .VI

Similar Messages

Maybe you are looking for