ProSoft Technology MVI69-DNP User Manual

Page 55

Advertising
background image

Diagnostics and Troubleshooting

MVI69-DNP ♦ CompactLogix or MicroLogix Platform

DNP 3.0 Master/Slave Communication Module

ProSoft Technology, Inc.

Page 55 of 129

November 3, 2008

4.1.3 Required

Software

In order to send and receive data over the serial port (COM port) on your
computer to the module, you must use a communication program (terminal
emulator).

A simple communication program called HyperTerminal is pre-installed with
recent versions of Microsoft Windows operating systems. If you are connecting
from a machine running DOS, you must obtain and install a compatible
communication program. The following table lists communication programs that
have been tested by ProSoft Technology.

DOS

ProComm, as well as several other terminal emulation programs

Windows 3.1

Terminal

Windows 95/98

HyperTerminal

Windows NT/2000/XP

HyperTerminal

The module uses the Ymodem file transfer protocol to send (upload) and receive
(download) configuration files from your module. If you use a communication
program that is not on the list above, please be sure that it supports Ymodem file
transfers.

4.1.4 Using the Configuration/Debug Port

To connect to the module's Configuration/Debug port:

1 Connect your computer to the module's port using a null modem cable.
2 Start the communication program on your computer and configure the

communication parameters with the following settings:

Baud Rate

57,600

Parity None

Data Bits

8

Stop Bits

1

Software Handshaking

None

3 Open the connection. When you are connected, press the [?] key on your

keyboard. If the system is set up properly, you will see a menu with the
module name followed by a list of letters and the commands associated with
them.

If there is no response from the module, follow these steps:

1 Verify that the null modem cable is connected properly between your

computer's serial port and the module. A regular serial cable will not work.

2 Verify that RSLinx is not controlling the COM port. Refer to Disabling the

RSLinx Driver for the Com Port on the PC (page 90).

3 Verify that your communication software is using the correct settings for baud

rate, parity and handshaking.

4 On computers with more than one serial port, verify that your communication

program is connected to the same port that is connected to the module.

If you are still not able to establish a connection, you can contact ProSoft
Technology Technical Support for further assistance.

Advertising