Changing Port Settings - Emerson ControlWave Instruction Manual

ControlWave I/O Expansion Rack Instruction Manual
Port PCB
COM3 SCB
COM4 SCB
Ethernet

4.2.2 Changing Port Settings

Caution
4-2
Default Configuration
Modbus Slave protocol
RS-485; 9600 baud, 8 bits, no parity, 1 stop bit, BSAP or ControlWave
Designer protocol
RS-232; 9600 baud, 8 bits, no parity, 1 stop bit, BSAP or ControlWave
Designer protocol
: You can re-enable the factory comm settings at any time by
Note
setting switch 3 on the CPU module's SW1 to "OFF."
The ControlWave I/O expansion rack can include one or three Ethernet
ports. You can connect directly or through a network to a PC equipped
with an Ethernet port.
The factory pre-configures the initial IP addresses and masks to:
 ETH1 IP Address: 10.0.1.1 IP Mask: 255.255.255.0
 ETH2 IP Address: 10.0.2.1 IP Mask: 255.255.255.0
 ETH3 IP Address: 10.0.3.1 IP Mask: 255.255.255.0
Because each unit ships from the factory with these addresses initially
pre-programmed, you should only use these addresses for "bench"
testing and configuration. You must change these addresses before
putting the I/O rack on an actual network, since an address conflict
would exist as soon as you place the second ControlWave unit online.
You change port settings (baud rate, port type, IP address, and so on)
using the Flash Configuration utility.
You must establish communications with the ControlWave using
NetView, LocalView, or TechView before you can run the Flash
Configuration utility.
For detailed information on using the Flash Configuration utility,
Note:
see Chapter 5 of the OpenBSI Utilities Manual (D5081).
When you change the baud rate for a port, the baud rate changes as
soon as you write the flash file changes to the RTU, and do not require
a reset. For this reason, you should not change baud rate for the active
port on which you are communicating, or communications will
immediately stop due to the baud rate mismatch between the PC port
and the controller port. If this happens accidentally, you can use CPU
switch settings as discussed in the notes in Section 4.2.1 to restore
defaults and re-establish communications.
Operation Revised Aug-2015