Modbus Manual - Evolution Controls

Transcription

Evolution
..CONTROLS INC..
EVO™/ECM-Modbus
http://www.gotoevo.com/
©2001 All Rights Reserved
Evolution Controls Inc.
San Diego, CA USA
EVO™/ECM-Modbus RTU
Application Guide
Series 1, July 2001
Application Guide
Series 1, July 2001
Contents
DESCRIPTION ................................................................................................................................................. 1
MOUNTING ...................................................................................................................................................... 3
ENCLOSURE ..................................................................................................................................... 4
WIRING............................................................................................................................................................. 5
Power Connection .............................................................................................................................. 5
Trunk Connection ............................................................................................................................... 5
Motor Connection ............................................................................................................................... 6
PROTOCOL...................................................................................................................................................... 7
Register Usage................................................................................................................................... 7
Dynamic Registers ......................................................................................................................... 7
Read Only Registers ...................................................................................................................... 7
Default Registers............................................................................................................................ 8
Configuration Registers.................................................................................................................. 8
RPM Alarm Limit Registers ............................................................................................................ 8
Register Assignments ........................................................................................................................ 9
Register 1 ....................................................................................................................................... 9
Motor Enable/Disable Nibble................................................................................................. 9
RPM Alarm Nibble................................................................................................................. 9
External Command Flag........................................................................................................ 9
Reserved Flags ................................................................................................................... 10
Communications Timed Out Flag........................................................................................ 10
Reset Flag ........................................................................................................................... 10
Register 2 ..................................................................................................................................... 10
Motor 1 - % Out ................................................................................................................... 10
Register 3 ..................................................................................................................................... 11
Motor 2 - % Out
…See Register 2 description .............................................................. 11
Register 4 ..................................................................................................................................... 11
Motor 3 - % Out
Register 5 ..................................................................................................................................... 11
Motor 4 - % Out
San Diego, CA USA
Application Guide
Series 1, July 2001
p. i.
Register 6 .....................................................................................................................................11
Motor 1 - RPM......................................................................................................................11
Register 7 .....................................................................................................................................11
Motor 2 - RPM
…See Register 6 description ................................................................11
Register 8 .....................................................................................................................................11
Motor 3 - RPM
…See Register 6 description ................................................................11
Register 9 .....................................................................................................................................11
Motor - 4 RPM
…See Register 6 description .................................................................11
Register 10 ...................................................................................................................................12
Motor 1 - Default % Out .......................................................................................................12
Register 11 ...................................................................................................................................12
Motor 2 - Default % Out
…See Register 10 description ................................................12
Register 12 ...................................................................................................................................12
…See Register 10 description ................................................12
Register 13 ...................................................................................................................................12
…See Register 10 description .................................................12
Register 14 ...................................................................................................................................12
Motor Enable/Disable Defaults Nibble .................................................................................12
Communications Timeout Flag (Register 14, Bit 4).............................................................13
AUTObaud Disable Flag (Register 14, Bit 5).......................................................................13
Group 1 Reply Flag (Register 14, Bit 6) ..............................................................................13
Reply Delay..........................................................................................................................14
Next Message Delay............................................................................................................14
Register 15 ...................................................................................................................................14
Group 1 Address..................................................................................................................14
Register 16 ...................................................................................................................................15
Group 2 Address..................................................................................................................15
Register 17 ...................................................................................................................................15
Unit Address ........................................................................................................................15
Register 18 ...................................................................................................................................15
Baud Rate ............................................................................................................................15
p. ii.
Application Guide
Series 1, July 2001
San Diego, CA USA
Register 19 ................................................................................................................................... 16
Motor 1 Low RPM Limit ....................................................................................................... 16
Register 20 ................................................................................................................................... 16
Motor 2 Low RPM Limit
…See Register 23 .................................................................. 16
Register 21 ................................................................................................................................... 16
…See Register 23 .................................................................. 16
Register 22 ................................................................................................................................... 16
…See Register 23 .................................................................. 16
Register 23 ................................................................................................................................... 17
Motor 1 High RPM Limit ...................................................................................................... 17
Register 24 ................................................................................................................................... 17
Motor 2 High RPM Limit
…See Register 23.................................................................. 17
Register 25 ................................................................................................................................... 17
…See Register 23.................................................................. 17
Register 26 ................................................................................................................................... 17
…See Register 23................................................................... 17
EVO™/ECM-Modbus RTU Command Structure............................................................................... 18
Read Registers Command (03) ............................................................................................... 18
Write Single Register Command (06)...................................................................................... 19
Write Multiple Registers Command (16).................................................................................. 20
ADDRESSING.................................................................................................................................. 21
Global Address ........................................................................................................................ 21
Unit Address ............................................................................................................................ 21
Group Address 1...................................................................................................................... 21
Group Address 2...................................................................................................................... 21
INTEGRATION ............................................................................................................................................... 23
MASTERS ........................................................................................................................................ 23
SCADA ............................................................................................................................................. 25
Communications Throughput................................................................................................... 25
Service Window................................................................................................................................ 26
San Diego, CA USA
Applications Guide
Series 1, July, 2001
p. iii.
CONFIGURATION ............................................................................................................................... 27
Configuration Tool ............................................................................................................................27
Program…. ...............................................................................................................................27
Signal Converter…...................................................................................................................27
RS-485 Test Cable…. ..............................................................................................................27
Connecting to the RTU .....................................................................................................................28
Starting The Configuration Program .................................................................................................29
Communication With The EVO™/ECM-Modbus.......................................................................30
Register Displays .....................................................................................................................30
Configuring The EVO™/ECM-Modbus ..............................................................................................31
Versions & Revisions ........................................................................................................................... 33
Hardware ..........................................................................................................................................33
Series 1 ....................................................................................................................................33
Series 1a ..................................................................................................................................33
FIRMWARE ......................................................................................................................................34
Version 0.0 ...............................................................................................................................34
Version 0.1 ...............................................................................................................................34
Version 1.0 ...............................................................................................................................34
Version 1.1 ...............................................................................................................................35
Version 1.2 ...............................................................................................................................36
Version 1.3 ...............................................................................................................................36
RTU Register Map................................................................................................................................. 37
p. iv.
Application Guide
Series 1, July 2001
San Diego, CA USA
DESCRIPTION
EVO™/ECM-Modbus
The EVO™/ECM-Modbus RTU (Remote Terminal
Unit) allows an industrial or building automation
system to monitor and control General Electric
ECM Motors over an industry standard Modbus
RTU serial data link. Each RTU connects up to
four ECM Motors.
General Electric’s ECM Motors are fractional
horsepower blower motors featuring an internal
microprocessor to provide exceptional efficiency,
performance and motor life. The motor may be
programmed for constant airflow or constant
torque.
Modbus is an industry standard communications protocol allowing connection to
most industrial and building automation systems.
The EVO™/ECM-Modbus RTU allows the automation system to control each
motor's output and on/off; monitor each motor's RPM and control status; and set
default values used during power up and communications interruptions.
A four-conductor low voltage control cable connects each motor to the RTU. Motor
control cables may be up to 150 Meters (500') long.
Low voltage on/off control is provided over the control cable by direct connection to
the motor. External relays or starters are not required for ECM Motors.
The EVO™/ECM-Modbus RTU allows adjustment of the motor output from 1% to
100% of the programmed control range. The ECM Motor sends a signal from its
commutator circuit to the RTU. The RTU translates this signal to a 0-1500 RPM
value.
During the course of operation, the automation system may dynamically change
motor outputs, and turn motors on and off to meet current operating needs. Should
communications from the automation system fail, the EVO™/ECM-Modbus RTU can
be set to hold the last commanded values from the automation system, or revert to
defaults stored in the RTU's non-volatile memory.
Defaults are invoked on power up. Defaults are overridden when communications is
established, and dynamic values sent to the RTU.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 1.
Notes…
Page 2.
Application Guide
Series 1, July 2001
San Diego, CA USA
MOUNTING
Mount the EVO™/ECM-Modbus RTU inside a metal control cabinet or enclosure.
Make sure the enclosure is earthed. When mounting the 24 Vac low voltage power
transformer in the same enclosure, be sure to separate the high and low voltage
sections of the enclosure, as required by good safety practice, and building codes.
To reduce EMI (electro-magnetic interference), tightly fasten the control mounting
posts to the earthed metal surface of the enclosure. Remove paint or other
insulating materials around the area where the mounting posts contact the metal
mounting surface, or otherwise insure good electrical contact between the mounting
posts and electrical earth.
2.34"
0.91"
2.69"
Low voltage communications and motor control wiring can be routed into the low
voltage section of the metal enclosure, or be plugged into an opening in the side of
the enclosure. All external connections are made to one side of the board. Make a
rectangular cutout in the side of the enclosure when the application requires external
plug in of motor and communication cables.
0.21"
0.67"
1.12"
2.03"
3.11"
3.41"
3.83"
0.21"
ø0.25"
Board Dimensions
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 3.
ENCLOSURE
These drawings detail the minimum inside floor and face dimensions for a suitable
enclosure. The inside height should be at least 2 inches (50 mm).
4.25"
3.36"
0.90"
0.12"
2.00"
1.00"
0.61"
0.20"
0.38"
2.20"
3.58"
Inside Face
0.90"
0.21"
2.75"
2.34"
Dimension from
inside edge of can
2.20"
0.38"
3.58"
Dimension from
inside edge of can
Page 4.
ø0.25"
Inside Floor
Application Guide
Series 1, July 2001
San Diego, CA USA
WIRING
POWER CONNECTION
Neutral
Power the EVO/ECM-Modbus RTU with a 24 Vac 50/60 Hz 10 VA
low voltage power source. Connect the hot side of the power source
to the 24Vac connection. Connect the neutral side of the power
source to the neutral connection. Observe all building and electrical
code requirements concerning low voltage power sources and wiring to
insure a safe, reliable installation. In most jurisdictions the neutral must be
earthed. We recommend you ALWAYS earth the low voltage neutral.
24Vac 50/60 Hz
EVO/ECM-Modbus
Ground
TRUNK CONNECTION
A single trunk routes from one EVO™/ECM-Modbus RTU to the next, connecting up
to 31 RTUs to the Modbus Master. The length may be up to 4000 feet. Connect a
120? 1/4W terminating resister at each end of the trunk. The most common
connection places the Modbus Master at one end of the trunk. Many Modbus Masters
have a non-removable built in terminator, or use an impedance altering means to
provide line bias. These masters must be placed at the end of the line.
Modbus Master
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
When possible, placing the Modbus Master in the center of the trunk improves
application versatility, often reduces installation costs, and improves communications
reliability. Please test your master in this application before designing your system
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
Modbus Master
EVO/ECM-Modbus
EVO/ECM-Modbus
EVO/ECM-Modbus
this way.
The trunk cable field terminates to a plug-in connector at each RTU. Use a twisted
pair cable with an overall foil shield. The shield must not short to earth, or other
conductors.
The shield wire is usually not insulated. Keep the shield leads short between the
cable sheath and the shield connection. Let the other wires be longer!
Twisted Pair
Foil Shield
AWG 22
Plugs may not be supplied
with Quads. Order DigiKey
PN ED1702-ND
http://www.digikey.com
San Diego, CA USA
Application Guide
Series 1, January 2001
Page 5.
MOTOR CONNECTION
Order
Motor Cable
Custom Lengths
To 100'
ECM-CBL_ _
substitute the length in feet
for the last two digits.
Motor 1
Motor 2
Motor 3
Motor 4
Communications
A four-conductor cable connects each motor to
the EVO™/ECM-Modbus RTU. Plug the motor
end of the cable into the motor, and plug the
circuit board end into motor connection 1, 2, 3,
or 4 on the RTU.
Motor cables are prefabricated, with
an ECM Motor connector on one
end, and a small 4-pin circuit board
connector on the other.
Some applications may not be suitable for prefabricated cables. Cut a short cable in
half, and splice cable in between as needed for the application. Cables can be field
fabricated using the parts and tooling identified on the cable drawing. The
pneumatic bench tool can be used in the field, or a hand-operated tool
(pns. 571-580741 & 571-582471) is available from http://www.mouser.com
Page 6.
Application Guide
Series 1, July 2001
San Diego, CA USA
PROTOCOL
The EVO™/ECM-Modbus RTU responds to three Modbus master commands to
address data registers 1 through 26. Registers 1 through 16 and 19 through 26 are
directly addressed. Registers 17 and 18 can only be accessed using the service
address 255.
Each Modbus register is 16 bits long. These bits are organized as two bytes (8
bits). Each byte contains two nibbles (4 bits). A Modbus register can hold one fact
(piece of information), or multiple facts. A fact can use both bytes (one fact per
register), or multiple facts can be stored in each byte, nibble or bit (multiple facts per
register).
The chart below describes the data (facts) stored in each register, and the Modbus
command that can be used with the register. Command 03 reads multiple registers.
Command 16 writes multiple registers, and command 06 writes to a single register.
REGISTER USAGE
Dynamic Registers
Registers 1 through 5 contain dynamic operating data. The EVO™/ECM-Modbus
RTU uses this information to turn the motors on/off, and to set each motor's airflow.
These registers may be written by the Modbus Master, or set to values stored in the
default registers. The defaults are restored on RTU power up, on RTU reset, or
when a communications timeout occurs. The Modbus master should read these
registers on each scan of the trunk.
Read Only Registers
Registers 6 through 9 only respond to a read command from the Modbus Master.
These registers contain each motor's RPM. The Modbus master should read these
registers on each scan of the trunk.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 7.
Default Registers
Registers 10 through 14 contain default operating data. The EVO™/ECM-Modbus
RTU stores this data in non-volatile E2PROM, so the data is available when the RTU
is powered up. Default values are copied to their respective dynamic registers on
RTU power up, on RTU reset, or when a communications timeout occurs.
The E2PROM has a limited life, guaranteed for 10,000 writes. Only write to the
E2PROM when commanded by the automation system operator. These registers
need to be read when the data is needed for a visual or printed display. Reading on
each scan is not required. NEVER automatically and continuously, write data to
these registers.
Configuration Registers
Registers 15 through 18 store EVO™/ECM-Modbus RTU configuration information in
non-volatile E2PROM.
these registers.
RPM Alarm Limit Registers
Registers 19 through 26 store high and low alarm limits for each motor. (High alarm
limits are not implemented in V1.2) These values are stored in E2PROM only.
There are no associated dynamic registers for RPM limits.
these registers.
Page 8.
Application Guide
Series 1, July 2001
San Diego, CA USA
REGISTER ASSIGNMENTS
Register 1
Low Byte
Motor Enable/Disable Nibble
Each of the 4 bits in this nibble represents the associated motor enable command. If
the associated bit is set (1), and the associated flow index is greater than "0" the
motor runs. If the bit is clear (0), the motor stops regardless of the associated flow
index. The Modbus Master writes to this nibble to enable/disable motors, and reads
the nibble to retrieve the motor enable/disable status.
Bit 0 = Motor 1, Bit 1 = Motor 2, Bit 2 = Motor 3, and Bit 3 = Motor 4.
RPM Alarm Nibble
Each of the 4 bits in this nibble represents the associated motor alarm status. If the
associated bit is set (1), the motor RPM is not between the low and high RPM limits.
If the associated bit is clear (0), the associated motor RPM is between the low and
high RPM limits. When a motor is turned off, the RPM Alarm bit is cleared. The
alarm bit is held clear for 20 seconds after a starting a motor. When an RPM alarm
bit is set, the alarm clears when the associated motor RPM is at least 50 RPM inside
the low and high RPM limits.
High Byte
External Command Flag
A Modbus Master may use the EC flag to mark that it has read default values from
the EVO™/ECM-Modbus RTU. The EC flag is cleared if a configuration tool or global
command changes default values. Resetting the RTU also clears the EC flag.
Use of this flag is optional. Using the EC flag increases communications throughput.
If the EC flag is not set, the Modbus Master reads registers 1 through 22, then sets
the EC flag. If the EC flag is set, the Modbus Master only needs to read registers 1
through 9.
Bit 0 = External Command Flag
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 9.
Reserved Flags
These flags reserved for future use.
Bits 1, 2, 3, 4, & 5 = Reserved Flags
Communications Timed Out Flag
If valid communications cease for three minutes, the controller sets the CTO flag.
When communications resumes, the Modbus master should report "Communications
Restored" then reset the CTO flag.
Bit 6 = CTO Flag
Reset Flag
When the Modbus Master sets the reset flag, the EVO™/ECM-Modbus RTU
acknowledges the command, then resets. The reset clears (0) the Reset Flag, and
sets the Motor On/Offs and Motor % Outs to their default values.
Register 1, High Byte, bit 7 = Reset Flag
Register 2
Motor 1 - % Out
The equipment manufacturer programs the ECM Motor to operate between a
minimum airflow (or torque) and a maximum airflow. A flow index between 1 and
100 (percent) in this register controls ECM Motor 1 to the associated airflow.
V = Vindex * (Vmax - Vmin) - Vmin
A zero flow index stops the motor. By setting the enable/disable bits to enable the
motor speed and on off using a single register.
Integer value from 0 to 100
Page 10.
Application Guide
Series 1, July 2001
San Diego, CA USA
Register 3
Motor 2 - % Out
…See Register 2 description
Register 4
Motor 3 - % Out
Register 5
Motor 4 - % Out
Register 6
Motor 1 - RPM
The EVO™/ECM-Modbus RTU reads commutator pulses from ECM motor 1. The
the register as an integer value between 0 and 1500.
Integer Value from 0-1500
Register 7
Motor 2 - RPM
Register 8
Motor 3 - RPM
Register 9
Motor - 4 RPM
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 11.
Register 10
When the EVO™/ECM-Modbus RTU is reset, the value stored in register 10 is
transferred to register 2. Register 2 sets the airflow (torque) for motor 1. The motor
operates at this airflow until the Modbus Master changes the value in register 2.
Defaults may also be selectively invoked during loss of communications with the
Modbus Master.
Lower Byte, Integer value from 1 to 100
Register 11
Register 12
Register 13
Register 14
Low Byte
Motor Enable/Disable Defaults Nibble
This nibble sets the default enable/disable state for each ECM Motor. When the
EVO™/ECM-Modbus RTU resets, the value stored in this nibble is transferred to the
enable/disable nibble in register 1. This causes each motor to be enabled or
disabled to the associated default value. The Modbus Master changes the value in
register 1 enable/disable nibble when communications is established. Defaults may
also be selectively invoked during a loss of communications with the Modbus
Master.
Page 12.
Application Guide
Series 1, July 2001
San Diego, CA USA
Configuration Flags Nibble
Flags may be set or cleared to modify the behavior of the EVO™/ECM-Modbus RTU.
The upper nibble of the lower byte of register 14 contains 4 flags.
Communications Timeout Flag (Register 14, Bit 4)
If the EVO™/ECM-Modbus RTU loses communications, it will continue to operate at
the last values set by the Modbus Master. If the communications timeout flag is set
(1), and the RTU does not receive a valid communications for 3 minutes, a reset will
occur, and the default values will be loaded into their respective dynamic registers.
AUTObaud Disable Flag (Register 14, Bit 5)
AUTObaud may timeout in applications with many RTUs. This will cause
communications errors while the EVO™/ECM-Modbus RTU searches for the valid
baud rate. Setting the AUTObaud Disable Flag disables AUTObaud. Disable
AUTObaud only after a suitable baud rate has been established. If you disable
AUTObaud when the baud rate is too high for reliable communications, you will need
to visit each EVO™/ECM-Modbus RTU with the configuration tool to lower the baud
rate.
Group 1 Reply Flag (Register 14, Bit 6)
Group addressing allows a write register (16) or write multiple registers (06)
command to be issued to a group of EVO™/ECM-Modbus RTUs. None of these
RTUs issue a reply to the Modbus Master, since all RTUs in the group would try to
reply at the same time. Some Modbus Masters can be configured so they do not
need a reply. Others will generate a communications error if they do not receive a
reply.
When the Group 1 Flag is set (1), this RTU will provide a reply when the Group 1
address is polled. Only set this flag for one of the RTUs in the group.
Group 2 Reply Flag (Register 14, Bit 7)
command to be issued to a group of EVO™/ECM-Modbus RTUs. None of these
RTUs issue a reply to the Modbus Master, since all RTUs in the group would try to
reply at the same time. Some Modbus Masters can be configured so they do not
need a reply. Others will generate a communications error if they do not receive a
reply.
When the Group 2 Flag is set (1), this RTU will provide a reply when the Group 2
address is polled. Only set this flag for one of the RTUs in the group.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 13.
High Byte
…delays
Reply Delay
The RTU may reply to a poll from the master before the master is turned around and
ready to receive. Setting these bits inserts a delay before the RTU replies to a poll.
Set this value as low as possible.
0=3ms, 1=11ms, 2=15ms, 3=19ms, 4=23ms, 5=27ms,6=31ms, 7=35ms
Bit 0 = 20, Bit 1 = 21, Bit 2 = 22
Next Message Delay
At the end of a transaction, the RTU immediately listens for new data. In some
applications, the line may ring, or have other noise. Setting this bit causes the RTU
to wait for three byte times before receiving data. Leave this bit clear if possible.
Bit 3
Register 15
Group 1 Address
command to be issued to a group of EVO™/ECM-Modbus RTUs. The group
address can be any address from 1 to 247. A group address should not be the
same as the unit address, or the unit address of any other RTU connected to the
same trunk.
When the Modbus Master writes to a group address, all the RTUs sharing the same
group 1 address respond. This feature allows logical grouping of EVO™/ECMModbus RTUs to fit building floor plans and ease interactive control with other
automated systems within the facility.
Each RTU may have two group addresses, allowing overlap of group functions.
Page 14.
Application Guide
Series 1, July 2001
San Diego, CA USA
Register 16
Group 2 Address
command to be issued to a group of EVO™/ECM-Modbus RTUs. The group
address can be any address from 1 to 247. A group address should not be the
same as the unit address, or the unit address of any other RTU connected to the
same trunk.
When the Modbus Master writes to a group address, all the RTUs sharing the same
address respond. This feature allows logical grouping of EVO™/ECM-Modbus RTUs
to fit building floor plans and ease interactive control with other automated systems
within the facility.
Each RTU may have two group addresses, allowing overlap of group functions.
Register 17
Unit Address
The Modbus Master uses the unit address when communicating with a specific
EVO™/ECM-Modbus RTU. Each RTU connected on the same trunk must have a
unique unit address in the range of 1 to 247.
The Modbus Master should NEVER write to this register! Only write this register
with one RTU attached to a Modbus utility device. This register can only be written
using address 255. Address 255 is outside the specified address range of the
Modbus protocol. Some Modbus utilities may not service address 255. See the
configuration section of this manual for more information.
Register 18
Baud Rate
The EVO™/ECM-Modbus RTU can be configured to one of three different baud
rates.
The Modbus Master should NEVER write to this register! Only write this register
with one RTU attached to a Modbus utility device. This register can only be written
using address 255. Address 255 is outside the specified address range of the
Modbus protocol. Some Modbus utilities may not service address 255. See the
configuration section of this manual for more information.
0=1.2 kb, 1=2.4 kb, 2 = 4.8 kb, 3 = 9.6 kb, 4 = 19.2kb, 5 = 38.4kb, 6=5.6kb
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 15.
Note: Registers after this point only available in Version 1.2 and above
Register 19
When Motor 1 RPM drops below this limit, and the motor has been commanded on
for at least 20 seconds, the corresponding alarm flag (Register 1) is set. The flag is
cleared when the RPM exceeds this limit by 50 RPM.
Register 20
…See Register 23
Register 21
…See Register 23
Register 22
Page 16.
…See Register 23
Application Guide
Series 1, July 2001
San Diego, CA USA
Note: Registers after this point only available in Version 1.3 and above
Register 23
When Motor 1 RPM increases above this limit, and the motor has been commanded
on for at least 20 seconds, the corresponding alarm flag (Register 1) is set. The flag
is cleared when the RPM drops below this limit by 50 RPM.
Register 24
…See Register 23
Register 25
…See Register 23
Register 26
San Diego, CA USA
…See Register 23
Application Guide
Series 1, July 2001
Page 17.
EVO™/ECM-Modbus RTU COMMAND STRUCTURE
Read Registers Command (03)
Query From Modbus Master
Address Command
Code
1-247
03
Starting
Register
00
Number of Registers Error Check
00
00
1-22
CRC-16
•
Unit, group 1, or group 2 address must be 1-247 (one byte).
•
The command code is 03 (one byte).
•
The starting register is two bytes long. The value must be 00 00 when
addressing an EVO™/ECM-Modbus RTU.
•
The number of registers is two bytes in length. The high byte is always 00.
The low byte is an integer between 1 and 26.
Reply to Modbus Master
Byte
Address Command
Code
1-247
03
Count
2-36
Data
Register 1 Register 2 Register .. Error Check
HI
LO
HI
LO
HI
LO CRC-16
•
The byte count is 2 times the number of registers requested in the query. The
EVO™/ECM-Modbus RTU allows polling of up to 26 registers, so this number will
be an even number between 2 and 52.
•
Register 1 is always the first register in the data string.
Page 18.
Application Guide
Series 1, July 2001
San Diego, CA USA
Write Single Register Command (06)
Register Number
Address Function HI
0-247
06
00
255
06
00
Data
LO
HI
LO
Error Check
1-5, 10-16,
19-26
17-18
00
0-255
CRC-16
00
0-255
CRC-16
All RTUs respond to an address "0" query. All EVO™/ECM-Modbus RTUs
process the write, but none reply.
The command code is 06.
The register number is two bytes long. The high byte is 00, the low byte is an
integer within the range of valid registers.
Registers 1-5 are dynamic data registers.
Registers 10-14 are default data registers.
Registers 15 and 16 are unprotected configuration registers.
Registers 17 and 18 are protected configuration registers. These registers
can only be queried at address 255.
Registers 19-26 are RPM alarm limit registers.
The data field is two bytes long. The high byte is always 00. The low byte
contains the data to be written to the low byte of the target register.
Register Number
Address Function HI
•
0-247
06
00
255
06
00
Data
LO
HI
LO
Error Check
1-5, 10-16,
19-26
17-18
00
0-255
CRC-16
00
0-255
CRC-16
The response to a write single register query is identical to the query.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 19.
Write Multiple Registers Command (16)
Starting Number of
Register Registers
Address Function HI LO
HI
LO
1-247
16
00 00
00
05
Byte
Count
10
Register 1 Register 2 Register ?
To 5
HI LO HI LO HI LO
00 0-255 00 0-100 00 0-100
Error Check
CRC-16
All EVO™/ECM-Modbus RTUs
•
All RTUs respond to an address "0" query.
process the write, but none reply.
•
The command code is 16.
•
The EVO™/ECM-Modbus RTU only responds to a query for the first five registers.
•
The register number is two bytes long. The high byte is 00 and the low byte is
05, representing the five dynamic data registers the EVO™/ECM-Modbus RTU
allows to be read by this command.
•
The byte count is fixed at 10.
Register Number
Address Function
0-247
•
16
Data
HI
LO
HI
LO
Error Check
00
00
00
05
CRC-16
Descriptions of the reply fields are the same as the descriptions of the query
fields above.
Page 20.
Application Guide
Series 1, July 2001
San Diego, CA USA
ADDRESSING
The EVO™/ECM-Modbus RTU responds to polls at four different addresses.
Global Address
Modbus RTU protocol defines address 0 as a global address. All RTUs on the trunk
respond to writes the Modbus Master issues to address 0. None of the
EVO™/ECM-Modbus RTUs reply.
Unit Address
Each EVO™/ECM-Modbus RTU must be assigned a unique address. The Modbus
Master uses this address when communicating with only that RTU.
Group Address 1
The Modbus Master may communicate with a group of EVO™/ECM-Modbus RTUs
having the same group 1 address. None, or only one of the RTUs in the group will
reply. A trunk may have as many different group 1 addresses as are required for the
application.
Group Address 2
The Modbus Master may communicate with a group of EVO™/ECM-Modbus RTUs
having the same group 2 address. None, or only one of the RTUs in the group will
reply. A trunk may have as many different group 2 addresses as are required for the
application.
Note: The EVO™/ECM-Modbus RTU facilitates two group addresses because
applications may need overlapping groups.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 21.
Notes…
Page 22.
Application Guide
Series 1, July 2001
San Diego, CA USA
INTEGRATION
MASTERS
EVO™/ECM-Modbus communications is half-duplex. All devices contain a
transmitter and a receiver. Only one transmitter on a trunk can be connected at a
time. All other devices on the trunk (Master and RTU slaves) must be in receive.
When a Master finishes sending, it must quickly "turn-around" so it is ready to
receive a reply from the RTU.
The EVO™/ECM-Modbus reply is very fast. Some Masters, especially those where
turn-around is controlled over a higher level network (server architecture) cannot turn
around fast enough to receive the RTU's reply. Flags in register 14 can be set to
delay the RTU's reply.
A variety of devices may be used as the Master. In a large system, the master may
be a PLC (Programmable Logic Controller). These devices have resources that
scan the RTUs, process the data, and pass it to a PC, usually over a network. The
PC and attending peripherals is often referred to an HMI (Human Machine Interface).
PLCs usually have RS-485 Modbus ports. Some have a combination of RS-485 and
RS-232 ports. Others have only RS-232 ports.
Another medium to large system architecture uses network servers to connect the
HMI to the RTUs. These devices regulate communication over the network. Master
resources are in the connected PC, so Modbus RTU timing may be disturbed by the
transport delay between the PC and the server. The EVO™/ECM-Modbus has
resources to deal with these delays. However, devices should be tested for
compatibility before commiting to a design. Servers are available to connect a
single, or multiple Modbus trunk. Most server's downlinks have RS-232 ports to
service the Modbus trunks.
Small system architecture connects the Modbus trunks directly to the PC. Trunks
may be connected to standard RS-232 ports com1: and com2:. Some systems will
use an RS-485 multi-port card plugged directly into the PC's motherboard. These
cards allow up to 8 trunks to be connected directly to the PC.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 23.
Two types of turn-around may be applied, timeout and software controlled. Timeout
turnaround is simple. Hardware times the flow of data, when data ceases for a
preset time, the transmitter disconnects from the trunk. This type is good for most
applications. However, they may not work where the RS-485 lines are in an
electrically noisy environment.
Software controlled turnaround is more accurate, and more complicated. This type
of turn-around requires the Master's resources to control turn-around.
Masters with RS-232 ports require a converter. These converters must change the
signal levels, and deal with turn-around. Simple converters like the R.E. Smith
identified in the configuration section of this manual use timeout flow control. Other
converters support software flow control using an RS-232 RTS/CTS handshake or
software flow control.
Blackbox offers rack-mounted RS-232 to RS-485 converters.
EVO/ECM-Modbus Controllers
Up to 31 Controllers/Trunk.
BlackBox 16 Slot
Equipment Rack
(-)
(-)
(-)
(-)
(+)
(+)
(+)
(+)
Shield
Shield
Shield
Shield
(-)
(-)
(-)
(-)
(+)
(+)
(+)
(+)
Shield
Shield
Shield
Shield
120 OHM
Typical, 1 of 16
Connections
TX-A
No Connect
1
TX-B
2
REC-A
120 OHM
3
120 OHM
REC-B
4
Switch Blackbox terminator OFF.
Use external terminator when
Blackbox is at the end of the line.
(This allows all cards in rack to
be configured the same).
Rack
Chassis
Make Good Earth
Ground On or Near
Rack Chassis.
BlackBox Switch & Jumper Settings
For Data Driven Flow Control
Install Header At XW1A (DCE)
Install R49 (100 Ohm) on each
card to connect common
to chassis ground.
S1=Out, S2=Off, S3=On
W5=AB, W7=100 ohm, W8=BC, W9=C,
W15=BC. W16=B, w17=E
No Connect
BlackBox
RS-232 (DB25) Connector
Minimum Connections
DB25-2=Transmit Data
DB25-3=Receive Data
DB25-7=Signal Common
EVO/ECM-Modbus Trunk
From Rack Mounted
Blackbox RS-232 <-> 485
Converter Plus &
Opto-Isolator/Converter
Typical Blackbox application
Page 24.
Application Guide
Series 1, July 2001
San Diego, CA USA
SCADA
The EVO™/ECM-Modbus RTU is usually connected to a SCADA (Supervisory
Control And Data Acquisition), Factory Automation, or building automation system.
These systems provide a means for a person to monitor the system using a PC's
video display, obtain reports using the printer, and receive alarms using the video
and audio functions. These systems are usually configured from off the shelf
software and components.
Communications Throughput
Proper SCADA design allows a great number of RTUs to be connected to one
system. If the system requires a large number of RTU connections, system
throughput must be considered.
Communications throughput is a function of the amount of data on the network, and
the time SCADA takes to process the points. During a routine and repetitive scan,
SCADA only needs part of the data from each RTU. Limiting the routine SCADA
scan and processing to "required data only" increases system throughput. The
lower numbered registers contain data that should be in the routine scan.
Some SCADA architectures map data into a data map file. In these systems, the
routine process should check the EC (see register 1) flag. If the flag is set, continue
the routine scan. If the flag is clear, read all registers, and update the data map.
Another SCADA architecture performs the routine scan, then performs event
generated scans to perform specific needs. An example is a scan that gathers data
for the currently displayed SCADA screen. Another example is a scan to gather data
for a printed log. Another common event generated scan changes data in the RTU.
A wide variety of SCADA systems and architectures are available. Each is different,
offering a variety of methods to improve throughput. These suggestions are
intended to spark the imagination of the SCADA designer, who must design a
system using the resources within the target SCADA.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 25.
SERVICE WINDOW
Some SCADA systems allow definition of a service window. The service window
allows all registers to be viewed and changed. Only one service window exists in
the system, so the window must allow the user to enter the target EVO™/ECMModbus RTU's address. Depending on the architecture, PLC, router or server
address information may also be required. This address must apply to all points in
the service window. If a service window can be implemented, a reduced size and
complexity SCADA application can be developed for the repetitive scan.
With a service window, an individual tag for seldom-used registers is not required.
These registers include the baud rate register and address register and many of the
default and alarm limit registers.
Page 26.
Application Guide
Series 1, July 2001
San Diego, CA USA
CONFIGURATION
CONFIGURATION TOOL
You will need a configuration tool to configure the EVO™/ECM-Modbus RTU. The
configuration tool must be able to communicate with the EVO™/ECM-Modbus RTU
via Modbus RTU protocol over a half duplex RS-485 communications loop. The
baud rate must selectable to at least 4.8kb.
Program….
Use an IBM compatible PC as a
configuration tool. The PC
needs Windows 95 or better to
run WinTech's ModScan32
Modbus Data Scanner.
http://www.win-tech.com
The help files with this program
also provide a good tutorial on
Modbus protocol.
Signal Converter….
Use an RS-232 to RS-485 signal converter to connect the communications signal
from the computer to the target EVO™/ECM-Modbus RTU.
http://www.rs485.com/
R.E. Smith Company provides a
suitable converter. It is available in a
kit, complete with plug-in powerpack
and the cable to connect the converter
to an IBM compatible PC.
The converter is shipped configured
so it will work at baud rates up to
38.4kb. This configuration is suitable
for communication with the EVO™/ECM-Modbus RTU.
RS-485 Test Cable….
Build a short cable to connect the signal converter to the EVO™/ECM-Modbus RTU.
Use a two conductor cable with shield, or a three
conductor cable. (The shield is not required for a short
test cable). The connector is Digi-Key PN ED1702ND
http://www.digikey.com/
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 27.
CONNECTING TO THE RTU
1. Install the Modscan 32 software on the PC.
2. Connect the RS232 cable that came with the R. E. Smith kit between your PC
and the converter.
3. Connect the signal converter power pack.
4. Connect the communications cable to the EVO™/ECMModbus RTU. We have not put a termination resistor on the
RS-485 line when configuring
a single EVO™/ECM-Modbus
RTU. If you want to add one,
place a120-ohm resistor
across the +/- connections of
the EVO™/ECM-Modbus RTU communications
connector.
5. If you have a series 1 RTU, place a
jumper plug on J7 to force 4.8kb
communications
6. Connect 24Vac to the RTU.
…and you are ready to configure the RTU!
Page 28.
Application Guide
Series 1, July 2001
San Diego, CA USA
STARTING THE CONFIGURATION PROGRAM
Start Modscan 32, and select Setup, then Display Options. Select Show Data, then
press Enter.
Select CONNECT from the menu bar.
Select connect from the pull down menu
to view the Connection Details screen. (If
you are already connected, you will need
to disconnect, then connect.)
Pull down Connect Using and select the
port (usually port 1) where you connected
the RS232 connector from the converter.
RTUs can be jumpered to 4800 baud. Otherwise, set any valid baud rate (index 0-5)
and AUTObaud (version 1.0 and above) will search the connection.
Set the parity to NONE. Stop bits can be 1 or 2.
Click on Protocol Selections…
Select STANDARD RTU.
Set the slave response timeout to 1000.
Click OK, taking you back to the previous
screen.
Click OK, taking you to the main screen and
enabling communications.
The EVO™/ECM Modbus RTU should be receiving polls. If it is, the green lamp
should be flashing!
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 29.
Communication With The EVO™/ECM-Modbus
You may need to re-arrange some of the windowpanes on the main screen. Try to
make it look just like the screen below! Or, use Modscan to open our file EVO-ECMModbus-S1.tst from the CD.
Set the address to 0001.
This is the first register
address. Do not confuse it
with the EVO™/ECMModbus RTU address.
Set the Length to 28 (it
can be any value from 1 to
28). This is the number of
registers you want to view.
(Ver. 0.0 to 1.1 = 18, Ver.
1.2=22, Ver 1.3=26).
Set the MODBUS Point
Type to 03. This is the
read register command.
Set the Device Id to 255.
You may not know the unit
address of the target
™
EVO /ECM-Modbus RTU. All RTUs will respond to address 255!
The EVO™/ECM-Modbus RTU should respond to these polls. The RED lamp on the
RTU flashes each time the RTU replies. You may need to wait up to 100 seconds
for AUTObaud to find the correct baud rate.
Select Reset Ctrs. to count valid slave responses. Select Setup, then Data
Definition to change the scan rate.
Register Displays
The Register Display Bar allows
you to select different number
systems to display the data in the
registers.
Leave the cursor on a Register Display Bar Icon for a moment. A drop down label
will appear to identify the number system. Select Decimal to set the display as
shown here.
Page 30.
Application Guide
Series 1, July 2001
San Diego, CA USA
CONFIGURING THE EVO™/ECM-MODBUS
Move the pointer to Register 17, and click to write to
a register.
The number in the Value box is the unit address.
You can change this number to any valid unit
address.
After Update, you will get a communications error
message. This is normal, because writing the unit
address register resets the EVO™/ECM-Modbus
RTU!
To configure the target EVO™/ECM-Modbus RTU, write registers 15, 16, and 17.
Refer to the Register Map (page 39) to determine the settings needed for each RTU.
If you want to change the baud rate, change register 18. Then, select Connection,
Disconnect, Connect, select the new baud rate, and OK. The RTU should now be
communicating at the new baud rate.
You can write the default registers 10 through 14 now, or you may choose to write
these registers with the automation system when connected to Modbus Master.
You need to set individual bits
to write registers 1 and 14.
Change the register display to
binary to write these registers.
Click on register 14 to bring up
the binary write register
window. The register is
displayed as bits, and the bits
are grouped into nibbles.
Select the bits to set or clear
them, and update the RTU. (A
check mark indicates the bit is
set, or 1).
Note:
Write Registers can also be used to write to dynamic
registers 1 through 5. Writing dynamic registers is
useful for testing connection to the GE ECM Motors.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 31.
Notes…
Page 32.
Application Guide
Series 1, July 2001
San Diego, CA USA
Versions & Revisions
HARDWARE
Series 1
Series 1 hardware changed the RS-485 communications driver and power supply
circuitry. Bridging connections similar to those on the zero series hardware were
moved to the logic side of the isolation circuitry. A test and force communications
jumper was added. A 4-pin connector was added for direct access to the EEPROM.
For setup and testing, a jumper may be
installed to force communications at
4.8kb upon power up. Install the
jumper on the 3-pin connector (J7),
between pins 1 & 2. The controller
reads the jumper on power up, and
immediately forces communications at
4.8kb.
Note: Jumping J7 (2-3) performs a
factory test. Do not jumper pins
2 to 3 with motors connected.
Series 1a
Series 1a corrects an artwork error on the Series 1 hardware and eliminates the
bridging and EEPROM connectors. Series 1a hardware is compatible with all
version 1.? Firmware.
San Diego, CA USA
Application Guide
Series 1, July 2001
Page 33.
FIRMWARE
A firmware number and copyright notice is on the EVO™/ECM-Modbus
microcontroller's label. All software, circuit design, circuit artwork, and printed
legends are included in this copyright. Firmware is numbered in a standard format
as follows:
_1. _2._3
_1 indicates the hardware series. The value(s) to the right of the leading decimal
point indicates the firmware version. Firmware is only compatible with the indicated
hardware series. _2 indicates a revision adding features to the product. _3 indicates
a revision to correct an existing feature or to add a manufacturing convenience.
Version 0.0
Product origin firmware and origin hardware.
Version 0.1
First production firmware
Version 1.0
Series 1 hardware changed some I/O assignments to accommodate a revised
communications scheme implemented on Series 1 hardware.
Page 34.
Application Guide
Series 1, July 2001
San Diego, CA USA
Version 1.1
Auto Baud feature was added
AUTObaud
Each controller automatically detects the baud rate. Twenty seconds after power up, the
controller listens to all communications on the trunk. It tests the integrity of the
communication, looking for proper data framing, proper data content, and a valid CRC
(cyclical redundancy check). The first check is made at the baud
Baud
rate associated with the index stored in register 18 (Baud Rate).
Rate
Baud
This baud rate validation process does not test for a valid address.
Index
Rate
Validation occurs in each Modbus RTU during any poll form the
0
1.2kb
Master.
If communications is valid, communications with the controller
begins. If no valid communication occurs within 20 seconds, the
controller indexes to the next baud rate and waits another 20
seconds for valid communications. Each test increments the baud
rate in sequence. When the maximum baud rate is reached, the
test starts over at the minimum baud rate.
1
2
3
4
5
2.4kb
4.8kb
9.6kb
19.2kb
38.4kb
Register 18
After establishing valid communications, the controller expects valid communications from
the Master at least once every 20 seconds. The controller restarts the auto baud search if
valid communications does not occur at least once every 20 seconds. During system
integration, set the Master baud rate as high as possible, while maintaining satisfactory
communications. When the best baud rate is found, set each Modbus RTU's baud rate to
that value. This minimizes the baud rate search time on system power up.
Disable AUTObaud by setting bit 5 in register 14 (Defaults ON/OFFS).
Page 28.
EVO/ECM-Modbus RTU Application Guide
San Diego, CA USA
Version 1.2
Features were added to reduce the number of points, or tags required to integrate a
network of EVO™/ECM-Modbus RTUs into a SCADA or automation system. One of the
features adds low RPM alarm limit processing.
In releases prior to V1.2, the EVO™/ECM-Modbus RTU reported the RPM. Where
required, the SCADA system added alarm limits, and the attending programming required
to determine when the motor was in alarm. V1.2 adds this programming to the RTU,
reducing the load on SCADA machine resources. SCADA only needs to monitor the RPM
alarm flags to determine the RPM alarm status of a motor. The
RPM alarm flags are assigned to a location that was reserved in earlier releases, allowing
a V1.2 RTU to be used in an application developed for an earlier version firmware.
Releases prior to V1.2 turned each motor on or off by setting motor on/off flags and motor
on/off default flags. These flags have been renamed enable/disable flags and
enable/disable default flags. Each motor's flow index and default flow index has been
modified to allow entry of a flow entry of "0". If the flow index is greater than 0, the motor
will run if enabled. If the flow index is "0", the motor will stop Make sure the flow indexes
and default flow indexes are above 0 to use a V1.2 RTU in an application developed for
an earlier version firmware.
This version has low alarm processing. It does not have high alarm limit processing.
Caution: DO NOT allow the Modbus Master to address any registers not defined for this
version. False data will appear in the defined registers, causing bad data and soft failures
requiring a reset.
Version 1.3
Version 1.3 adds high alarm limit processing.
Version 1.4
Failure when the Modbus Master writes to an undefined register is eliminated.
Write and read coil commands are added to reduce Modbus Master Complexity when
dealing with register 1 and register 14 flags. Refer to the version 1.4 Register Map for
details.
During RTU setup, the RTU can be forced to the default settings. Set the Unit Address
(I.D.) to 255. Then, set register 17 to 255. The RTU recognizes this invalid address as an
instruction to write all registers to the defaults, then reset. After reset, all registers will be
set to factory defaults and the unit address forced to 1. For most applications, force the
defaults, then write register 17 to the desired unit address.
Page 36.
San Diego, CA USA
Version 1.5
Features were added to enhance communications and reduce accidental global baud rate
and address changes.
•
Communications error handling was improved by implementing hardware overrun
detection and correction. This feature speeds up communications error handling.
•
Register 14, High bit 6 (coil/flag 31) can be set to lock the address and baud rate
registers. Set this flag after the system baud rate and addresses are set. Clear the
flag if an address or baud rate needs to be changed.
San Diego, CA USA
Series 1
Page 37.
Bit 3
4
Bit 4
5
Bit 5
6
Motor 2 Alarm
0=Norm, 1=Alarm
Bit 6
7
Motor 3 Alarm
0=Norm, 1=Alarm
Bit 7
8
Motor 4 Alarm
0=Norm, 1=Alarm
Write Single Register
3
Read Single Register
Bit 2
Write Multiple Register
2
Read Multiple Register
Bit 1
Y
Y
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
Y
Y
Detail
Value/Range
1
1=Enable
0=Disable
1=Enable
0=Disable
1=Enable
0=Disable
1=Enable
0=Disable
0=Norm, 1=Alarm
Coil/Flag #
Bit 0
Motor 1
Enable/Disable
Motor 2
Enable/Disable
Motor 3
Enable/Disable
Motor 4
Enable/Disable
Motor 1 Alarm
Location
Function
EVO/ECM-ModBus Registers Coils
Register 1
On/Off Control
Low Byte
Alarm Flag resets when
motor is off. Alarm inhibited
for 20 seconds after motor
starts.
Status
High Byte
External Comand 0= External Access
Flag
1=No Ext. Access
A global command
or reset clears this Flag.
Bit 0
9
Bit 1
10
Not Used
0
Bit 2
11
Not Used
0
Bit 3
12
Not Used
0
Bit 4
13
Not Used
0
Bit 5
14
Not Used
0
Bit 6
15
Communications
Timed Out
0
Sets when a timemout
occurs. Cleared by Master
Bit 7
16
Reset Controller
1=Reset
Flag cleared when
reset occurs
Dynamic
integer 0-100
Low Byte
High Byte
Not Used, reads as 0, write only 0's
Motor 2 Flow Index
Register 3
Low Byte
High Byte
Dynamic
Low Byte
Motor 3 Flow Index
Dynamic
High Byte
integer 0-100
Motor 4 Flow Index
Register 5
Low Byte
integer 0-100
Register 4
High Byte
These Flags are cleared
on power up & reset.
The Master may set/clear
them as needed.
Motor 1 Flow Index
Register 2
Page 38.
Remote sets on/off to reg
14 values on power up &
reset. Master changes
them to dynamic values
Dynamic
integer 0-100
Series 1.5 ©2007 All Rights Reserved
San Diego, CA USA
.
Dynamic
integer 0-1500
High Byte
Dynamic
Low Byte
High Byte
integer 0-1500
EEPROM
Integer 0-100
High Byte
High Byte
High Byte
San Diego, CA USA
Integer 0-100
Y
Updates every 833
milliseconds
Y
Y
Y
Updates every 833
milliseconds
Y
1-100% Flow Index
0 = Motor Off
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
1-100% Flow Index
0 = Motor Off
Y
Y
Motor 3 Flow Index
EEPROM
Integer 0-100
Motor 4 Flow Index
Register 13
Low Byte
Y
Motor 2 Flow Index
EEPROM
Register 12
Low Byte
Updates every 833
milliseconds
Motor 1 Flow Index
Register 11
Low Byte
integer 0-1500
Dynamic
Register 10
Low Byte
Y
Motor 4 RPM
Register 9
High Byte
Y
Motor 3 RPM
Register 8
Low Byte
integer 0-1500
Motor 2 RPM
Register 7
High Byte
Detail
Dynamic
High Byte
Low Byte
Updates every 833
milliseconds
Motor 1 RPM
Register 6
Low Byte
Value/Range
Function
Coil/Flag #
Location
EEPROM
Integer 0-100
Page 39.
Detail
Value/Range
Function
Coil/Flag #
Location
Y
Y
On/Off Control
Register 14
Low Byte
EEPROM
Defaults & Configuration Flags
Motor 1
Enable/Disable
Motor 2
Enable/Disable
Motor 3
Enable/Disable
Motor 4
Enable/Disable
1=Enable
0=Disable
1=Enable
0=Disable
1=Enable
0=Disable
1=Enable
0=Disable
0=Dynamic values
1= Default Values
Bit 0
17
Bit 1
18
Bit 2
19
Bit 3
20
Bit 4
21
Com Fail
Action
Bit 5
22
Not Used
Bit 6
23
Group 1 Reply
0=No Reply
1=Reply
Bit 7
24
Group 2 Reply
0=No Reply
1=Reply
High Byte
Takes Action After 3.5
minutes of no com.
Set flag causes the
respective controller to
reply to a group command
EEPROM
Configuration Flags
Bit 0
25
Bit 1
26
Bit 2
27
Bit 3
28
Bit 4
Delay Flag RD0
Delay Flag RD2
Set Flags for binary
value of 0-7 (Each count=4
ms @ 38.4kb
Next Message
Delay
0 = 3 Bit timeout
1 = no timeout
Delay between end of reply
and start of new transaction
29
Not Used
0
Bit 5
30
VSpd
1=Auto
0=Manual
Vspd pulse always present,
even when off & full on.
Bit 6
31
Lock
1=Locked
0=unlocked
Locks address & baud
Registers
Bit 7
32
Alarm Select
0 = RPM Alarms
1 = Contact Alarms
Version 1.3 & Above
Turn Around
Delay
Delay Flag RD1
Strobed Coils/Flags
33 Write defaults to dynamic registers.
34 Reset Controller
Page 40.
San Diego, CA USA
.
High Byte
EEPROM
High Byte
Low Byte
High Byte
Low Byte
EEPROM
High Byte
High Byte
EEPROM
(V1.2 & Above)
Low Byte
EEPROM
(V1.2 & Above)
High Byte
EEPROM
(V1.2 & Above)
High Byte
San Diego, CA USA
Y
Y
Integer 0-1500
Set to 0
to disable alarm.
Y
Y
Integer 0-1500
Set to 0
to disable alarm.
Y
Y
Integer 0-1500
Set to 0
to disable alarm.
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
EEPROM
(V1.2 & Above)
Integer 0-1500
Set to 0
to disable alarm.
EEPROM
(V1.3 & Above)
Integer 0-2000
Set to 3000
to disable alarm
EEPROM
(V1.3 & Above)
Integer 0-2000
Set to 3000
to disable alarm
EEPROM
(V1.3 & Above)
Integer 0-2000
Set to 3000
to disable alarm
Register 26
Low Byte
0=1.2kb, 1=2.4kb,
2=4.8kb, 3=9.6kb, 4=19.2kb,
5=38.4kb
Register 25
Low Byte
Y
Register 24
High Byte
Y
Register 23
Low Byte
Integer 0-5
Register 22
Low Byte
Y
Baud Rate Select
Register 21
High Byte
Integer 1-247
Register 20
Low Byte
Y
Unit Address
EEPROM
Register 19
High Byte
Integer 1-247
Register 18
Low Byte
Y
Group Address 2
Register 17
Low Byte
Low Byte
Y
Group Address 1
Register 16
High Byte
High Byte
Integer 1-247
Value/Range
EEPROM
Register 15
Low Byte
Detail
Function
Coil/Flag #
Location
EEPROM
(V1.3 & Above)
Integer 0-2000
Set to 3000
to disable alarm
Page 41.

Modbus Manual - Evolution Controls

Transcription

Documents pareils

motor For pool cover

Tested: STO-Tuned Astra OPC/Coupe

PM Speed Adjusting Motor

motor for pool cover

motor for pool cover

PD1-013 / PD2-013 / PD3-013 Stepper Motor with

Mercedes Benz W208 CLK 320 Replacement of Windscreen washer motor

P ro ject B rief - S asaram P o w er C o n verter

Application Note 5466: Stepper Motor

Larman evoaug603