re the new variable can be configured. The target to which the shared variable belongs is the node from which LabVIEW deploys and hosts the shared variable (in our case, the above-mentioned "My Computer"). After shared variables are added to the LabVIEW project, they can be simply dragged into the block diagram of the VI (that reads or writes these shared variables or part of them), thus, creating the "Shared Variable" read or write nodes (see the following Server VI and Client VI diagrams). The NI Publish and Subscribe Protocol (NI-PSP) is a simplified network- ing protocol optimized to be the transport for network-published shared variables. Service Delivery Platforms Project Explorer - incercare.lvproj Project Operate Tools Window Project: incercare.lyproj My Computer server_shared.vi client.vi librarie_shared.lvlib Variable1 Variable2 Variable3 Dependencies Build Specifications Windows Mobile 5.0 Pocket PC Emulator client_shared.vi Dependencies Build Specifications client_shared Windows Mobile 5.0 Pocket PC Device PocketPCScreen 3.vi Dependencies Build Specifications PocketPCScreen 3 Figure 12.21 Remote and mobile control project tree. The underlying layer of NI-PSP has been written to be more efficient by optimized architecture of TCP/IP use. This requires LabVIEW to run on all the nodes involved in the communication. The Shared Variable Network Stack is presented in Figure 12.22. LogosXT is the layer that is optimizing the throughput for the shared variable by an 8 KB transmit buffer (unique for all the connections between two distinct endpoints) and a 10 ms timer thread (so every network operation has a fixed overhead both in packet size and in latency time, for target stream of data). Deployment of network-published shared variables is done toward a shared variable engine (SVE) that hosts the shared variable values on the network (see LabVIEW Shared variable engine NI-PSP LogosXT TCP/IP Ethernet Figure 12.22 The NI Shared Variable Network Stack. Tele-Measurement Services for m-Learning client.vi Front Pan