Components > Communication > Multi-IO-IP

Entries editor

The properties of the entry editor depend on the selected transport protocol.

Features independent of transmission:

Name

This name is displayed as an input name on the component.

Prefix / Postfix

Here a prefix / postfix can be selected from a list.

Data filters

A previously defined data filter can be selected from a list.

Answer

In order to process received data from several filters, entries can be concatenated. The "Redirect" field of each entry contains a list of all other entries. If an entry is selected, this means that the received data is processed by the filter of the current entry as well as by the filter of the entry selected here. It is possible to concatenate several filters by selecting additional entries. If a filter can not extract data and an entry is selected in the Redirect field, the data is still passed to the selected entry.

There is the possibility to direct a response to any number of MultiIO outputs.

Protocol-dependent transmission:

TCP / UDP

command

When an "On" or "Off" arrives at the corresponding data point, the value of the "Command (Hex or ASCII)" field is sent. If the value is not equal to bool, this value is used to create the request URL and the value in the "Command (Hex or ASCII)" field is ignored. Since TCP / UDP allows the sending of binary data, Hex values and Escap sequences can also be specified here (see chapter "Binary representation and Escap sequences").

If the value of the "Command (Hex or ASCII)" field is used for the user data, the following steps and conversion attempts are applied to the data:

It is first tried to convert the string completely into a binary representation. For this purpose, the entire string can only consist of hex values. If this is successful, the binary data to be sent already exist and the data are sent.

If the conversion is unsuccessful, all supported escap sequences are substituted.

Then, the data is concatenated with the possible prefix / postfix values (here the same strategy, first hex values try to convert, then convert the escap sequences) and the finished user data are sent.

If the data has been transferred to the component via the EisBaer network, DataPointValue and String values are converted to a byte array. Thereafter, the same conversion rules as explained above are applied.

Example:

Expected answer

After the component has sent the data to the server or device via the TCP or UDP protocol, a response is compared to the value of this field to implement the principle of positive and negative acknowledgment. If the received value corresponds to this value, the device has acknowledged reception and nothing happens. If the value is not equal, a message is sent to the error message output. Similarly, if a connection has not been established. This value is also used to convert hex to a byte array and to substitute the escaped sequences.

Only receivable

To be able to receive asynchronous request data asynchronously, the "Only receivable" field can be activated. Data received from the network without a request has been filtered only by those entries that are marked with this check mark. For example, two EisBaer instances can communicate with each other by exchanging these UDP telegrams with a particular structure.

Coding

This parameter defines the coding of the data to be sent over the network. Depending on the remote, the correct coding must be set here.

The following encodings can be selected:

ASCII (7 bit)

Unicode (16 bit, little endian)

Unicode (16 bit, big endian)

HTTP

The component can be used to send HTTP-GET Web Requests and HTTP Post Commands.

The first two fields allow the user to select entries from the prefix postfix and the data filter editor list.

command

Here a fixed value can be specified, which can be sent as a Web Request by the component. This value is only sent by the component if an "On" or "Off" arrives at the corresponding input. If a value is not equal to bool for this input, the string from the "Command" field is ignored and the received value, in character string representation, is taken instead of the value of the "Command" field to form the request URL. The prefix / postfix entry is still applied to it.

Example:

URL

In the "URL" field, both the IP and the target port as well as parts of the request URL can be attached, to which the complete string (see above) is attached.

Example:

Http: // <IP_ADDRESS>: <PORT> / XXX

The resulting request URL has the following pattern:

Http: // <IP_ADDRESS>: <PORT> / XXX <PREFIX> <DATA> <POSTFIX>

HttpMethod

GET - Queries of data from a specified resource

POST - Sends data to a specified resource to be processed

Channel

Channel