EC-FCU-L;EC-HPU-L;EC-RTU-L;EC-UV-L
Secondary Control Units
EC-FCU-L, EC-HPU-L, EC-RTU-L, EC-UV-L,
Date Last Saved: 5/27/2005 8:49:34 AM
Product Name(s):
|
EC-FCU-L;EC-HPU-L;EC-RTU-L;EC-UV-L
|
Product Description:
|
The Easycontrols EC-FCU-L, EC-HPU-L, EC-RTU-L, EC-UV-L controllers use the LonWorks communication protocol and are LonMark certified using the following profile:
-#8080 unit ventilator (EC-UV-L)
-#8020 fan coil (EC-FCU-L)
-#8051 heat pump (EC-HPU-L)
-#8030 roof top (EC-RTU-L)
These controllers can be configured through any LNS compliant software.
|
Product Application(s):
|
The EC-FCU-L is designed to meet the requirements of two and four pipe heating and cooling fan coil units with different stages of heating/cooling.
The EC-RTU-L is designed to meet the requirements of a rooftop unit application with or without an economizer. Including mechanical stages, modualting valves, and floating outputs. Can control up to 4 stages of heating/cooling.
The EC-HPU-L is designed to work with all types of heat pump, including dual mode and water to refrigerant heat pumps.
The EC-UV-L is designed for unit ventilator applications.
|
|
Point Quantity
|
Characteristics
|
Analog Input (AI):
|
N.A.
|
|
Digital Input (DI):
|
N.A.
|
|
Universal Input (AI or DI):
|
6
|
Dry Contact Thermistor 0-10 VDC 4-20 ma
|
Analog Output (AO):
|
2
|
0-10 VDC (linear) 0-12 VDC (pwm or digital)
|
Digital Output (DO):
|
5
|
Triac (24 VAC @ 1 Amp)
|
Universal Output (UO):
|
|
|
Other:
|
|
|
Control Unit Model #: | AI | DI | UI | DO | AO | UO | Other |
EC-FCU-L
|
|
|
6
|
5
|
2
|
|
|
EC-HPU-L
|
|
|
6
|
5
|
2
|
|
|
EC-RTU-L
|
|
|
6
|
5
|
2
|
|
|
EC-UV-L
|
|
|
6
|
5
|
2
|
|
|
|
A/D Converter Resolution
|
|
D/A Converter Resolution
|
|
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
|
|
Indicating status LED on each output?
|
|
Integral Flow Sensor?
|
N.A.
|
Integral Damper Actuator?
|
N.A.
|
Can controller accept occupant override from thermostat?
|
N.A.
|
Can controller accept occupancy sensor input?
|
N.A.
|
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
|
(1) LonTalk TP/FT-10
|
External Communication Ports, Speeds and Access Devices
|
Information not provided
|
Additional Information (Optional)
|
|
Network Accessing Capabilities via Controller
|
|
Controller Access Devices
|
|
Zone-Based Interface Access
|
None. But see the EC-Display V-2 Product detail. (Can interface with up to 250 variables)
|
Zone Interface Hardware
|
|
*Note: This section covers the capabilities for accessing the controller or other parts of the network from the controller (i.e.
'bottom-up').
Standard access functionality is covered in the Architecture and Software sections.
**Does NOT include front-end OI functions. See vendor for specific functions available.
|
Microprocessor(s)
|
Neuron 3150 @ 10 Mhz
|
Clock Type
|
|
Clock Synchronization
|
N.A.
|
Volatile Memory (RAM) Capacity
|
8k bytes
|
Volatile Memory (RAM) Uses
|
|
|
Is Volatile Memory Supported By Battery?
|
N.A.
|
Battery Type(s)
|
N.A.
|
Battery Life
|
N.A.
|
Backup Battery Operating Time
|
N.A.
|
Non-Volatile Memory Capacity (EEPROM/Flash)*
|
64K (application)
|
Non-Volatile Memory Uses
|
|
Additional Information
|
|
* Items in NV memory are not lost upon power or battery failure. Other types of NV memory such as EPROM, NOVROM, etc. do not directly
impact system performance.
|
Can trend data be stored in this controller?
|
No
|
How many total trend values can be stored?
|
N.A.
|
What is the controllers role in trending?
|
N.A.
|
Can controller be programmed to 'push' data to archive or are trends 'pulled' from controller?
|
|
When full, does controller automatically send up trend data, overwrite data, or stop logging data?
|
N.A.
|
Programming Method(s)
|
Through an LNS plug-in.
|
Resident vs Non-Resident Program Execution
|
Information not provided
|
Scheduling
|
|
Resident Energy Management
|
|
Specific Pre-Programmed Algorithms Available
|
|
Additional Programming Functions
|
|
DDC Loops (P, PI, PID)
|
PID
|
Automatic PID Tuning Feature
|
no
|
Automatical-Dial Alarm Support
|
No alarms
|
Does controller perform multiple retries and buffer/store alarm until connection is made?
|
No alarms
|
Are multiple destinations possible?
|
No alarms
|
Upon controller power loss or hardware failure:
|
Are network communications affected?
|
Information not provided
|
Is loss recognized on/by the network and alarm reported?
|
Information not provided
|
DO and AO response?
|
|
Volatile memory functions?
|
|
Upon restoration of power does the controller:
|
Auto-reboot without operator intervention?
|
Yes
|
Automatically reset/synchronize the clock?
|
N.A.
|
Update all monitored functions?
|
Yes
|
Generate an alarm if backup battery is dead?
|
N.A.
|
Upon network or communications failure does controller:
|
Continue to operate standalone?
|
Yes
|
Operate with last global settings or user-specified value?
|
N.A.
|
Do broken network segments continue to communicate within the remaining segment?
(Note: May depend on proper termination of segments for higher speed networks.)
|
No
|
Does network automatically reconfigure upon restoration?
|
Information not provided
|
Does network store 'loss of communications' alarm with time of event?
|
Information not provided
|
Additional Information (optional)
|
|
Self Test Diagnostics
Does controller have internal self-test diagnostics to check:
|
Processor failure?
|
Information not provided
|
Internal hardware failure?
|
Information not provided
|
Open/shortened sensor?
|
Information not provided
|
Others?
|
|
|
Control Enclosure
|
Metal 18 awg
|
Power Supply Required
|
|
Voltage
|
24 VAC +/- 15%, 50/60 Hz or 24 VDC
|
VA
|
10 VA
|
Surge Protection
|
1.35 Auto-Reset Fuse
|
Underwriters Laboratories
|
Yes
|
FCC
|
Yes
|
CE
|
No pending October 2004
|
LonMark Certified
|
|
BACnet (BTL) Certified
|
|
Other
|
|