Further adventures in modbus ethernet land

[LightWorker]

Some progress in trying to understand why my ethernet modbus VI runs but the executable does not. After generating a simple VI that runs the slave demon.vi with an invoke node, waits for a stop command in a loop and then aborts the VI,  I could get this to run as an executable. Great I thought, now to add some ethernet modbus slave functionality to the while loop as per the ethernet modbus slave example vi. At this point I started having problems with the invoke node calling the slave demon.vi in the executable, as posted previously. 

So some progress in that I can call and run the slave demon  using an executable, but no solution to the overall problem of incorporating the ethernet slave functionality.

[LightWorker]

This VI ran as an executable with no problems.

[LightWorker]

Spoiler

Correction - Simple VI #2 showed the same error as version 3 when I added the general error handler. So the executable does not work at all with invoke node calling slave demon VI although the VI runs perfectly well.

Back to the drawing board.....

[LightWorker]

Think I may have found a solution thanks to a post from a few years back.

I converted my modbus llb into a windows folder and mass compiled. Then I created the project and added this folder. I then moved the slave demon vi and the slave example vi out of the modbus folder so that they appeared separately in the project files window. See jpg attachment.

In the build environment I put the slave example.vi into the "start up VI" folder and the slave demon.vi  into the "always include" folder.

One other thing - I kept the path to the slave demon as it was in the slave example. I didn't use a path constant this time (this might have been the problem)!

The application.exe seems to work fine thus far. Fingers crossed.