DDC Online direct digital controls
Solidyne - IZAC Control and Monitoring System  [Archived]

Intelligent Zone Automation Controller (IZAC);Clipper Zone Automation Controller (CLIPZAC)

Secondary Control Units
IZAC-4, IZAC-8, and CLIPZAC
Date Last Saved: 12/19/2003 8:58:36 AM

Product Name(s): Intelligent Zone Automation Controller (IZAC);Clipper Zone Automation Controller (CLIPZAC)
Product Description: The IZAC-4 is a 9-point application specific controller. The IZAC-8 and CLIPZAC are 17-point general purpose controllers. The following specs are specifically for the IZAC controllers although the CLIPZAC is very similar to the IZAC.
Product Application(s): These controllers can be used for control of air-handling units, roof top units, chillers, boilers, lighting, and any other controllable load.
Point Quantity Characteristics
Analog Input (AI):
Digital Input (DI):
Universal Input (AI or DI): See below 4-20 mA
0-10 Vdc
thermistor or variable resistance
dry contact
pulse (resolution: 1 pulse/second)**
Analog Output (AO): 1 0-10 Vdc
Digital Output (DO): See below IZAC-4 Form A or B @ 24Vac/3Amp
IZAC-8 Form A @ 24Vac / 3 Amp
IZAC-8 has 1 DO that is jumper selectable as Form A or Form B
Universal Output (UO):
Other:
Control Unit Model #:AIDIUIDOAOUOOther
IZAC-4 4 4 1
IZAC-8 8 8 1
CLIPZAC 8 8 1
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit
Other +0.07% accuracy (approx. 10 bit)
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
Other + 1.0% accuracy (approx. 6 bit)
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
No
Both AO and DO
DO Only
Other
Indicating status LED on each output?
No
AO and DO indicates 'energized' status of outputs
AO Only
DO Only
Other
Integral Flow Sensor?
Integral Damper Actuator?
Can controller accept occupant override from thermostat?
Can controller accept occupancy sensor input?
Expander Boards AO-4 is a 0-10 Vdc expansion module for the IZAC-4 or IZAC-8.
Expansion Device Model #AIDIUIDOAOUOOther
AO-4 4
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary port to proprietary IZAC controller network
External Communication Ports, Speeds and Access Devices (1) - Port for interface to a local display panel (zone-mounted) or to a zone thermostat (with communication interface access port at this thermostat)
Additional Information (Optional)
Network Accessing Capabilities via Controller
Access controller only
Access controller plus additional controllers on network segment / LAN
Access all controllers on system
No access available on this controller
Other
Controller Access Devices
Laptop/PC
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Other
Zone-Based Interface Access local display panel (zone-mounted) permits keypad access to certain controller settings and configuration parameters as part of system set-up/commissioning and can display input/output status of up to 32 controllers on the secondary network.

A laptop/PC can also be used to interface with the controller through a jack at the zone thermostat (Requires M204 interface box/converter).
Zone Interface Hardware
Zone-Mounted touchpad (thermostat or stand-alone display)
HID (proprietary device)
PDA (3rd party HID, with software)
Laptop/PC
none
Other
*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.
Functions Available Through Field Interface**:View ParamsChange ParamsChange
Programs/Logic
O&M SupportTAB/Cx Support
Laptop/PC
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Other
Microprocessor(s) 8/16 bit Motorola
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
None
Other
Clock Synchronization Synched up by OWS during initial set-up/installation
Volatile Memory (RAM) Capacity 2 kB
Volatile Memory (RAM) Uses
RAM use unrestricted
RAM use restricted as shown below
Information Not Provided
Program Execution / Calculation storage
Data / Trends / Alarms storage
Configuration / Parameter storage
Control Programming storage
Others Alarms stored in M-202A or I3 Device
Is Volatile Memory Supported By Battery? Yes
Battery Type(s) Lithium battery
Battery Life 10 years
Backup Battery Operating Time Information not available
Non-Volatile Memory Capacity (EEPROM/Flash)* EEPROM only stores node-addressing information. It's size is not applicable because the execution program is stored in RAM and the controller is otherwise application specific
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
Control Programming Storage
Controller Operating System
Other Node Addressing information
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? Yes
How many total trend values can be stored? AI's:
15 minute average for past 2 days (720 values)

Daily peak (high or low) for past 35 days

AO's (0-10 Vdc or PWM):
15 minute average for past 2 days (720 values)

DO's:
Cumulative 'On' time (hours and minutes)

Override time (hours and minutes)
What is the controllers role in trending? Trend data is pulled from controller
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? Old data is overwritten
Programming Method(s) Template (question/answer) based programming is the primary programming method although (up to 8) virtual points can be programmed to perform logical and math operations using line code programming
Resident vs Non-Resident Program Execution All program execution is resident in the controller although some labels such as sensor ID, name, alarm text, alarm destination, etc. are resident in the OWS
Scheduling
Resident/Supervisory. This controller supervises the scheduling of other controllers.
Resident/Stand Alone. This controller contains its own schedule.
Non-Resident. This controller is dependent upon another controller for its schedule.
None. This controller has no scheduling features.
Other
Resident Energy Management
Energy management algorithms for this controller can be custom programmed
Pre-programmed/built-in algorithms available, and are fully editable using custom programming
Pre-Programmed/built-in with limited editing via template-based programming
Controller is not typically used for energy management functions
Others
Specific Pre-Programmed Algorithms Available
None (custom programming only)
None (not applicable)
Optimal Start/Optimal Stop
Peak Demand Limiting/Load Shedding
Economizer (enthalpy, dry-bulb, CO2, modulating/2-position, etc.)
Other Setpoint reset of cooling or heating based on demand, humidity, or adjustment pot
Additional Energy Management functions are resident at SI
Additional Programming Functions
DDC Loops (P, PI, PID) PI
Automatic PID Tuning Feature No
Automatical-Dial Alarm Support Available with M-202A
Does controller perform multiple retries and buffer/store alarm until connection is made? No. Available with M-202A
Are multiple destinations possible? No. Available with M-202A
Upon controller power loss or hardware failure:
Are network communications affected? No
Is loss recognized on/by the network and alarm reported? No
DO and AO response?
Outputs fail to a user pre-specified position
Outputs fail to a normal (unpowered) position
Outputs fail to last position
Other
Volatile memory functions?
Lost
Retained for life of backup battery
Other
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Yes
Automatically reset/synchronize the clock? No
Update all monitored functions? Yes
Generate an alarm if backup battery is dead? No
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? Yes. Peer-to-peer system communication continues within remaining segments
Does network store 'loss of communications' alarm with time of event? Yes - peer-to-peer system communication is automatically restored within segment
Additional Information (optional) None
Self Test Diagnostics
Does controller have internal self-test diagnostics to check:
Processor failure? No
Internal hardware failure? No
Open/shortened sensor? No
Others?
 
Control Enclosure Optional NEMA-1
Power Supply Required
Voltage 22 to 26.5 Vac 50/60 Hz
VA 6 VA consumption
Surge Protection Electrical isolation via dedicated 24 Vac power supply.
Underwriters Laboratories UL E7657524G9 and CSA listed
FCC
CE
LonMark Certified
Yes
No
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Yes
No
Not submitted for testing
Information not provided
Other