W And T 48V Web-IO Digital 4.0 Instructions

In addition, the reply is inserted in an HTTP frame and only then sent by setting the option Reply HTTP conformal.
7

TCP/IP-Sockets – Commandstrings

The following list contains an overview of all supported commands with their associated parameters.

Web-IO Digital Commands
GET /inputx
GET /counterx
GET /counter GET /outputx

Parameter
?PW=password& The administrator or user password must be used instead of password. If no password has been assigned, PW=& is entered. (applies to all commands!)
?PW=password&
?PW=password&
?PW=password&

Description
Input status request x optionally specifies the no. of the input and can be between 0 and 16 depending on the model. The feedback of the Web IO is a string starting with inputx; followed by the input status: ON = signal at the input and OFF = no signal at the input If x is omitted completely, the Web IO returns a bit pattern corresponding to the input signals in hexadecimal notation.
Counter value request x can be a value between 0-11 and indicates the input. The feedback from the Web IO is a string beginning with counterx;. The counter value of the selected counter is appended in decimal notation.
Requesting all counter values The feedback of the Web IO is a string beginning with counter;. The counter values are added in decimal notation separated by semicolons.
Output status request x optionally specifies the No. of the output and can be between 0 and 16 depending on the model. The feedback from the Web IO is a string starting with outputx; followed by the output status: ON = signal at the output and OFF = no signal at the output If x is omitted completely, the Web IO returns a bit pattern corresponding to the output signals in hexadecimal notation.

8

TCP/IP-Sockets – Commandstrings

Commands
GET /outputaccessx
GET /counterclearx
GET /allout
GET /time GET /settime GET /diagnosis

Parameter

Description

?PW=password& [Mask=XXXX&] State=ON/OFF/YYYY& [NA=ON&] ON: Output = 1, OFF: Output = 0, TOGGLE: Change of state XXXX: Hex value between 0000 and 0FFF according to the bits that are to be set YYYY: Hex value between 0000 und 0FFF according to the output bit pattern.

Set one or more outputs x can be a value between 0-11 and spec-
ifies the output to be set. The feedback of the Web IO is a string starting with ,,output;” followed by a bit pattern corresponding to the output signals in hexadecimal notation.
The specification of Mask is optional. If Mask is not sent, the outputaccess command applies to all outputs. With NA=ON it is optionally achieved that no response to the outputaccess command is sent by the Web IO.

?PW=password& [Set=value&] value: Counter preset, value between 0 and 2 billion

Sets the counter value of a counter. If the Set parameter is not sent, the default is 0. x can be a value between 0-11 and specifies the input whose counter is to be reset. The response of the Web IO is a string beginning with counterx;. The new count of the selected counter is appended in decimal notation. If x is not specified, all counters are set.

?PW=password&

Collective request of the input, output states and all counter values. The Web IO responds with a string of the following structure:
input;0xxx;output;0xxx;counter;n0;n1;n2,… 0xxx corresponds to the status of the inputs or outputs in hexadecimal notation. n0,n1 etc. contain the counter states in decimal notation.

?PW=password&

Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second

?PW=password& time=DD.MM.YYYY,
hh:mm:ss&

Sets the system time of the Web IO to the value passed with time.

?PW=password&

Requests the status of the diagnostic memory. The Web IO returns:
diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.

9

TCP/IP-Sockets – Commandstrings

Commands
GET /diagnosisx

Parameter
?PW=password&

GET /diaglistx
GET /diagclear GET /errorclear

?PW=password&
?PW=password& ?PW=password&

Description
With x, the index for one of the currently stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.
Returns the messages for the individual message bits (max. 92)
Clears message memory
Clears load errors and releases the affected outputs.

Web-IO Analog Commands
GET /singlex

Parameter
none

GET /outputx

none

GET /outputaccessx

?PW=password&
State=N,NNN& N,NNN: Strom- bzw. Spannungswert der am entsprechenden output eingestellt werden soll

GET /time GET /settime

?PW=password&
?PW=password& time=DD.MM.YYYY, hh:mm:ss&

Description
Request for the current current or voltage values in mA or V. x optionally indicates the no. of the IO channel and can be 1 or 2. The feedback of the Web-IO is a string that shows the value with three decimal places and unit [N]N.NNN mA or [N] N.NNN V If x is omitted completely, the Web IO returns the values of both channels separated by semicolons.
gives the same result as GET /singlex (even if IO channels work as input)
Setting an output x can be 1 or 2 and indicates the output to be set. The feedback of the Web IO is a string in the format [N]N.NNN mA or [N] N.NNN V. and indicates the current value. Please note that the Web IO needs a few ms to set the desired value. Therefore, the value does not correspond to the desired value.
Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second
Sets the system time of the Web IO to the value passed with time.

10

TCP/IP-Sockets – Commandstrings

Commands
GET /diagnosis

Parameter
?PW=password&

GET /diagnosisx

?PW=password&

GET /diaglistx GET /diagclear

?PW=password& ?PW=password&

Description
Requests the status of the diagnostic memory. The Web IO returns: diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.
With x, the index for one of the currently stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.
Returns the messages for the individual message bits (max. 92)
Clears message memory

Web-IO Klima (Web-Thermometer, …) und VOC

Commands

Parameter

Description

GET /singlex

none

Request for the current climate data x optionally indicates the no. of the sensor. The feedback of the Web-thermometer is a string that shows the value with one decimal digit and unit
24,0°C If x is omitted completely, the Web IO returns the values of both channels separated by semicolons.

GET /time

?PW=password&

Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second

GET /settime

?PW=password& time=DD.MM.YYYY,
hh:mm:ss&

Sets the system time of the Web IO to the value passed with time.

GET /diagnosis

?PW=password&

Requests the status of the diagnostic memory. The Web IO returns:
diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.

11

TCP/IP-Sockets – Commandstrings

Commands
GET /diagnosisx

Parameter
?PW=password&

GET /diaglistx GET /diagclear

?PW=password& ?PW=password&

Description
With x, the index for one of the currently stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.
Returns the messages for the individual message bits (max. 92)
Clears message memory

TCP Server
To access the Web-IO as a TCP server via ASCII sockets, enable TCP ASCII- Sockets under Communication paths >> Socket API. Specify which TCP-Port should be used to receive Web-IO connections. The Web-IO can provide up to eight TCP connections at the same time on the specified port (only 7 if UDP-ASCII access is also used), and any additional connection attempt is rejected.
If the Web-IO does not receive a valid command within 30 seconds after the connection is opened, it closes the connection and enables access again. The Web-IO behaves the same way if a faulty or unknown command is received.
To be able to switch the outputs using ASCII sockets, Enable outputs for ASCII-Sockets must be checked.
UDP Peer
In contrast to TCP, there is no fixed connection between the Web-IO and the other communication partner when using the UDP protocol. Data are exchanged via datagrams.
To access the Web-IO as a UDP peer via ASCII sockets, enable UDP ASCII-Sockets under Communication paths >> Socket API. Specify which UDP-Port should be used for the Web-IO to receive UDP datagrams under Local UDP Port.
In normal situations a 0 should be entered as the Remote UDP Port so that the Web-IO sends reply datagrams to the UDP port from which the request was issued. Alternately a fixed port to which the Web-IO sends all datagrams can be specified under Remote UDP Port.
12

TCP/IP-Sockets – Commandstrings
UDP communication always takes place by polling. This means the application uses the command strings to request the desired values and set the outputs. To be able to switch the outputs using UDP ASCII sockets, Enable outputs for UDP- Sockets must be checked.
Communication between Web-IO and application
Querying the inputs The inputs are generally read using polling. This means the client application uses the command strings to request the desired values. Either the status of one particular input can be queried or all inputs are queried. To query just one input, add the keyword input to the input number. To query all inputs simply skip the indication. If the Web-IO is password protected, the password is appended with ? as a separator with the statement PW The command string ends with & If no password has been assigned, the & follows directly behind PW= Example for querying Input1 with the password “blue” set:
GET /input1?PW=blue&
The Web-IO then returns:
input1;ON+(0x00)
if a valid signal is sent to the input, or:
input1;OFF+(0x00)
If no signal is present. All replies from the Web-IO end with a null byte (0x00). To query all inputs the command is:
GET /input?PW=blue& 13

TCP/IP-Sockets – Commandstrings

The Web-IO replies with the keyword input and a one- or four-character hex number. The hex number corresponds to the bit pattern which results from the set or not-set inputs
Example for Web-IO 2xIn,2xOut with Input 1 = ON:
input;2+(0x00)
The Value is calculated according to the following calculation:

2

hexadecimal

bit 3 bit 2 bit (Intput) 1 bit (Intput) 0

0010

dual / binary

0 x 20 = 0 x 1 = 0

1 x 21 = 1 x 2 = 2

0 x 22 = 0 x 4 = 0

0 x 23 = 0 x 8 = 0

total

2 =^ hex 2

Example for Web-IO 12xIn, 12xOut with Inputs 1,5,6,8,10 and 11 = ON:
input;0D62 +(0x00)
The Value is calculated according to the following calculation:

14

TCP/IP-Sockets – Commandstrings

High byte

0

D

For Web-IO 12xDigital allways 0

Low byte

6

2

hexadecimal

bit 15 bit 14 bit 13 bit 12 bit (output) 11 bit (output) 10 bit (output) 9 bit (output) 8 bit (output) 7 bit (output) 6 bit (output) 5 bit (output) 4 bit (output) 3 bit (output) 2 bit (output) 1 bit (output) 0

0000110101100010

dual / binary

0 x 20 = 0 x 1 = 0

1 x 21 = 1 x 2 = 2

0 x 22 = 0 x 4 = 0

0 x 23 = 0 x 8 = 0

total

2 =^ hex 2

0 x 20 = 0 x 1 = 0

1 x 21 = 1 x 2 = 2

1 x 22 = 1 x 4 = 4

0 x 23 = 0 x 8 = 0

total

6 =^ hex 6

1 x 20 = 1 x 1 = 1

0 x 21 = 0 x 2 = 0

1 x 22 = 1 x 4 = 4

1 x 23 = 1 x 8 = 8

total

13 =^ hex D

0 x 20 = 0 x 1 = 0

0 x 21 = 0 x 2 = 0

0 x 22 = 0 x 4 = 0

0 x 23 = 0 x 8 = 0

total

0 =^ hex 0

Event-driven messaging (TCP only) Some applications require that changes to certain outputs are automatically reported on the existing TCP connection.
One reason can be reducing the data load on the network. If the inputs are queried a cyclical intervals, there is a continuous data load. There is also the risk that changes to the inputs between two cycles may not be recognized.
To have the Web-IO automatically send signal changes on the inputs, check the corresponding Input Triggers under Communication paths >> Socket access.
The messages from the Web-IO have the same structure as the replies when querying all inputs

15

TCP/IP-Sockets – Commandstrings

Querying the outputs
Read access to the outputs is done in the same manner as querying the inputs, except that the keyword input is replaced with output

Switching the outputs
To switch the outputs use the command outputaccess.
Either a single output, all outputs at the same time, or some of the outputs can be switched.
Switching one output As with reading, the output is specified. The number of the output to be switched is appended to the keyword outputaccess
In addition, the parameter State is used, for which in this case there are three possible values:
· ON · OFF · TOGGLE (state change)
Example:
GET /outputaccess1?PW=blue&State=ON&

switches Output 1 to ON. Als Antwort sendet das Web-IO z.B.
output;0EAC +(0x00)

whereby the actually returned value depends on which state the other outputs were in before switching.

Initial state of the outputs: Output 1:
State after switching:

bitwise representation 0000 1110 1010 0100
1 0000 1110 1010 0110

hexadecimal
output; 0EA4 State=ON
output; 0EAC

16

TCP/IP-Sockets – Commandstrings

Simultaneous switching of all outputs To switch all outputs at the same time, no output is specified and the State parameter is used to send the hex number for the desired bit pattern of the outputs.
If for example you wish to switch outputs 1, 6 and 11 to ON and all others to OFF, the command looks as follows:
GET /outputaccess?PW=blue&State=0842&

in reply the Web-IO sends
output;0842 +(0x00)

Initial state of the outputs: State:
State after switching:

bitwise representation
0000 1110 1010 0100 0000 1000 0100 0010 0000 1000 0100 0010

hexadecimal
output; 0EA4 State=0842
output; 0842

Simultaneous switching of selected outputs To switch only some of the outputs, the same command structure as for switching all outputs is used. The difference is that the Mask parameter precedes the State parameter. The Mask parameter specifies which outputs should be switched, and State specifies to what state.
For example to switch outputs 1, 6 and 11 to ON and outputs 5 and 10 to OFF, the command looks as follows:
GET /outputaccess?PW=blue&Mask=0C62&State=0842&

in reply the Web-IO sends
output;0AC6 +(0x00)

whereby the actually returned value depends on which state the other outputs were in before switching.

Initial state of the outputs: Mask: State:
State after switching:

bitwise representation
0000 1110 1010 0100 0000 1100 0110 0010 0000 1000 0100 0010 0000 1010 1100 0110

hexadecimal output; 0EA4
Mask=0C62 State=0842 output; 0AC6

17

TCP/IP-Sockets – Commandstrings
Querying the counters
The Web-IO inputs include a counter which is incremented by one with each rising edge, i.e. a change from OFF to ON.
The counters are queried using the command counter. As with the inputs and outputs, the values for all counters or just a single counter can be queried.
When a counter state of 2147483648 is reached it turns over to 0
Querying one counter The counter number of the input whose counter should be queried is appended to the keyword counter.
Example for querying Counter 0:
GET /counter0?PW=blue&
in reply the Web-IO sends e.g.
counter;3974 +(0x00)
The counter value is returned in decimal format, separated by a semicolon, behind the keyword counter.
Querying all counters If the counter command is sent to the Web-IO without specifying the number of an input, the Web-IO returns the counter states of all inputs separated by semicolons.
Example for querying all counters of a Web-IO with 12 inputs:
GET /counter?PW=blue&
in reply the Web-IO sends e.g.
counter;3974;453;99;0;0;984;712;4;334;1076;0;6543 +(0x00)
The counter value is returned in decimal format and semicolon separated behind the keyword counter.
18

TCP/IP-Sockets – Commandstrings
Clearing the counters
The command counterclear can be used to clear a specified or all counters to 0 or if needed to set it/them to another value.
Clearing one counter Example for clearing Counter 0:
GET /counterclear0?PW=blue&
in reply the Web-IO sends
counter0;0 +(0x00)
Presetting one counter To preset a counter to a particular value, the optional parameter Set=& is appended.
Example for setting Counter 0 to 12345:
GET /counterclear0?PW=blue&Set=12345&
in reply the Web-IO sends
counter0;12345 +(0x00)
Clearing all counters Example for clearing all counters for a Web-IO with 12 inputs:
GET /counterclear?PW=blue&
in reply the Web-IO sends
counter0;0;0;0;0;0;0;0;0;0;0;0;0 +(0x00)
Presetting all counters To preset all counters to a particular value, the optional parameter Set=& is also appended. It is not possible to preset all counters to individual counter states in one command.
Example for setting all counters to the value 12345 for a Web-IO with 12 inputs:
19

TCP/IP-Sockets – Commandstrings
GET /counterclear?PW=blue&Set=12345&
in reply the Web-IO sends
counter0;12345;12345;12345;12345;12345;12345; 12345;12345;12345;12345;12345;12345 +(0x00)
At hoc reading of inputs, outputs and counters
By using the command allout you can query the complete process map of the Web- IO.
Example:
GET /allout?PW=blue&
in reply the Web-IO with 12 Inputs and 12 Outputs sends for example
input;0C3B;output0842counter;3974;453;99;0;0;984; 712;4;334;1076;0;6543 +(0x00)
Communication between Web-IO Analogue and Application
Querying the IO channels
Reading the IO channels is usually done in polling mode. This means: the client application requests the desired values with the help of the corresponding command string.
Either the status of a specific IO channel can be requested or a request is made for both IO channels.
If only one IO channel is to be queried, the number of the IO channel is added to the keyword single. For the query of all channels, indexing is waived. In contrast to the digital Web IOs, the indexing of the IO channels in the analogue Web IO does not start at 0 but at 1.
In response, the Web IO sends back the current or voltage value with three decimal places followed by a space and the unit. When both IO values are queried, they are returned separated by a semicolon.
20

TCP/IP-Sockets – Commandstrings
Example of polling IO channel2 at 7.5 mA current flow :
GET /single2&
The Web IO then sends back:
7,500 mA+(0x00)
Example of polling both IO channels at 15.340 mA and 7.5 mA current flow :
GET /single&
The Web IO then sends back:
15,340 mA ;7,500 mA+(0x00)
As an alternative to the single command, the output command can also be used to read out the status of the IO channels (even if the channels are configured as inputs). The output command is used in the same way as single. However, the Web IO prefixes the response with the word output and, if a channel is requested, with the corresponding index separated by a semicolon. Example of polling IO channel2 at 7.5 mA current flow :
GET /output2&
The Web IO then sends back:
output2;7,500 mA+(0x00)
Example of polling both IO channels at 15.340 mA and 7.5 mA current flow :
GET /output&
The Web IO then sends back:
output;15,340 mA ;7,500 mA+(0x00)
21

TCP/IP-Sockets – Commandstrings
Set current/voltage value of an output
As with read access, indexing is used. The number of the output to be set is appended to the keyword outputaccess.
In addition, the parameter PW= is used to pass the password and the parameter State= to pass the value. The parameter State is transferred with a maximum of three decimal places and without a unit.
The parameter set is separated from the command by ? and each parameter ends with &.
Example:
GET /outputaccess1?PW=blau&State=15,340&
sets output 1 to 15.340 mA.
As a response, the Web IO sends e.g.
GET /outputaccess1?PW=blau&State=15,340& +(0x00)
Web-IO Climate, VOC and Application
Querying the IO channels
Reading the climate values is also usually done in polling mode. This means: the client application requests the desired values with the help of the corresponding command string.
Either the value of a specific channel can be requested or a request is made for all existing channels.
If only one channel is to be queried, the number of the channel is added to the keyword single. If all channels are to be queried, indexing is omitted. Unlike the digital Web IOs, the indexing of channels in the Web IO Climate does not start at 0 but at 1.
As a response, the Web IO sends back the current temperature, humidity, air pressure or air quality value with three decimal places followed by a space and the unit. If all values are requested, they are returned separated by a semicolon.
Example for the query of channel 2 (humidity) of a web thermo-hygrobarometer:
22

GET /single2&

TCP/IP-Sockets – Commandstrings

The Web Thermo-Hygrobarometer then sends back:
28,6% +(0x00)
Example for the query of all channels:
GET /single&
The Web Thermo-Hygrobarometer then sends back:
23,6°C;28,5%;988,8hPa+(0x00)
Query and set date and time
Querying date and time
Use the command time to query the set date and time of the Web-IO. The request
GET /time?PW=blue&
causes the Web-IO to reply with
01.08.2016,15:14:59

Setting the date and time
The system time of the Web-IO can be set using the command settime. The parameter time is used to send the desired settings formatted
time=DD.MM.YYYY,hh:mm:ss
Example:
GET /settime?PW= blue&time= 01.08.2016,15:14:59
the Web-IO replies with
23

TCP/IP-Sockets – Commandstrings
01.08.2016,15:14:59
Reading the error memory
When the Web-IO detects one or more errors while processing one of its tasks, these are stored and can be viewed under Diagnostics in the navigation tree. In some applications it is desirable to handle error management not manually by viewing a website, but rather to evaluate errors in automated fashion in a program. For this the Web-IO provides a few command strings that can be used with either TCP or UDP. Creating a list of possible error messages The Web-IO can manage a maximum of 127 different error types. The actual number may vary up to this limit depending on the firmware version. To receive an overview of the possible errors, you can send the command
GET /diaglistx?PW=password&
to the Web-IO. In place of x a value between 0 and 127 is used. Instead of password enter the administrator or operator password. The Web-IO replies to the request with the corresponding error message.
diaglistx;errortext
Example: If the application sends (password = “blue”)
GET /diaglist2?PW=blue&
the Web-IO replies with
diaglist2;Formatfehler in der DNS Anfrage
24

TCP/IP-Sockets – Commandstrings
You can use the diaglist command with a for next loop to read out all possible error messages and store them as a static list. In binary mode for example you can only determine how many errors are currently present. In addition the associated error numbers are transmitted. Using the static error list a readable error can then be output.
Direct evaluation of the current errors To get the current error status of the Web-IO you can use the command
GET /diagnosis?PW=password&
The Web-IO responds with
diagnosis;iiii;zzzzzzzz;yyyyyyyy;xxxxxxxx
In iiii the Web-IO returns the number of current errors in 4-place hex format.
zzzzzzzz;yyyyyyyy; xxxxxxxx may be ignored for normal, standard applications.
For expert programmers: zzzzzzzz; yyyyyyyy; xxxxxxxx are three 32-bit values, each in 8-place hex format. The resulting 64 bits substitute for the 64 possible error types. By using the static error list (see GET /diaglist…) the individual bits can be decoded. The LSB appears to the right in the x range and the MSB to the left in the y range.
To get the current errors as an error text, the Web-IO provides the command
GET /diagnosisx?PW=&
Here x is the index for the error in decimal format beginning with 1.
The reply from the Web-IO then looks as follows:
diagnosisx;errortext
In contrast to the error texts which are read from the Web-IO using diaglist, the error text for diagnosis may also contain dynamic elements such as IP addresses or port numbers.
Example:
25

TCP/IP-Sockets – Commandstrings
The application sends:
GET /diagnosis?PW=blue&
The Web-IO responds:
diagnosis;0005;00400040;008A0000;00000000
The application sends:
GET /diagnosis1?PW=blue&
The Web-IO responds:
diagnosis1;Mail Server antwortet nicht.
The application sends:
GET /diagnosis2?PW=blue&
The Web-IO responds:
diagnosis2;Das Versenden der Mail wurde abgebrochen und wird wiederholt.
The application sends:
GET /diagnosis3?PW=blue&
The Web-IO responds:
diagnosis3;Ziel IP-Adresse unbekannt: 172.16.232.8.
The application sends:
GET /diagnosis4?PW=blue&
The Web-IO responds:
diagnosis4;Watchdog Timer abgelaufen!
The application sends:
26

GET /diagnosis5?PW=blue&

TCP/IP-Sockets – Commandstrings

The Web-IO responds:
diagnosis5;TCP Client Alarm: Server nicht erreicht.
Clearing the error memory The list of errors occurring during runtime remains stored in the Web-IO, even if the error is no longer present at the time of query. To clear the error memory, use the command
GET /diagclear?PW=password&
The Web-IO responds with
diagnosis;0000;00000000;00000000;00000000
if there are no current errors.

27

TCP/IP-Sockets – Binary
TCP/IP Sockets – Binary
In addition to access using command strings, the Web-IO also provides four socket accesses for binary data exchange.
All four accesses work independently of each other. Under Communication paths

Socket-API you can enable the binary accesses and specify which if the three following modes to use:
· TCP server · TCP client · UDP peer For the various functions such as reading the inputs, setting the outputs etc. the Web-IO defines binary structures. Access is only by exchanging these structures.
TCP server
Under Communication paths >> Socket-API in the desired binary area select BINARYx TCP-Server as the Socket-Type and specify which local Port to use for accepting the connection.
Unlike TCP Server mode for command strings in which up to 8 clients can connect to the common server port, the Web-IO permits only one connection for the respective binary access. All further connection attempts are rejected as long as a client is connected.
Binary access can be password protected if desired.
When setting input triggers and there is an existing connection, the Web-IO automatically informs the application of changes to the selected inputs.
To switch the outputs via binary access as well, this must be checked under Enable outputs for Binaryx-Sockets.
28

TCP/IP-Sockets – Binary
TCP client
If BINARYx TCP-Client is selected as the Socket-Type, the Web-IO opens a connection to a TCP server application when there is a change to one of the inputs selected under Input/Trigger.
Under Server-IP enter the IP address or host name of the destination server and under BINARYx Server Port specify which TCP port the connection should be opened on.
In normal situations the BINARYx local Port should be configured for AUTO. This means the sender port increments dynamically at each connection, which is helpful in dealing with firewalls. Alternately you can also use a randomly selected, fixed sender port.
Under Inactive Timeout you can specify after how much time with no activity on the inputs a connection should be closed. A value of 0 means the connection remains open until the opposite endpoint closes it.
To switch the outputs via binary access as well, this must be checked under Enable outputs for Binaryx-Sockets.
UDP peer
If BINARYx UDP-Peer is selected as the Socket-Type, the Web-IO opens a connection to the UDP port set under UDP local port for receiving UDP datagrams.
All datagrams sent by the Web-IO go to the IP address entered under RemotePeer-IP on the UDP port configured as UDP remote port.
When there is a change to the inputs defined as Input-Trigger, corresponding datagrams are sent to the configured remote peer.
To switch the outputs via binary access as well, this must be checked under Enable outputs for Binaryx-Sockets.
BINARY ­ The IO structures
Regardless of which BINARY Socket Type was selected, there are a clear number of binary structures (variable fields) for communication between the application and the Web-IO.
29

TCP/IP-Sockets – Binary

Such structures are provided for the following functions:

· Password prompt and sending · Reading the inputs · Reading the inputs and outputs · Setting the outputs · Reading the counters · Resetting the counters · Configuring cyclical and
is a state change

automatic

messaging

when

there

The user program uses the convenient socket interface (Windows: WinSock, UNIX, Linux: Berkley Sockets) for exchanging the data in the form of these IO structures with the Web-IO and over the network via TCP/IP.

Definition of the structures
To be able to unambiguously identify and evaluate the content of a packet, in BINARY mode all the data must be sent to the Web-IO in the form of these IO structures.

All structures begin with the same header, which consists of the following 4 WORDS (16-bit_Integer):

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

high byte 2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

high byte 4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

high byte 6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

high byte 8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

Start_1, Start_2 Start_1 and Start_2 are there for reasons of compatibility with earlier models, but they are not used. Both values are always 0.
StruktTyp The value struct_typ identifies the structure. Both the PC application and the WebIO use the value struct_typ when data are received to determine how the structure should be evaluated.

30

TCP/IP-Sockets – Binary

StructLength length indicates the total length of the structure in bytes, i.e. including th first 4 WORDs.
1Note: The following applies to all IO structures:

A word corresponds to 16bit integer. A char corresponds to one byte (8bits) A long corresponds to a 32bit integer

Hexadecimal format 0x in front of the value
1For sending and receiving the variable Low-Byte first applies to all structure variables.

Start_1

Start_2

StructType

StructLength

7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8

00 00 00 00 01 00 08 00 low byte
1. byte of structure

high byte 2. byte of structure

low byte 3. byte of structure

high byte 4. byte of structure

low byte 5. byte of structure

high byte 6. byte of structure

low byte 7. byte of structure

high byte 8. byte of structure

es.l

In the examples all numbers are in hex format!

31

TCP/IP-Sockets – Binary

Password protected access
In TCP Server mode binary access can be protected from unauthorized attempts using a password protection.
If Password protected access is checked under Communication paths >> Socket access > TCP/UDP Sockets BINARY-Mode in the BINARYx TCP-Server area, a multi- step login procedure is required.

Unauthorized access attempt
If a client application attempts to begin communication with the Web-IO using the password protected binary access, the Web-IO sends the structure AuthRequired.

The structure Authrequired

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 04 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

When the AuthRequired structure is received, the client application must start with the login procedure.

Login procedure
To get access to the IOs with password protection, the client application must prompt a key. This is done by sending the KeyRequest structure.

32

TCP/IP-Sockets – Binary

The structure KeyRequest

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 02 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

When the KeyRequest structure is received the Web-IO generates a maximum 64byte long key to the Web-IO which is embedded in the Key structure.

The structure Key

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 03 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 4C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 XX 12. byte of structure

11. byte of structure

10. byte of structure

9. byte of structure

32 bit value

76543210

XX 13. byte of structure

1 byte

76543210

XX 14. byte of structure

1 byte

76543210
XX 75. byte of structure
1 byte 76543210
XX 76. byte of structure
1 byte

Start_1

Word always = 0

Start_2

Word always = 0

StructType

Word Structure type

StructLength

Word Length in bytes

KeyLength

Long Number of KeyBytes

actually used

KeyBytes

Long byte array always 64 bytes, even if the actual key is shorter

How many bytes long the key actual is is indicated by the variable KeyLength.

33

TCP/IP-Sockets – Binary

The structure Login
The client application must now generate an MD5 hash from the password assigned for the Web-IO and the received key.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 01 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 28 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

76543210

XX 9. byte of structure

1 byte

76543210

XX 10. byte of structure

1 byte

Start_1

Word always = 0

Start_2

Word always = 0

StructType

Word Structure type

StructLength

Word Length

in

bytes

MD5-Hash

Long byte array 32 bytes MD5 hash of password + key

76543210
XX 39. byte of structure
1 byte 76543210
XX 40. byte of structure
1 byte

The MD5 hash sum is sent to the Web-IO using the Login structure. If the Web- IO accepts the login, it sends the AuthOK structure to the client application and normal data exchange can begin.

The structure AuthOK

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 05 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

34

TCP/IP-Sockets – Binary

The structure AuthFail

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

80 06 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

If the login is incorrect the Web-IO sends the AuthFail structure and closes the TCP connection.
Digital IO-Access with Binary Structures

The structure ReadRegister
Sending this structure to the Web-IO causes it to send the status of Inputs 0 – 11 to the application program. The packet consists only of these four WORDs. This structure is used by the user program and the Web-IO always responds by sending the WriteRegister structure.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 01 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

The structure WriteRegister
This structure is used to send the state of the inputs or outputs for the Web- IO 12xDigital. If the application program sends this structure to the Web-IO, the WebIO sets the outputs corresponding to the value transmitted in value.
If the Web-IO sends this structure to the user program, value has the value corresponding to the input state.

35

TCP/IP-Sockets – Binary

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 01 high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength Amount Value

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word always = 1 Word Binary equivalent of the input status

For Web IOs with relay outputs, a pause of at least 200ms must be observed between two switching processes at an output!

The structure SetBit
This structure enables the setting of individual outputs at the Web IO. If, for example, the entire process status is not mapped in the user programme, individual outputs can be set without changing the value of the others. The bits 0..11 in set_bits and value correspond to the corresponding outputs. This structure is only used by the user programme.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 09 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength Mask Value

Word always = 0
Word always = 0
Word Structure type
Word Length in bytes Word Bits that are to be changed = 1 Word Binary equivalent of the output status

Beispiel.:
set_bits = 0x0124 / value = 0x0104 36

TCP/IP-Sockets – Binary

Output 2 and Output 8 (counting Output0..1) are set to ON and Output 5 is set to OFF. All other outputs are not changed.

The structure RegisterRequest
The user programme sends this structure to the Web IO in order to be able to read the contents of inputs and outputs in overview. The Web IO always responds with the RegisterStateert I/O structure.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 21 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

The structure RegisterState
The Web IO uses this structure to transmit the content of the inputs and outputs. This structure is only sent if the user application has sent the Register Request structure to the Web IO.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 31 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0E high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 02 high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
14. byte of structure

low byte 13. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength DriverID InputValue OutputValue

Word always = 0
Word always = 0
Word Structure type
Word Length in bytes Word always = 2 Word Binary equivalent of the input status Word Binary equivalent of the Output status

37

TCP/IP-Sockets – Binary

The structure Send Mode
This structure is used to specify the trigger conditions the Web-IO 12xDigital uses to send the status of the inputs to the user program. There are basically three possibilities, but they may be combined with each other:
1. The user program polls the Web-IO by sending the READ structure 2. The Web-IO sends the WriteRegister – structure with the status of the inputs in
a configurable interval 3. The Web-IO sends the WriteRegister – structure with the status of the inputs
after a state change of the configured inputs

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 01 high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength Amount Value

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word always = 1 Word Binary equivalent of the input status

The structure ReadCounter
The user program sends this structure to the Web-IO to request the counter state of a certain input counter. Which input is intended is sent in the variable counter_index. The Web-IO always replies with the Counter structure.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 B0 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0A high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

38

Start_1 Start_2 StructType StructLength Counterindex

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word Input number

TCP/IP-Sockets – Binary

The structure ReadClearCounter
The application program sends this structure to the Web-IO in order to request the counter status of a particular input counter and then immediately set to counter to 0. Which input this involves is transmitted in the variable counter_index. The WebIO always replies with the structure Counter.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 C0 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0A high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength Counterindex

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word Input number

The structure Counter
With this structure the Web-IO sends the counter state of the input counter specified in counter_index.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 B4 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0E high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 14. byte of structure

13. byte of structure

12. byte of structure

11. byte of structure

32 bit value

Start_1 Start_2 StructType StructLength CounterIndex CounterValue

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word Nummer des Inputs Long Zählerwert

39

TCP/IP-Sockets – Binary

The structure ReadAllCounter
The user program sends this structure to the Web-IO to request the counter states of all the inputs in a data packet. The Web-IO always replies with the structure AllCounter.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 B1 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

The Structure ReadClearAllCounter
The application program sends this structure to the Web-IO in order to request the counter states of all inputs in a data packet and then immediately sets the counters to 0. The Web-IO always replies with the structure AllCounter.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 C1 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

40

TCP/IP-Sockets – Binary

The structure AllCounter
The Web-IO uses this structure to send the counter states of all the inputs at one time.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 B5 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0E high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 14. byte of structure

13. byte of structure

12. byte of structure

11. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 18. byte of structure

17. byte of structure

16. byte of structure

15. byte of structure

32 bit value

Start_1 Start_2 StructType StructLength CounterNoOf CounterValue1 CounterValue2

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word Numner of Counters Long Counter value 1 Long Counter value 2

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX XX. byte of structure

XX. byte of structure

XX. byte of structure

XX. byte of structure

32 bit value

CounterValuen

Long Counter value n

The structure ClearCounter
The user program sends this structure to the Web-IO to reset the counter state of a certain input counter to 0. Which input is intended is sent in the variable counter_index

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 B2 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

41

TCP/IP-Sockets – Binary

The struktur Options
This structure is used to set certain options in the Web IO. For this purpose, 32 bits are available in the options variable.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 F0 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 10 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 01 12. byte of structure

11. byte of structure

10. byte of structure

9. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 16. byte of structure

15. byte of structure

14. byte of structure

13. byte of structure

32 bit value

Start_1 Start_2 StructType StructLength Version Options

Word always = 0 Word always = 0 Word Structure type Word Length in bytes
Long Currently 1 Long Binary coding

In the present version of the Web IO, only bit 0 of the options variable is used.
· Bit 0 = 1 //the Web IO returns the RegisterState structure when an output is set. · Bit 0 = 0 //the Web IO does not give any feedback when an output is set.
In order to reliably receive the status after setting the output(s) in the feedback, there should be a time of at least 50ms between two output-changing accesses.

42

TCP/IP-Sockets – Binary

IO structures for reading the logger content (#57756)
The data records stored in the Web-IO 4.0 Digital Logger can also be read by using binary structures.
Even if you do not want to access the inputs or outputs, but only want to read out the logger, Binary1 must be activated in the Web-IO menu under Communication paths >> Socket API >> Binary1.

The struktur LOGGER_REQUEST
The LOGGER_REQUEST structure is used to initially transfer the time period for the desired data records to the Web-IO Digital Logger.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte of structure

Low-Byte 1. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte of structure

Low-Byte 3. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 E0 High-Byte
6. Byte of structure

Low-Byte 5. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 14 High-Byte
8. Byte of structure

Low-Byte 7. Byte of structure

16 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 12. Byte of structure

11. Byte of structure

10. Byte of structure

9. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 16. Byte of structure

15. Byte of structure

14. Byte of structure

13. Byte of structure

32 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0X XX High-Byte
18. Byte of structure

Low-Byte 17. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0X XX High-Byte
20. Byte of structure

Low-Byte 19. Byte of structure

16 Bit Variable

Start_1 Start_2 StructType StructLength StartTime StopTime StartTime ms StopTime ms

Integer Always = 0 Integer Always = 0 Integer Struktur type Integer Length in bytes Long (Seconds) from 01.01.1970 Long (Seconds) from 01.01.1970 Integer Milliseconds Integer Milliseconds

The start and stop times are specified in seconds from 01.01.1970 00:00:00. In addition, the ms (in steps of a hundred) up to the next full second can be specified for both times.

The struktur LOGGER_ NOACCESS
The content of the data logger can only be read by one instance at a time. If another read operation is already active, the Web-IO Digital Logger responds with the LOGGER_NOACCESS structure.
43

TCP/IP-Sockets – Binary

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte of structure

Low-Byte 1. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte of structure

Low-Byte 3. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 E3 High-Byte
6. Byte of structure

Low-Byte 5. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 High-Byte
8. Byte of structure

Low-Byte 7. Byte of structure

16 Bit Variable

Start_1 Start_2 StructType StructLength

Integer Always = 0 Integer Always = 0 Integer Struktur type Integer Length in Bytes

In this case, the connection should be terminated and access to the logger should be attempted again at a later time.

The struktur LOGGER_CHECK
If access to the logger is not assigned, the structure LOGGER_REQUEST is answered by the Web-IO Digital Logger with the structure LOGGER_CHECK.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte of structure

Low-Byte 1. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte of structure

Low-Byte 3. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 E1 High-Byte
6. Byte of structure

Low-Byte 5. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 14 High-Byte
8. Byte of structure

Low-Byte 7. Byte of structure

16 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 12. Byte of structure

11. Byte of structure

10. Byte of structure

9. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 16. Byte of structure

15. Byte of structure

14. Byte of structure

13. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 20. Byte of structure

19. Byte of structure

18. Byte of structure

17. Byte of structure

32 Bit Variable

Start_1 Start_2 StructType StructLength LoggerState MemSize Memprogress

Integer Always = 0 Integer Always = 0 Integer Struktur Integer Length in Bytes Long Check state Long Memory size Long Search progress

The Web-IO Digital Logger must first check how many data records are stored for the desired time period. This can take some time depending on the memory utilization and the size of the time period. To inform the application about the current status of the data set search, the Web-IO Digital Logger returns the corresponding information with the LOGGER_CHECK structure.
· There are 4 states for LoggerState:
0 = No search active (yet)
44

TCP/IP-Sockets – Binary

1 = Initialization of the search process 2 = Loading a memory area to be searched 3 = Recognizing the data records 4 = Evaluation completed
· In MemSize the Web-IO Digital Logger returns the total size of the memory to be scanned in bytes.
· The MemProgress parameter indicates how far the search has progressed.
As long as the return value for logger_state is not equal to 4, the application must respond with the LOGGER_CHECK structure, whereby LoggerState, MemSize and MemProgress are set to 0.
LOGGER_CHECK structures are exchanged until LoggerState has the value 4.

The struktur LOGGER_DATAREQUEST
After the LOGGER_CHECK structure has been received with LoggerState = 4, the data records can be requested.

This is done by sending an EADriver structure with structure type 0x01E2 from the application to the Web-IO Digital Logger.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte of structure

Low-Byte 1. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte of structure

Low-Byte 3. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 E2 High-Byte
6. Byte of structure

Low-Byte 5. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 High-Byte
8. Byte of structure

Low-Byte 7. Byte of structure

16 Bit Variable

Start_1 Start_2 StructType StructLength

Integer Always = 0 Integer Always = 0 Integer Struktur type Integer Length in Bytes

The struktur LOGGERDATASET
The Web-IO Digital Logger starts sending the data sets after receiving the LOGER DATAREQUEST structure. Each individual data set available for the desired time period is sent within a LOGGER_DATASET structure.

45

TCP/IP-Sockets – Binary

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte of structure

Low-Byte 1. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte of structure

Low-Byte 3. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 E2 High-Byte
6. Byte of structure

Low-Byte 5. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 88 High-Byte
8. Byte of structure

Low-Byte 7. Byte of structure

16 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 12. Byte of structure

11. Byte of structure

10. Byte of structure

9. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 16. Byte of structure

15. Byte of structure

14. Byte of structure

13. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 20. Byte of structure

19. Byte of structure

18. Byte of structure

17. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 24. Byte of structure

23. Byte of structure

22. Byte of structure

21. Byte of structure

32 Bit Variable 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX High-Byte
26. Byte of structure

Low-Byte 25. Byte of structure

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX High-Byte
28. Byte of structure

Low-Byte 27. Byte of structure

16 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 32. Byte of structure

31. Byte of structure

30. Byte of structure

29. Byte of structure

32 Bit Variable 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 36. Byte of structure

35. Byte of structure

34. Byte of structure

33. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 48. Byte of structure

47. Byte of structure

46. Byte of structure

45. Byte of structure

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 52. Byte of structure

51. Byte of structure

50. Byte of structure

49. Byte of structure

32 Bit Variable

………………………

Start_1 Start_2 StructType StructLength MaxCount ProcessCount TimeStamp TimeStamp ms Outputs Inputs Reserve Alarms1-30 Counter0 Counter1

Integer Always = 0 Integer Always = 0 Integer Struktur type Integer Length in Bytes Long Qty. of Datasets Long Current Datasets Long (Seconds) ab 01.01.1970 Long + Milliseconds Integer Output bit pattern Integer Input bit pattern Long not used Long Alarm bit pattern Long Counter value Long Counter value

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 104. Byte d. Struktur

103. Byte d. Struktur

102. Byte d. Struktur

101. Byte d. Struktur

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 108. Byte d. Struktur

107. Byte d. Struktur

106. Byte d. Struktur

105. Byte d. Struktur

32 Bit Variable

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 112. Byte d. Struktur

111. Byte d. Struktur

110. Byte d. Struktur

109. Byte d. Struktur

32 Bit Variable

………………………

Counter14 Counter15 ErrorCounter0

Long Counter value Long Counter value Long Bidirectional Counting errors

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 138. Byte d. Struktur

137. Byte d. Struktur

136. Byte d. Struktur

135. Byte d. Struktur

32 Bit Variable

ErrorCounter7

Long Bidirectional Counting errors

· The MaxCount parameter shows the total number of data records, while ProcessCount shows which data record is currently being transferred.
· Each data record contains the appropriate time stamp with TimeStamp (seconds from 01.01.1970 00:00:00) and TimeStamp ms (milliseconds).
· The binary status of the inputs and outputs is transferred in the Inputs and Outputs fields.

46

TCP/IP-Sockets – Binary

· The alarm status is signaled in the first corresponding bits of Alarms. · The structure contains the 16-fold counter array for the counter readings. · In the event that the bidirectional counter mode is used and direction detection
was not clearly possible, the counting errors are incremented in the 8-fold ErrorCounter array. · The Web-IO Digital Logger sends all data records for the selected time period without a new request from the application side. This process cannot be stopped.
The exact procedure for reading out the logger is clearly illustrated in the following flow chart.

Connect to the logger
Send to logger: LOGGER_REQUEST
Receive structure from Logger

Send to logger: LOGGER_DATASET
Receive structure from Logger

yes

Received structure

LOGGER_NOACCESS?

no
Send to logger: LOGGER_CHECK

Receive from Logger LOGGER_CHECK

Received structure

no

LOGGER_DATASET?

(1 of n)

yes
LOGGER_DATASET 2 of n received

no LoggerState = 4?
yes

LOGGER_DATASET n von n empfangen
Verbindung zum Logger trennen

47

TCP/IP-Sockets – Binary

Analog I/O access with binary structures

The structure ReadRegister
Sending this structure to the Web-IO causes it to send the status of the ports to the user program.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 01 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

The package consists only of these four WORDs. This structure is only used by the user program and the Web-IO always reacts by sending the structure AnalogRegisterState.

The IO structure AnalogRegisterState
The Web-IO Analog-In/Out transmits the status of both ports with this structure. This structure is sent if the user program has sent the ReadRegister structure to the Web-IO, or if an output value has been set with this structure.
This structure also serves to transmit the output values of the ports to be set. If the user program sends this structure to the Web-IO, the Web-IO sets the outputs according to the value transferred in Port 1 and Port 2.
Here the value is not transmitted in the configured unit, but always in 1/100,000 of the maximum value. An output value of 15.4mA must be transmitted as 77000 or 0x012CC8 .
If the Web-IO sends this structure to the user program, port 1 and port 2 have the value corresponding to the input status.

48

TCP/IP-Sockets – Binary

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 B8 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 14 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 02 12. byte of structure

11. byte of structure

10. byte of structure

9. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0X XX XX 16. byte of structure

15. byte of structure

14. byte of structure

13. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0X XX XX 20. byte of structure

19. byte of structure

18. byte of structure

17. byte of structure

32 bit value

Start_1 Start_2 StructType StructLength Amount Port1Value Port2Value

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Long always 2 Long Value in 1/100.000 Long Value in 1/100.000

The structure AnalogSingleRegister
This structure is used to transmit the output value of a single port at Web-IO Analog-In/Out (Port 1 = 0, Port 2 = 1). The procedure is the same as for AnalogRegisterState.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 BB high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 14 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 01 12. byte of structure

11. byte of structure

10. byte of structure

9. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 0X 16. byte of structure

15. byte of structure

14. byte of structure

13. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0X XX XX 20. byte of structure

19. byte of structure

18. byte of structure

17. byte of structure

32 bit value

Start_1 Start_2 StructType StructLength Amount Channel PortValue

Word always = 0 Word always = 0 Word Structure type Word Length in bytes
Long always 1 Long Chanel no. (0 / 1) Long Value in 1/100.000

49

TCP/IP-Sockets – Binary

The IO structure Send Mode
This structure defines the trigger conditions with which the Web-IO Analog- In/Out sends the status of the ports to the user program. The trigger can be configured for status changes of both ports. The respective hysteresis for the trigger must be set in the web configuration.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 10 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 0X high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength Mask Interval

Word always = 0 Word always = 0 Word Structure type Word Length in bytes Word Bits for input trigger = 1 Word Interval in 100ms for Transmission of the

The following combinations can be configured as variable masks:

0x0000 0x0001 0x0002 0x0003

Port 1
off on off on

Port 2
off off on on

50

TCP/IP-Sockets – Binary

The IO structure Options
This structure is used to set certain options in the Web-IO. For this purpose 32 bits are available in the variable options.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
2. Byte der Struktur

Low-Byte 1. Byte der Struktur

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 High-Byte
4. Byte der Struktur

Low-Byte 3. Byte der Struktur

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

01 F0 High-Byte
6. Byte der Struktur

Low-Byte 5. Byte der Struktur

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 10 High-Byte
8. Byte der Struktur

Low-Byte 7. Byte der Struktur

16 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 01 12. Byte der Struktur

11. Byte der Struktur

10. Byte der Struktur

9. Byte der Struktur

32 Bit Variable

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 16. Byte der Struktur

15. Byte der Struktur

14. Byte der Struktur

13. Byte der Struktur

32 Bit Variable

Start_1 Start_2 StructType StructLength Version Options

Integer Immer = 0 Integer Immer = 0 Integer Strukturtype Integer Länge in Bytes Long Version z.Zt. 1 Long Binäre Kodierung

In der vorliegenden Version des Web-IO wird nur das Bit 0 der Variablen options verwendet.

· Bit 0 = 1 //das Web-IO sendet die AnalogRegisterState Struktur zurück, wenn ein Output gesetzt wird.
· Bit 0 = 0 //das Web-IO gibt bei Setzen eines Output keine Rückmeldung.
Um in der Rückmeldung zuverlässig den Zustand nach Setzen des/der Output(s) zu bekommen, sollte zwischen zwei Output-verändernden Zugriffen min. eine Zeit 50ms liegen.

51

TCP/IP-Sockets – Binary

Device status via binary structures

The structure ReadDiagnosis
If the Web-IO determines that there is a communications or system error, the latter is listed on the HTML page diag and can be read using the browser. Since error management via browser for program-controlled applications is not always available, the error status of the Web-IO can be queried using the structure ReadDiagnosis

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 D1 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

The Web-IO replies with a Diagnosis type structure.

The structure Diagnosis
The Web-IO replies to the ReadDiagnosis structure with a Diagnosis type structure.

52

TCP/IP-Sockets – Binary

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 D0 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 1C high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 04 12. byte of structure

11. byte of structure

10. byte of structure

9. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 00 XX 16. byte of structure

15. byte of structure

14. byte of structure

13. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 20. byte of structure

19. byte of structure

18. byte of structure

17. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 24. byte of structure

23. byte of structure

22. byte of structure

21. byte of structure

32 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

XX XX XX XX 28. byte of structure

27. byte of structure

26. byte of structure

25. byte of structure

32 bit value

Start_1

Word always = 0

Start_2

Word always = 0

StructType

Word Structure type

StructLength

Word Length in bytes

Version

Long currently = 4

ErrorCount Errorbits1

Long current error number Long binary error coding

Errorbits2 Errorbits3

Long binary error coding Long binary error coding

The variable diag_error_count returns how many various errors are currently in the error memory. The Web-IO distinguishes a total of up to 64 different error sates, whereby each set bit of the two variables diag_errrorbits0 and diag_errorbits1 stands for an error type.
The exact text description can be obtained on TCP Port 80. For a more detailed description, see the section on socket programming with command strings.

The structure ClearDiagnosis
This structure clears the error memory of the Web-IO.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 D2 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

53

TCP/IP-Sockets – Binary

Device features via binary structure

The structure InventoryRequest
To query the IO equipment of the Web IO, the InventoryRequest structure is sent to the Web IO.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 F1 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 08 high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

Start_1 Start_2 StructType StructLength

Word always = 0 Word always = 0 Word Structure type Word Length in bytes

the structure Inventory
If the Web IO receives the InventoryRequest structure, it responds with the Inventory structure.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
2. byte of structure

low byte 1. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 00 high byte
4. byte of structure

low byte 3. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 F2 high byte
6. byte of structure

low byte 5. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
8. byte of structure

low byte 7. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
10. byte of structure

low byte 9. byte of structure

16 bit value

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

00 XX high byte
12. byte of structure

low byte 11. byte of structure

16 bit value

Start_1

Word always = 0

Start_2

Word always = 0

StructType

Word Structure type

StructLength

Word Length in bytes

Amount

Word Number of IO mode entries

IO-Mode

Word high byte = IO chanel no. low byte = IO chanel mode

15 14 13 12 11 10 9 8 7 6 5 4 3

high byte 12+n*2 Byte

XX low byte 11+n*2 byte of

16 bit value

210
XX

In the Amount variable, the Web IO specifies how many IO mode entries the structure contains.
54

TCP/IP-Sockets – Binary
Each entry consists of the channel number as a high byte and the available IO mode as a low byte. If more than one value or state can be retrieved from an IO channel, there is an entry for each retrievable parameter (e.g. for digital input, one entry for the input state and another for the counter value). IO chanel mode The IO modes are numbered as follows: 1 analogue input (4..20mA or 0..10V) 2 digital input 3 digital output (read and write access) 4 counter 5 digital output (read access only) 6 analogue output IO chanel no The IO channel number corresponds to the indexing of the individual inputs or outputs. Depending on the IO type, the indexing can start at 0 (e.g. for digital Web IOs) or 1 (e.g. for analogue Web IOs)
55

HTTP-Request
HTTP-Request

In addition to the classic socket access, the Web-IO can also be addressed directly via the HTTP access by HTTP requests
This access is disabled at in factory defaults and must be activated in the menu tree at Communication paths >> Web-API.
In addition, the Web-IO offers the option of uploading and saving your own, self-programmed website under visualizations >> My website. Your own website can be accessed via the menu tree under My Website or the name you have given. But there is also a direct call via the URL possible:
http: // / user
Supported requests (commands)
The following list shows all supported HTTP requests
Further details on access using web techniques such as AJAX or PHP can be found on the following pages.

Web-IO Digital Kommandos
/inputx

Parameter
?PW=password& The administrator or user password must be used instead of password. If no password has been assigned, PW=& is entered. (applies to all commands!)

Beschreibung
Input status request x optionally specifies the no. of the input and can be between 0 and 16 depending on the model. The feedback of the Web IO is a string starting with inputx; followed by the input status: ON = signal at the input and OFF = no signal at the input If x is omitted completely, the Web IO returns a bit pattern corresponding to the input signals in hexadecimal notation.

56

Kommandos
/counterx /counter /outputx
/outputaccessx
/counterclearx

HTTP-Request

Parameter

Beschreibung

?PW=password&

Counter value request x can be a value between 0-11 and indicates the input. The feedback from the Web IO is a string beginning with counterx;. The counter value of the selected counter is appended in decimal notation.

?PW=password&

Requesting all counter values The feedback of the Web IO is a string beginning with counter;. The counter values are added in decimal notation separated by semicolons.

?PW=password&

Output status request
x optionally specifies the No. of the output and can be between 0 and 16 depending on the model. The feedback from the Web IO is a string starting with outputx; followed by the output status: ON = signal at the output and OFF = no signal at the output If x is omitted completely, the Web IO returns a bit pattern corresponding to the output signals in hexadecimal notation.

?PW=password& [Mask=XXXX&] State=ON/OFF/YYYY& [NA=ON&] ON: Output = 1, OFF: Output = 0, TOGGLE: Change of state XXXX: Hex value between 0000 and 0FFF according to the bits that are to be set YYYY: Hex value between 0000 und 0FFF according to the output bit pattern.

Set one or more outputs x can be a value between 0-11 and spec-
ifies the output to be set. The feedback of the Web IO is a string starting with ,,output;” followed by a bit pattern corresponding to the output signals in hexadecimal notation.
The specification of Mask is optional. If Mask is not sent, the outputaccess command applies to all outputs. With NA=ON it is optionally achieved that no response to the outputaccess command is sent by the Web IO.

?PW=password& [Set=value&] value: Counter preset, value between 0 and 2 billion

Sets the counter value of a counter. If the Set parameter is not sent, the default is 0. x can be a value between 0-11 and specifies the input whose counter is to be reset. The response of the Web IO is a string beginning with counterx;. The new count of the selected counter is appended in decimal notation. If x is not specified, all counters are set.

57

HTTP-Request
Kommandos
/allout
/time /settime /diagnosis
/diagnosisx
/diaglistx /diagclear /errorclear

Parameter
?PW=password&
?PW=password& ?PW=password& time=DD.MM.YYYY, hh:mm:ss& ?PW=password&
?PW=password&
?PW=password& ?PW=password& ?PW=password&

Beschreibung
Collective request of the input, output states and all counter values. The Web IO responds with a string of the following structure: input;0xxx;output;0xxx;counter;n0;n1;n2,… 0xxx corresponds to the status of the inputs or outputs in hexadecimal notation. n0,n1 etc. contain the counter states in decimal notation.
Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second
Sets the system time of the Web IO to the value passed with time.
Requests the status of the diagnostic memory. The Web IO returns: diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.
With x, the index for one of the currently stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.
Returns the messages for the individual message bits (max. 92)
Clears message memory
Clears load errors and releases the affected outputs.

58

HTTP-Request

Web-IO Analog Kommandos
/singlex
/outputx /outputaccessx
/time /settime /diagnosis
/diagnosisx /diaglistx /diagclear

Parameter
keine
keine ?PW=password& State=N,NNN& N,NNN: Strom- bzw. Spannungswert der am entsprechenden output eingestellt werden soll
?PW=password&
?PW=password& time=DD.MM.YYYY, hh:mm:ss& ?PW=password&
?PW=password&
?PW=password& ?PW=password&

Beschreibung
Request for the current current or voltage values in mA or V. x optionally indicates the no. of the IO channel and can be 1 or 2. The feedback of the Web-IO is a string that shows the value with three decimal places and unit [N]N.NNN mA or [N] N.NNN V If x is omitted completely, the Web IO returns the values of both channels separated by semicolons.
gives the same result as GET /singlex (even if IO channels work as input)
Setting an output x can be 1 or 2 and indicates the output to be set. The feedback of the Web IO is a string in the format [N]N.NNN mA or [N] N.NNN V. and indicates the current value. Please note that the Web IO needs a few ms to set the desired value. Therefore, the value does not correspond to the desired value.
Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second
Sets the system time of the Web IO to the value passed with time.
Requests the status of the diagnostic memory. The Web IO returns: diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.
With x, the index for one of the currently stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.
Returns the messages for the individual message bits (max. 92)
Clears message memory

59

HTTP-Request

Web-IO Klima (Web-Thermometer, …) und VOC

Kommandos

Parameter

Beschreibung

/singlex

keine

Request for the current climate data x optionally indicates the no. of the sensor. The feedback of the Web-thermometer is a string that shows the value with one decimal digit and unit
24,0°C If x is omitted completely, the Web IO returns the values of both channels separated by semicolons.

/time

?PW=password&

Returns the system time of the Web IO. Format: DD.MM.YYYY,hh:mm:ss D=Day, M=Month, Y=Year, h=Hour, m=Minute, s=Second

/settime

?PW=password& time=DD.MM.YYYY,
hh:mm:ss&

Sets the system time of the Web IO to the value passed with time.

/diagnosis

?PW=password&

Requests the status of the diagnostic memory. The Web IO returns:
diagnosis;0000;00000000; 00000000;00000000 the four-digit value indicates the number of stored messages. With the three eight-digit hexadecimal values, each set bit represents one of the 92 possible messages.

/diagnosisx

?PW=password&

With x, the index for one of the currently
stored messages is specified. The Web IO sends the corresponding message text as a return. x must not be greater than the number of the currently present messages.

/diaglistx

?PW=password&

Returns the messages for the individual message bits (max. 92)

/diagclear

?PW=password&

Clears message memory

60

HTTP-Request
An example for use of HTTP requests
The following example shows how you can construct a self-refreshing Web page for the Web-IO using JavaScript and
HTML – structure of a static web page
HTTP requests (AJAX). First the purely HTML section of the Web page, which serves in essence as a display foundation for AJAX:
<!DOCTYPE html PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>

HTTP-Request

HTTP-Request
JavaScript and AJAX – Change content dynamically
The functions shown below are based on two basic techniques:
· Identification and later changing of an HTML object using a unique ID · Communication with the server (Web-IO) after loading the Web page using
HTTP requests
The JavaScript which is part of the Web page uses both these techniques.
First maxi and maxo are used to determine how many inputs and outputs are to be supported. A variable applicationstep is defined for the various program steps. 500ms is specified as the request interval, and a variable is entered for the password.
var maxi = 2; var maxo = 2; var applicationstep = 0; var interval = 500; var iopassword = ,; The HextoInt function calculates hexadecimal strings to decimal values. function HexToInt(HexStr) { var TempVal; var HexVal=0; for( var i=0; i<HexStr.length;i++) { if (HexStr.charCodeAt(i) > 57) { TempVal = HexStr.charCodeAt(i) – 55; } else { TempVal = HexStr.charCodeAt(i) – 48; } HexVal=HexVal+TempVal*Math.pow(16, HexStr.length-i-1); } return HexVal; } The function CommandLoop combines the HTTP requests and sends them to the DataRequest function. function CommandLoop() { var commandstring =”; applicationstep++; switch(applicationstep) { case 1: commandstring =input?PW=’ + iopassword + &’; break; case 2: commandstring =output?PW=’ + iopassword + `&’;
63

HTTP-Request
break; case 3:
commandstring = counter?PW=’ + iopassword +&’; applicationstep = 0; break; } DataRequest(commandstring); maintimer = setTimeout(“CommandLoop()”, interval); }

The DataRequest function is the heart of this JavaScript. It receives the HTTP request and sends it to the server (Web-IO). The DataRequest function also receives the reply from the Web-IO and sends it to the updateDisplay function.

function DataRequest(SendString)

{ var xmlHttp;

if( window.ActiveXObject )

// Internet Explorer

{ xmlHttp = new ActiveXObject( Microsoft.XMLHTTP” );

}

else if(window.XMLHttpRequest ) // Mozilla, Opera und Safari

{ xmlHttp = new XMLHttpRequest();

}

if (xmlHttp)

{ xmlHttp.onreadystatechange = function()

{ if (xmlHttp.readyState == 4)

{ if (xmlHttp.status == 200)

{ if (xmlHttp.responseText.length > 0)

{ updateDisplay(xmlHttp.responseText);

}

xmlHttp=null;

}

}

}

xmlHttp.open(“GET”, SendString, true);

xmlHttp.setRequestHeader(“Connection”, “close”);

xmlHttp.setRequestHeader(“If-Modified-Since”, “Thu, 1 Jan 1970

00:00:00 GMT”);

xmlHttp.send(null);

}

}

The updateDisplay function evaluates the reply from the Web-IO and correspondingly adjusts the browser display. A check is made as to whether the Web-IO reply refers to inputs, outputs or counters. JavaScript uses document.getElementById(ID) to identify the objects for changing and adjusts their properties to the actual IO status
function updateDisplay(ReceiveStr) { var HexVal;
var state; var ReceiveData = ReceiveStr.split(;’) // Display Intput state if (ReceiveData[ReceiveData.length – 2].substring(0, 1) ==i’) { HexVal = HexToInt(ReceiveData[ReceiveData.length – 1]);
64

HTTP-Request

for (var i = 0; i < 2; i++)

{ state = false;

if ((HexVal & Math.pow(2, i)) == Math.pow(2, i))

{ state = true;

}

document.getElementById(`input’+i).firstChild.data =( !state ) ?

`OFF’:’ON’;

document.getElementById(`input’+i).style.color

= ( !state ) ? #000000′ :#006600′;

document.getElementById(`input’+i).style.fontWeight

= ( !state ) ? normal’ :bold’;

}

}

// Display Output state

if (ReceiveData[ReceiveData.length – 2].substring(0, 1) == `o’)

{ HexVal = HexToInt(ReceiveData[ReceiveData.length – 1]);

for (var i = 0; i < 2; i++)

{ state = false;

if ((HexVal & Math.pow(2, i)) == Math.pow(2, i))

{ state = true;

}

document.getElementById(`output’+i).firstChild.data = ( !state ) ?

OFF’ :ON’;

document.getElementById(`output’+i).style.color

= ( !state ) ? #000000′ :#006600′;

document.getElementById(`output’+i).style.fontWeight

= ( !state ) ? normal’ :bold’;

}

}

//Display Counter

if (ReceiveData.length – maxi – 1 >= 0)

{ if (ReceiveData[ReceiveData.length – maxi – 1].substring(0, 1) == `c’)

{ for (var i = 0; i < maxi; i++)

{ document.getElementById(`counter’ + i).innerHTML

= ReceiveData[ReceiveData.length – maxi + i]

}

}

}

//Display cleared Counter

if (ReceiveData[ReceiveData.length – 2].substring(0, 1) == `c’)

{ document.getElementById(`counter’

+ ReceiveData[ReceiveData.length – 2].substring(7,

ReceiveData[ReceiveData.length –

2].length)).innerHTML =

ReceiveData[ReceiveData.length – 1];

}

}

The setOutput function sends the corresponding command for toggling the selected output to the DataRequest function.
function setOutput(iNr) { var commandstring = `outputaccess’+iNr+’?PW=’+iopassword+’&State=TOGGLE&’;
DataRequest(commandstring); }
The clearCounter function sends the corresponding command for clearing the
65

HTTP-Request
counter state of the selected counter to the DataRequest function.
function clearCounter(iNr) { DataRequest(counterclear’+iNr+’?PW=’+iopassword+’&’); } The setPassword takes the entered password and writes it to the iopassword variable, which is a component of the command string. function setPassword() { iopassword = document.getElementById(pw’).value;
document.getElementById(pw’).value =’; }
The AJAX technique shown here, which is based on HTTP requests, can only be used if the web page is can only be used if the web page is loaded directly from the Web IO. For security reasons the most common browsers prevent HTTP requests that are sent subsequently from being to other servers than the one from which the original web page was loaded was loaded. This technique is called Same Origin Policy (SOP).
A decisive disadvantage of this SOP restriction is that the normal AJAX technology does not allow a common web page to display, for example, the states of two different web IOs.
CORS – Cross Origin Resource Sharing
To circumvent the SOP restriction, cross-origin resource sharing is used. sharing. In order to be able to use this technique with the Web IO, Cross Origin must be activated under Communication Routes >> Web API in the Advanced Settings area, Cross Origin must be activated.
The URL of the server from which the original web page was loaded must be entered as the URL of the requestor, from which the original web page was loaded.
If the web page is loaded directly from the hard disk of the local PC, ,,” must be entered as the URL of the requester. ,,” is synonymous with all URLs allowed.
66

HTTP-Request
In the JavaScript part, the DataRequest function in particular must be structured differently.
function DataRequest(device, SendString) { var cor;
if(window.XDomainRequest) { cor = new XDomainRequest(); } else { cor = new XMLHttpRequest(); } if (cor) { cor.onreadystatechange = function()
{ if(cor.readyState == 4) { updateDisplay(cor.responseText); }
} cor.open(GET’,http://’+device+’/’+SendString); cor.send(); } else { alert(`Your Browser does not support Cross Origin Request’); } }
In contrast to the original function, the extended request method XDomainRe-
67

HTTP-Request
quest() or XMLHttpRequest() is used. When formulating the request, the complete URL including the IP address or the host name must be passed (variable device).var device = 10.40.22.242′; The functions that call DataRequest must of course be adapted accordingly. function CommandLoop() { var commandstring =”; applicationstep++; switch(applicationstep) { case 1: commandstring =input?PW=’ + iopassword + &’; break; case 2: commandstring =output?PW=’ + iopassword + &’; break; case 3: commandstring =counter?PW=’ + iopassword + &’; applicationstep = 0; break; } DataRequest(device, commandstring); maintimer = setTimeout(“CommandLoop()”, interval); } function setOutput(iNr) { var commandstring=outputaccess’+iNr+’?PW=’+iopassword+’&State=TOGGLE&’; DataRequest(device, commandstring); } function clearCounter(iNr) { DataRequest(device, counterclear’+iNr+’?PW=’+iopassword+’&’);
Using W&T Tags
As described in section ,,5.1.4 Labeling and texts” the Web-IO itself can be used to freely name and label inputs, outputs and counters.
A corresponding display in the browser is accomplished by using W&T tags. W&T tags are placeholders which are replaced by the Web-IO when sending the Web page to the browser using the stored names. This makes it possible for one and the same Web page to have a different appearance in different Web-IOs.
These tags consist of <w&t_tags= and the actual function invocation.
<w&t_tags=time>
for example shows the current system time and the date in the browser.
68

HTTP-Request

There is a special feature of the W&T tags which show the status of the outputs and the counter states of the input counters.
<w&t_tags=ox> and <w&t_tags=cx>

When there is an administrator or operator login the displayed contents (ON/OFF or counter state) has a hyperlink. Clicking on this link changes the state of the outputs or sets the counter to 0.
So that the changed state is then displayed, the browser automatically reloads the Web page.
The following W&T tags are available:

W&T-Tag <w&ttags=device name> <w&ttags=device text> <w&t_tags=location>
<w&t_tags=contact>
<w&t_tags=inputx>

Beschreibung/Funktion Inserts the name assigned for the Web-IO in the web site.
Inserts the description defined for the Web-IO in the web site. Inserts the location assigned for the Web-IO in the web site. Inserts the contact assigned for the Web-IO in the web site.
Inserts the name specified for input no. x.

<w&t_tags=ix> <w&t_tags=cx> <w&t_tags=outputx>

x can be a number between 0-11 and indicates which input the invoke refers to. This applies as well to the output and counter invokes described below.
Indicates the state (ON/OFF) of the input corresponding to x.
Fügt den Zählerstand des Counters für Input x in die Webseite ein.
Inserts the name specified for Output x

69

HTTP-Request
W&T-Tag <w&t_tags=ox>
<w&t_tags=time>

Beschreibung/Funktion
Shows the state (ON/OFF) of the output corresponding to x. When logging in with Operator or Administrator rights, the state indication is given a hyperlink. Clicking on this link changes the state of the corresponding output and refreshes the web site
Inserts the system time and data of the Web-IO in the Web site.

HTTP requests outside the browser
The HTTP requests shown here can also be used with other web techniques such as PHP.
The web IOs can also be controlled via HTTP requests using tools such as cURL.
When calling cURL, the URL should be placed in inverted commas when passing the parameters:
Example:
curl “http://10.40.22.242/outputaccess1?PW=&State=TOGGLE&”

A combination of cURL and PHP is also possible:

<?php

$URL = ‘http://10.40.22.242/outputaccess1?PW=&State=TOGGLE&’;

$ch = curl_init();

$options = array(

CURLOPT_URL

=> $URL,

CURLOPT_RETURNTRANSFER => true,

CURLOPT_HEADER

=> false,

CURLOPT_ENCODING

=> “”,

CURLOPT_USERAGENT

=> “webio”,

CURLOPT_CONNECTTIMEOUT => 20,

CURLOPT_TIMEOUT

=> 20,

CURLOPT_MAXREDIRS

=> 1,

CURLOPT_SSL_VERIFYHOST => false,

CURLOPT_SSL_VERIFYPEER => false);

curl_setopt_array( $ch, $options );

$data = curl_exec($ch);

if ($data==false)

{ die(‘ERROR ‘.$URL); }

else

{ $http_status = curl_getinfo($ch, CURLINFO_HTTP_CODE);

if ($http_status==200)

70

{ echo $data; } else { die(‘Not found ‘.$URL); } } curl_close($ch);
?>

HTTP-Request

71

REST – Representational State Transfer
REST – Representational State Transfer
With REST (Representational State Transfer), the Web IOs provide another webbased communication channel.
Communication takes place via Web IO specific HTTP requests via the HTTP or HTTPS port entered under Basic Settings >> Network >> Access for Web Services.
To be able to exchange REST data, access must first be activated via Communication Paths >> Rest.
If REST access is to be protected against unauthorised access, you have the option of activating digest authentication. The requests must then be made as user “admin” with the administrator password or as user “operator” with the user password.
For the Web-IO Digital and Analogue units, it can also be specified whether the outputs may be changed via REST.
For read access, REST uses the HTTP command GET.
The Web IO supports three formats for responses to REST requests:
· JSON · XML · Text
JSON
Read access
For read access REST uses the HTTP command GET.
The Web-IO supports three formats for replies to REST requests:
The format used for replies can be determined using the request. Using
http:///rest/json
72

REST – Representational State Transfer
for example opens the entire process image of the Web-IO in JSON format. The re-
ply then looks as follows:
{ “info” : { “request” : ” / rest / json”, “time” : “2016 – 09 – 09, 09 : 42 : 54”, “ip” : “10.40.22.227”, “devicename” : “WEBIO – CAFE27” }, “iostate” : { “input” : [ { “number” : 0, “state” : 0 }, { “number” : 1, “state” : 0 } ], “output” : [ { “number” : 0, “state” : 0 }, { “number” : 1, “state” : 0 } ], “counter” : [ { “number” : 0, “state” : 0 }, { “number” : 1, “state” : 0 } ] }, “system” : { “time” : { “time” : “2016 – 09 – 09, 09 : 42 : 54” }, “diagnosis” : [ { “time” : “06.09.2016 09 : 42 : 54”, “msg” : “Gerätestatus : OK” } ], “diagarchive” : [
73

REST – Representational State Transfer
{ “time” : “06.09.2016 09 : 42 : 54”, “msg” : “Gerätestatus : OK”
} ] } }
With the Web-IO Analogue, the answer would be structured as follows:
{ “info”: { “request”: “/rest/json”, “time”: “2020-01-27,10:37:23”, “ip”: “10.40.22.13”, “devicename”: “WEBIO-0873E3” }, “iostate”: { “output”: [{ “name”: “kanal 1”, “number”: 0, “unit”: “mA”, “value”: 3.8 }, { “name”: “Kanal 2”, “number”: 1, “unit”: “mA”, “value”: 16.8 }] }, “system”: { “time”: “2020-01-27,10:37:23”, “diagnosis”: [{ “time”: “27.01.2020 10:37:23”, “msg”: “Gerätestatus: OK” }], “diagarchive”: [{ “time”: “27.01.2020 10:37:23”, “msg”: “Gerätestatus: OK” }] }
}
To query only individual areas or points, the query can be formulated in more detail. Here, for example, the query of the inputs of a Web-IO Digital:
http:///rest/json/iostate/input
This causes the Web IO to return the status of all inputs:
{ “iostate” : { “input” : [ { “number” : 0,
74

REST – Representational State Transfer
“state” : 0 }, {
“number” : 1, “state” : 0 } ] } }
With
http:///rest/json/iostate/input/0
the state of input 0 can be specifically queried.
{ “iostate” : { “input” : [ { “number” : 0, “state” : 0 } ] }
}
Changing access
For accesses that change the switching state of the outputs or delete the counters, POST is used.
For example, to set Output 1 to ON, a POST is sent to the following URL:
http:///rest/json/iostate/output/1
The following parameters are passedas payload:
Set=ON
The Web IO responds with
{ “iostate” : { “output” : [ { “number” : 1, 75

REST – Representational State Transfer
“state” : 1 } ] } }
The Web IO responds with
The output can be switched off via the same URL with the parameter Set=OFF. The deletion, e.g. of Counter1, is done via a POST to the following URL:
http:///rest/json/iostate/counterclear/1
The Web IO responds with
{ “iostate” : { “counter” : [ { “number” : 1, “state” : 0 } ] }
}
To get the answers in one of the other formats, simply replace the keyword json with xml or text.
76

REST – Representational State Transfer
XML
Reading access
With
http:///rest/xml
the entire process image of the Web IO can be retrieved in XML format. The response then looks like this:
<?xml version=”1.0″ encoding=”UTF-8″?>