When you run the vi from the project window you are "targeting" the cFP. Once you have your vi is finished and tested, you need to build the executable and deploy it.
Here is a link to get you started. http://digital.ni.com/public.nsf/allkb/258110F1F6415B1C86257213000E065A
hi Ching Pi,
Thanks for the response. Actually, I have been doing what was described in the link you posted. The VI _did_ keep running, which I verified by viewing a logged datafile and printing out the loop iteration. However, the input data from my channels would be repeated each time step, until I reconnected. Any further thoughts?
For output channels, it is really easy to set the value if network communication goes down. What you would do is set the network watchdog timer in Measurement and Automation Explorer (MAX). For more information on that, you can look at the FieldPoint help (Start » All Programs » National Instruments » FieldPoint X.XX » FieldPoint Help). Go to the search tab and type Watchdog. The first result should be Configuring the Network Watchdog. This document should give you all the information you need to get started with watchdog timers. If you have additional questions, you can also look here.
For input channels, this is not as easy. What you can do is read the error output of the FP Read or FP Write and manually set the value if there is an error. Below is an example of what you could do. A more accurate way to do this is to only manually set the value for network communication errors. You will need to unbundle the error cluster from the FP Read or FP Write and just wire the error code into the case structure. I believe the code you will want to look for is: -33804 Ethernet communication has failed. Possible cause: missing or
disconnected network card or network card drivers.
Please let me know if you have any additional questions or concerns.
Message Edited by Ching P. on 08-03-2007 10:30 AM