Orion System RNE Modular Controller - Manual (Page 49)

RNE Modular Controller Field Technical Guide
START-UP & COMMISSIONING
49
WARNING: Observe Polarity! All boards must be wired
with GND-to-GND and 24 VAC-to-24 VAC. Failure to ob-
serve polarity will result in damage to one or more of the
boards. Expansion modules must be wired in such a way that
the Expansion modules and the RNE Controller are always
powered together. Loss of power to the Expansion module
will cause it to become inoperative until power is restored
to the Expansion module.
Check all wiring leads at the terminal block for tightness. Be sure that
wire strands do not stick out and touch adjacent terminals. Confi rm
that all sensors required for your system are mounted in the appropriate
location and wired into the correct terminals on the RNE Controller. Be
sure any expansion modules connected to the RNE Controller are also
correctly wired just as you did for the RNE Controller.
After all the above wiring checks are complete, apply power to the RNE
Controller and all expansion modules connected to it.
Initialization
On system power up, a 30-second startup delay is performed where all
default setpoints are initialized, LED’s are initialized, and all outputs
are turned off.
When power is fi rst applied, LED1 and LED2 will fl ash out the controller
address. LED1 will fl ash to represent the tens position. LED2 will fl ash
to represent the ones position. After the controller address is complete,
there will be a short pause and then 60 fast fl ashes to represent controller
initialization. There will be no controller operation or communications
during initialization. After initialization, LED1 and LED2 will continu-
ously fl ash the status code.
Example of a controller address of 59:
LED1 will fl ash 5 times. LED2 will fl ash 9 times.
See Table 3 on page 71 in the RNE Controller Troubleshooting section
of this manual for detailed diagnostic blink code information.
Operating Summary
There is a standard set of operating instructions that are continuously
repeated during normal operations. They are listed below.
1. Read Analog Inputs for Temperatures, Pressures, and
Binary Contact Closures.
2. Calculate Occupied/Unoccupied Mode of Operation.
3. Calculate HVAC Mode of Operation.
4. Set all outputs to match calculations for Heating or Cooling
or
Vent Mode.
5. Broadcast information to other controllers if confi gured.
6. Log all temperatures and output conditions.
7. Repeat steps 1 through 6 continuously.
Programming the Controller
The next step is programming the controller for your specifi c require-
ments. In order to confi gure and program the RNE Controller, you must
use an operator interface. Four different operator interfaces are avail-
able for programming and monitoring of the RNE Controller These are
depicted in Figure 39 and are as follows:
• Modular Service Tool SD and Modular System
Manager SD
•
System Manager TS II
• Computer with Prism 2 Software Installed and
the CommLink 5 Communications Interface
Any of these devices or a combination of them can be used to access
the status, confi guration, and setpoints of any controller on your com-
munications loop.
If using the Modular Service Tool SD, Modular System Manager SD, or
System Manager Touch Screen II with your system, refer to the VCM-X
/ RNE Controller Operator Interfaces SD Technical Guide or System
Manager TS II Technical Guide for programming instructions.
If using a computer and the Prism 2 Software, refer to the Prism 2
Technical Guide.
No matter which operator interface you use, we recommend that you
proceed with the programming and setup of the RNE Controller in the
order that follows:
1. Confi gure the Controller for your application.
2. Program the Controller setpoints.
3. Program the Controller operation schedules.
4. Set the Controller current time and date.
5. Review Controller status screens to verify system
operation and correct Controller confi guration.
Programming the Controller
Figure 39: Modular Service Tool SD, Modular
System Manager SD, System Manager TS II, and
Prism 2 Graphical Software Operator Interfaces
ENTER
CLEAR ESC
PREV NEXT
DOWN
UP
6 5 4
DEC
7
0
8
1 3 2
9
MINUS
-
STATUS
SETPOINTS
SCHEDULES
ALARMS
OVERRIDES
System Manager