DDC Online direct digital controls
KMC Controls - KMDigital  

KMD-7011, 7013; KMD-7101, 7102; KMD-7301; KMD-7302; KMD-7401

Secondary Control Units
Terminal Secondary Control Units
Date Last Saved: 7/20/2010 10:39:00 AM

Product Name(s): KMD-7011, 7013; KMD-7101, 7102; KMD-7301; KMD-7302; KMD-7401
Product Description: The KMDigital Terminal SCUs all have a common processor but each have a different I/O board (4 inputs/4 outputs). They can operate stand-alone or communicate peer-to-peer when networked together. They have pre-programmed control sequences but can be user modified for special sequences, or totally reprogrammed.
Product Application(s): The following part numbers and descriptions outline the various specific applications for the KMDigital Terminal SCUs. Specific I/O corresponding to these controllers are described in the next section. KMD-7011, 7013 - VAV Unit KMD-7101, 7102 - Fan Coil Unit KMD-7301 - Air Handling Unit KMD-7302 - Roof Top Unit KMD-7401 - Heat Pump Unit
Point Quantity Characteristics
Analog Input (AI): See below
Digital Input (DI): N.A.
Universal Input (AI or DI): See below 0-5 Vdc (analog)
Thermistor (10K)
Dry Contact
Analog Output (AO): N.A.
Digital Output (DO): See below Mechanical relays
Universal Output (UO):
Other:
Control Unit Model #:AIDIUIDOAOUOOther
KMD-7101 (Fan Coil unit) 4 (2) Triacs, (3) SPST Relay
KMD-7102 (Fan Coil Unit w/ Aux. Heat) 4 (2) Triacs, (4) SPST Relay
KMD-7301 (Air Handling Unit) 4 (1) Triac 3
KMD-7302 (Roof Top Unit) 4 (2) Dual Triacs, (1) Triac 1
KMD-7401 (Heat Pump Unit) 4 (4) Triacs
KMD-7011 (VAV) 3 4 1 airflow input
KMD-7013 (VAV) 3 2 1 airflow, 1 Triac, 1 tristate Triac
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit
Other
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
Other
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
AO Only
DO Only
Other
Integral Flow Sensor? No
Integral Damper Actuator? No
Can controller accept occupant override from thermostat? Yes
Can controller accept occupancy sensor input? Yes
Expander Boards None
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - EIA 485 to secondary network @ 38.4 kbps (peer-to-peer)
External Communication Ports, Speeds and Access Devices (1) RJ-12 port to NetView local display panel or NetSensor
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 NetView (separate wall or desk unit). NetView can read trend and runtime logs as well as change schedules.
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) Information not provided.
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
None
Other "C" units only
Clock Synchronization Synchronized to 60 Hz power cycle, and/or synched up by OWS, and/or synched up by a master controller, and/or synched up by SCU with hardware clock at lowest address on subnetwork.
Volatile Memory (RAM) Capacity Information not provided.
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
Is Volatile Memory Supported By Battery? Information not provided.
Battery Type(s) Information not provided.
Battery Life Information not provided.
Backup Battery Operating Time Information not provided.
Non-Volatile Memory Capacity (EEPROM/Flash)* Information not provided.
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
Control Programming Storage
Controller Operating System
Other
Additional Information These controllers can be purchased with an optional on-board real time clock with auto-reset of time across network after power restoration.
* 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? All Terminal SCUs: Up to 2 trend logs and 2 runtime totalizers.
What is the controllers role in trending? Information not provided.
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? Information not provided.
Programming Method(s) The Terminal SCUs come pre-programmed for their specific applications, but can be reprogrammed as needed. Programming uses a combination of fill-in template and characteristic pick bars for I/O point, virtual point (VARs), PID control loop, trend log, schedules, and runtime log definition. They use a non-proprietary (open) line-based programming language (ControlBASIC) for operating sequences.
Resident vs Non-Resident Program Execution All program execution is resident.
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 "Canned" programs available
Additional Energy Management functions are resident at SI
Additional Programming Functions Custom programming can be done. Weekly schedule is standard. More detailed scheduling can be provided by a Local Controller (with clock option) or LAN Controller.
Enthalpy and wet-bulb algorithms are built in to the controller logic and can be used as needed.
DDC Loops (P, PI, PID) 4 loops (PID)
Automatic PID Tuning Feature No
Automatical-Dial Alarm Support Available from controller using optional CommTalk DEM communications interface
Does controller perform multiple retries and buffer/store alarm until connection is made? Yes, via CommTalk DEM
Are multiple destinations possible? Yes, via CommTalk DEM
Upon controller power loss or hardware failure:
Are network communications affected? No, once the next network token-pass determines unit is offline.
Is loss recognized on/by the network and alarm reported? Yes
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 Information not provided.
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Yes
Automatically reset/synchronize the clock? Yes. Use of at least one KMD-5801 or 5831, KMD-5210 'LAN Controller' or one KMD7xxx'C' Controller is required to reset clocks across the secondary network.
Update all monitored functions? Yes
Generate an alarm if backup battery is dead? Information not provided.
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.)
Yes. When the secondary network is broken, a token-based peer-to-peer system generates a second token to operate the bus as two peer-to-peer systems.
Does network automatically reconfigure upon restoration? Yes, restored controller generates new token.
Does network store 'loss of communications' alarm with time of event? No
Additional Information (optional)
Self Test Diagnostics
Does controller have internal self-test diagnostics to check:
Processor failure? No
Internal hardware failure? No
Open/shortened sensor? Yes
Others?
 
Control Enclosure Yes-Models 740x,730x. Enclosures avaialble for 710x .
Power Supply Required
Voltage 24 VAC -15%/ +20%
VA 10 VA maximum
Surge Protection Information not provided.
Underwriters Laboratories Information not provided.
FCC Information not provided.
CE Information not provided.
LonMark Certified
Yes
No
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Yes
No
Not submitted for testing
Information not provided
Other