Working with .net dll

[john_joe]

I've never called a custom dll before so please bare with me. 

I am working with a Kawasaki robot and there are .dll files that can be used to communicate to the robot. I am trying to integrate these dlls into labview but have no idea on how to do this. I believe the are .NET 4.0 dlls but opening them with the .NET constructor instruction causes errors. I've attached the .dll and the help files provided with them. Any support would be apricated!

[ShockHouse]

1. Are you using LabVIEW 64-bit? Based on the name of the dll it's 64-bit.
2. Have you used something like Dependency Walker to see if there are additional dll dependencies it can not find? 

[Kyle97330]

In addition to the two items ShockHouse mentioned, which are very common issues, another one to check is to see if Windows has blocked access to the DLL.  A lot of times, when you get a DLL via a method other than a signed installer, Windows blocks access to it in the name of security. 

If you right-click it in Explorer and select "Properties", it might reveal an "Unblock" button that you have to press.

[john_joe]

I am using Labview 64 bit. I went into the properties of the DLL and unblocked it.

Using the dependency software, it found no missing dependencies

[Kyle97330]

Can you be more specific on the error that the constructor node gave you?

Option 1:

This usually means the file is corrupt or it's not actually a .NET dll.

Option 2:

This one is usually blocked access, wrong bit level, or missing dependencies.  Sometimes, it means it's the wrong .NET version.

Option 3:

"Other"

If it's not one of those two, provide a screenshot of what it actually is.

[john_joe]

This is the error I'm getting. I checked to make sure I have .NET 4.0 installed and I do.

All dependencies loaded correctly

[Kyle97330]

Well, not sure what to tell you here.  I finally downloaded your DLL and put it on my system, LabVIEW 2021 64-bit, and fired it up and got this:

So, I know it doesn't explicitly help you on account of I don't know what our system's difference is, but it definitely can be done in LabVIEW... somehow.

Are you using 2025? I know they changed the .NET implementation a bit to add beta support for newer .NET versions.  Maybe you could try an earlier LabVIEW version?

[john_joe]

I am using 2025 Q1 perhaps that is the only difference