1.Introduction
This function allows any structured data to be sent via an IP connection. Sending is not limited to pure text, rather also enables working with binary data.
Two different types of telegram are supported:
- Telegrams to IP devices
- Telegrams to 14-byte communication objects
In order to send a defined telegram, there is the command type "Send IP/EIB telegram" under Commands. The last telegrams that were sent are logged on the debug page in the Send event section.
Two different types of telegram are supported:
- Telegrams to IP devices
- Telegrams to 14-byte communication objects
In order to send a defined telegram, there is the command type "Send IP/EIB telegram" under Commands. The last telegrams that were sent are logged on the debug page in the Send event section.
2.Application
- Exchange of values between two HS/FS.
- Control of external IP devices, e.g., IP cameras.
- Display of values on devices with 14-byte capability.
- Control of serial devices via serial IP converter.
- Control of external IP devices, e.g., IP cameras.
- Display of values on devices with 14-byte capability.
- Control of serial devices via serial IP converter.
4.Importing and exporting libraries
Completed telegrams can be saved as a library with import and export functions and used again in other projects. It is possible to export individual telegrams or complete folders including subfolders. If a library contains several queries, these are always imported in a single stage, this means one folder is saved at maximum. All telegrams can then be found in this folder.
During the import, it possible to directly enter the IP/Host address, the IP port, or the communication object for all telegrams. The data is suggested that is found in the library to be imported from the HS/FS-Expert. All the imported telegrams are pre-assigned these values. Different fields can be active depending on the type of the library.
If further objects are used in the library (e.g. communication objects, sequences, etc.), a project-specific implementation has to be carried out in the "Objects" tab. On the basis of the object description, you can recognise which function the object has.
During the import, it possible to directly enter the IP/Host address, the IP port, or the communication object for all telegrams. The data is suggested that is found in the library to be imported from the HS/FS-Expert. All the imported telegrams are pre-assigned these values. Different fields can be active depending on the type of the library.
If further objects are used in the library (e.g. communication objects, sequences, etc.), a project-specific implementation has to be carried out in the "Objects" tab. On the basis of the object description, you can recognise which function the object has.
5.Recipient
Telegram type
The following types are supported:
- TCP (TCP stands for Transmission Control Protocol)
- UDP (UDP stands for User Datagram Protocol)
- UDP/Multicast
- UDP/Broadcast
- TCP (TCP stands for Transmission Control Protocol)
- UDP (UDP stands for User Datagram Protocol)
- UDP/Multicast
- UDP/Broadcast
Note
UDP/Multicast addresses are located as a rule in the range 224.x.x.x to 239.x.x.x
Note
As a rule, UDP/Broadcast addresses end with x.x.x.255
6.Send
The different data blocks to be sent are defined in this list. All of the data blocks defined in this list result in a telegram. They are sent in the defined sequence.
7.Commands
Commands can be executed after the sending process. A difference is made between successful and failed transmission.
The Send event section is provided on the debug page for troubleshooting.
The Send event section is provided on the debug page for troubleshooting.