Page History

...

• Backlog: Sets the number of connections to keep backlog. Default: is 100

• DisableRetainedFile: The broker stores the last retained message and the corresponding QoS for that topic. The valid value is true or false. The default is false.

• ClientID: This parameter can enable limitation  This parameter enables limitations for specific MQTT Clients related to For configuring clients. To configure more than one MQTT Client client, you need to create a whole new whole line changing and change the last number to the next sequence number. 

  
  

  Code Block
  add key="ClientID1" value="<MQTTClientID>; Topic1=<Topic>, Subscribe1=<True or False>, Publish1=<True or False>" />

  
  

  There are 4 internal parameters:

• value: Sets the MQTT Client ID
• Topic: Specific topic that will set the limitation
• Subscribe: flag (true or false) that allows the client to subscribe to a topic (can receive messages)

• Publish: flag (true or false) that allows the client to publish a topic (can write messages) 

  Code Block
  <add  key="ClientID1"  value="MQTTClientTest;Topic1=*,Subscribe1=True,  Publish1=True"/> <add  key="ClientID2"  value="32443fsa6546fa;Topic1=*,Subscribe1=True,  Publish1=False"/> <add  key="ClientID3"  value="7323rt304343r4;Topic1=*,Subscribe1=False,Publish1=True"/>

  
  

...

• TimeUpdateTSevers: Time between update TServer; Default is 500 milliseconds 
• GroupId: Alias that will be used in the topic
• TagProperties: List of tag properties that are sent to the MQTT client when they change values

...

• Group Id: is a name that is configured in the .config
• Message Type: The following message type elements are defined for the Sparkplug specification. Almost of the For most clients that support SparkplugB should set , the message type automat-will automatically be set. 
• NBIRTH – Birth certificate for MQTT EoN
• NDEATH – Death certificate for MQTT EoN
• DBIRTH – Birth certificate for devices
• DDEATH – Death certificate for devices
• NDATA – Node data
• DDATA – Device data
• NCMD – Node command
• DCMD – Device command
• STATE – Critical application state
• Project Name: is the same name configured in the .config
• MQTT Device Name: it can be a namespace or an object from the runtime project. Individual objects should be avoided and uses the namespaces for performance

...

In this scenario, the TMQTTBroker works as if you combined the last two scenarios together. As a simple gateway exchange any data between the MQTT Clients and publishing data projects to the topics that match the project configuration in the TMQTTBroker.exe.config.

...

The first step in setting up communication between the TMQTTBroker and the MQTTdriver is to create a Channel using this the protocol shown in the image below.

In the Engineering environment, go to Edit>Devices>Channels and find the desired protocol inside the list.

...

In the Points tab, you need to configure the topic so that your variable can publish or subscribe to messages according to its AccessType. More information on is available for each item is available in the MQTT driver documentationAddress columns, under Edit > Devices > Points.

Mosquitto Client (without SparkPlugB)

...