Code interface Node:call Interface Node No longer Supported

[mikewieliczki]

That said, that is a temporary workaround.  CIN's should be replaced with Call Library Function Node ASAP - as they are no longer supported in LabVIEW.

Thanks @softball for the for the CIN link:

Archived: LabVIEW Code Interface Reference Manual (December 1997) - NI

[rolfk]

---

@mikewieliczki wrote:

That said, that is a temporary workaround.  CIN's should be replaced with Call Library Function Node ASAP - as they are no longer supported in LabVIEW.

In my not very relevant opinion this should rather read:

CIN's should have been replaced with Call Library function Nodes 15 years ago already!

[softball]

Hi

Rolf is modest when stating CIN's should have been replaced 15 years ago.

I noted this paragraph in a NI-DAQ 6.7 release readme from 1999 :

*** Changes to LabVIEW for Windows Data Acquisition Library LLBs

As of NI-DAQ 6.7, the LabVIEW for Windows Data Acquisition Library LLBs shown below (installed in <LabVIEW>\vi.lib\daq) now contain function calls to a dynamic link library (DLL) called LVDAQ.DLL.

This DLL is located in the same directory as the LLBs and replaces the code interface nodes (CINs) that were previously embedded in each VI.

So, NI already replaced some/all CIN calls 25+ years ago.

Regards

[rolfk]

NI started replacing all CINs ca. LabVIEW 5 (1998) and by LabVIEW 7 (2003) had finished that process pretty much completely in all shipping libraries.

I was just giving a little leeway to end users 😀

[banksey255]

One NI didn't include in that that I'm aware of is their Dynamic Data Exchange library, which still uses CIN, and because that's one example shipped with LabVIEW, I presume there is the possibility of others. I wonder if all shipping libraries that still use CIN will now no longer be shipped with LabVIEW.

[rolfk]

Considering that DDE is something that Microsoft would wish they could burry under a rock that nobody is ever going to lift again, I don't think you can blame NI for not having ported that. In fact it has been removed from the palettes since about LabVIEW 8 and the library simply ships for backwards compatibility. But it was never ported to 64-bit (technically impossible since 64-bit CINs never officially existed). While there were some attempts to enable 64-bit CIN support in LabVIEW by some people on LavaG, this eventually got a useless exercise since NI actively removed the support code for CINs in 64-bit LabVIEW around 2020, so even with backdoor tricks it could not be enabled anymore. Technically a CIN is a DLL too in principle, but with a very specific function interface, that must export at least one function and optionally 4 or 5 more. And it needs to be linked with specific object code to interface to the LabVIEW CIN interface. So the technology would work for 64-bit just as much but it is an interface that is quite work intense to maintain, support and keep working across multiple platforms, both for NI and any 3rd-party wanting to create a library with CINs.

Rumors has it that whoever wrote the DDE CIN and library, took the code to wherever they went and NI wouldn't really be able to recreate that without rewriting it from scratch, even if they wanted to. Of course they were not inclined to do that when LabVIEW 8.0 was released and are nowadays even less, if that was even a possibility.

And LabVIEW 32-bit will at some point be sunset. After that day there is simply no way anymore to run VIs containing CINs.