MultiSmart Installation & Operation Manual
40.3 Handling of Redundant Channels with Connection Details
The port number of the first Connection Detail record will identify the primary communications channel,
and is saved to the Comms Channel parameter under DnpSlave.Slave._1.Session. If the channel is a
TCP/IP channel, then the IP address, port number, and mode (UDP or TCP) are also updated for the
relevant channel under the Telemetry node. If the channel is a PSTN channel, then the phone number is
updated.
Any additional records which refer to the same port number must be limited to identifying alternate IP
addresses or phone numbers. For example, if the second record refers to the same TCP/IP channel as
the first record, then the IP address of the second record is updated as the second address under the
Telemetry node. The port number and mode would be ignored for this second record, since there is no
mechanism for defining alternate port numbers or modes for the same channel.
If there are any other Connection Detail records which define a different port number, then that record
identifies the redundant communications channel, and is saved to the Redundant Comms Channel
parameter under DnpSlave.Slave._1.Session.
When a Comms Fail alarm is triggered for the current channel, then the details defined by the next
Connection Detail record are used in an attempt to re-establish communications. This may involve the
use of an alternate IP address / phone number, or may make use of the redundant communications
channel. This automatic switching can be turned off via the Switch Channel on Comms Fail parameter
under DnpSlave.Slave._1.Session.
40.4 Device On/Off Scan
WITS incremental record type 0 defines whether a device is on or off scan. This controls the following
MultiSmart configuration parameter under the DnpSlave.Slave._1.Session node:
Device On Scan?
40.5 Scheduled Connection
WITS incremental record type 2 defines configuration for scheduled connections. This controls
configuration parameters under the following configuration node:
DnpSlave.Slave._1.WitsSchedConnect
MultiSmart_IO_Manual_R20
Page 249 of 260
Need help?
Do you have a question about the MultiSmart and is the answer not in the manual?