Components > Communication

Using the "Multi-IO-IP" component, IP-Commands can be sent and received from any device or website. The component is invisible, ie, the operator cannot see it in Runtime.

Introduction

The multi-IO-IP component is used to send arbitrary data to an IP network and / or receive from this. In addition, software serialized internal data types between two Multi-IO components in different instances of Eisbaer (on different computers) can be replaced. For this the transport protocols TCP /IP, UDP / IP "and" http " are available, for example, to query data from a Web server.

The component can operate as usual client by parameterized or even on Input sent values sent to another IP endpoint, and the subsequent answer is processed and forwarded to an output of the component. This is based on the TCP, UDP and HTTP alike. The component can act as a server (receiver) by listening on a UDP port and received telegrams will be processed through the filters. Subsequently, these are forwarded to a data point connection. The component is not STANDALONE and send Telegrams back to the network, only when one other component above it should from a a received telegram send a value again to the component. The multi-IO-IP component is not an independent bidirectional server and can only receive telegrams based on UDP.

To extract from as formatted data structures, certain values, there are a number of filters. These filters can, for example, XML documents after retrieving an XML Document from a Web server to parse and extract a certain value. Subsequently it can in an internal data type in the editor configured to be converted and will be forwarded to an Output data point. The multi-IO-IP component is available for the PC under Microsoft. NET and Microsoft Windows CE under the. NET Compact Framework 2.0 in the same range of functions executable. The individual settings are discussed in the dialogues.

Data points of the component

Name	Type	Function
Debug [Text]	Output	Error messages (for example network errors, conversion errors, exceptions ...) are output here. These may be send to e.g. the "Value-dependent text" component.
Dynamic	Folder	The inputs / outputs for the data elements are displayed in the Dynamic folder. Different data points are made available depending on the type.
Driver On/Off	Bidirectional	Komponente zur Laufzeit (de)aktivieren
Sent telegrams [Text]	Output	The transmitted telegram is output in text form.
Sent telegrams [HEX]	Output	The transmitted telegram is output in HEX form.

Properties of the component

Name		Function
Transport Type	TCP	The transmission protocol (TCP, UDP or HTTP) is defined here
Filter	0	The data filter editor is used to extract values from the received raw data from the network and to send them to an ice bear network via the corresponding bi-directional input. After the data has been received and a data filter for an entry has been selected in the input list, this data is processed by one of the selected filters.
Prefix/Postfix	0	List of Prefixes/Postfixes for the commands of the Multi-IO-IP component.
Channels	0	The dynamic data points (inputs, outputs) of the Multi-IO-IP component are defined here
Settings	TCP/UDP	Settings for the HTTP/TCP/UDP connections
Timeout	1000	Response time to wait (in milliseconds) after an HTTP or TCP / UDP request. An error text is sent via the data point debug.
Driver On/Off		Hierüber kann eingestellt werden, ob die Komponente bei Start des Systems aktiv sein soll.