Anyone made use of the "Call Library Node"?

[gvarndell]

I would like to hear from any teams that have used the LabView Call Library Node to call C code in their LabView robots.
Our team is solidly hooked on LabView, but (looking forward already to next year) I would like to explore this as a means of compromise.
Much to my dismay, my daughter is kind of taking to LabView but still wants to learn C.
Anyway, good or bad experiences, failed or successful, please share your tales.

[Omar]

Originally Posted by gvarndell

I would like to hear from any teams that have used the LabView Call Library Node to call C code in their LabView robots.

I have not used it on a Robot, but use it all the time for work related projects.
But the way "they" have the FRC cRIO configured (locked) you might not be able to mix the two.

You might want to ask on the WindRiver C++ Sub-Forums if anyone has been able to create and deploy a dll. For if they are able to create one, deploy it and then use it on a FRC cRIO, then LabVIEW should be able to run it also.

[Greg McKaskle]

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