CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

CIN(Code Interface Node)

NI engineers:
I am one of your users (labVIEW 6.1).
Now, I have some questions to ask you. Please give me some help.
I try to use the CIN(Code Interface Node) function, but I can not pass compile.I do not know why?
The c file is very simple, and the Compiling result is as following.
Please help me to solve the problem.
Thank you !
Chenyong
2002/7/7
* CIN source file
#include "extcode.h"
CIN MgErr CINRun(int a,int b,int c);
CIN MgErr CINRun(int a,int b,int c) {
/* ENTER YOUR CODE HERE */
int a;int b;int c;
a=1;b=2;
c=a+b;
return noErr;
--------------------Configuration: try - Win32 Debug--------
Compiling...
629.c
c:\labview\labview 6.1\z_beginner\629.c(17) : fatal error C1010: unexpected end of file while looking for precompiled header directive
Error executing cl.exe.

Hallo
re-declaring the parameters as local variables will prevent the function to do what you expect.
But your error is more probably a problem the compiler configuration. Make sure the path to the include file extcode.h (and all it's own includes) is known to your compiler.
Gabi
7.1 -- 2013
CLA

Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

Hi all,
I'm having a peculiar problem.
I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding". Error message pops up, then all LV windows close.
It's very similar to that described in here:
http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help.
Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
Finally, I manage to get this out of it:
FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000012D4: A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
I don't think that really helps at all, but it's there.
Here is the function prototype of the .dll:
void _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
(never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))
I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file.
I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
Any ideas? Thank you for you help.
Regards,
Mark G
Solved!
Go to Solution.

MarkCG wrote:
Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But The call type makes no difference when using LV 8.6 on the same machine, however.
Now I've got to make the .DLL run corretly on a compact fieldpoint.... and avoid crashing IT.
Thank you for the help all!
Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Code interface node.

I'm trying to determine if using the CIN and c code will increase the speed
of some simulations that I'm doing. Does any one have some examples of how
to do matrix operations or array operations in visual c++ version 6.0? Any
help would be much appreciated.

Yoichiro wrote:
> How is what is necessary just to make arrangement (for example, Sine?Wave)
> using Code Interface Node? Please teach me a way.
Have you read the online documentation under "Search the LabVIEW
Bookshelf" and there the selection "Using External Code in LabVIEW (PDF
Only)"
You need Acrobat Reader on the computer to read those informations but
it explains basically anything you probably want to know about that.
Now, why you want to create a CIN to generate a Sine Wave is another
question. LabVIEW Full Development System and higher comes already with
VIs to do that, and even if not it would be a lot easier to create a G
code VI to generate a Sine Wave than it would be to generate a CIN even
if you already knew how CINs are created.
Rolf Kalbermatte
r
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Code Interface Nodes and multithreading (openMP)

Hi,
We are experiencing a rather strange problem with the use of Code Interface Nodes (CIN) in LabView. The CINs are built with the Intel Compiler in the Visual Studio .NET 2003 IDE and use the openMP directives to easily implement multithreading. This does not seem to give any problems, as long as we do not declare our code threadsafe. If the code is declared threadsafe, everything runs smoothly but LabView crashes when the VI where the CIN is located is closed. If we do not declare the code threadsafe, there is no problem but our user interface is blocked during execution of the CIN. Since we are building an application for other users this is not acceptable.
It clearly has to do with the multithreading, because forcing the compiler to create sequential code solves the problem. But off course we don't want to implement multithreading to disable it afterwards.
We could switch to DLLs, but we are building an exe version which is under full development and can be updated by our users through the internet. Since CINs are part of the exe file itself and DLLs are not, we would like to keep it this way.
We know this is a very specific problem, but we do not know if the problem is related to the multithreading in general or to the use of openMP in particular. Has anyone else tried multithreaded CINs and experienced any problems ? We basically just want to be able to stop the CIN from using our user interface, since we know everything is threadsafe.Message Edited by Raistlin on 05-07-2005 07:34 AM

I have tried putting the vi in another execution system (standerd,other 1,other 2, ...) and the problem persists. I now built a DLL and have the same problem : marking it as reentrant makes the vi crash at closure, marking it as running in the UI does not give a problem. I now sent some code to Intel to check the thread safety, but I am quite certain there is no problem there.
I found another thread where the problem was mentioned but also without an answer that could get me any further :
http://forums.ni.com/ni/board/message?board.id=170&message.id=47264&requireLogin=FalseMessage Edited by Raistlin on 05-10-2005 02:04 AM

Please teach me how to make the arrangement using Code Interface Node.

How is what is necessary just to make arrangement (for example, Sine?Wave)
using Code Interface Node? Please teach me a way.

Try to get hold of the 'Advanced Analyis' library for labview. It contains VIs for doing FFT! No need to reinvent the wheel.
If you can't get it and want to take the hard way, try to learn CIN programming by
- reading the manual (no joke or cynism intended)
- look for advice in NI's developer zone (www.ni.com/devzone) by using the search phrase 'CIN tutorial': you'll get several links which should be helpful in your case.
- better than a CIN: try to use the DLL calling mechanisms and compile your C code into a dll. In order to learn dll intewrfacing for LabVIEW, follow the route explained under point 1 and 2 above...
Good luck,
Franz

Installing Labview runtime engine 2011

Hi,
Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ?
Thanks.

No, you should actutally keep the older runtime engine installed in case you still have applications that depend on it. The 2011 run time will only support applications built with LabVIEW 2011.
LabVIEW Champion . Do more with less code and in less time .

How does a CIN code works in LabVIEW?

hi..can any one explain as to how a CIN code (written in c/c++) works in LabVIEW.Do we have to import the c/c++ file too when we import the respective VI? How does the CIN code work in an exe file without having to load the C/C++ code?

When you create the VI that calls the CIN you load the binary object code into the code interface node itself and it's stored as part of the VI. Hence you don't need to include anything special in your build. Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How do I tie an Code Interface Node to the dos command prompt or Windows FTP stuff

I have tried to use the System Exec.vi to do some ftp-ing with a box that If developing an automated ATP for. The sys exe vi dose most of what I need but not all. I can not modify the sys exe vi, nor can I copy the code interface node to another vi,I think that is because it has been compiled. So I need to generate my own vi that call the Windows ftp stuff or command prompt. I have spent several hours searching the NI site and the web in general and have not been able to find what to link the CIN to.
Can somebody please explain this to me?
I'm using:
LabVIEW 8.6.0
Windows XP Professional with service pack 3
Thanks
TeBlues

Yes this is related to the post of yesterday. I tried your suggestions yesterday and was unable to get any of them to work.
I down loaded the ftp library form OPENG and was unable to get it to connect to my box under test, and was unable to find any helping documentation on the OPENG site.
I down loaded the vi from the earlier post you referred to and do to my lack of knowledge of windows was unable to figure out how the incorporate it in to my vi. For example what is the "lpsz Window?
To complete this project I'm having to go deeper in to the stuff that goes on behind the seen than I have ever need before. So to me it looked like the next steep is to create a vi that used an CIN similar the the sys exe vi but add a few things around it..
If this is wrong, What do you suggest? Keeping in mind I do not have the internet tool kit and the project dose not want to purchase it if we can avoided it.
Thanks for your interest and time
TeBlues

Win32 API calling by Code Interface Node

Hi all,
I wish to call a Win32 API function by using the code interface node.
However, I don't know the data types in LabVIEW corresponding to the "HANDLE
*" in Visual C++.
Here's the function I wish to call:
BOOL bOpenDriver (HANDLE * phDeviceHandle, PCHAR devname) {
*phDeviceHandle = CreateFile(devname,
GENERIC_WRITE,
FILE_SHARE_WRITE,
NULL,
OPEN_EXISTING,
0,
NULL);
if (*phDeviceHandle == INVALID_HANDLE_VALUE) {
return (FALSE);
} else {
return (TRUE);
Thank you in advance.
JJ

If this is really a Windows API function, then the handle can most likely be treated as an I32.
Note that you can't actually do anything with the handle other than passing it to other functions.
If you search this site for "LabVIEW" and "DLL" you should find some resources about working with DLLs and Win32 API DLLs.
Try to take over the world!

Code interface node - .lsb generated but does not load

Howdy,
i am using labview 6.1 and VC++/visual studio .NET 2003.
i tried creating a simple code interface node to add two numbers. i followed the steps given in the "Using External Code in Labview" Manual. I made only one change, which is switching out "$(WkspDir)\$(OutDir)" (under custom build) with "$(ProjectDir)$(OutDir)" as the $(WkspDir) macro is missing from VC++.
The build occurs successfully and i get a .lsb file. But when i ask the code interface node to load it up, it doesn't. The error description is, "Code Interface Node: object code not loaded."
any suggestions? thanks in advance.

Hi,
This KB describes what may be the issue. I hope this is helpful.
Regards,
Ankita

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Labview runtime engine plugin problem in Mac OS X

Hi:
We have just recently acquired a macBook Pro and am trying to test some instrumentation modules we have previously developed online for Circuit Theory courses on the MAc platform.
These VI's are installed on lab view server and we have no difficulty accessing them in Windows XP or Vista from a browser either Firefox or IE. Of course the latest version of runtime engine is installed on the pc prior to accessing the vi using remote panel and secondly we have to disable any virus protection software.
I have also installed the 8.5 version of LV runtime engine on the macbook with Leopard 10.5.x OS. I can see the LV plugin with the proper version in the Installed plug in check for the Safari browser. But every time the Remote panel is accessed I get a missing plugin message.
Here is the message:
Safari cannot find the Internet plug-in.
The page “Blackboard Academic Suite” has content of MIME type “application/x-labviewrpvi82”, but you don’t have a plug-in installed for this MIME type. A plug-in should be available on this page:
http://digital.ni.com/express.nsf/express?openagent&code=exck2m&
Do you want to open the page?
The page it suggests is the NI site for the plugin download?
I am really in a corner and donot know what I am doing is wrong? Any help will be appreciated?
Vishnu

I'm not a Mac expert, but it sounds like you are missing the LabVIEW Browser Plugin which is necessary to view remote front panels. That plugin installs with the LabVIEW runtime engine which you can find here. I don't think Safari requires any extra configuration to work with the plugin but it might... let us know if installing the runtime engine doesn't resolve the problem.
Travis M
LabVIEW R&D
National Instruments

LabVIEW Runtime Engine 2010 NI_AALPro Error

Hi All,
I have an problem with the executable version of my LabVIEW program. I just created an LabVIEW program in LabVIEW Professional 2010 version to acquire some FFT spectrums so it also use some function palettes of Sound and Vibrations toolkit like Power Spectrum, Peak Search, Power in Band etc.
Then I just created an executable version of the program to run on a different system (Tools>>Build Executable Verion(EXE)). But when I tried to run the executable verion on a different system is showed some errors. I am attaching a printscreen of all errors showed.
So, the executable version of the program is working fine in the develoment system but showed some errors when we try to run it on a different system. We have already installed the LabVIEW runtime engine 2010 as well in the second system.
My one more question is when we build an executable version of a LabVIEW program then it should run on all PC without any other software (Runtime engine) because it got an extension of .exe
so is there any chance or way to build a totally standalone executable version of the program without using any runtime engine as well.
Thanks
Attachments:
error.JPG ‏28 KB
dll & lvlib.JPG ‏41 KB

Hi PSBRRR,
It seems like you didn't include all the dependencies of your VI or project to your build specification. Can you send a screenshot of the Source Files Setting page of the Application Properties dialog box ? You have to add all the VIs and DLLs that are used in the Sound & Vibration toolkit and any others you are using to your executable file or support directory.
For the last question : no you can't. Since LabVIEW 2010, the Run-Time Engine is like the "Java Virtual Machine". The compiled code inside your EXE is interpreted by the "LabVIEW Virtual Machine" included in the LabVIEW Run-Time Engine. That's why it requires the Run-Time Engine to be executed or at least the development environment (previous versions of LabVIEW didn't use this principle but it was also required to have the Run-Time Engine installed).
Regards,
Da Helmut

CIN (Code interface node) LabVIEW runtime engine dependency

Similar Messages

Maybe you are looking for