Orion-M
CONFIGURING THE UDC2500/3200 CONTROLLER
FDC Orion-M
3.1
3 Configuring the Honeywell UDC2500/3200 Controller
The unique and inherently flexible design of the Orion-M system allows the OEM to tailor each component of
the system to the application. By using independent loop controls, each one can be configured for various
input and output types, control algorithms, etc., based on the requirements of the application. It also allows
control loops to be added or replaced on the system at any time, simply by connecting the controller to the
Orion-M’s control module, RS-485 communication link.
If the application requirements change and a different input or output type is required, or if the controller were
to fail, it can be replaced quickly, and at a lower cost as compared to having to repair or replace larger,
integrated multi-loop controllers. The Orion-M only requires that the communications settings for each loop
control be properly assigned, and that the input type of the controller is set in the Orion-M Configurator, so
that the control loop input and set point can be displayed and set properly through the Orion-M interface.
3.1 Assigning the Proper Communications Settings
The Orion-M can support up to 15 UDC2500 and/or UDC3200 controls. They can be mixed and matched as
required, but each one must have its own communication address. The allowable address range is 1 – 15
corresponding to Loop Input #1 – 15 in the Orion-M Configurator. Communication addresses must be
assigned to all controllers on the communications link beginning with 1, up to the total number of controllers.
As control loops are enabled in the Orion-M Configurator, the Orion-M will automatically use the Loop Input #
as the corresponding controller address. If more than one UDC controller has the same address, or a loop
input is enabled but a controller is not assigned to that address, the Orion-M will report a communications
alarm for that loop input when the runtime application is started.
NOTE:
The order of the loop controls on the communication link is not important. The communications
address for a controller can be assigned regardless of its position on the link.
In addition to the communications address, the baud rate, floating point format, shed enable and computer set
point options must also be set to match the control module of the Orion-M. The Orion-M uses a default
communication rate of 9600 baud, 8 data bits, 1 stop bit and no parity, which are typical settings for Modbus
RTU communications and compatible with the UDC2500/3200 controller.
*
Required UDC2500/3200 Communications Group Settings:
•
Communications station address (ComADR): 1-15
(based on system design)
•
Communications selection (COMSTA):
MODBUS
•
Infrared communications (IRENAB):
DIS
(recommended but not required)
•
Baud rate (BAUD):
9600
•
Transmit delay (TX DLY):
1
•
Floating point data format (WS FLT):
FP B
•
Shed enab le (SDENAB):
ENAB
•
Shed time (SHDTIM) :
60
(recommended – minimum of 30 seconds)
•
Shed mode (SDMODE):
LAST
•
Shed set point (SHD SP):
CSP
•
UNITS:
EGR
•
Computer set point ratio (CSP RATIO):
1
•
Computer set point b ias (CSP BIAS);
0
*
See section 3 Configuration, in the Honeywell UDC2500/3200 Product Manual for instructions on
accessing the control’s configuration menus and setting the above parameters as required.
Summary of Contents for Orion-M
Page 4: ......