SmartSwarm 300 Series
:
32
We recommend that you choose appropriate MQTT topics for your Slave registers, which enable ease-of-
use for your solution domain. By defining your Topics carefully, you can enable ease-of-consumption of
the data.
In some cases, you will want to consume the data on dashboards.
See Appendix 6 in this manual for an example of how to create your own dashboards using a server-side
Node RED service.
●
Revisit your Slave Map Rules
The data that will be published to your MQTT broker is entirely dependent on the rules that you create.
We recommend that you do
not
enable a Read Rule for every register. The IoT environment for
consuming data is not intended to be a real-time replica of your Modbus control network. Publishing
every read to every register is not only extremely data-intensive across the entire system, it will also have
real cost associated with it. We recommend that you do
not
enable a Read Rule for every register. The
IoT environment for consuming data is not intended to be a real-time replica of your Modbus control
network. Publishing every read to every register is not only extremely data-intensive across the entire
system, it will also have real cost associated with it (e.g. data usage on cellular networks).
We recommend that you
do
enable appropriate Event Rules for any interesting or non-normal conditions
that you want to keep track of, or be notified about.
We recommend that you
do
enable appropriate Schedule Rules for any data that you wish to monitor on
a regular basis.
Again, it’s best to prototype different scenarios until you find one that suits your need.
It’s very easy to change and modify rules at any time, and to re-apply them in run-time without any
impact to your system.
