Main Page | Features | Central Services | csv-Files | Types | Transfer | Access | API-C | API-.NET | API-Java | Examples | Downloads
page generated on 09.11.2024 - 04:45
Accessing Your Server in LabView

Client Calls from a Static Listener

We'll begin by getting a set of data from our Workshop server and displaying the output.

LabView clients use the 'lvTineGet...' and lvTinePut...' VIs exclusively for getting and sending data. In the normal case, the 'get' VIs will start an asynchronous static listener which monitors the data end point you are insterested in (as long as it is not pointing to a query property). Thus your LabView application calls the 'get' VI whenever it needs the data (i.e. synchronously within the application), but the data are always coming from an underlying buffer being filling in by the listener. The 'put' VIs on the other hand always work synchronously.

It the normal case, then, there is some potential latency regarding the data retrieved into the application and the data at the source. This latency can be overcome in a couple of ways.

First, the calling string parameter defining the link can always append a "@0" to the string, which signals the underlying data retrieval to make the call synchronously, i.e. no latency, but it's synchronous.

Second (better), the LabView application can use the lvTineClnWaitForData.vi to wait for a LabView Occurence to signal that new data have just arrived from the server and thus respond immediately (no latency).


Impressum   |   Imprint   |   Datenschutzerklaerung   |   Data Privacy Policy   |   Declaration of Accessibility   |   Erklaerung zur Barrierefreiheit
Generated for TINE API by  doxygen 1.5.8