Effeciency of HDL Interface Node compared to IP Net

Hi,
If I use HDL Interface Node for VHDL code in FPGA VI, Will it be more efficient than IPs which are available at http://www.ni.com/ipnet/ ?
Kindly guide me.
Thanks and Regards,
Rashid
Solved!
Go to Solution.

Hello Rashid,
IP on IPNet will be written using CLIP which is much better for implementing VHDL into your LabVIEW FPGA code. The following document discusses some of the differences between the two.
http://digital.ni.com/public.nsf/allkb/ce502221933fcceb8625750000011fb5?OpenDocument
Also, something to keep in mind, as of LabVIEW 2010 the HDL node will be deprecated so for future compatibility, you are better going the CLIP route.
David_L | Certified LabVIEW Architect
LabVIEW Tools Network | LabVIEW Tools Network Developer Center

Similar Messages

How to use netlist of verilog hdl code in hdl interface node

Hello,
In labview 8.6, hdl node doesnot support verilog. I studied that netlist can be used in hdl interface node. How can I use netlist of verilog hdl code, in hdl interface node.
Please clarify
Thanks
Prashanth

Check out the given link. Similar problem is discussed over there.
http://forums.ni.com/ni/board/message?board.id=170&message.id=253724&requireLogin=False

Unable to find HDL Interface Node

I have MyRio and LabView 2014 with all the modules installed and updated.
Xilinx 2014 is also installed and I can compile for FPGA.
However in block diagram I can't find HDL interface Node for importing VHDL code. As you see in the second screenshot.
How may I solve this issue?
Solved!
Go to Solution.

You mean that IP Integration node?
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

HDL Interface Node (UsingFilterCore.vi) and "timing constraint" error when compiling

I'm trying to use the HDL interface node in LV8 FPGA with a PCI-5640R and had the "timing constraint" error when compiling my VI, however, the same VI was successfully compiled on a CRIO-9104, it seems the FPGA on PCI-5640R is not good as the one on CRIO-9104, or I'm not using it right. could you please kindly help me out?
I tested it with the sample code downloaded from NI website
( http://zone.ni.com/devzone/conceptd.nsf/webmain/456722DDDE17986A86256E7B0065EE6F ) which demonstrates using an IP core for a filter. To simplify it, I only keep the HDL Interface Node and the While Loop (see "UsingFilterCore.vi" in attached zip file), and then I created 2 projects including this VI (1 for CRIO-9104, in sub folder "CRIO-9104", the other for PCI-5640R, in sub folder "IFRIO 5640"). When opening the 2 projects separately in LV8.0 and selecting the VI for compile, the one for 9104 passed and the other failed. Here I attach the source code, error message screenshot and the NIReport from MAX, hope you can reduplicate the problem.
Can you help me out？ Thanks very much !
Message Edited by Jerry_L on 03-26-2006 09:28 PM
Message Edited by Jerry_L on 03-26-2006 09:29 PM

Hi Jerry,
I'm just tried to make all these steps by myself (http://zone.ni.com/devzone/cda/tut/p/id/3516). I have generated FIR filter using Xilinx ISE and got *.VHD file which was going to use in HDL Node.
In the Parameters tab of the HDL Interface Node configuration dialog, double-click in the Names column to add parameters. Create parameters as shown below.
Next, switch to the Code tab. Notice that your parameters now appear in the entity section. To complete the next two sections of code, you will need to refer to the filt.vhd file that you generated earlier and interface the filter core to the LabVIEW FPGA execution system.
1. The first problem I met was integrating VHDL code from earlier generated *.VHD file to CODE tab in properties of HDL Node. Content of entity section in *.VHD is not the same that in your attached file. Please check it in attached files. I'm sure this is the main reasen of problem.
Next, switch to the External Files tab. Click the Add File button and select the filt.edn file that you created earlier. This is the EDIF netlist file that you generated earlier.
2. I have no idea where can I get it and when during filter generation using Xilinx ISE it was generated too. How can I get it? I had to use your attached file filt.edn.
3. After that I have made the same schematics like you have in your VI FPGA and try to run. But I've got two error messages:
HDL Interfave node: enable chain not handled. Details: Refer to the documentation for the correct assignments for the enable_out output from your HDL code.
HDL Interfave node: output not handled. Details: Right-click the node, select Configure to open the Configure HDL Interface Node dialog box, and use the Code tab to handle all output parameters.
Actually I need to model FIR filter:
Bandwidth 200-600 Hz
Sampling 8 KHz
Attenuation 80 dB
That's why I tried to follow all these steps by myself to understand how does it work.
Thanks a lot.
Nikita
Attachments:
Filter1.vi ‏16 KB

Design a 32bit counter using HDL Interface

Hi,
I am new to Labview FPGA, and i am trying to explore the HDL interface node in Labview,
i could sucessfully implement an adder and MAC using the same interface,
and tested the same using a File IO.
But the problem araised when i tried implementing a counter code using the HDL Interface,
the values i observed in the display panel and in the File output are not producing any count.,
is there any care to be taken for implementing the above, the same VHDL code is tested for
producing the count using the simulator.Below is the code which i tried to implement
process( clk, reset )
begin
    if( reset = '1' ) then
       debug_out <= (others=>'0');
         debug_cnt <= (others=>'0');
    enable_out <= '0';
    elsif rising_edge(clk) then
         if (ErrorIn(0) = '0') then
              debug_out <= debug_cnt;
               if(debug_cnt = X"000000FF") then
                        debug_cnt <= (others=>'0');
               else
                       debug_cnt <= debug_cnt + X"00000001";
           end if;
         else
                debug_cnt <= (others=>'1');
         end if;
      if( enable_clr = '1' ) then
        enable_out <= '0';
      elsif( enable_in = '1' ) then
        enable_out <= '1';
      end if;
end if;
end process;

Hi Ipshita,
Thanks a lot for your reply,
1. By 'display panel' do you mean front panel?
       Yes! i mean the Display panel means the Numaric Indicator in the front panel.
2. Are you sending this counter data to a file and if yes, what kind?
     Yes! am sending the output data to a file, am wiriting the data to a binary file.
3. By "it works with the simulator" do you mean that with an actual
FPGA card it is producing no data in the front panel and file?     Yes! it works well when i checked with my modelsim simulator, but when using the Labview FPGA i could not get proper output.
Anyways am attaching the VI project, please go through and let me know,if some problem is there with the design
Thanks & Regards
KalyanSuman.KV
Attachments:
RegDelay.zip ‏123 KB

Difference between Interface node and normal node?

What is the main difference between Interface node and normal node?
Cheers
Aisurya.

Hi surya,
Interface node or methods comes into picture whenever you want to use one component as used component. I mean to say
Component usages. If you select node as interface node, it will available in another component so you can use that node or methods.
Normal node means in that component only. Simply we can say for component usages we go for interface nodes.
Cehck This...
http://help.sap.com/saphelp_nw70ehp1/helpdata/EN/79/555e3f71e41e26e10000000a114084/content.htm
Cheers,
Kris.

Access an interface node : the mapping has not been completed

Hello all,
by getting an element of interface-node within a component I get follow error message
"the mapping to node COMPONENTCONTROLLER.1.INIT_DATA" has not been completed"
Can anybody say me, what does it mean?
Some more information (in case for somebody need it):
1. I have a component A, where I have defined usage component of component B.
2. Component B has an interface node INIT_DATA, which is mapped with the node INIT_DATA of component A.
3. I set attributes of node INIT_DATA of component A and expect, that those values will be assigned to the node INIT_DATA of component B (becouse they are mapped)
4. by doing it within a component A:
lo_node = wd_context->get_child_node( name = if_componentcontroller->wdctx=>init_data).
lo_elem->get_element( ).
lo_elem->set_attribute(....).
I get this error message:
"the mapping to node COMPONENTCONTROLLER.1.INIT_DATA" has not been completed"
Please let me know, what I do wrong?
thanks in advance
Anna

Hi Anna,
You should not be having the node INIT_DATA defined separately in both components. It should be defined only in component B and marked as Interface node. Now when you define a usage of component B in component A, you will be able to see this node. You need to map this in component A by drag and drop.
Also, in the properties tab of the component controller of component A, declare the usage of component B using the F4 help. I think that should solve your problem.
Regards
Nithya

External component usage with interface node

Hi everyone,
I have component A , which has an interface node with Input element checked:
Nodes
Node Name     IF_HROBJID
Interface Node     1
Input Element (Ext.)     1
Dictionary structure     ZHR_HROBJID_LIST
Cardinality     0..n
I have another component: Component B Where I want to bind a table to this interface node.
In component B :
1. I definied the Componenet Usage of component B in the componenet controller.
2. I drag & drop the IF_HROBJID node to the component controller's context (the node is mapped)
But when I try to bind a table, I always get the " The Mapping to Node COMPONENTCONTROLLER.1.IF_HROBJID Has Not Been Completed. " error.
nd_if_hrobjid = wd_context->path_get_node( path = 'IF_HROBJID' ).
nd_if_hrobjid->bind_table( lt_if_hrobjid ).
Can someone tell me what is the problem, and how can I solve it?
Thanks
N.

Hi,
Here you are trying to use component A in component B right?
Then what you need to do is:
1. Declare the component usage of A say A_USAGE in properties tab of component B.
2. Create a node say 'DATA' in component controller of component B. The node 'DATA' would have the same structure as the node in your component A.
3. Fill the node 'DATA' in component controller's method.
4. Under your webdynpro component B, you will see Component Usages -> A_USAGE. open interface controller inside that.
    Goto context tab and drag the 'DATA' node from component controller of B on to the node in interface controller.
Hope this is clear!
Best Regards,
Srilatha

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 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

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

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

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

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

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

Effeciency of HDL Interface Node compared to IP Net

Similar Messages

Maybe you are looking for