Honeywell Universal Modbus InterfaceReference
2 – Universal Modbus Controller Setup10 Connecting your ControllerMany different types of controllers can be connected to the same Universal Modbus n
5 – Device Information100 CONFIG_CLEARCONFIG_CLEAR Floating Point WO RSX, VPR100, VRX100, VRX180, UDC5300, HC900LOAD_RECIPE LOAD_RECIPE Floating Poin
Honeywell Universal Modbus Interface Reference 1016HC900 and UMC800 SPP and Recipe Support
6 – HC900 and UMC800 SPP and Recipe Support102 OverviewThe HC900 and UMC800 SPP & Recipe Support is an application that enables you to configure
Planning Honeywell Universal Modbus Interface Reference 103PlanningThis section describes the planning and design-related issues concerned with confi
6 – HC900 and UMC800 SPP and Recipe Support104 Display LockingFor safety reasons and data integrity, recipes and SP programmers can only be configure
Planning Honeywell Universal Modbus Interface Reference 105RecipesNo utility exists to transfer existing recipes from an HC900 or a UMC800 controller
6 – HC900 and UMC800 SPP and Recipe Support106 ConfigurationIn this section, you will learn how to configure HC900 and UMC800 recipes, SP profiles, a
Configuration Honeywell Universal Modbus Interface Reference 107When the Recipe Configuration display opens, the server attempts to read a list of al
6 – HC900 and UMC800 SPP and Recipe Support108 To configure a SP profile, perform the following steps:1 In Station select Configure > Applications
Configuration Honeywell Universal Modbus Interface Reference 109is used to control multiple, similar processes. It is up to the user to configure the
Connecting your Controller Honeywell Universal Modbus Interface Reference 11Using an RS-232/485 ConverterHoneywell recommends that you use the Black
6 – HC900 and UMC800 SPP and Recipe Support110 ControllerEach destination has a controller to which each component of the combined recipe is download
Configuration Honeywell Universal Modbus Interface Reference 111The SPP Trend display allows the user to view the history of a SP programmer and comp
6 – HC900 and UMC800 SPP and Recipe Support112 The following diagram illustrates a typical HC900/UMC800 configuration. In this example, when configur
Operation Honeywell Universal Modbus Interface Reference 113OperationThis section describes how to use the HC900/UMC800 SPP & Recipe Support on a
6 – HC900 and UMC800 SPP and Recipe Support114 6 Click Download to accept the recipe destination or Cancel to remove the dialog box. The message “Dow
Operation Honeywell Universal Modbus Interface Reference 115To download a combined recipe:1 In Station select Configure > Applications > HC900/
6 – HC900 and UMC800 SPP and Recipe Support116 5 A confirmation dialog box appears. Click Ok to accept the action or Cancel to remove the dialog box.
Troubleshooting Honeywell Universal Modbus Interface Reference 117TroubleshootingThis section describes cross-checks and remedies to perform if HC900
6 – HC900 and UMC800 SPP and Recipe Support118 The trend does not display the program history or the ideal profile.Check that a point has been built
Honeywell Universal Modbus Interface Reference 119IndexAAddressNamed28Non-named 32architecture 10BBlack Box Connections 11CChannelWrite Delay20chann
2 – Universal Modbus Controller Setup12 Ensure that the black box switches are configured with the following settings.Figure 3 Black Box (4-wire) Con
120 Indexset point programs 110SPP monitoring 110Stallion 13UUMC800 recipes 106Wwizard, configuration 8
Connecting your Controller Honeywell Universal Modbus Interface Reference 13Using an RS-485 AdapterHoneywell recommends using the Stallion EasyConnec
2 – Universal Modbus Controller Setup14 Universal Modbus TCP ConnectionTo connect controllers to the server communicating using the UModbus TCP proto
Connecting your Controller Honeywell Universal Modbus Interface Reference 15Redundant Communication ArchitectureIf you require redundant communicatio
2 – Universal Modbus Controller Setup16 Configuring Communication ParametersRS485 DevicesBefore using your Control Products controllers, ensure that
Honeywell Universal Modbus Interface Reference 173Universal Modbus Controller Configuration and AddressingThis chapter describes how to configure a
3 – Universal Modbus Controller Configuration and Addressing18 Defining a Universal Modbus ChannelBuild a channel for each RS-485, RS-232 or Ethernet
Defining a Universal Modbus Channel Honeywell Universal Modbus Interface Reference 19Marginal Alarm Limit The communications alarm marginal limit at
2NoticeThis document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no
3 – Universal Modbus Controller Configuration and Addressing20 Channel Write Delay SettingsSerial devices using the RS-485 protocol require a minimum
Defining a Universal Modbus Channel Honeywell Universal Modbus Interface Reference 21Serial Port PropertiesNoteThe Serial Port settings must match th
3 – Universal Modbus Controller Configuration and Addressing22 TerminalServer Port PropertiesHandshaking Options RS-232• Enable RTS/CTS flow control.
Defining a Universal Modbus Channel Honeywell Universal Modbus Interface Reference 23Redundant Port PropertiesA communication port used as a redundan
3 – Universal Modbus Controller Configuration and Addressing24 Defining a Universal Modbus ControllerYou need to define a controller to describe each
Defining a Universal Modbus Controller Honeywell Universal Modbus Interface Reference 25Marginal Alarm Limit The communications alarm marginal limit
3 – Universal Modbus Controller Configuration and Addressing26 Available Device TypesUsing OffsetsThe server can only access a maximum of 4096 record
Defining a Universal Modbus Controller Honeywell Universal Modbus Interface Reference 27Parameter Category OFFSET Address for ControllerUMC800 HC900
3 – Universal Modbus Controller Configuration and Addressing28 Defining a Universal Modbus Address for a Point Parameter ValueDifferent addresses are
Defining a Universal Modbus Address for a Point Parameter Value Honeywell Universal Modbus Interface Reference 29For addresses that occur in only one
Honeywell Universal Modbus Interface Reference 3Contents1 Getting StartedSupport and Documentation for Universal Modbus . . . . . . . . . . . . . .
3 – Universal Modbus Controller Configuration and Addressing30 Loop Tuning constants (possible AUX parameters for a loop point):Digital Output values
Defining a Universal Modbus Address for a Point Parameter Value Honeywell Universal Modbus Interface Reference 31“Digital” Signal Tag Example:“Digita
3 – Universal Modbus Controller Configuration and Addressing32 Location Syntax for Non-named AddressesAddresses without names can be addressed direct
Defining a Universal Modbus Address for a Point Parameter Value Honeywell Universal Modbus Interface Reference 33Data FormatsThe data format tells th
3 – Universal Modbus Controller Configuration and Addressing34 Troubleshooting Point ConfigurationErrors when point building84E0hInvalid address for
Optimizing Scanning Performance Honeywell Universal Modbus Interface Reference 35Optimizing Scanning PerformanceThe maximum amount of data that can b
3 – Universal Modbus Controller Configuration and Addressing36
Honeywell Universal Modbus Interface Reference 374Server and Station Tasks for Universal ModbusThis chapter describes tasks for the Universal Modbus
4 – Server and Station Tasks for Universal Modbus38 Testing Communications with the ServerUse the test utility umbtst to test the communications.Befo
Testing Communications with the Server Honeywell Universal Modbus Interface Reference 39qIf you do not know the device name of your channel, select V
Contents4 Non-numbered Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996 HC900 and UMC80
4 – Server and Station Tasks for Universal Modbus40 Troubleshooting Universal Modbus Configuration ErrorsCommon ProblemsError message/problem Explana
Troubleshooting Universal Modbus Configuration Errors Honeywell Universal Modbus Interface Reference 41Problems with Specific Controller ModelsUDC330
4 – Server and Station Tasks for Universal Modbus42 The address PID n PV doesn’t download.The PID part of the address is not valid and doesn’t appear
Troubleshooting Universal Modbus Configuration Errors Honeywell Universal Modbus Interface Reference 43HC900 Problems You see the error:***** PNTBLD
4 – Server and Station Tasks for Universal Modbus44 For analog inputs in the first rack, you know that you should use the address AI n but you don’t
Troubleshooting Universal Modbus Configuration Errors Honeywell Universal Modbus Interface Reference 45For analog inputs in the first rack, you know
4 – Server and Station Tasks for Universal Modbus46 You want to write to a digital output. Honeywell recommends against writing to a digital output s
Troubleshooting Universal Modbus Configuration Errors Honeywell Universal Modbus Interface Reference 47You want to know which HC900 Signal Tags or Va
4 – Server and Station Tasks for Universal Modbus48
Honeywell Universal Modbus Interface Reference 495Device InformationThis chapter lists numbered and non-numbered addresses, their parameter details
Honeywell Universal Modbus Interface Reference 51Getting StartedThis reference describes how to set up, configure, and test Universal Modbus control
5 – Device Information50 For information about non-numbered addresses, see “Non-numbered Addresses” on page 99.Alarm Status Com page 70Alarm Status D
Devices Honeywell Universal Modbus Interface Reference 51DevicesBaud Rates SupportedThe following table lists the devices and their supported baud ra
5 – Device Information52 The following table lists the details of the PID Loop parameters.VRX100 LOOP [n] [param] [n] = 1 to 2VRX180 LOOP [n] [para
Devices Honeywell Universal Modbus Interface Reference 53Prop Band #1 LOOP [n] PROP1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300,
5 – Device Information54 Alarm #1 SP #2 LOOP [n] AL1SP2 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC
Devices Honeywell Universal Modbus Interface Reference 55Local Set Point #1LOOP [n] LSP1 Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR43
5 – Device Information56 OP High Limit LOOP [n] OPHIGH Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, DR4300, DR4500, UDC2300, UDC3300, UMC8
Devices Honeywell Universal Modbus Interface Reference 57Remote / Local Set Point StateLOOP [n] RSP_STATEDiscrete (bits). [Status Point Only]Bit 0, 0
5 – Device Information58 Remote Set Point (RSP)LOOP [n] RSP Floating Point RW RSX, VPR100, VRX100, VRX180, UDC5300, UMC800, HC900Set Point #2 LOOP [n
Devices Honeywell Universal Modbus Interface Reference 59Set Point State LOOP [n] SP_STATE Discrete (bits). [Status Point Only]Bit 0, 0 = SP1, 1 = SP
1 – Getting Started6 Support and Documentation for Universal ModbusAbout the Universal Modbus InterfaceThe Universal Modbus Interface enables the ser
5 – Device Information60 Analog InputThe following table lists the devices which support Analog Inputs and their formats.On/Off Output HysteresisLOOP
Devices Honeywell Universal Modbus Interface Reference 61The following table lists the details of the Analog Input parameters.Tagged SignalThe follow
5 – Device Information62 The following table lists the details of the Tagged Signal parameters.Communication or Constant Value GroupThe following tab
Devices Honeywell Universal Modbus Interface Reference 63Math, Variable or Calculated Value GroupThe following table lists the devices which support
5 – Device Information64 Totalizer Value GroupThe following table lists the devices which support the Totalizer Value group and their formats.The fol
Devices Honeywell Universal Modbus Interface Reference 65The following table lists the details of the Alarm Set Point Value Group parameters.Alarm Se
5 – Device Information66 The following table lists the details of the Math or Calculated Value Status parameters.Totalizer Value StatusThe following
Devices Honeywell Universal Modbus Interface Reference 67The following table lists the details of the Totalizer Value Status parameters.Alarm StatusT
5 – Device Information68 Alarm Status AnalogThe following table lists the devices which support the Alarm Status Analog and their formats.The followi
Devices Honeywell Universal Modbus Interface Reference 69Alarm Status EventThe following table lists the devices which support the Math or Calculated
Support and Documentation for Universal Modbus Honeywell Universal Modbus Interface Reference 7UDC3300 51-52-25-7051-52-25-38 UDC3000 A Modbus 485 RT
5 – Device Information70 Alarm Status ComThe following table lists the devices which support the Alarm Status Com and their formats.The following tab
Devices Honeywell Universal Modbus Interface Reference 71Digital Input TableThe following table lists the devices which support the Digital Input Tab
5 – Device Information72 The following table lists the details of the Digital Input Table parameters.Digital Output TableThe following table lists th
Devices Honeywell Universal Modbus Interface Reference 73Digital Output TableThe following table lists the devices which support the Digital Output T
5 – Device Information74 The following table lists the details of the set point program parameters.HC900 SPP [n] [param] [n] = 1 to 4Device Suppor
Devices Honeywell Universal Modbus Interface Reference 75Set Point Programmer Status - HoldSPP [n] STATUS_HOLDDiscrete (bits). [Status Point Only]RO
5 – Device Information76 Set Point Programmer Current Segment NumberSPP [n] SEG_NO Floating Point RW UMC800, HC900Set Point Programmer Status - Type
Devices Honeywell Universal Modbus Interface Reference 77Set Point Programmer Segment Event #7SPP [n] EV07 Discrete (bits). [Status Point Only]RO VPR
5 – Device Information78 Set Point Program Additional ValuesThe following table lists the devices which support the Set Point Program Additional Valu
Devices Honeywell Universal Modbus Interface Reference 79Set Point Programmer #1 Profile SegmentThe following table lists the devices which support t
1 – Getting Started8 Control Products WizardThe Control Products wizard makes it easy to configure a controller and its associated points. The wizard
5 – Device Information80 Event #1 SPP1_SEG [n] EV01 Discrete (bits). [Status Point Only]RW UMC800, HC900Event #2 SPP1_SEG [n] EV02 Discrete (bits). [
Devices Honeywell Universal Modbus Interface Reference 81Set Point Programmer #2 Profile SegmentThe following table lists the devices which support t
5 – Device Information82 The following table lists the details of the Set Point Program #2 Profile Segment parameters.UDC5300 SPP2_SEG [n] [param]
Devices Honeywell Universal Modbus Interface Reference 83Event #8 SPP2_SEG [n] EV08 Discrete (bits). [Status Point Only]RW UMC800, HC900Event #9 SPP2
5 – Device Information84 Set Point Programmer #3 Profile SegmentThe following table lists the devices which support the Set Point Programmer #3 Profi
Devices Honeywell Universal Modbus Interface Reference 85Event #3 SPP3_SEG [n] EV03 Discrete (bits). [Status Point Only]RW UMC800, HC900Event #4 SPP3
5 – Device Information86 Set Point Programmer #4 Profile SegmentThe following table lists the devices which support the Set Point Programmer #4 Profi
Devices Honeywell Universal Modbus Interface Reference 87The following table lists the details of the Set Point Program #4 Profile Segment parameters
5 – Device Information88 Set Point Scheduler ValuesThe following table lists the devices which support the Set Point Scheduler Values and their forma
Devices Honeywell Universal Modbus Interface Reference 89The following table lists the details of the Scheduler Values parameters.HC900 SCHED [n] [pa
Honeywell Universal Modbus Interface Reference 92Universal Modbus Controller SetupThis chapter describes how to set up an Universal Modbus controlle
5 – Device Information90 Current Program NumberSCHED [n] PROG_NOFloating Point RW UMC800, HC900Current Segment NumberSCHED [n] SEG_NO Floating Point
Devices Honeywell Universal Modbus Interface Reference 91Event #5 SCHED [n] EVENT_05Discrete (bits). [Status Point Only]RO UMC800, HC900Event #6 SCHE
5 – Device Information92 Set Point Scheduler #1 SegmentThe following table lists the devices which support the Scheduler #1 Segment and their formats
Devices Honeywell Universal Modbus Interface Reference 93Soak Type #7 SCHED1_SEG [n] GUAR7Discrete (bits). [Status Point Only]RW UMC800, HC900Soak Ty
5 – Device Information94 Event #12 SCHED1_SEG [n] EVENT_12Discrete (bits). [Status Point Only]RW UMC800, HC900Event #13 SCHED1_SEG [n] EVENT_13Discre
Devices Honeywell Universal Modbus Interface Reference 95Set Point Scheduler #2 SegmentThe following table lists the devices which support the Schedu
5 – Device Information96 Soak Type #2 SCHED2_SEG [n] GUAR2Discrete (bits). [Status Point Only]RW HC900Soak Type #3 SCHED2_SEG [n] GUAR3Discrete (bits
Devices Honeywell Universal Modbus Interface Reference 97Event #7 SCHED2_SEG [n] EVENT_07Discrete (bits). [Status Point Only]RW HC900Event #8 SCHED2_
5 – Device Information98 Output #5 SCHED2_SEG [n] OUTPUT5Floating Point RW HC900Output #6 SCHED2_SEG [n] OUTPUT6Floating Point RW HC900Output #7 SCHE
Devices Honeywell Universal Modbus Interface Reference 99Non-numbered AddressesThe following table lists the details of the Non-numbered Address para
Kommentare zu diesen Handbüchern