Page Tree
Previous Releases
...
Info | ||
---|---|---|
| ||
Quick video tutorial: MQTT Broker Without Sparkplug, TMQTT Broker And Sparkplug, MQTT With Mosquitto Broker (no audio) |
As defined in http://mqtt.org/:
...
The TMQTTBroker can be connected to a runtime project, and it will make all of the project's namespaces and properties available. When connected like this, the project information will be available following the SparkplugB specification.
...
...
Before running TMQTTBroker.exe, the file TMQTTBroker.exe.config must be configured with the desired configuration. TMQTTBroker.exe.config is in the product installation folder, and you can open it in any text editor. It is very important that the file name and extension (.exe.config) remain the same.
...
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 enables limitations for specific MQTT clients. To configure more than one MQTT client, you need to create a whole new line and change the last number of the ClientID to the next sequence sequential number.
Code Block |
---|
add key="ClientID1" value="<MQTTClientID>; Topic1=<Topic>, Subscribe1=<True or False>, Publish1=<True or False>" /> |
There are 4 internal parameters:
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"/> |
...
Examples of namespaces: Tag, Script, Device, Info, Script, Server, Security, Alarm, Historian DataSets, TemplatesName and MainTag for arrays.
...
Code Block |
---|
{ "timestamp": 1580152490182, "metrics": [ { "name": "Integer1", "timestamp": 1580152489659, "dataType": "Int32", "value": 30 } ], "seq": 1 } |
As defined in http://mqtt.org/:
”MQTT is a machine-to-machine (M2M)/”Internet of Things” connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. For example, it has been used in sensors communicating to a broker via satellite link, over occasional dial-up connections with healthcare providers, and in a range of home automation and small device scenarios. It is also ideal for mobile applications because of its small size, low power usage, minimized data packets, and efficient distribution of information to one or many receivers (more...)”.
As defined in https://www.bevywise.com/blog/sparkplug-b-mqtt-simulation/.
...