Jump to content
Tomi Maila

A Rolf Kalbermatter Article - External Code in LabVIEW

Recommended Posts

I'm very excited to announce that Rolf Kalbermatter will be blogging a series of articles on LabVIEW external code interface at Expressionflow. The first article in the series is

To avoid missing the next articles in the series, please subscribe to the Expressionflow feed with your favorite feed reader.

Tomi

  • Like 1

Share this post


Link to post
Share on other sites

Rolf Kalbermatter has posted two interesting articles in the series External Code in LabVIEW at Expressionflow.

External Code in LabVIEW, Part 2: Comparison between shared libraries and CINs.

Not looking at ActiveX and .Net since they both are Windows technologies only and are not really suited to integrate generic external code into LabVIEW, there remain two similar possibilities nowadays to integrate external code into LabVIEW. These are CINs and shared libraries through use of the Call Library Node. While CINs used to have certain advantages over shared libraries in the past this is basically since about LabVIEW 6 not true anymore and with LabVIEW 8.20 the Call Library Node got additional features that remove the last (esoteric) advantages CINs had over shared libraries. On the other side the use of shared libraries through the Call Library Node has quite a few advantages.

In this article I will try to compare the most important differences between these two thechnologies and try to make a point, why anyone should nowadays go for the Call Library Node with shared libraries instead of using CINs....

External Code in LabVIEW, Part 3: How to use Call Library Node properly to ease multi platform support

Shared libraries are since about LabVIEW 6 the preferred way for use with external code in LabVIEW. While they can directly interface with many existing shared libraries for the platforms LabVIEW supports, they can also be used to interface to shared libraries that were specifically developed for use with LabVIEW. And one of the very neat features of LabVIEW itself is its multi-platform support. This multi-platform support can even be taken to external shared libraries that were specifically developed for use with LabVIEW. If one observes a few rules and makes smart use of some not very well documented facts and features of the Call Library Node, this will result in a very easily maintainable solution both in terms of the C code as well as the LabVIEW VI libraries....

To avoid missing the next articles in the series, please subscribe to the Expressionflow feed with your favorite feed reader.

Share this post


Link to post
Share on other sites

QUOTE(Irene_he @ May 21 2007, 08:49 PM)

This is very good, thank you Rolf and Tomi.

Don't thank me. All the honor belongs to Rolf! ;)

Tomi

Share this post


Link to post
Share on other sites

Hi Tomi,

are these links taken off ?

I would like to gain some knowledge on these topics. can you please provide the links or the content in some other form if links dont work anymore ?

i would greatly appreciate it.

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.