LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Anybody used nodetalk32.dll in LabWindows CVI

Hi we have an old application in LabWindows CVI using nodetalk32.dll to setup echelon chip related hardware. We would like to upgrade this software to Windows 10 PC. we can not find nodetalk32.dll. is it possible to use the old version .dll and the CVI codes will still work? Thanks.

0 Kudos
Message 1 of 4
(1,393 Views)

Hi,

I don't know what nodetalk is, but if you have the .h and the dll, there's no reason you can't create an export library and use it in your 32 bit project.

0 Kudos
Message 2 of 4
(1,370 Views)

Thanks. We upgraded the baseline cvi codes to current cvi version without broken errors. does this mean that we can run the application? there is one place that define the hardware name, like "LON1", now we use different hardware, if we change the hardware name in the source codes to match the correct hardware name in the PC system, will we be able to run the application? Thanks.

0 Kudos
Message 3 of 4
(1,364 Views)

This kind of answer can only be given from someone with access to the source code of nodetalk32.dll. It seems to be related to LON network communication, according to the very few links that can be found online. As such it is probably a proprietary solution for a possibly proprietary hardware that may or may  not work under Windows 10. There isn't to much activity in LON after 2010, even though that they claim in the Wikipedia page for LonWorks that there were a "whooping" 90 million devices talking LON, by the end  of 2010. I guess that there still might be quite a few devices out there, but that LON has gotten a bit of a liability in a more and more hostile cyber environment and that many have since moved to more mainstream internet based protocols with the necessary encryption technology that is to complex to get tackled by a single entity.

 

For reliable information about nodetalk32.dll compatibility with newer Windows versions you really will need to find the manufacturer of that DLL. Nobody else can give you more information than some more or less educated guesses. It's definitely not, and never was, a standard DLL that comes with Windows.

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 4
(1,307 Views)