Expert - Data block (reception)

A received data block can contain the following data:
- Any desired quantity of data
- Fixed quantity of data
- Text
- Binary data
- Communication object as plain text
- Communication object as binary data
- Text from the predefined list
- Text/Value with fixed length

1.Data block: Any desired quantity of data

The response contains any random quantity of data that does not need to be processed. A "text" or binary data must follow. If you use this character, the data for this section is not processed.

2.Data block: Fixed quantity of data

If a fixed quantity of data is expected in the response. The respective length must be specified.

3.Data block: Text

Expects a text. A Carriage Return (CR) and/or a Line Feed (LF) can be appended to the text as an option. In addition, the text can also contain special characters as hexadecimal values. The special characters are then entered in the form \x??, and the hexadecimal value is initiated with an \x and must always be two-digit. In order to keep \, it is also possible to enter \\. A help function for entering hexadecimal values is also available in the input line.

Example: \x09 (Expects a TAB character)

4.Data block: Binary data (in hex form)

Expects data in binary form. This means the hexadecimal value FF80FF would send three bytes (255,128,255) as a response.

5.Data block: Communication object as plain text

Expects a value as plain text. The received value is written to a communication object.

Note

If the value contains spaces, tabulators, or line breaks, before or after the text, these are truncated.

Note

Negative values are only recognised if the minus sign is directly in front of the number.

5.1.Communication object

The received value is written to this communication object

Numerical format

Determines in which numerical format the data is received. The following formats are possible:

Standard
The data is "normal". A point is expected as decimal separator. The value can be introduced with a minus/plus character.
#
An integer value is expected.
Example: If the data block contains the value 1234.56, the communication object receives the value 1234.
#,###
An integer value with comma is expected as thousand separator.
Example: If the data block contains the value 1,234.56, the communication object receives the value 1234.
#.###
An integer value with a period is expected as thousand separator.
Example: If the data block contains the value 1.234,56, the communication object receives the value 1234.
#.#
A floating-point value with a period as decimal separator is expected.
Example: If the data block contains the value 1234.56, the communication object receives the value 1234.56.
#,#
A floating-point value with a comma as decimal separator is expected.
Example: If the data block contains the value 1234,56, the communication object receives the value 1234.56.
#,###.#
A floating-point value with a comma as thousand separator and period as decimal separator is expected.
Example: If the data block contains the value 1,234.56, the communication object receives the value 1234.56.
#.###,#
A floating-point value with a comma as thousand separator and a comma as decimal separator is expected.
Example: If the data block contains the value 1.234,56, the communication object receives the value 1234.56.

Note

Numerical values end as soon as an alphanumeric character occurs in the data block. Example: If the data block contains the value 14.5°C, the numerical value is recognised up to the ° sign, so in this case 14.5.

6.Data block: Communication object as binary data

Expects a value as binary data. The received value is written to a communication object. The expected value can be defined in the following data formats:
- 1 byte (0..255)
- 1 byte (-128..127)
- 2 bytes (0..65535)
- 2 bytes (-32768..32767)
- 4 bytes (-2147483648..2147483647)
- 4 bytes (0..4294967295)
- 4-byte floating point
- 8-byte floating point

7.Data block: Text from the predefined list

Expects a text from a defined selection list. The text is assigned to the value in the following field. A corresponding notation must be complied with for this purpose.

7.1.Communication object

In this communication object, the value controlled by the received text is written.

List

General notation:
Text=value

Example:
Rainy=0
Fair to cloudy=1
Sunny=2
Undefined=4

Each text-value combination has to be in its own line. Partial hits are possible in the evaluation of the defined list. If the telegram contains, for example, the text Northern, but only the text North is defined in the list, and not the value Northern, then text Northern is accepted as a hit. The value of the hit found first is used. Observe use of upper case/lower case characters. If the text does not correspond to any text in the list, the communication object receives the value 0.

8.Data block: Text/Value with fixed length

Expects an n-character long value as plain text. The received value is written to a communication object.

Note

If the value contains spaces, tabulators, or line breaks, before or after the text, these are truncated.

Convert data

The subsequent fields depend on the set type of the data block.

8.1.Use URL quoting

Yes: The data block is coded in accordance with the HTTP standard. Example: The text Fair%20to%20cloudy then becomes Fair to cloudy
No: The text is processed untreated.

8.2.Use conversion table

Yes: Converts the data before processing using the defined conversion table.
No: The data continues to be processed without being treated.

8.3.Cut off data after zero byte

Yes: If the data block contains a zero byte, all the data behind the zero byte is cut off.
No: The data continues to be processed without being treated.