It's either your Hardware or your Software (or possibly the physical wiring of your Hardware to the Real World). Let's assume it is your Software, either an outright error in the code or perhaps a missing "Check for the Framistat going offline unexpectedly" routine that might point to a problem elsewhere.
If you want us to look at your LabVIEW code to either (a) spot the coding error, (b) make suggestions for reducing run-time errors, or (c) suggesting better ways to do things, then you have to post your code. This means attaching VIs (or entire LabVIEW Projects, which you do by compressing the folder containing the Project and all its VIs and attaching the resulting .ZIP file). When we see the code, we'll be better able to interpret the error messages.
Bob Schor
