60
Access from your own applications
If the Web-IO receives no valid command within 30 seconds,
it closes the connection and is then free again to open a
new connection. The Web-IO behaves the same way when a
defective or unknown command is received.
Reading the input is generally done by polling. Event-driven
processing is only possible after configuring the input trigger
correspondingly.
UDP peer
To access the Web-IO via UDP using ASCII sockets, enable
UDP ASCII-Sockets
under
Communication paths >> Socket-API
.
Specify on which local UDP port the Web-IO should accept
datagrams.
Using
Remote UDP-Port
you can specify to which UDP port of
the requestor the replies from the Web-IO should be sent.
Entering AUTO means that the replies go to the port which is
entered as the sending port in the received datagram.
Reading the inputs is possible only using polling. Event-driven
processing can be achieved by adding a corresponding action
(see Actions section).
Binary structures BINARY
The Web-IO provides for binary structures for various functions
such as reading the input, setting the output etc. Access is only
by exchanging these structures.
In this mode the Web-IO can work as a TCP client, TCP server or
UDP peer. Access can be password protected.
Four binary accesses are available which can be enabled and
configured independently of each other under Communication
paths >> Socket-API.
In TCP server mode only one client can connect to the correspond-
ing binary access at a time. Any other connection attempt is reject-
ed.
