Application Executable is different to LabVIEW Source code

[Shirui_Of_The_Rain]

I developed and built A software interface to allow control of two 6 DOF Bosch E2700 motion platforms. The System architecture is designed around having a supervisor application which monitors and displays data being read from the Bosch hexapods and a controller application which directly sends data to the platforms via UDP messages. The design pattern architecture used for the controller application and the Supervisor application is the QMH. 

The cRIO Application is the controller which handles relaying the data generated from commands in the supervisor application. The cRIO Application is deployed onto the cRIO and is interfaced with the host PC via a direct ethernet connection. The PC runs the supervisor application which streams the data to the cRIO which then commands the hexapod to move. The output data from the hexapods is then read by the cRIO and streamed via NSW to the supervisor application on the host PC. The built executable for the host pc and the crio project but the executables don't work as expected it works fine in source code but when built as an executable it doesn't. any advice is welcome if anyone needs any further information I will be to post some screenshots. 

[GerdW]

Hi Shirui,

please define "not as expected"...

How should we help with your code problem when all we get is some text or screenshots? Please attach real code...

[James_W]

I'd bet straight up it's timing (or error handling) related and the code hasn't been written as well as the OP thinks it has.

[JÞB]

What I read from your long description is.

MyRIO and the LabVIEW Project context instances communicate correctly.   Something undefined unexpectedly happens between MyRIO and MyApp context instances.  I would compare MyApp.aliases and <project>.aliases for MyComputers ip address.

How are you testing your application? Do you just run the exe from the exe build spec in the project or do you do something bad?