ProSoft Technology MVI56-103M - Manual (Page 87)

MVI56-103M ♦ ControlLogix Platform Diagnostics and Troubleshooting
IEC 60870-5-103 Master Communication Module User Manual
ProSoft Technology, Inc. Page 87 of 152
February 22, 2013
4.5 Frequently Asked Questions
This section provides answers frequently asked questions about the ProLinx
103M module.
4.5.1 Why is the module not communicating with the slave?
First, ensure that the slave Data Link Address is configured as a slave (session)
in the configuration file. The module will only try to initialize slaves identified by
Data Link Addresses that are currently configured as sessions. Refer to technical
specification for your protection equipment for its Data Link Address. You should
also check to see if the common ASDU address is configured as a sector in the
module. Make sure all port communication parameters match the slave
parameters (baud rate, parity, and so on). Finally, look at the cables and ensure
that the correct communication mode is set (RS-232 or RS-495).
4.5.2 The slave is responding but I cannot see the monitor data in
the Module database.
Ensure that the monitor points are correctly configured. Refer to your protection
equipment’s documentation for the correct ASDU type, Function Code, and
Information Number. These values must match the parameters that are entered
for every monitor point in the [IEC-103 Master Session 0] section of the
configuration file.
The addressing type in the module database depends on the point ASDU type.
The Database Index parameter can be interpreted as bit, byte, word, or double-
word address. For more details, refer to Data Types and Mapping (page 99).
4.5.3 How can I confirm if the configuration was received by the
module?
You can verify this using the Debug menu. Refer to Diagnostics and
Troubleshooting in this manual for information on using the Debug menu (page
67).