Honeywell Universal Modbus Interface Reference
Issue Date 7 November 2003 Notice This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell Limited Australia.
Contents 1 Getting Started Support and Documentation for Universal Modbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Universal Modbus Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Documentation for Universal Modbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Products Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Non-numbered Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 6 HC900 and UMC800 SPP and Recipe Support Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Resource Requirements. . . . . . . . . . . . .
1 Getting Started This reference describes how to set up, configure, and test Universal Modbus controller communications with the server. There is detailed information for defining the controller using Quick Builder. Complete each step before commencing the next.
1 – Getting Started Support and Documentation for Universal Modbus About the Universal Modbus Interface The Universal Modbus Interface enables the server to interface to any Control Products controller that implements the Honeywell Universal Modbus protocol. The Honeywell Universal Modbus protocol is the Honeywell implementation of the Modbus RTU Communications protocol for serial RS-485, RS-232 or Ethernet networks.
Support and Documentation for Universal Modbus Instrument Model User Manual Part Number UDC3300 51-52-25-70 51-52-25-38 UDC3000 A Modbus 485 RTU Communication Manual DPR180 / DPR250 EN1I-6189 DPR180/DPR250 Communication Option Manual UMC800 52-52-25-87 Modbus RTU Serial Communications User Manual HC900 51-52-25-107 51-52-25-111 HC900 Hybrid Controller Ethernet Modbus/TCP Communications User Manual TrendView - Minitrend, Multitrend, ez Trend 43-TV-25-08 Communications Manual Ethernet Bridge Card
1 – Getting Started Control Products Wizard The Control Products wizard makes it easy to configure a controller and its associated points. The wizard guides you through the standard configuration tasks, and can download the configuration details to the server. You can also use the wizard to modify the configuration details of an existing controller. You can access the wizard either in Quick Builder, where the wizard adds the controller to the current project.
2 Universal Modbus Controller Setup This chapter describes how to set up an Universal Modbus controller.
2 – Universal Modbus Controller Setup Connecting your Controller Many different types of controllers can be connected to the same Universal Modbus network. The only requirements are that every controller on the same network use the same connection type and baud rate, and that each controller use a unique device identification number. Setting up Your Connections Control Products controllers are designed to communicate using the Modbus TCP Ethernet, RS485 or the RS-232 specification.
Connecting your Controller Using an RS-232/485 Converter Honeywell recommends that you use the Black Box LD485-HS RS-232/485 Interface Converter, model number ME837A, or a Black Box IC109A-R2. These converters have been qualified by Honeywell. Use of another converter might produce unexpected results.
2 – Universal Modbus Controller Setup Figure 3 Black Box (4-wire) Connections Black Box RS-485 Port Tx A Tx B Rx A Rx B RS-485 Network 120 RxRx+ TxTx+ RxRx+ TxTx+ RxRx+ TxTx+ Honeywell Control Products Controllers 120 Ensure that the black box switches are configured with the following settings. Switch Setting Description XW1A jumper in* Configure RS-232 port as DCE. XW1B jumper out Do not configure RS-232 port as DTE. W8 B-C 2-wire (half-duplex) operation. W9 C* 0 ms RTS/CTS delay.
Connecting your Controller Using an RS-485 Adapter Honeywell recommends using the Stallion EasyConnection 8/32 ISA, 8/32 PCI, 8/64 ISA or 8/64 PCI adapters with the Stallion RS-232 to RS-485 8-port dual interface asynchronous module. Honeywell has qualified this adapter. Use of another adapter may produce unexpected results.
2 – Universal Modbus Controller Setup Figure 6 Stallion RS-485 (4-wire) Connections RS-485 Network Stallion RS-485 120 3 Rxd 120 18 Conv 15 Rx+ 19 Tx+ Rx+ Tx+ RxTx- 17 Rx25 Tx- Rx+ Tx+ RxTx- Rx+ Tx+ RxTx- Universal Modbus TCP Connection To connect controllers to the server communicating using the UModbus TCP protocol, you are required to have network adapter (NA card) connected to an Ethernet network on both the server as well as the controller.
Connecting your Controller Redundant Communication Architecture If you require redundant communications, you must have two separate network adapters (NA card) on both the server and the controller which are connected to separate Ethernet subnets. This architecture is not presently supported in the controllers.
2 – Universal Modbus Controller Setup Configuring Communication Parameters RS485 Devices Before using your Control Products controllers, ensure that all communication parameters are configured correctly for each controller. Configure each controller to use the following communication parameters. Parameter Value Number of Start Bits 1 Number of Data Bits 8 Number of Parity Bits 0 Number of Stop Bits 1 Make sure that each controller on the RS-485 network is configured for the same Baud rate.
Universal Modbus Controller Configuration and Addressing 3 This chapter describes how to configure a Universal Modbus controller for the system using Quick Builder. For each configuration procedure, there is detailed information covering all supported Universal Modbus devices.
3 – Universal Modbus Controller Configuration and Addressing Defining a Universal Modbus Channel Build a channel for each RS-485, RS-232 or Ethernet TCP/IP physical connection from your server. Note that you can multi-drop several controllers on the one serial RS-485 channel, provided they all use the same Baud settings. To define a channel using Quick Builder: 1 Click to add a channel. 2 In the Add Items dialog box, select Channel as the item and Universal Modbus as the channel type.
Defining a Universal Modbus Channel Property Description Marginal Alarm Limit The communications alarm marginal limit at which the channel is declared to be marginal. When this limit is reached, a high priority alarm is generated. A channel barometer monitors the total number of requests and the number of times the controller did not respond or response was incorrect. The barometer increments by 2 or more, depending on the error and decrements for each good call.
3 – Universal Modbus Controller Configuration and Addressing Property Description Item Number This field displays the unique item number currently assigned to this item by Quick Builder. You can change the item number displayed in this field if you need to match your current server database configuration. The item number must be between 1 and the maximum number of channels allowed for your system.
Defining a Universal Modbus Channel Serial Port Properties Note The Serial Port settings must match the settings on your communication devices. Property Description Serial Port Name The device name of the serial port. Baud Rate The number of data bits per second. The default is 9600. Number of Data Bits The number of data bits used for transmission. The default is 8. Stop Bits The number of stop bits used for transmission. The default is 1. Parity The parity verification used on the port.
3 – Universal Modbus Controller Configuration and Addressing Property Description Handshaking Options RS-232 • Enable RTS/CTS flow control. Select to stop a receiver from being overrun with messages from a sender by using RTS/CTS for flow control. • Detect DCD. Select if the Data Carrier Detect communication status line of the COM port requires monitoring (usually when using modem or microwave linking).
Defining a Universal Modbus Channel Redundant Port Properties A communication port used as a redundant link has the same channel name but a requires a different port name to its twin. All other entries are identical to those of the primary port.
3 – Universal Modbus Controller Configuration and Addressing Defining a Universal Modbus Controller You need to define a controller to describe each product on a channel. To define a controller using Quick Builder: 1 Click to add a controller. 2 In the Add Items dialog box, select Controller as the item and Universal Modbus as the controller type. 3 Enter the property definitions for the controller on the controller Main property page.
Defining a Universal Modbus Controller Property Description Marginal Alarm Limit The communications alarm marginal limit at which the controller is declared to be marginal. When this value is reached, a high priority alarm is generated. This limit applies to the controller barometer which monitors the total number of requests to the controller and the number of times the controller did not respond or response was incorrect.
3 – Universal Modbus Controller Configuration and Addressing Available Device Types Type Acronym Controller Device RSX RSX Controller VPR100 VPR100 Controller VRX100 VRX100 Controller VRX180 VRX180 Controller UDC5300 Universal Digital Controller 5300 UDC2300 Universal Digital Controller 2300 UDC3300 Universal Digital Controller 3300 DR4300 DR4300 Circular Chart Recorder DR4500 DR4500 Circular Chart Recorder DPR180 Digital Process Recorder 180 DPR250 Digital Process Recorder 250 UMC8
Defining a Universal Modbus Controller Parameter Category OFFSET Address for Controller UMC800 HC900 Point Addressing 0 (loops 1 to 16) 0 (loops 1 to 24) Named (acronyms) Control Loops (25 – 32) Not applicable 6000 Modbus Hex codes Variables (MATH_VAR) 0 (all Variables, 1-600) Named (acronyms) SP Programmers 1 to 4 0 0 Named (acronyms) SP Programmers 5 to 8 Not applicable Not supported Signal Tags (TAG) 2000 (Signal Tags 1–1000) Named (acronyms) Signal Tags 1001-2000 Not applicable 40
3 – Universal Modbus Controller Configuration and Addressing Defining a Universal Modbus Address for a Point Parameter Value Different addresses are available depending on the type of device to which you are connected. Addresses that are read-only can only be used as source addresses. Addresses that are write-only can only be used as destination addresses. Addresses that are available for both read and write operations can be used as both source and destination addresses.
Defining a Universal Modbus Address for a Point Parameter Value For addresses that occur in only one location, specify the name of a register within your controller simply using the syntax: AddressName [Format] Part Description AddressName Matches an address from “Non-numbered Addresses” on page 99. Format (Optional) Specify only if the device does not use the default format for that address. Different addresses will have different default formats.
3 – Universal Modbus Controller Configuration and Addressing Parameter Source Address Destination Address MODE (MD) LOOP n LOOPSTAT LOOP n MODEIN 1. LSP1 or SP1 can be used if the parameter WSP is unavailable. 2. OP can be used if the parameter OPWORK is unavailable.
Defining a Universal Modbus Address for a Point Parameter Value “Digital” Signal Tag Example: Parameter Source Address Destination Address PV TAG n Not Configurable “Digital” Variable Example: Parameter Source Address Destination Address PV MATH_VAR n Not Configurable OP MATH_VAR n MATH_VAR n “Analog” Variable Example: Parameter Source Address Destination Address PV MATH_VAR n Not Configurable SP MATH_VAR n MATH_VAR n Digital Output Control Strategies Some controllers support the us
3 – Universal Modbus Controller Configuration and Addressing Figure 10 Digital Output Control Strategy - Example 2 Digital Switch A Digital Variable "Forced Value" Digital Output B Calculated Value SA Digital Variable "Force Enabled" Location Syntax for Non-named Addresses Addresses without names can be addressed directly using the format: n:0xA [Format] Part Description n Table number. See “Table Types” on page 32 for table descriptions and their number. A Address within the table.
Defining a Universal Modbus Address for a Point Parameter Value Data Formats The data format tells the server how to interpret the register value. The possible formats are: Data Format Description Point Type IEEEFP 32-bit IEEE floating point value. (Big Endian) Status/Analog/Accumulator n Bit field. n represents the starting bit (0 to Status 15). This cannot be used with a named address. MODE Informs the server that the address is a mode parameter.
3 – Universal Modbus Controller Configuration and Addressing Troubleshooting Point Configuration Errors when point building 84E0h Invalid address for this type of controller specified. 8426h Invalid data format for this type of controller specified. Error when scanning (Errors appear in log) 0106h A request to the controller timed out. This could be caused by a communication setup problems (for example, wrong address or Baud rate). A channel write delay value being too low could also cause this problem.
Optimizing Scanning Performance Optimizing Scanning Performance The maximum amount of data that can be acquired from an controller is influenced by the rate of sending scan packets to the controller. An understanding of the Universal Modbus scan packets will help you configure points so that optimal data acquisition performance can be achieved by maximizing the amount of data acquired with each scan packet. The scan packets that have been built can be listed by using the list scan utility, lisscn.
3 – Universal Modbus Controller Configuration and Addressing 36
Server and Station Tasks for Universal Modbus 4 This chapter describes tasks for the Universal Modbus controller that you perform either on the server or from any Station.
4 – Server and Station Tasks for Universal Modbus Testing Communications with the Server Use the test utility umbtst to test the communications. Before using the utility, make sure that: • You have set up your Control Products controllers according to their user manuals. • All cables are connected. • You have configured your channels in Quick Builder without error and downloaded all configuration information to the server without error.
Testing Communications with the Server q If you do not know the device name of your channel, select View > System Status > Channels from the Station menu. To the left of the channel name is the channel number. The device name of the channel will be the letters “chn” followed by the two-digit channel number. For example, your Universal Modbus channel “COM3” might be channel number 1. Its device name will be “chn01”.
4 – Server and Station Tasks for Universal Modbus Troubleshooting Universal Modbus Configuration Errors Common Problems Error message/problem Explanation/solution You see the error in the server log file: The server has not received a response from the controller. Error code 0106 (Device Timeout) You see the error in the server log file: Error code 8102 (MODBUS error 2 - illegal data address) You either specified an illegal address, or an illegal number of addresses.
Troubleshooting Universal Modbus Configuration Errors Error message/problem Explanation/solution The address LOOP n SP doesn’t download. The SP parameter is not a valid named address because there are a number of set point types available, and a simple SP is ambiguous. WSP stands for working set point and SP1 stands for set point 1. In most cases, WSP works best.
4 – Server and Station Tasks for Universal Modbus Error message/problem Explanation/solution The address PID n PV doesn’t download. The PID part of the address is not valid and doesn’t appear in the Universal Modbus driver documentation. You cannot use the names of control blocks within Control Builder as Universal Modbus addresses. You can only use the addresses listed in the Universal Modbus documentation. You know that you should use the address AI n but you don't know what value to use for n.
Troubleshooting Universal Modbus Configuration Errors Error message/problem Explanation/solution You see the error: Signal tags are read-only parameters, so cannot be used as destination addresses. Please read ***** PNTBLD ERROR ***** illegal MODICON plc address the Universal Modbus documentation about read-only and write-only addresses. in the Quick Builder output when trying to download a signal tag, such as TAG 2, as a destination address to the server. You don’t know what number to use for 1.
4 – Server and Station Tasks for Universal Modbus Error message/problem Explanation/solution For analog inputs in the first rack, you For the first rack only, the analog input number know that you should use the address AI is calculated using the formula: n but you don’t know what value to use n = (m-1) * 8 + c. for n. n = the analog input number m = the module/slot number. The HC900 has up to 12 slots depending on rack size, numbered 1 to 12. c = the channel number (of the analog input).
Troubleshooting Universal Modbus Configuration Errors Error message/problem Explanation/solution For analog inputs in the first rack, you For the first rack only, the digital or output know that you should use the address DI number is calculated using the formula: n or DO n but you don’t know what n = (m-1) * 16 + c. value to use for n. n = the analog input number m = the module/slot number. The HC900 has up to 12 slots depending on rack size, numbered 1 to 12.
4 – Server and Station Tasks for Universal Modbus Error message/problem Explanation/solution You want to write to a digital output. Honeywell recommends against writing to a digital output since this forces cannot be returned to normal via Modbus communications. Use the HC Designer tool concurrently for force actions where force removal is supported. You may also use digital Variables and logic blocks in the controller configuration to implement the force more safely via Station.
Troubleshooting Universal Modbus Configuration Errors Error message/problem Explanation/solution You want to know which HC900 Signal You can apply Signal Tags (read only) and Tags or Variables are digital in nature so Variables (read/write) to digital Status points if that they can be applied to Status points. they are digital data types. See above for information related to viewing/printing the Tag Information Report. The Data Type column lists whether the parameter is Digital or Analog.
4 – Server and Station Tasks for Universal Modbus 48
5 Device Information This chapter lists numbered and non-numbered addresses, their parameter details and the devices which are supported.
5 – Device Information For details about: Go to: Alarm Status Com page 70 Alarm Status Digital page 68 Alarm Status Event page 69 Alarm Status Math page 70 Analog Input page 60 Communication or Constant Value Group page 62 Digital Input Table page 71 Digital Input Table page 71 Digital Output Table page 72 Digital Output Table page 73 Math, Variable or Calculated Value Group page 63 Math or Calculated Value Status page 65 PID Loop page 51 Set Point Scheduler #1 Segment page 92
Devices Devices Baud Rates Supported The following table lists the devices and their supported baud rates. Note Baud rates are not applicable to HC900 or TrendView devices. These devices use Ethernet connections.
5 – Device Information Device Supported Address Format Range VRX100 LOOP [n] [param] [n] = 1 to 2 VRX180 LOOP [n] [param] [n] = 1 to 8 UDC5300 LOOP [n] [param] [n] = 1 to 2 DR4300 LOOP [n] [param] [n] = 1 to 1 DR4500 LOOP [n] [param] [n] = 1 to 2 UDC2300 LOOP [n] [param] [n] = 1 to 1 UDC3300 LOOP [n] [param] [n] = 1 to 2 UMC800 LOOP [n] [param] [n] = 1 to 16 HC900 LOOP [n] [param] [n] = 1 to 24 Param Format Access The following table lists the details of the PID Loop paramet
Param Address Line Param Format Access Devices Devices Prop Band #1 LOOP [n] PROP1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 DIR LOOP [n] DIR Floating Point RO RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Reset #1 LOOP [n] RESET1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Rate #1 LOOP [n] RATE1 Floating Point RW RSX, VPR100,
Param Format Access 5 – Device Information Param Address Line Alarm #1 SP #2 LOOP [n] AL1SP2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Gain #2 LOOP [n] GAIN2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Prop Band #2 LOOP [n] PROP2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 DB LOOP [n] DB Floating Point RW RSX,
Param Address Line Param Format Access Devices Devices Local Set Point #1 LOOP [n] LSP1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Local Set Point #2 LOOP [n] LSP2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Alarm #2 SP #1 LOOP [n] AL2SP1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Alarm #2 SP #2 LOOP [n] AL2SP2
Param Address Line Param Format Access 5 – Device Information OP High Limit LOOP [n] OPHIGH Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Output Working LOOP [n] OPWORK Floating Point Value RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 RATIO LOOP [n] RATIO Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 BIAS LOOP [n] BIAS Floating Point
Param Address Line Param Format Access Devices Remote / Local Set Point State LOOP [n] RSP_STATE Discrete (bits). RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 [Status Point Only] Bit 0, 0 = LSP, 1 = RSP Tune Set State LOOP [n] Discrete (bits).
Param Address Line Param Format Access 5 – Device Information Remote Set Point (RSP) LOOP [n] RSP Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, UMC800, HC900 Set Point #2 LOOP [n] SP2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, UMC800, HC900 Working Set Point (WSP) LOOP [n] SPWORK Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, UMC800, HC900 Remote Set Point (RSP) LOOP [n] RSP Floating Point RO DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Set Point #2 LO
Param Address Line Param Format Set Point State LOOP [n] SP_STATE Discrete (bits).
Param Address Line Param Format Access 5 – Device Information On/Off Output Hysteresis LOOP [n] OUT_HYST Floating Point RW UMC800, HC900 Carbon Potential LOOP [n] CPD Dewpoint Floating Point RW UMC800, HC900 Three Position LOOP [n] MOTOR Step Motor Time Floating Point RW UMC800, HC900 Fuzzy State Discrete (bits). RW UMC800, HC900 LOOP [n] FUZZY_STATE Devices [Status Point Only] Bit 0, 0 = Disable, 1 = Enable Demand Tune Request LOOP [n] TUNE_REQ Discrete (bits).
Devices Device Supported Address Format Range VRX100 AI [n] [param] [n] = 1 to 12 VRX180 AI [n] [param] [n] = 1 to 48 UDC5300 AI [n] [param] [n] = 1 to 3 DR4300 AI [n] [param] [n] = 1 to 1 DR4500 AI [n] [param] [n] = 1 to 4 DPR180 AI [n] [param] [n] = 1 to 24 DPR250 AI [n] [param] [n] = 1 to 64 UDC2300 AI [n] [param] [n] = 1 to 2 UDC3300 AI [n] [param] [n] = 1 to 3 UMC800 AI [n] [param] [n] = 1 to 64 HC900 AI [n] [param] [n] = 1 to 64* TrendView AI [n] [param] [n] = 1
5 – Device Information Param Address Line Param Format Access The following table lists the details of the Tagged Signal parameters. Devices Tagged Signal Value TAG [n] VALUE1 Floating Point RO UMC800, HC900 1. The default Parameter if only “TAG [n]” is entered. Communication or Constant Value Group The following table lists the devices which support the Communication or Constant Value group and their formats.
Devices Math, Variable or Calculated Value Group The following table lists the devices which support the Math or Calculated Value group and their formats.
5 – Device Information Totalizer Value Group The following table lists the devices which support the Totalizer Value group and their formats.
Devices Param Address Line Param Format Alarm Set Point ALMSP [n] VALUE1 Floating Point Value Access The following table lists the details of the Alarm Set Point Value Group parameters. Devices RW RSX, VPR100, VRX100, VRX180, UDC5300, DPR180, DPR250 1. The default Parameter if only “ALMSP [n]” is entered. Alarm Set Point Value Group The following table lists the devices which support the Alarm Set Point Value group and their formats.
5 – Device Information Device Supported Address Format Range VRX100 MATH_STATUS [n] [param] [n] = 1 to 32 VRX180 MATH_STATUS [n] [param] [n] = 1 to 64 UDC5300 MATH_STATUS [n] [param] [n] = 1 to 16 DR4500 MATH_STATUS [n] [param] [n] = 1 to 1 DPR180 MATH_STATUS [n] [param] [n] = 1 to 24 DPR250 MATH_STATUS [n] [param] [n] = 1 to 32 UDC3300 MATH_STATUS [n] [param] [n] = 1 to 2 Param Address Line Param Format Math or MATH_STATUS [n] Discrete (bits).
Devices Param Address Line Param Format Access The following table lists the details of the Totalizer Value Status parameters. Totalizer Status TOTALIZER_STAT US [n] STATUS1 Discrete (bits). RO RSX, VPR100, VRX100, VRX180, DR4300, DR4500, UDC3300 [Status Point Only] 0 = Totalizer Off Devices 1 = Totalizer On 1. The default Parameter if only “TOTALIZER_STATUS [n]” is entered. Alarm Status The following table lists the devices which support the Alarm Status and their formats.
Param Address Line Param Format Access 5 – Device Information Devices 1. The default Parameter if only “ALMSTAT [n]” is entered. Alarm Status Analog The following table lists the devices which support the Alarm Status Analog and their formats. Device Supported Address Format Range DPR180 ALMSTAT_ANALOG [n] [param] [n] = 1 to 24 DPR250 ALMSTAT_ANALOG [n] [param] [n] = 1 to 64 Param Address Line Param Format Alarm Status ALMSTAT_ANALO Discrete (bits).
Devices Alarm Status Event The following table lists the devices which support the Math or Calculated Value Status and their formats. Device Supported Address Format Range DPR180 ALMSTAT_EVENT [n] [param] [n] = 1 to 6 DPR250 ALMSTAT_EVENT [n] [param] [n] = 1 to 6 Param Address Line Param Format Access The following table lists the details of the Alarm Status Event parameters. Devices Alarm Status ALMSTAT_EVENT [n] STATUS1 Discrete (bits). RO DPR180, DPR250 [Status Point Only] 1.
5 – Device Information Alarm Status Com The following table lists the devices which support the Alarm Status Com and their formats. Device Supported Address Format Range DPR180 ALMSTAT_COM [n] [param] [n] = 1 to 24 DPR250 ALMSTAT_COM [n] [param] [n] = 1 to 32 Param Address Line Param Format Alarm Status ALMSTAT_COM [n] Discrete (bits). STATUS1 [Status Point Only] Access The following table lists the details of the Alarm Status Com parameters. Devices RO DPR180, DPR250 1.
Devices Digital Input Table The following table lists the devices which support the Digital Input Table and their formats.
5 – Device Information Param Address Line Param Format Access The following table lists the details of the Digital Input Table parameters. Devices Digital Input Value DI [n] VALUE1 Discrete (bits). RO DPR180, DPR250 [Status Point Only] 1. The default Parameter if only “DI [n]” is entered. Digital Output Table The following table lists the devices which support the Digital Output Table and their formats.
Param Address Line Param Format Access Devices Devices 1. The default Parameter if only “DO [n]” is entered. 2. Applies to Rack 1 only, allocation is 16 outputs (bits), 12 slots maximum. Digital Output Table The following table lists the devices which support the Digital Output Table and their formats.
5 – Device Information Device Supported Address Format Range HC900 SPP [n] [param] [n] = 1 to 4 74 Param Address Line Param Format Access The following table lists the details of the set point program parameters.
Param Address Line Param Format Access Devices Set Point Programmer Status - Hold SPP [n] STATUS_HOLD Discrete (bits). RO VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Set Point Programmer Status - End SPP [n] STATUS_END Discrete (bits). [Status Point Only] [Status Point Only] Devices RO VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 Set Point SPP [n] Discrete (bits).
Param Format Access 5 – Device Information Param Address Line Floating Point RW UMC800, HC900 Set Point SPP [n] Discrete (bits). Programmer STATUS_HOLD_TY [Status Point Status - Type of PE Only] Hold RO UMC800, HC900 Set Point SPP [n] Programmer STATUS_RAMP Status - Current Segment is a ramp Discrete (bits). RO UMC800, HC900 Set Point Programmer Active Time SPP [n] ACT_TIME Floating Point RO VPR100, VRX100, VRX180, UDC5300 Set Point Programmer Segment Event #1 SPP [n] EV01 Discrete (bits).
Param Address Line Param Format Access Devices Set Point Programmer Segment Event #7 SPP [n] EV07 Discrete (bits).
5 – Device Information Set Point Program Additional Values The following table lists the devices which support the Set Point Program Additional Values and their formats. Device Supported Address Format Range UMC800, HC900 SPP_ADD [n] [param] [n] = 1 to 4 Param 78 Param Format Access The following table lists the details of the Set Point Program Additional Values parameters.
Param Address Line Param Format Access Devices Ramp Units SPP_ADD [n] UNITS_RAMP Discrete (bits). RW UMC800, HC900 Guaranteed Soak SPP_ADD [n] Type SOAK_TYPE Devices [Status Point Only] Discrete (bits). RW UMC800, HC900 [Status Point Only] 1. The default Parameter if only “SPP_ADD [n]” is entered. Set Point Programmer #1 Profile Segment The following table lists the devices which support the Set Point Program #1 Profile Segment and their formats.
Param Address Line Param Format Event #1 SPP1_SEG [n] EV01 Discrete (bits). Access 5 – Device Information Devices RW UMC800, HC900 [Status Point Only] Event #2 SPP1_SEG [n] EV02 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #3 SPP1_SEG [n] EV03 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #4 SPP1_SEG [n] EV04 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #5 SPP1_SEG [n] EV05 Discrete (bits).
Param Address Line Param Format Event #13 SPP1_SEG [n] EV13 Discrete (bits). Access Devices Devices RW UMC800, HC900 [Status Point Only] Event #14 SPP1_SEG [n] EV14 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #15 SPP1_SEG [n] EV15 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #16 SPP1_SEG [n] EV16 Discrete (bits).
5 – Device Information Device Supported Address Format Range UDC5300 SPP2_SEG [n] [param] [n] = 1 to 63 DR4300 SPP2_SEG [n] [param] [n] = 1 to 24 DR4500 SPP2_SEG [n] [param] [n] = 1 to 12 UDC2300 SPP2_SEG [n] [param] [n] = 1 to 12 UDC3300 SPP2_SEG [n] [param] [n] = 1 to 12 UMC800, HC900 SPP2_SEG [n] [param] [n] = 1 to 50 Param Address Line Param Format Access The following table lists the details of the Set Point Program #2 Profile Segment parameters.
Param Address Line Param Format Event #8 SPP2_SEG [n] EV08 Discrete (bits). Access Devices Devices RW UMC800, HC900 [Status Point Only] Event #9 SPP2_SEG [n] EV09 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #10 SPP2_SEG [n] EV10 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #11 SPP2_SEG [n] EV11 Discrete (bits). RW UMC800, HC900 [Status Point Only] Event #12 SPP2_SEG [n] EV12 Discrete (bits).
Param Address Line Param Format Access 5 – Device Information Devices Ramp or Soak Value SPP2_SEG [n] SEG_VALUE Floating Point RW VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900 1. The default Parameter if only “SPP2_SEG [n]” is entered. Set Point Programmer #3 Profile Segment The following table lists the devices which support the Set Point Programmer #3 Profile Segment and their formats.
Devices Address Line Param Format Event #3 SPP3_SEG [n] EV03 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #4 SPP3_SEG [n] EV04 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #5 SPP3_SEG [n] EV05 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #6 SPP3_SEG [n] EV06 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #7 SPP3_SEG [n] EV07 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #8 SPP3_SEG [n] EV08 Discrete (bits).
Param Address Line Param Format Event #16 SPP3_SEG [n] EV16 Discrete (bits).
Devices Param Address Line Param Format Access The following table lists the details of the Set Point Program #4 Profile Segment parameters. Ramp/Soak Segment SPP4_SEG [n] SEG_TYPE Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #1 SPP4_SEG [n] EV01 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #2 SPP4_SEG [n] EV02 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #3 SPP4_SEG [n] EV03 Discrete (bits).
5 – Device Information Address Line Param Format Event #12 SPP4_SEG [n] EV12 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #13 SPP4_SEG [n] EV13 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #14 SPP4_SEG [n] EV14 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #15 SPP4_SEG [n] EV15 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #16 SPP4_SEG [n] EV16 Discrete (bits).
Devices Device Supported Address Format Range HC900 SCHED [n] [param] [n] = 1 to 2 Param Address Line Param Format Access The following table lists the details of the Scheduler Values parameters.
Param Format Access 5 – Device Information Param Address Line Floating Point RW UMC800, HC900 Current Segment SCHED [n] SEG_NO Floating Point Number RW UMC800, HC900 Program Elapsed SCHED [n] Time EL_TIME Floating Point RO UMC800, HC900 Segment Time Remaining SCHED [n] TIME_REMAIN Floating Point RO UMC800, HC900 Schedule Save Request SCHED [n] SCHED_SAVE Floating Point RW UMC800, HC900 Guaranteed Soak SCHED [n] Limit #1 SOAK_LIMIT_1 Floating Point RW UMC800, HC900 Guaranteed Soak SCHE
Param Address Line Param Format Access Devices Devices Event #5 SCHED [n] EVENT_05 Discrete (bits). [Status Point Only] RO UMC800, HC900 Event #6 SCHED [n] EVENT_06 Discrete (bits). [Status Point Only] RO UMC800, HC900 Event #7 SCHED [n] EVENT_07 Discrete (bits). [Status Point Only] RO UMC800, HC900 Event #8 SCHED [n] EVENT_08 Discrete (bits). RO UMC800, HC900 Event #9 SCHED [n] EVENT_09 Discrete (bits).
Param Address Line Param Format Access 5 – Device Information Devices Advance Schedule SCHED [n] ADVANCE UINT2 WO UMC800, HC900 Reset Schedule SCHED [n] RESET UINT2 WO UMC800, HC900 Time Units SCHED [n] UNITS_TIME Discrete (bits). [Status Point Only] RW UMC800, HC900 1. The default Parameter if only “SCHED [n]” is entered. Set Point Scheduler #1 Segment The following table lists the devices which support the Scheduler #1 Segment and their formats.
Param Address Line Param Format Access Devices Devices Soak Type #7 SCHED1_SEG [n] GUAR7 Discrete (bits). [Status Point Only] RW UMC800, HC900 Soak Type #8 SCHED1_SEG [n] GUAR8 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #1 SCHED1_SEG [n] EVENT_01 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #2 SCHED1_SEG [n] EVENT_02 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #3 SCHED1_SEG [n] EVENT_03 Discrete (bits).
Param Address Line Param Format Access 5 – Device Information Devices Event #12 SCHED1_SEG [n] EVENT_12 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #13 SCHED1_SEG [n] EVENT_13 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #14 SCHED1_SEG [n] EVENT_14 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #15 SCHED1_SEG [n] EVENT_15 Discrete (bits). [Status Point Only] RW UMC800, HC900 Event #16 SCHED1_SEG [n] EVENT_16 Discrete (bits).
Param Format Access Devices Param Address Line Devices Soak Value for SCHED1_SEG [n] Auxiliary Output AUX_SOAK_3 #3 Floating Point RW UMC800, HC900 Soak Value for SCHED1_SEG [n] Auxiliary Output AUX_SOAK_4 #4 Floating Point RW UMC800, HC900 Soak Value for SCHED1_SEG [n] Auxiliary Output AUX_SOAK_5 #5 Floating Point RW UMC800, HC900 Soak Value for SCHED1_SEG [n] Auxiliary Output AUX_SOAK_6 #6 Floating Point RW UMC800, HC900 Soak Value for SCHED1_SEG [n] Auxiliary Output AUX_SOAK_7 #7 Float
Param Address Line Param Format Access 5 – Device Information Devices Soak Type #2 SCHED2_SEG [n] GUAR2 Discrete (bits). [Status Point Only] RW HC900 Soak Type #3 SCHED2_SEG [n] GUAR3 Discrete (bits). [Status Point Only] RW HC900 Soak Type #4 SCHED2_SEG [n] GUAR4 Discrete (bits). [Status Point Only] RW HC900 Soak Type #5 SCHED2_SEG [n] GUAR5 Discrete (bits). [Status Point Only] RW HC900 Soak Type #6 SCHED2_SEG [n] GUAR6 Discrete (bits).
Param Address Line Param Format Access Devices Devices Event #7 SCHED2_SEG [n] EVENT_07 Discrete (bits). [Status Point Only] RW HC900 Event #8 SCHED2_SEG [n] EVENT_08 Discrete (bits). [Status Point Only] RW HC900 Event #9 SCHED2_SEG [n] EVENT_09 Discrete (bits). [Status Point Only] RW HC900 Event #10 SCHED2_SEG [n] EVENT_10 Discrete (bits). [Status Point Only] RW HC900 Event #11 SCHED2_SEG [n] EVENT_11 Discrete (bits).
Param Address Line Param Format Access 5 – Device Information Output #5 SCHED2_SEG [n] OUTPUT5 Floating Point RW HC900 Output #6 SCHED2_SEG [n] OUTPUT6 Floating Point RW HC900 Output #7 SCHED2_SEG [n] OUTPUT7 Floating Point RW HC900 Output #8 SCHED2_SEG [n] OUTPUT8 Floating Point RW HC900 Soak Value for SCHED2_SEG [n] Auxiliary Output AUX_SOAK_1 #1 Floating Point RW HC900 Soak Value for SCHED2_SEG [n] Auxiliary Output AUX_SOAK_2 #2 Floating Point RW HC900 Soak Value for SCHED2_SEG
Devices Non-numbered Addresses Param Address Line Param Format Access The following table lists the details of the Non-numbered Address parameters. Relay #1 RELAY1 Discrete (bits). [Status Point Only] RO DR4300 Relay #2 RELAY2 Discrete (bits). [Status Point Only] RO DR4300 Alarm Relay #1 ALMRLY1 Discrete (bits). [Status Point Only] RO DR4500 Alarm Relay #2 ALMRLY2 Discrete (bits). [Status Point Only] RO DR4500 Control Relay #1 CR1 Discrete (bits).
Param 100 Param Format Access 5 – Device Information Address Line Devices CONFIG_CLEA CONFIG_CLEAR R Floating Point WO RSX, VPR100, VRX100, VRX180, UDC5300, HC900 LOAD_RECIPE LOAD_RECIPE Floating Point WO UMC800 CHART_SPEE D CHART_SPEED Floating Point RO DR4300, DR4500 Pen #1 High Value PEN1HI Floating Point RO DR4300, DR4500 Pen #1 Low Value PEN1LO Floating Point RO DR4300, DR4500 Number of Chart CHART_DIVS Divisions Floating Point RO DR4500 CHART_STAT US CHART_STATUS Floating
HC900 and UMC800 SPP and Recipe Support 6 Honeywell Universal Modbus Interface Reference 101
6 – HC900 and UMC800 SPP and Recipe Support Overview The HC900 and UMC800 SPP & Recipe Support is an application that enables you to configure and control Set Point (SP) programmers and variables in one or more HC900 and/or UMC800 controllers through Station. The application allows operators to easily configure set point profiles and Variable-based recipes offline, before downloading to a specific controller. Also supported is the monitoring and configuration of running set point programs.
Planning Planning This section describes the planning and design-related issues concerned with configuring HC900 and UMC800 SPP and Recipe Support. After reading this section, you will be able to plan for the configuration process. Resource Requirements This section details the requirements and restrictions for the HC900/UMC800 application. Set Point Profile and Recipe Slots The server database allows you to configure and store up to 1000 SP profiles.
6 – HC900 and UMC800 SPP and Recipe Support Display Locking For safety reasons and data integrity, recipes and SP programmers can only be configured and maintained by one user at a time. Any users who try to access these displays while they are in use are locked out. A message indicating the lockout is displayed, indicating the Station number that is currently using the display. These displays remain locked until the Station either exits the displays or is disconnected.
Planning Recipes No utility exists to transfer existing recipes from an HC900 or a UMC800 controller to the server database of 1000 recipes. Recipes need to be re-created manually in Station.
6 – HC900 and UMC800 SPP and Recipe Support Configuration In this section, you will learn how to configure HC900 and UMC800 recipes, SP profiles, and combined recipes. Configuration requirements for setting up the set point programmer monitoring displays are also presented. Prerequisites Before configuring the HC900/UMC800 SPP and Recipe Support, ensure that you have: • Access to the MNGR operator account in Station. • Fast and Extended history.
Configuration When the Recipe Configuration display opens, the server attempts to read a list of all variables from the currently selected “Compatible” controller. If the controller is not a valid HC900 or UMC800 controller or the upload fails, an alarm is raised. The variable list does not overwrite any of the variables configured in the current recipe, nor do variables in the recipe need to be members of the list.
6 – HC900 and UMC800 SPP and Recipe Support To configure a SP profile, perform the following steps: 1 In Station select Configure > Applications > HC900/UMC800 > Set Point Programs > Profile Setup. The Profile Selection display opens. 2 Select the profile that you want to configure or modify, or click a blank slot to create a new profile. 3 Click the profile name to load its configuration. The Profile Configuration display allows all the details of a SP profile to be edited from a single display.
Configuration is used to control multiple, similar processes. It is up to the user to configure the Variable tag names with the proper suffixes in the controller configuration so that the recipe with values for the Variables with these suffixes can be loaded from the server database. An error is posted if these Variable tag names are not found on download.
6 – HC900 and UMC800 SPP and Recipe Support Controller Each destination has a controller to which each component of the combined recipe is downloaded. Prog A & B These identify the SP programmers in the destination controller to which profiles A and B will be downloaded. Var. Suffix Identifies a short string that will be appended to every variable name in the recipe component of a combined recipe before it is downloaded.
Configuration The SPP Trend display allows the user to view the history of a SP programmer and compare it to the ideal profile. To collect history, a point needs to be built for each SP programmer in a controller. These points are used to monitor the process PVs driven by the primary and auxiliary outputs of the programmers, collecting the values and storing them in history. Building Points for SPP Monitoring Quick Builder can be used to build the points for monitoring the SP programmers.
6 – HC900 and UMC800 SPP and Recipe Support The following diagram illustrates a typical HC900/UMC800 configuration. In this example, when configuring a point in Station to track programmer block SPP3, you should configure the point’s PV parameter to read the PV of loop PID2, and it’s A1 parameter to read the calculated PV from CARB5.
Operation Operation This section describes how to use the HC900/UMC800 SPP & Recipe Support on a routine basis. Standard tasks include downloading recipes and SP profiles, and issuing commands to the SP programmers. After reading this section, you will be able to control HC900 and UMC800 controllers from Station. Prerequisites It is assumed that you have successfully completed the configuration procedure detailed in the previous section and that all prerequisites have been met.
6 – HC900 and UMC800 SPP and Recipe Support 6 Click Download to accept the recipe destination or Cancel to remove the dialog box. The message “Downloading recipe…” appears. If successful, the message “Recipe download complete.” appears. Otherwise “Recipe download failed.” is displayed and an alarm is raised. See the section “Troubleshooting” on page 117 for possible fail reasons.
Operation To download a combined recipe: 1 In Station select Configure > Applications > HC900/UMC800 > Combined Recipes. The Combined Recipe Selection display opens. 2 Click the combined recipe that you want to configure or modify, or click a blank slot to create a new combined recipe. 3 Click on the combined recipe name to load its configuration. 4 Click the Download button to download the combined recipe. Select a controller destination and click on its “Download” button.
6 – HC900 and UMC800 SPP and Recipe Support 5 A confirmation dialog box appears. Click Ok to accept the action or Cancel to remove the dialog box. If the command is successful, the message “Command sent.” appears and the SP programmer status changes to reflect the command. Otherwise “Failed to send command.” appears. See the section “Troubleshooting” on page 117 for possible fail reasons. While the program is running, the present segment number is highlighted and the segment and elapsed timers are active.
Troubleshooting Troubleshooting This section describes cross-checks and remedies to perform if HC900/UMC800 SPP & Recipe Support does not respond as anticipated. Behavior Things to try or confirm Cannot use Station to control an Ensure that the application has been installed HC900 or UMC800. The correctly and that all prerequisites have been met. commands appear to have no effect. Make sure the UMC800SP.EXE task is running. Check that Station R1.1, Build 1358 or later is installed.
6 – HC900 and UMC800 SPP and Recipe Support Behavior Things to try or confirm The trend does not display the Check that a point has been built and specified for program history or the ideal profile. the SP programmer. Ensure that HC900 and UMC800 channel(s) are enabled and the point has “Scanning and Control enabled” set. Ensure you are licensed for Fast and Extended history collection. Check that the point parameters have been configured properly and are collecting history.
Index A D Address Named 28 Non-named 32 architecture 10 data formats 33 documentation for Universal Modbus 6 B formats, data 33 Black Box Connections 11 H C HC900 recipes 106 Channel Write Delay 20 channel definition 18 combined recipes, configuring 108 configuration wizard 8 configuring Universal Modbus, steps for 5 connecting controllers to Universal Modbus 10 controller definition 24 L F location syntax 28 P Port tab 20 R recipes configuring 106 downloading 113 RS-232 10 RS-485 13 S scann
Index set point programs 110 SPP monitoring 110 Stallion 13 U UMC800 recipes 106 W wizard, configuration 8 120