A Rolf Kalbermatter Article - External Code in LabVIEW, Part1: Historical Overview

[Tomi_Maila]

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

External Code in LabVIEW Part1: Historical Overview

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

Tomi

[Tomi_Maila]

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

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.

[freemason]

Hi Tomi,

can you resurrect the links please, says not found on expression flow.

Thanks

[jcarmody]

http://web.archive.org/web/20070525153607/http://expressionflow.com/?

The Wayback Machine has it.

[freemason]

Great,

Thanks

[Tomi_Maila]

Sorry the old data is lost unfortunately.

[freemason]

http://web.archive.org/web/20070525153607/http://expressionflow.com/

Thanks to jcarmody

[rolfk]

Or you can go here now, to read the resurrected data on a blog I recently started:

https://blog.kalbermatter.nl

I still need to reactivate the link for the Taskbar library on there, but everything else is there.

[Ben]

Hi Rolf,

Under the section for LV 6 you wrote...

"

This were external code fragments not loaded into the VI itself but instead being left as independent files on the file system,

"

Should the word "this" actually be "These" ?

Yes that is being asked by someone with no ability to spell or type BUT I just wanted to make a most excellent blog "perfect in every way" (see Marry Poppins) !

Ben

[RavensFan]

---

Ben wrote: BUT I just wanted to make a most excellent blog "perfect in every way" (see Marry Poppins) !

Or do you mean Sharry Bobbins?

---