DDC Online direct digital controls
KMC Controls - KMDigital  

PLC16 (KMD-5801 & KMD 5802); PLC 28 (KMD-5831)

Secondary Control Units
Programmable Local Controllers (KMD-58xx Series)
Date Last Saved: 7/27/2010 2:36:13 PM

Product Name(s): PLC16 (KMD-5801 & KMD 5802); PLC 28 (KMD-5831)
Product Description: The KMDigital 5800- Series controllers are general purpose, programmable controllers. They can operate stand-alone or communicate peer-to-peer with all other KMD controllers when networked together. They are similar, except for point counts, programming capacity, A/D converters, and that the KMD-5801 and 5831 have the ability to auto-reset time after power restoration. For this reason, KMC recommends at least one KMD-5801, KMD-5831, or KMD-7xxx'C' (refer to KMD-7000 series) on each network.
Product Application(s): The PLC16 and PLC28 are recommended for all general-purpose HVAC applications including air-handling units, chillers/boiler/central plant control and distribution systems, data acquisition, and other related industry applications. The PLC16+ is recommended for higher resolution input requirements such as in clean rooms.
Point Quantity Characteristics
Analog Input (AI): N.A.
Digital Input (DI): N.A.
Universal Input (AI or DI): See below 0-5 Vdc (analog)
4-20 mA
Thermistor (10K)
Dry Contact
16 Hz pulsed
Analog Output (AO): N.A.
Digital Output (DO): N.A.
Universal Output (UO):
Control Unit Model #:AIDIUIDOAOUOOther
PLC16, PLC16+ 8 8
PLC28 16 12
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit On PLC16+
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
Both AO and DO
DO Only
Indicating status LED on each output?
AO and DO Optional
AO Only
DO Only
Integral Flow Sensor?
Integral Damper Actuator?
Can controller accept occupant override from thermostat?
Can controller accept occupancy sensor input?
Expander Boards Not available
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary to secondary network ('SubLAN') @ 38.4 kbps (peer-to-peer)
External Communication Ports, Speeds and Access Devices (1) - EIA-485 Serial port (RJ-11)
To: Laptop/PC; NetView local display panel, NetSensor zone-based interface; or Windows CE-based handheld device.
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
Controller Access Devices
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Zone-Based Interface Access NetSensor (temperature and temperature/humidity models)
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)
*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
O&M SupportTAB/Cx Support
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
Other Powered, capacitor-backed
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(PLC16; PLC28)
128 kB RAM (PLC16+)
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
Is Volatile Memory Supported By Battery? Optional battery available to back RAM
Battery Type(s) Rechargeable 'gel cell' battery with integral charger.
Battery Life N.A.
Backup Battery Operating Time Optional battery is capable of providing 24 hours of RAM memory backup.
Non-Volatile Memory Capacity (EEPROM/Flash)* Information not provided (PLC16; PLC28)
512 kB FLASH (PLC16+)
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
Control Programming Storage
Controller Operating System
Additional Information The PLC 16+ and PLC 28 have an on-board real time clock with auto-reset of time across network after power restoration. The PLC 16 has no clock function.
Clock capacitor backup is 72 hours and requires no maintenance
* 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? PLC16 and PLC16+: Up to 8 trend reports can be stored consisting of 4 points per report and 400 values per point (for a total of 12,800 stored points per controller)

PLC28: Up to 12 trend reports can be stored consisting of 4 points per report and 400 values per point (for a total of 25,600 stored points per controller)

Programming is executed from RAM and is backed in FLASH at 24 hr or closer intervals.
What is the controllers role in trending? Programming resident within controller gathers and stores trend data on-board. Daily, or at set intervals (as operator selected), data is pulled by OWS from controller for archival. Trend data is written to flash daily, or more frequently as programmed in ControlBASIC using "write to flash" command.
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? If controller trend data buffer fills before being called by archive workstation, old data is overwritten.
Programming Method(s) The PLC-Series controllers use 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. Programming is retained in non-volatile (FLASH) memory. Any calculations temporarily stored in RAM are lost.
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.
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
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.)
Additional Energy Management functions are resident at SI
Additional Programming Functions Enthalpy and wet-bulb algorithms are built in to the controller logic and can be used as needed.
DDC Loops (P, PI, PID) PLC16, PLC16+: 5 Loops (PID)
PLC28: 10 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
Volatile memory functions?
Retained for life of backup battery
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? Only if optional battery status is input point.
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? Reversed 24 VAC hot/neutral indication
Short protection on outputs
Automatic, pre-programmed self-test diagnostics are not supported. Exceeded parameters and sensor error flags can be user programmed to set alarm.
Control Enclosure Field-supplied, and available from manufacturer if needed.
Power Supply Required
Voltage 24 Vac
VA 20 VA maximum
Surge Protection Network lightning protection available from manufacturer as an option. Surge protection for up to 230 Vac is integral for inputs, and communication lines.
Underwriters Laboratories UL and CUL 916 PAZX (Energy Management)
PLC16 only: UUKL 864 UDTZ (Smoke Control)
FCC Part 15, Sub-Part B, Class A
CE Yes
LonMark Certified
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Not submitted for testing
Information not provided