Hello Ching,
Apparently, we are still not on the same page. The solution you suggested will not work because once the code reaches the Read FP block, it will try to read the remote IO, once it timeouts, the code will quit, as thought you pushed the abort button on the labview menu bar. There is nothing you can do. This is a fatal error which causes the code to crash.
I am attaching a simple example to show you what I mean. In the code I have attached, M1 is the RT (local) controller. Every second I write to the LED A and toggle its state. It should flash until the end of time. Now, the other Fieldpoint Read is trying read a themocouple channel from a bank which is OFFLINE. If you run this on the RT machine, not on a Windows machine, the code will abort once it reaches the fieldpoint read. It is not just the communication that is lost, the LED never blinks. The code stops executing, leaving the programmer with no way to handle the error. Again, this only happens if the FIRST time you go to read the remote IO, it is offline. If communication to the remote IO is established the first time, then if communication is lost later, error-33800 is returned. But if communication is not established the first time it goes to read the IO, then Labview running on the Real Time target will stop executing, not because I have the error status wired to the stop input, because labview crashes.
Ching, I really feel that this is an error that should be fixed on future fieldpoint drivers so if I am not doing a good job explaining this error, please give me a call so I can talk to you about it. My rep is Autumn Ferrell and I am sure she can get you all my contact info.
Damien Gaudry
Emprise Corporation
