Thread: Native call
View Single Post
  #2   Spotlight this post!  
Unread 18-12-2010, 09:32
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Native call

There are several ways to use the CLF (Call Library Function) node, but the typical is simply to input the name of the library in the dialog. The checkbox beneath lets you expose the param and dynamically load the library. For RT, I'm not sure there is any difference between the two options.

You'll notice that many of the NI DLF nodes use name.* so that the code will more easily port to different OSes. This minimal spec will tell LV to use the normal library search mechanisms for the OS and use the LV search paths. It will also use the typical OS suffix.

If you still get this message, give a bit more info as to when it shows up.

One trick in LV is to ctl-double-click on a subVI to open the subVI with the diagram opened on top.

Greg McKaskle
Reply With Quote