MultiSmart Integrator Guide
Page 17 of 20
MultiSmart_Integrator_Guide_R01.doc
7.6 Peer to peer / “Store and forward”
MultiSmart supports multiple masters and slaves, and is also able to have multiple devices (e.g. one
one slave or two slaves) on one comms port, using the
Connection manager
feature.
This is currently disabled by default – see section 0 for how to determine this – but needs to be enabled if
the requirement is for multiple devices on the one port.
As well as communicating to an MTU as a slave device, MultiSmart can also operate as a Modbus or
DNP Master device, talking to other slave devices. When set up in this manner, it is possible for a
command to be sent via the MTU to the MultiSmart, which then forwards that command on to other slave
device/s. The values received from the slave devices can also be sent back to the MTU by the MultiSmart
device.
In order to forward commands, first define the command as a binary or analog output (DNP), or coil or
holding register (Modbus). There are a pool of spare tags reserved for this purpose. For DNP, this pool of
tags can be located under DnpMaster.Master._1.Slave._1.SpareTags. For a binary output, link to one of
the tags under DigitalControls. For an analog output, link to one of the tags under AnalogControls.
Then, link this same tag as a binary or analog output in DNP Slave (which communicates back to the
MTU). Then, when the device receives a command from the MTU, the master running on the MultiSmart
device will automatically trigger a command to the slave device.
7.7 IO and deadbands
DNP3 works on reporting change of state. Analog values report a change of state when they change
outside of their deadband.
Deadband values are accessed by accessing the DNP3 configuration on the LCD:
, then
select a tag and the deadband, as well as other DNP parameters, are available to be changed. In v2.0,
the DNP (and Modbus) configuration can be exported as .csv, amended and re-imported. This
export/import will include deadband as well as other DNP parameters.
7.8 Remote
configuration
MultiSmart supports DNP3 file transfer and will shortly be implementing a complete remote upgrade
feature.
8 Modbus
configuration
Because of the limited nature of Modbus, inter-operability issues are much less common, however, they
can occur. This is often due to non-standard implementations of Modbus such as extensions or limitations
in the master.
The MultiSmart Modbus master and slave are completely compliant to the standard and have been tested
against many other devices. MultiSmart supports Modbus RTU, Modbus ASCII and Modbus TCP.
9 Export points list to csv
For easier management of the DNP3 and Modbus points list, the MultiSmart has an “Export to csv
function” from the LCD interface. This creates a csv and copies it onto a Compact Flash card.
The Points list can also be cleared and regenerated via the LCD.
MultiSmart v2.0, available in Q3 2008, will support importing back from csv – allowing integrators the
ability to manage and change the points list on a PC interface.
Lobley St SPS SP331 General (Electrical Manual (MPA) Multismart Manual Multitrode System Integrator Guide) General
Q-Pulse Id VM357
Active 26/09/2013
Page 17 of 20
