Thread: Anyone made use of the "Call Library Node"?
View Single Post
  #3   Spotlight this post!  
Unread 23-02-2010, 20:15
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: Anyone made use of the "Call Library Node"?
NI makes use of the Call Library function in a number of places in the framework. It is not locked. The only things not visible and open are the elements that implement safety protocols. I believe this is identical across all of the languages.

The Call Library Function node is used to call into an existing .out file on the cRIO or a new .out file that you build and deploy. The difficult part of doing this will be debugging any issues within the .out or in the calling of the .out. In order to successfully use this feature, you actually need to know both languages quite well. Once you have enough experience, this is a very powerful way to combine high level and low level languages to gain the benefits of both.

Greg McKaskle
Reply With Quote