I've written an application that incorporates a modbus ethernet slave - similar to the one included in the LabView examples (2013). If I run this as a VI then there is no problem. However, if I create an executable then I get an error message about the slave demon version 8.6 being too old to convert to version 2013. I'm using NI Modbus Library 1.2.1 and the 86 folder. To isolate the modbus issue from my original application I've taken the LabView MB Ethernet slave example (2013) and created a project which includes the slave demon vi and the modbus 8.6 vi.lib. I've modified the path to the slave demon in the slave example so that it points to the location of the slave demon vi in my project. If I build the application and run it I get a slightly different error - "the slave demon vi is not executable". I don't understand why the slave demon won't execute in an exe program but will within a VI.

That error doesn't make much sense. LV 2013 can certainly open and run LV8.6 files. You said the executable it the one giving you this error. Where are you running this executable? Is it on the same PC you developed and created the .exe on? Or a different PC? I'm wondering if you are running it on a different PC, that you don't have the proper runtime engine installed. Also, once you moved the Modbus VI's over to your newer LV2013 environment, have you gone through and mass compiled that library?

LabVIEW

Error when running ethernet modbus slave demon in an executable

Solved!

Author

This is all a bit pathetic isn't it. RavensFan asked me a question and I answered him, qualifying my answer with a statement. It wasn't a second question - it was just a statment. Get over it.

Message 11 of 11

(430 Views)

LabVIEW

Error when running ethernet modbus slave demon in an executable

Re: Error when running ethernet modbus slave demon in an executable