W&T 57630, Manual

Page: 77 / 211

77
W&T
Controlling the Web-IO with TCP/UDP Sockets
Subject to errors and modifications:
Example 1 : Query the status of Input 3, where there is a +12 V
signal present. No administrator password was assigned for the
Web-IO.
The application sends the following string to the Web-IO:
GET /input3?PW=&
The Web-IO responds as follows:
input3;ON
Example 2 : Set outputs 3,4,7,9. In binary this is 0000 0010 1001
1000, which corresponds to 0298 hex.
The administrator password for the Web-IO is: „blue“
The application sends the following string to the Web-IO:
GET /outputaccess?PW=blue&State=0298&
The Web-IO responds as follows:
output;0298
1
The Web-IO works with null-terminated strings!
This means that everything the Web-IO sends to the
application ends with a chr(0) character
Event-driven messaging
Some applications make it necessary to report changes on
certain inputs automatically over the existing TCP connection.
One reason for this is to reduce the data load on the network. If
the inputs are polled at a cyclical interval, this will create a
continuous data load. There is also the risk that changes on
the inputs will not be detected if they occur between intervals.
To set the conditions for event-driven messaging, go to the
navigation tree and select
Config >> Device >> Basic Settings