nvent 910 Series Installation, Operating And Maintenance Instructions page 45

5.6.4 MODBUS SUB ADDRESS
Purpose: The MODBUS SUB ADDRESS along with the MODBUS ADDRESS define the com-
munications address to be used by the controller when using either MODBUS protocol to
communicate with a MODBUS compatible device.
Range: 0 to 31
Procedure: Set the communications sub address as desired. Together with the MODBUS
ADDRESS, this combination must be unique to the entire communications network to avoid
messaging conflicts. Either MODBUS protocol must be selected in order to set the MODBUS
SUB ADDRESS.
IMPORTANT: Since a 910 HTC does not use all 65,535 data registers that are available for
each MODBUS ADDRESS, the data register range is subdivided to allow up to 32 HTCs to share
the same MODBUS ADDRESS. This increases the number of HTCs allowed on a single Modbus
port from 247 to 7,904 (= 247 x 32). This requires that any HTC sharing the same MODBUS
ADDRESS as another HTC must have its own unique MODBUS SUB ADDRESS.
5.6.5 BAUD RATE
Purpose: Defines the data rate at which communications occur.
Setting: AUTO or 9600 or 4800 or 2400 or 1200 or 600 or 300
Procedure: Select the data rate to be compatible with other devices that will be connected to
the controller for communications purposes.
IMPORTANT: Not all communications interfaces will support the various data rates—it is
recommended that the setting be set to AUTO. The controller will automatically select a BAUD
RATE that is compatible with the communications interface installed. If BAUD RATE = AUTO
and a MODEM communication interface is used then a data rate of 300 will always be used.
Otherwise, if BAUD RATE = AUTO and a non-MODEM communication interface is used the
PROTOCOL is either MODBUS protocol then a data rate of 9600 is used.
5.6.6 PARITY (MODBUS)
Purpose: Defines the type of parity bit to be used with MODBUS communications.
Setting: NONE or ODD or EVEN
Procedure: Select the desired type of parity. Note that PARITY can only be selected when using
either MODBUS protocol.
5.6.7 HARDWARE
Purpose: Identifies the type of communications interface installed in the 910. The controller
will automatically determine and display which communications interface type is available.
Values: NONE, MODEM or RS-232 or RS-485
5.6.8 DRIVER
Purpose: Defines the way in which the controller's program communicates with the com-
munications interface.
Setting: AUTO or RS-232 or RS-485 or MODEM
Procedure: It is recommended that the setting be set to AUTO—this will allow the controller to
automatically choose the setting to match the type of communications interface installed.
5.6.9 PROFILE
Purpose: Defines the way in which the controller's program supports communications
handshaking and communication interface signals.
Setting: AUTO or
3-WIRE RS-232 or
RS-485 or
1200 BAUD MODEM or
300 BAUD MODEM
Procedure: Select the PROFILE to be compatible with other devices that will be connected to
the controller for communications purposes. It is recommended that the setting be set to
nVent.com | 45