Use a network-published shared variable (NPSV) just as you would a global variable; the only difference is that a NPSV has network scope, i.e., is accessible by multiple network-connected devices
Especially useful when you need multiple host PCs to monitor a single RT target
Because this is tag-based (latest value) communication, rapid changes of a variable in one process can be missed in the other process
Ensure that control signals remain active long enough for the other process to detect them, or devise a hand-shaking scheme
Suitable for small, frequent data transfers where relatively low throughput rate is acceptable; for example, the host could:
adjust RT configuration parameters
read RT status or a single data measurement
initiate an RT process
Relatively low setup overhead per call, but relatively high CPU usage per call
NOTE: Data transfers through the network are subject to latency (unpredictable delays). Enable the ‘RT FIFO’ option when the NPSV is placed inside an RT timed (deterministic) loop.
Using the Right Networking Protocol (http://www.ni.com/white-paper/12079/en)
Discusses the three most-common communication models -- command or message-based, process data, and streaming/buffered -- and the available networking protocols that are best suited to each model: TCP, UDP, network-published shared variables, network streams, and web services.