Emerson Bettis Rts Extension Board Instruction Manual

Bettis RTS Extension Board
Instruction Manual

Installation, Operation, and Maintenance Manual
VCIOM-16741-EN Rev. 0 November 2021
Bettis RTS
Extension Board for Modbus RTU

Section 1: Extension Board for Modbus RTU on RTS Control Unit

1.1 General Information
For Bettis RTS actuators, the standardized Fieldbus interface Modbus RTU is available.
This interface is a product option represented in hardware on the device, thus making it beneficial to advertise intended use upon ordering. Although enabling Modbus RTU a posterior is possible, such upgrades should only be performed by authorized Emerson engineers or specially trained personnel.
Modbus RTU determines the technical and functional characteristics of the serial Fieldbus system used to connect distributed autonomous devices. Modbus RTU distinguishes Master- and Slave-Devices and has been designed for data transmission at the field level, hence, the communication of central control units – as SPS or PC – with decentralized field devices over a fast serial connection. Communication functionality is standardized by the MODBUS Organization (modbus.org).
The physical communication layer is based on an RS-485 interface connected through a shielded twisted two-wire cable.
Bettis RTS control units are always slave devices.
1.1.1 Communication Settings

The detection of the settings of the Modbus RTU communication is done automatically in the Bettis RTS Modbus RTU slave module during communication start-up.

The supported baud rates are:

The byte frame has the following bits:
· 1 start bit
· 8 data bits, LSB first
· 1 parity bit (even, odd or mark)
· 1 stop bit

If mark parity is not supported by the Modbus RTU master, you can use no parity and 2 stop bits instead.

Section 2: Connection

Depedning on the order, here are the following connections possible:

• standard design: connection board
• explosionproof design: terminals

Standard Design

Connecting the actuator to the fieldbus system is accomplished through connecting the bus cable to the connection print in the connection compartment of the actuator. Thus for convinience, the Modbus RTU connector is pluggable like every other external connector for signal or power on our actuators. Disconnecting a device will have no effect on the communication of other devices in the same strand. Meaning, the network maintains full functionality if a device is disconnected while the network is in operation. But beware, at the end of each strand Modbus RTU has to be terminated. This termination can either be performed by RTS control unit or a separate active bus termination device. Note that the power for the termination resistors of RTS control unit comes from the actuator. Hence, disconnecting the terminating RTS control unit renders the bus in this strand inoperational. Therefore, it is advised to use active bus termination through a dedicated device. The single-channel version of RTS control unit is connected to Modbus RTU via channel I. The dual channel version (Option: redundant) is connected via channel I and II.

Connection Board (Customer End)
The connection board is situated in the connection compartment under the topmost cover.
Figure 1 Connection Board

Connecting to Modbus RTU
Recommended Cable Confectioning
Prior to connection the bus lines are to be confectioned as seen in the Figure 2 below:
Figure 2

The clamps on the connection board are designed for a maximum line cross-section of 1.5 mm 2
. The line diameter has to be in the range of 5 to 8 mm.
Connecting to a Strand between Devices
Other devices are connected to the bus in front and behind of the new Slave-Device.
Line configuration:
Figure 3 

Connecting at the End of a Strand, Bus Termination
There is either no device connected to the bus in front or behind of the new Slave-Device.
Line configuration:
Figure 4

Bus termination:
Modbus RTU has to be terminated on both ends of every strand. Termination can be accomplished through the termination resistor implemented in your RTS control unit. Bus termination is activated when the respective switch on the connection board is switched to “ON” as seen in Figure 4 (A. Single Channel).

Explosionproof Design
Normally, in explosionproof design, there is no termination available in the control unit.
That means, the bus termination must be done seperate outside of the control unit.
Optionally, a bus termination in the control unit is possible as well, this must be specified by the order.
In this case, you can activate the bus termination by connecting the following terminals:

• A with AT and B with BT (single channel version) or
• A1 with A1T, B1 with B1T, A2 with A2T and B2 with B2T (dual channel version)

WARNING
The shield must be connected to the shielding connection clamp (windowcut), see Figure 5 or Figure 6.
Design with Binary Inputs and Outputs Figure 5

1. Shielding connection clamp
2. Additional frame
3. Metallic cable glands (closed with blind screw connections at delivery) 4xM20x1.5
4. Terminal strip
   Design without Binary Inputs and Outputs Figure 6

1. Shielding connection clamp
2. Terminal strip
   An additional frame with 4xM20 holes is possible on special request.

Section 3: Setup
If Modbus RTU is activated, the following additional parameters will be visible in the control menu of your Bettis Electric Actuator. Each device connected to a Modbus RTU- network has to receive a unique address during setup.
Table 1.

Section 4: Specification of Input and Output Data

General requirement: Depending on the Master it is possible that the Lowbyte (Bit 0 – 7) and the High byte (Bit 8 – 15) are to be switched. Generally speaking, the mode of transmission (Big Endian / Little Endian) has to be set in a way that ensures the correct transmission of the analogue information. Only after this has been accomplished, the  binary data can be transmitted.

Input Data Modules (Master to Slave Communication)
Input data can be handled with following Modbus functions:
Table 2.

Function

Setpoint
Register number: 1, address 0000Hex
Data format: 16 bit, only the lowest 10 bit (0 – 1023) are in use.
Other bits are reserved for future use and have to be set to zero.
Table 3.

Command
Register number: 2, address 0001Hex
Data format: 16 bit (Bitfield)
Table 4.

Command 2
Register number: 3, address 0002Hex
Data format: 16 bit (Bitfield)
Table 5.

Setpoint Revolution Speed
Register number: 4, address 0003Hex
Data format: 16 bit, only the lowest 8 bit (Bit 7: Direction OPEN; Bit 6 – 0 : 0 – 100 corresponding to 0 – 100%) are in use.
Other bits are reserved for future use and have to be set to zero.

Output Data Modules
(Slave to Master Communication)
Output data can be handled with following Modbus functions:
Table 6.
Function

Actual Position Value
Register number: 257, address 0100 Hex
Data format: 16 bit, only the lowest 10 bits (0 – 1023) are in use.
Other bits are reserved for future use and have to be set to zero.
Table 7.

Status
Register number: 258, address 0101Hex
Data format: 16 bit (Bitfield)
Table 8.

Actual Torque Value
Register number: 259, address 0102Hex
Data format: 16 bit, only the lowest 8 bit (Bit 7: Direction OPEN; Bit 6 – 0 : 0 – 100 corresponding to 0 – 100%) are in use.
Other bits are reserved for future use and have to be set to zero.

Actual Speed Value
Register number: 260, address 0103Hex
Data format: 16 bit, only the lowest 8 bit (Bit 7: Direction OPEN; Bit 6 – 0 : 0 – 100 corresponding to 0 – 100%) are in use.
Other bits are reserved for future use and have to be set to zero.

External Actual Value
Only with Option PID-Controller
Register number: 261, address 0104Hex
Data format: 16 bit, only the lowest 10 bit (0 – 1023) are in use.
Other bits are reserved for future use and have to be set to zero.

Status 2
Register number: 262, address 0105Hex
Data format: 16 bit (Bitfield)

Table 9.
Structure 

NOTE:
Using parameter P15.6 it is possible to assign alternative output-functions to “Status 2”.

Status 3
Register number: 263, address 0106Hex
Data format: 16 bit, error codes
Table 10.

NOTE:
Using parameter P15.7 it is possible to assign alternative output-functions to “Status 3”.

Status 4
Register number: 264, address 0107Hex
Data format: 16 bit (Bitfield)
Reserved for future use.
NOTE:
Using parameter P15.8 it is possible to assign alternative output-functions to “Status 4”.

For complete list of sales and manufacturing sites, please visit www.emerson.com/actuationtechnologieslocations or contact us at [email protected]

www.emerson.com/bettis
VCIOM-16741-EN ©2021 Emerson. All rights reserved.
The Emerson logo is a trademark and service mark of Emerson Electric Co. BettisTM is a mark of one of the Emerson family of companies.
All other marks are property of their respective owners.

The contents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or their use or applicability. All sales are governed by our terms and conditions, which are available upon request. We reserve the right to modify or improve the designs or specifications of such products at any time without notice.