Multiple Modbus libraries causes issues when loading project.

[Oksavik]

Hello,

I currently have two different Modbus libraries installed, as projects for different clients are based on these.

They are the "NI Modbus Library" from VIPM and "Modbus" installed with DSC.

Are there any reason to choose one or the other? Both have similar functionality, except that DSC Modbus works on Real Time system as well?

My issue is that for one project, that uses the "NI Modbus Library", it seems like some vis from "Modbus" are loaded, and this causes several problems.

If I move the "Modbus" folder out of "Labview 2016/vi.lib" the project loads all files correctly from the "NI Modbus Library" folder.

• Why is this happening?
• What determines where LabVIEW loads dependencies from?
• Should I add the correct Modbus Library to the project, to ensure that the correct is loaded?

Thank you for taking the time.

[jackstokley · Accepted solution]

Hi,

It sounds like LabVIEW is finding a couple of VI's with the same name, or something equivalent to this.

LabVIEW loads dependencies from it's search directories; here's how to add something to these.

https://www.ni.com/docs/en-US/bundle/labview/page/adding-a-directory-to-vi-search-path.html

With some dependency management, you should be able to have both libraries installed but use the correct one for individual applications, it'll just take a little dependency management:

https://www.ni.com/docs/en-US/bundle/labview/page/managing-dependencies-in-labview-projects.html

Jack

[Oksavik]

Thank you for the helpful resources.