|
<< Click to Display Table of Contents >> Navigation: Components > IoT > MQTT > MQTT Bridge [x200] |
The MQTT-Bridge is used to exchange information between 2 MQTT-Brokers. The functionality of the bridge corresponds to two MQTT clients. Therefore, the access to topics can be set accordingly in the broker under "Allowed Clients".
Data points of the component
Name |
Type |
Function |
|---|---|---|
Diagnosis [Text] |
Output |
Error texts are output here. These can be displayed e.g. with the component "Protocol window". Attention: Diagnosis or debug outputs are only provided for the case of an error. Please use only after consultation with the support team! If used, these can considerably impair the performance of the service. |
Extended diagnosis |
Input |
(De)Enables the extended debug output. Attention: Diagnosis or Debug - outputs are only provided for the case of error. Please use only after consultation with the support team! If used, these can significantly affect the performance of the service. |
Driver On/Off |
Bidirectional |
(De)Activate the component. |
uptime bridge |
Output |
Runtime, how long the bridge connection between 2 brokers is online. |
Uptime Client A |
Output |
Term, how long the Broker A connection is online. |
Uptime Client B |
Output |
Runtime, how long the Broker B connection is online. |
Connection status Bridge |
Output |
Outputs the current connection status of the bridge as on/off signal. |
Connection status Client A |
Output |
Outputs the current connection status of Client-A as an on/off signal. |
Client B connection status |
Output |
Outputs the current connection status of client B as an on/off signal. |
Properties of the component
Name |
Standard |
Function |
|---|---|---|
Channels |
0 |
The topic to be transferred is entered here. If only # is entered, all topics are forwarded. |
Connection A |
... |
Editor for specifying the connection data to MQTT Broker A. |
Connection B |
... |
Editor for specifying the connection data to MQTT Broker B. |
Driver On/Off |
|
(De)Activating the component |
Connection A/B (to the broker):
Designation |
Function |
|---|---|
Server URL/IP |
Specification of the MQTT server (broker) to be queried. |
Port |
Specifying the communication port (1883 or 8883(TLS)). This port must be entered in the firewall. |
User / Password |
For authentication, the user name and password are required (leave blank for anonymous access). |
Timeout |
Communication timeout in seconds. |
Client ID |
Name for the client (this EisBaer component). This may only be used once. If the component is copied, a new ID must be generated. The ID must be at least 10 characters long. |
Websocket |
Optionally, you can specify whether the connection should be established via web socket. |
TLS |
Depending on the server, the connection can also be encrypted with TLS. This will activate the fields for "Accept all certificates" and "Server certificate". |
Accept all certificates |
The client accepts all server certificates. |
Server certificate |
Path specification to the server certificate that is to be used for communication. Example: C:\Program Files (x86)\Alexander Maier GmbH\EisBaer SCADA 3.0\mqttbroker.cer |