ACM Install Guide
ACM Install Guide
INSTALLATION AND
OPERATIONS GUIDE
User agreement and limited warranty
IMPORTANT - PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION (DEFINED BELOW) IS SUBJECT TO LICENSE RESTRIC-
TIONS AND LIMITED WARRANTY. CAREFULLY READ THIS AGREEMENT BEFORE USING ALERTON PRODUCTS, SOFTWARE, FIRMWARE AND/OR DOCUMENTATION.
This is a legal "Agreement," concerning the purchase of Products and use of Software, Firmware and/or Documentation, between you, the "User" (either individually or as an authorized representative of the
company that is purchasing, has purchased, or is using the Products, Software, Firmware or Documentation) and Honeywell, 16201 25th Avenue West, Lynnwood, WA, Washington 98087 USA. ("Honey-
well").
PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION INDICATES USER'S COMPLETE AND UNCONDITIONAL ACCEP-
TANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
Honeywell provides Alerton products ("Products"), software programs ("Software"), firmware, e.g., protocols, software program code, device drivers and related hardware ("Firmware") and accompanying
documentation ("Documentation") and grants a non-exclusive and non-transferable license ("License") to User to use the Software and the Firmware only on the following terms and conditions. Taken
together, Products, licensed Software, licensed Firmware and accompanying Documentation are collectively defined as "Alerton Product(s)" in this Agreement.
1. Copyright. The Software, Firmware and Documentation are copyrighted and protected by United States copyright laws and international treaty provisions and laws, contain valuable proprietary products,
information and trade secrets, and shall remain the property of Honeywell. User may not and shall not copy or otherwise reproduce or make available to any other party any part or all of the Software, Firm-
ware or Documentation nor decompile, disassemble, reverse engineer, manufacture or modify any portion of the Products, Software, Firmware, Documentation or any portion of the same for any purpose or
otherwise attempt to determine the underlying source code of the Software or Firmware or permit any such action; provided however, User may either (a) make one (1) copy of the Software solely for backup
or archival purposes, or (b) transfer one (1) image of the Software to a single hard disk, CD or other comparable media, provided User keeps the original solely for backup or archival purposes.
2. License. User is hereby licensed to use one (1) copy of the Software for User's own use in operating the Products. User may not rent, lease or otherwise assign or transfer all or any part of the Software,
Firmware or Documentation. In addition, User may not sublicense, assign or transfer this License or Agreement, or any part thereof. Any attempt to do so shall terminate this License and User's right to use
the Software and Firmware and shall subject User to liability for damages to Honeywell. LICENSING TO USER OF THE SOFTWARE AND FIRMWARE COMMENCES WHEN USER USES THE SOFT-
WARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION.
3. Copies, Modification or Merger. Except as specifically set forth in Paragraph 1, User may not copy, modify, transfer all or any portion of the Software, Firmware or Documentation or merge it or them into
another program, unless expressly authorized in advance in writing by Honeywell. User must, as a condition of this License, reproduce and include the identifying marks, copyright and proprietary notices on
any permitted copy of the Software, Firmware and Documentation. "Copies" shall include, without limitation, any complete or partial duplication on any media, adaptations, translations, compilations, partial
copies within modifications, mergers with other material from whatever source and updated works. User will use its best efforts to prevent any unauthorized copying or other activity with respect to the Soft-
ware, Firmware and Documentation.
4. Third-Party Beneficiary. For any software or other technology under this Agreement licensed by Honeywell from Microsoft( or other licensors, Microsoft or the applicable licensor is a third party beneficiary
of this Agreement with the right to enforce the obligations set forth in this Agreement.
5. Warranty. Honeywell warrants Honeywell manufactured or produced Alerton Products to be materially free from defects and to substantially conform to Honeywell's published specifications for a period of
twenty-four (24) months from date of shipment from Honeywell (the "Product Warranty Period"). This entire Section 5 is defined as the "Warranty."
Honeywell also warrants Alerton Products that it has previously repaired or replaced for the greater of ninety (90) days from the date of their shipment from Honeywell or the remainder of the Product War-
ranty Period of the originally shipped Alerton Product (the "Repair/Replacement Warranty Period").
During the Product Warranty or Repair/Replacement Warranty Period, Honeywell will repair or replace the applicable Alerton Products without charge and will add applicable engineering changes and
upgrades.
This Warranty only applies to defective materials and workmanship of Alerton Products and excludes defects that result from misuse, neglect, improper installation, unauthorized repair or alteration, damage
during or after shipping, accident and/or misapplication of such products. This Warranty does not apply to parts, equipment, software, firmware, components, documentation or any other item that Honeywell
does not manufacture or produce. This Warranty is also voided by removal or alteration of Alerton Product identification labels.
Honeywell's sole responsibility with respect to Alerton Products shall be, within the applicable Product Warranty Period, to furnish a replacement Alerton Product (FOB factory) or, at the option of Honeywell,
to repair and return (FOB Factory) the defective Alerton Product. HONEYWELL HEREBY EXCLUDES ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PUR-
POSE AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES WHATSOEVER WITH RESPECT TO ALERTON PRODUCTS. In no event shall Honeywell be liable for personal injury, loss of profit, loss of
production, loss of business or goodwill, business interruption, loss of business information or data, loss due to delays, any other pecuniary loss, any cost or liability of Users or any other parties, to them-
selves or to others, increased or uncovered operating or fixed costs, inefficiency, or any other special, exemplary, consequential, incidental, indirect or remote damages in any manner, directly or indirectly,
related to design, manufacturing, supply, installation or use of, or inability to use, Alerton Products, or any other act or failure to act by Honeywell or its agents or contractors.
HONEYWELL MAKES NO CLAIMS OR WARRANTIES WITH RESPECT TO THE SOFTWARE OR THE FIRMWARE AND SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABI-
LITY OR FITNESS FOR A PARTICULAR PURPOSE AND EXPRESS OR IMPLIED WARRANTIES THAT THE OPERATION OF THE SOFTWARE OR FIRMWARE OR ANY PORTION THEREOF WILL BE
INTERRUPTION OR ERROR FREE. Notwithstanding anything to the contrary contained in this Warranty, Honeywell shall not be liable to Users or any other parties for any damages, including, but not limited
to consequential, incidental, indirect, special, exemplary remote or pecuniary damages and any stated or express warranties set forth in this warranty are in lieu of all obligations or liability for any damages
arising out of or in connection with the use or performance of, or inability to use, Alerton Products and the licensed Software and Firmware.
User's exclusive remedy and Honeywell's entire liability arising from or in connection with the Alerton Products, Software, Firmware, Documentation and/or this License and Agreement (including, without lim-
itation, any breach of any warranty, express or implied) shall be, at Honeywell's option, the repair or replacement of the Products or Software or Firmware as applicable, as stated above. ACCORDINGLY,
HONEYWELL AND ITS DESIGNATED DEALERS AND THEIR DESIGNATED ASSOCIATE DEALERS HAVE EXCLUDED AND DISCLAIM ANY AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, WHATSOEVER, WITH RESPECT TO THE PRODUCTS, THE SOFTWARE, THE FIRMWARE,
THE DOCUMENTATION AND/OR THE LICENSE. USER HEREBY ACKNOWLEDGES THE SAME.
6. Remedies of Honeywell. IF USER BREACHES THIS AGREEMENT, USER'S LICENSE HEREUNDER SHALL BE AUTOMATICALLY TERMINATED. Upon termination, User shall return the Software,
Firmware and all Documentation to Honeywell and destroy any copies of the Software, Firmware and the Documentation or any portions thereof which have not been returned to Honeywell, including copies
resident on electronic or digital media. If User breaches this Agreement, Honeywell shall be entitled to all damages suffered by Honeywell resulting from such breach and Honeywell shall be entitled to equi-
table and injunctive relief in addition to all other remedies at law. In this regard, User acknowledges that its breach of any provision of this Agreement will cause Honeywell immediate and irreparable injury for
which there are inadequate remedies at law. The prevailing party in any dispute concerning this Agreement shall be entitled to the costs of collection and enforcement, including but not limited to reasonable
attorneys' fees, court costs and all necessary expenses, regardless of whether litigation is commenced.
7. Export. Alerton Products are subject to regulation by local laws and United States government agencies, which prohibit export or diversion of certain products, information about the products, and direct
products of the products to certain countries and certain persons. User agrees that User will not export in any manner any Alerton Product or direct product of Alerton Product, without first obtaining all nec-
essary approval from appropriate local and United States government agencies.
8. RESTRICTED RIGHTS NOTICE. Alerton Products, Software, Firmware and Documentation have been developed entirely at private expense and are commercially provided with RESTRICTED RIGHTS.
Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions pursuant to DFARS 227.72013 (October 1988) and DFARS 52.227-19 (June 1987),
as amended and as applicable. Manufacturer, licensor and publisher is Honeywell, 16201 25th Avenue West,
Lynnwood, WA 98087 USA.
9. Statute of Limitations. No action for any breach of a warranty, if any, deemed or actual, may be commenced more than one (1) year following the expiration of such warranty.
10. Other. User further agrees that this Agreement is the complete and exclusive statement of the agreement between User and Honeywell and supersedes any proposal or prior agreement or any other
communications between Honeywell or any of its representatives and User relating to the use of the Software, Firmware, Documentation and purchase of the Products. This Agreement may only be modified
by a physically signed writing between User and Honeywell. Waiver of terms or excuse of breach must be in writing and shall not constitute subsequent consent, waiver or excuse. If any provision of this
Agreement is finally determined to be unenforceable, the remaining provisions shall remain in effect. The laws of the State of Washington and the United States, including U.S. copyright laws, shall govern
this Agreement. Venue in the event of any suit, proceeding or claim shall be in the courts located in Snohomish County, Washington, USA. If User has any questions regarding this Agreement, User may con-
tact Honeywell by writing Honeywell at the above address.
This Agreement shall inure to the benefit of and be binding upon the parties and their successors, administrators, heirs and permitted assigns. Notwithstanding any termination of this Agreement and not in
limitation of any other provision of this Agreement, User shall specifically continue to be fully obligated to comply with all of the requirements of paragraphs one (1) through four (4), as if the Agreement were
not terminated and all remedy provisions hereunder shall apply to any breach of such obligations.
Important safety information and installation precautions
Read all instructions
Failure to follow all instructions may result in equipment damage or a hazardous condition. Read all instructions carefully before installing
equipment.
Electrostatic sensitivity
This product and its components may be susceptible to electrostatic discharge (ESD). Use appropriate ESD grounding techniques while
handling the product. When possible, always handle the product by its non-electrical components.
!
All wiring and controllers must be installed to minimize the possibility of accidental contact with other potentially hazardous and disruptive
power and lighting wiring. Never place 24VAC or communications wiring near other bare power wires, lightning rods, antennas,
transformers, or steam or hot water pipes. Never place wire in any conduit, box, channel, duct or other enclosure containing power or
lighting circuits of any type. Always provide adequate separation of communications wiring and other electrical wiring according to code.
Keep wiring and controllers at least six feet from large inductive loads (power distribution panels, lighting ballasts, motors, etc.). Failure
to follow these guidelines can introduce electrical interference and cause the system to operate erratically.
Warning
This equipment has been tested and found to comply with the limits for a class B digital device, pursuant to part 15 of the FCC rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.
Contents
About this guide 5
How to use this guide 5
Other information resources 5
Key illustrations 6
About the Ascent Control Module (ACM) 10
Overview 10
Technical specifications 11
Compatibility information for Alerton devices 12
Data persistence 12
Real-time Operating Code (ROC) files 13
Battery backup and ROC files 13
Licensing 13
Hardware installation and operation 14
Mounting 14
Power 14
Communications 14
Device instance 15
Using DIP switches on the ACM 15
ACM configuration 17
Connecting to an ACM with operator workstation software 17
Configuring Universal Inputs (AIs, BIs) 25
Working with the ACM in Device Manager 26
Using the Console Port to enable the BACnet Ethernet protocol 28
Appendix A: ACM features compared to BCM features 32
The ACM platform 32
ACM-GC program 32
Appendix B: ACM Niagara implementation 34
WorkPlace AX login 34
Supported Niagara components 34
MS/TP Drivers 34
Protocol integration 36
Appendix C: BACnet object and property reference 37
Properties of AV objects 38
Properties of BV objects 38
Properties of the device object 39
Properties of event enrollment objects 41
Properties of file objects 41
Properties of notification class objects 43
Properties of program objects 43
Properties of schedule objects 44
Appendix D: ACM diagnostic AVs 45
Appendix E: Troubleshooting 54
Appendix F: ACM Security 55
Appendix G: Installing Niagara Distribution Files 58
What are Niagara distribution files? 58
Do I need the Niagara distribution files? 58
Installing the Niagara distribution files 58
Appendix H: ACM Battery 59
Document ID Contains
Compass Installation and Upgrade Guide Information needed to use Device Manager to view device information about ACMs
(LT-COMPASSIUG) or to download a ROC file.
Compass Web Interface User Guide (LT-UG- Information for setting up automated control features for your Compass system.
CMPSWEB) and online Help
Compass Dealer Guide (LT- DG-CMPSWKSTN) Information about engineering the Compass primary operator workstation.
Key illustrations
4.5 IN
(114.3 MM)
2.7 IN 1.75 IN
(68.6 MM) (44.5 MM)
J
J
COM 0 +
COM 0 -
WARNING! Use COM 1 +
COM 1 -
only ACM-BATT IN 0
COM
battery pack. IN 1
BI 2
COM
BI 3
Feature Highlights
Scalable Supports up to six EIA-485, or two EIA-485 and two EIA-232, or two EIA-485 and two LON networks. There are
two onboard EIA-485 connectors plus two Option Card slots. NOTE: These are example configurations.
Inter-operable Supports the BACnet Protocol on Ethernet, BACnet IP, MS/TP, LON, SNMP, as well as many NiagaraAX
supported protocols. NOTE: No BACnet protocol integration requires the use of Niagara WorkPlace.
Enterprise ready Supports BACnet/IP and can operate as a BACnet broadcast management device (BBMD) with NAT support for
integration on enterprise and wide-area networks.
Powerful Powered by a high-speed, quad-core CPU based on the ARM® Cortex™-A9 architecture. 1 GB DDR3 SDRAM
provides a fast, reliable platform for running DDC programming and global automation routines.
Segmented DDC Allows multiple DDC program instances to run within a single controller, providing the ability to logically group sub-
code systems, improve uptime by enabling service on one system without impacting another, and maximizing flexibility
in programming configuration.
Table 3 Specifications.
Technical Data
Processor and Efficient, high-speed, quad-core CPU based on the ARM® Cortex™-A9 architecture (Freescale i.MX6Quad); 1GB
memory DDR3 SDRAM, 64-bit-wide, 533 MHz (1066 MT/s).
BACnet/IP IP support for interoperability on enterprise and [Link] as up to four BACnet broadcast management
devices (BBMDs) in accordance with Annex J BACnet/IP. Supports Alerton and BACnet Standard network
address translation (NAT) implementations.
MS/TP Supports two onboard networks that can be used for BACnet MS/TP or EIA-485 and up to two expansion cards
(two networks each) for a maximum of six BACnet MS/TP networks per ACM.
Expansion Supports up to two expansion cards for interface adapters, such as EIA-485, EIA-232 and LON.
Persistent memory Stores ACM configuration and licensing information through a power outage.
Communications Provides two Ethernet ports, two onboard 485 networks, two universal inputs, two binary inputs, two expansion
cards give the ability to add up to four additional networks (for a total of six), or two 232 networks, or two LON
networks.
Dimensions 7-1/4 W x 8-9/16 H x 1-11/16 D (inches) 185 W x 220 H x 44 D (millimeters); fits 12 x 12 x 4 (inch) panel enclosure.
Platform Linux
Table 3 Specifications.
Technical Data
Ethernet Two integrated 8P8C modular connectors for use with two 10Base-T, 100Base-TX, and 1000Base-T Ethernet
networks.
Networking Supports both BACnet and Alerton network address translation (NAT).
Ethernet port ETH0 can be assigned a Gateway. ETH1 uses RIP to route to other subnets.
Software Programming interface is the Alerton Compass operator workstation software. Supports full Niagara AX station.
Certifications and ROHS compliant, applicable CE requirements, FCC Class B, IEC 60703, C-Tick listed, UL 916 for open energy
standards management equipment.
Data persistence
All programmed objects (such as schedules, trendlogs, and alarms), DDC, data values, and the ROC
file execute in RAM and are periodically backed up in flash memory. Data is retained through power
loss as follows:
• Orderly shutdown: no data lost
• ACM-GC data is backed up every 5 minutes or less.
• Niagara has its own periodic writing schedule. This is configurable; the default is once per day.
Configuration parameters are stored in flash memory. Likewise, all configuration data is retained
through power loss.
NOTE Using the optional ACM Battery backup increases the chance that even in the instance of a
power loss, the ACM will go through the orderly shutdown and data will not be lost. The ACM
Battery backup must be connected to the ACM for 24 hours before it provides backup power
support.
Configuration parameters can be saved in the DCF file and then sent to the ACM. This facilitates off-site
setup and easy replication of settings to other controllers in similar installations.
Unique to application,
DDC Automation
user interactive
Figure 7 Relationship of ACM system boot code, ROC, and application files
The ROC file is the foundation of controller operations and is required for the ACM to host DDC and
automation features. Although, an initial ROC file is loaded at the factory, periodic updates may be
required (for example, when a new version of operator workstation software becomes available).
Download ROC files from the <bactalk root>\system directory using Compass operator workstation
software. See Compass software online Help for more information about downloading ROC files or
checking ROC file versions.
NOTE Best practice: check what is on disc before you send the ROC to device. Then check it after you
send it to make sure you have the latest.
Licensing
When you purchase an ACM you specify the capabilities you want it to support and your purchase
includes the ACM unit and a license file. The license file may include licenses for multiple drivers
purchased.
If you want to add a license to the ACM, buy the new license, download the license from Niagara
Central, and then load the license into the ACM to activate its device capabilities.
There are two methods to add a license to the ACM: through Compass or the Niagara WorkPlace AX.
Compass
Niagara WorkPlace AX
Only Niagara-certified users can use WorkPlace AX to add licenses to the ACM. Add a license using
the standard Niagara Licensing mechanism.
Mounting
The ACM is designed to mount to a 35mm DIN rail, in either the North-South or East-West orientation.
Labels can be read easily in either orientation.
The ACM may also be mounted using the screw mounting holes located at each corner of the device.
ACM modules are intended for indoor applications. Install in a UL-listed enclosure, in a dry location,
away from direct sunlight, and free from excessive dust, vibration, and electrical interference.
The ACM Battery can be mounted on a 35mm DIN rail, or panel mounted using the screw holes.
Power
24 VAC @ 40 VA, 47–63 Hz, full-wave rectified.
Communications
This topic describes hardware network connections to the ACM.
To terminate cable
1. Strip a maximum of 3/8” (10 mm) of the wire jacket from
the end of the cable.
2. Use a small screwdriver (1/8” max.) to turn the
adjustment screw fully counter-clockwise.
The clamps in the wire slot separate as you turn the
screw.
3. When the clamps in the wire slot are fully open, insert
the stripped end of the cable (insulation end must be
flush with the terminal block). Be sure to insert all cable
strands into the wire slot.
4. Hold the cable in place and turn the adjustment screw
clockwise to tighten it until the clamps in the wire slot
secure the cable.
5. Tug gently on the cable to ensure that it’s secure.
CAUTION Set up firmware before physically connecting networks. This helps to avoid potential
network conflicts and communication errors.
Ethernet
Ethernet is a high-speed LAN widely installed in commercial buildings.
2 Transmit –
3 Receive +
1 2 3 4 5 6 7 8
6 Receive –
MS/TP
MS/TP is a LAN standard designed specifically for BACnet applications. It uses the EIA–485 signaling
standard. The ACM communicates over MS/TP through EIA-485 option cards installed into one or both
of the option card slots located on the right side of the ACM.
Device instance
The device instance is a unique number throughout the BACnet internetwork that identifies the device
for BACnet communications. Valid range for the device instance is 0 to 4,194,302. Ensure that the
device instance is different from any other device on any connected network.
BACnet reserves device instance 4194303 for special purposes. Do not use device instance 4194303.
NOTE Host name information is accepted via DHCP only if it comes in through ETH0. This is true even
if only ETH1 is enabled. DHCP host name information coming in through ETH1 is ignored.
Default Gateway
Configure a maximum of one default gateway per ACM. Problems will occur if you set up default
gateways on both Ethernet ports. Use address [Link] to mean “none.”
ACM 1.1 has the RIPD v1 and RIPD v2 protocols enabled so it can automatically discover IP routes
through both ETH0 and ETH1. This feature allows the ACM to reach subnets in the internal BAS/private
network, even if there are IP routers in the building.
Setting a default gateway on ETH0 is appropriate if you are using static (non-DHCP) configuration and
you need to reach the Internet through ETH0. In such cases, the ETH0 gateway should be the internal
IP address of the NAT firewall between the ACM and the Internet. See the following diagram.
If you are not using ETH0 to reach the Internet, then you can use the Default Gateway setting to specify
the address on one IP router. There are legitimate cases where the Niagara components do need
Internet access, for example:
• To send e-mail to Internet services such as [Link], [Link], etc
• To access time servers
• To access weather services
The Description property of diagnostic AV-100025 shows routing information automatically gathered by
the ACM. The description should be displayed using a fixed pitch font such as Courier New.
BACnet configuration
NOTE The ACM is initially configured with BACnet/Ethernet protocols enabled for both Ethernet ports.
The ACM has 6 “slots” for running programs. The Internal Virtual BACnet/IP network must be enabled
to communicate with devices in slots 1-5.
All networking is configured through the BACnet device in slot 0, including the choice of which
applications to run in the other slots. BACnet devices in slots 1-5 have much smaller configuration data
that does not include any networking configuration. Slots can also be left empty; it is not required to run
an application in all of them.
3. Click Apply.
4. Under BACnet Configuration click Internal Virtual BACnet/IP Network, set up the internal
virtual BACnet/IP network, and then click Apply.
Note It is recommended that you do not change factory default settings unless you are certain the
default settings conflict with system design or existing system settings or you have more than
one ACM in your BACnet system.
6. Click Virtual Controllers, specify the device type for each Slot used, and then click Apply.
8. Click BACnet/Ethernet, and then click ETH0 BACnet/Ethernet Configuration in the tree.
9. Click Enable or Disable BACnet/Ethernet on eth0 (as dictated by your sites architecture),
type the Ethernet Network Number, and then click Apply.
11. Repeat for ETH1 BACnet/Ethernet Configuration, if desired, and then click Apply.
WARNING Using both Ethernet ports can create network loops resulting in reduced performance and
limited system functionality.
3. (Optional- only necessary for BBMD installations where more than 1 subnet is used.) Click
BACnet/IP Instance 0 Broadcast Distribution Table, set the parameters, and then click
Apply.
MS/TP configuration
When a COM port is assigned for MS/TP use, you must choose which slot to route MS/TP through. It is
important to not choose an empty slot.
Also, if an MS/TP is routed through slot 1-5, the Internal Virtual BACnet/IP network must be enabled in
order to be able to route from Ethernet to that MS/TP network. See “To configure BACnet networks” on
page 21. for more information about configuring Internal Virtual BACnet/IP networks.
COM0 MS/TP Configuration and COM1 MS/TP Configuration are the built on MS/TP connections
located on the left side of the ACM. COM2 and COM3 MS/TP Configuration are option card Slot0 on
the right side of the ACM. COM4 and COM5 MS/TP Configuration are option card Slot1 on the right
side of the ACM.
WARNING Only route MS/TP COM ports through slots that have been enabled.
NOTE If a COM port is assigned for MS/TP use, it should not be assigned in the Niagara AX Station for
any network.
2. Click the ACM you want to add to Device Manager and then click Save to Table.
The new ACM device record is saved in the Device Manager Table.
2. Update the ACM parameters on the Identification tab, and then click OK.
3. Click the Capabilities tab, click Auto-Select, and then click Select by Polling Device.
4. Click the Preferences tab, set the UTC Offset, DDC, Application, Host Controller, and Com-
munication Alarms parameters, and then click OK.
Locked out? The Console Port connection provides a limited number of options and should only be
used to enable BACnet/Ethernet if you can no longer communicate with the ACM. The Console Port
provides a method to reconnect with the ACM and verify settings. You can enable/disable the BACnet/
Ethernet protocol and assign BACnet/Ethernet network numbers for either Network Interface Card. The
ACM must have a BACnet Ethernet network number to work.
You cannot enable or change the BACnet/IP settings using the Console Port. You must do that using
the remote device configuration tool that is available in Compass.
1. Download the driver for the USB cable and Console Port from [Link]
wp-content/uploads/[Link].
2. Select the .INI file for the driver (control panel -> device manager and look for “unknown”
USB device).
3. Right-click and choose “update driver software”, then “browse my computer for driver soft-
ware”. You need to browse to the folder containing the .INF file for the ACM. When all is
working, you should see a serial port corresponding to the ACM.
4. For instructions on how to use Putty or HyperTerminal, please visit the suppliers website.
3. Launch PuTTY.
4. Specify the ACM connection parameters, and then click Open to display the ACM Console
screen.
IMPORTANT! Do Not leave the ACM with default login credentials! The installer is strongly
encouraged to change the password.
Saving changes
After you make changes in PuTTY, you must exit appropriately to save your changes.
CAUTION You will lose changes if you close the PuTTY session or disconnect without saving. After
making any changes, be sure to exit appropriately to save your work.
ACM-GC program
Features exceeding the BCM-ETH
• Number of AVs and BVs is configurable per slot.
• One slot can have as many BACnet objects as six BCM-ETH devices combined. However, you
cannot max out all 6 slots. The following overall per-ACM limits must be observed:
• Max 2000 trendlogs
• Max 2000 alarms
• Max 6000 AVs
• Max 6000 BVs
• Max 384 schedules
• Max 10 demand limiters
• Max 384 zones
WorkPlace AX login
The default login for the platform is username=alerton, password=niagara.
IMPORTANT! Do Not leave the ACM with default login credentials! The installer is strongly
encouraged to change the password.
[Link] No
Any components with dependencies on non-supported platform components will not work.
MS/TP drivers
Be sure to use the appropriate driver for the ACM.
• ACM-DR-MSTP-AX This driver supports MS/TP communications on all 6 ACM ports when
working in a Niagara AX workstation. Order the ACM-DR-MSTP-AX driver with the ACM as a
variant configuration (VC) option, or order it later and add it to the ACM. This driver does not work
with Alerton AIE or Tridium JACE products.
• I-DR-MSTP-AX Do not use this driver with the ACM because it limits MS/TP communications to 5
ports. Use I-DR-MSTP-AX driver with Alerton AIE products.
You can add up to 6 MstpPorts to the BACnet Network, depending on installed option cards and
licensing.
NOTE If you enable any of the COM ports for MS/TP using the Device Manager’s Device Configuration
option, you can not use that COM port in WorkPlace AX.
Protocol integration
Alerton has tested and found that the ACM does support the following protocols.
Driver compatibility
Alerton drivers
Alerton maintains a list of AX drivers that are compatible with the ACM. This list is updated as Alerton or
Alerton dealers test more drivers. View the current Alerton ACM Niagara AX Driver List (LT-
ACMDRIVERS) on the Ascent pages, which are available through the Alerton Support Network.
Alternatively, the Tridium website has a list of Niagara AX drivers for JACE products.
Search [Link] for the latest information; more recent versions might be available.
Use the following guidelines to determine if a driver is likely to work on the ACM:
• If the “Niagara Platform” includes “JACE,” then it should also run on the ACM (subject to other
criteria below). Otherwise, assume it won't run on the ACM.
• If the “Connection Type” says the driver supports “Serial,” “Serial EIA-232,” “Serial EIA-485,” “TCP,”
“UDP,” or “IP,” then it should work on the ACM. If it says anything else (or if it just says “Ethernet”),
then assume the driver will not work on the ACM.
• The “Niagara Version” criteria must be met. The ACM runs Niagara version 3.8.
Object (instance
Remarks
range)
Calendar Describes a list of calendar dates, special event dates, holiday dates, and date ranges.
Event Enrollment Defines an event and connects the occurrence of the event to the transmission of an event
notification. Used in Compass primarily for alarms.
Notification Class Stores a list of available recipients for the distribution of event notifications (alarms, trendlog
gathering, and so on.).
Program (1024) Stores program status information about the current DDC program.
Schedule Controls designated properties by periodic schedule that may recur during a range of dates.
Trendlogs Helps troubleshoot problem areas and identify critical operating trends in the BACnet system.
Zones * Defines a space in a building that is controlled by a Compass system. Zones provide a
convenient mechanism to monitor, manage and arbitrate multiple Envision features, such as,
schedules, optimum start, and tenant activity. Optimum start and tenant activity require a zone
to be setup. A zone may represent one floor of a building, multiple floors, a particular room or
area on a floor, a hallway, foyer, or stairwell.
Demand Limiting* Monitors and controls energy demand and then automatically adjust equipment operation to
limit the demand and reduce costs.
Properties of AV objects
Table 10 AV object properties.
description Yes Character string Occupied A description assigned to describe the object’s function.
Setpoint
object- BACnet_ Object_ AV 1 This property consists of the object-type property and the
identifier Identifier object instance, which is a numeric code that identifies the
object of interest.
object-type Enumerated AV
present-value Yes Real 76.4 Range is +/−3 x 1038 (six significant digits of resolution).
status-flags Bit string <Bit string> A four-position bit string that indicates the status of the AV.
If a status bit =1, that status is TRUE.
units Yes Enumerated Deg F Indicates the unit of measure, in BACnet engineering units,
for the AV present-value.
Properties of BV objects
Table 11 BV object properties.
description Yes Character string Occupied Setpoint A description assigned for the object’s function.
object- BACnet_ BV 5413 This property consists of the object-type property and
identifier Object_ the object instance, which is a numeric code that
Identifier identifies the object of interest.
status-flags Bit string In alarm = 0, fault A four-position bit string that indicates the status of the
= 0, overridden =0, object. If a status bit =1, that status is TRUE.
out of service =0
priority-array BACnet <Array of BACnet An array of prioritized values (indexes 1-16) controlling
PriorityArray PriorityValue> the present-value, index 1 having the highest priority.
The value with the highest priority controls the
present- value. Possible values for priority-array
indexes are ACTIVE, INACTIVE, or NULL. A NULL
value indicates no command is issued at that priority-
array index.
relinquish- Yes Enumerated Inactive Default value to be used for present-value property
default when all priority-array indexes are NULL.
APDU-Segment Yes Unsigned 6000 The time after transmission of a “segment” until the lack of
Timeout a reply means it was assumed to be lost (in milliseconds,
1000 = 1 sec.). Default = 6000.
APDU-Timeout Yes Unsigned 6000 The time after transmission of an APDU until the lack of a
reply means it was assumed to be lost. The APDU
timeout value for this device in milliseconds (1000 = 1
sec.). Default = 6000.
Application- Character 1.0.31 Indicates the version of the application that is running for
Software-Version string that slot. For example, ACM-GC application.
Description Yes Character Second floor Assigned by the user to describe the device’s function.
string controller
Device-Address- List Lists all devices bound to the ACM. Basically, all devices
Binding the ACM needs to talk to will show up in the list. For
example, all devices referenced by schedules, trendlogs,
alarms, DDC, etc, that are hosted in the ACM.
Firmware- Character 1.0.31 Indicates the ACM ROC version. The ACM ROC is
Revision string essentially the OS that allows applications like the ACM-
GC application to run.
Local-Date Yes Date Sunday, 09/ Indicates date: day of the week, month/day/year. Writable
26/2020 using Time Sync. NOTE: Change the date using Sync or
UTC Sync services.
Local-Time Yes Time 10:15:56.00a Indicates the time stored in the device. Writable using
m Time Sync. NOTE: Change the time using Sync or UTC
Sync services.
Location Yes Character East Wing Indicates the physical location of the device.
string
Max-APDU- Unsigned 1476 The maximum message packet size that the device can
Length-Accepted handle.
Max-Info-Frames Yes Unsigned 60 Number of MS/TP messages the device will send per
token hold. Default = 60. Max. = 200.
Max-Master Unsigned 127 Highest MAC address above this unit's that another
MS/TP master should be set to.
Model-Name Character ACM-GC Assigned by the vendor to indicate the device model.
string
Number-Of- Yes Unsigned 3 The number of times a message will be resent after it is
APDU- Retries assumed to be lost.
Object-Identifier BACnet_ Device 200 This property consists of the object-type property and the
Object_ device instance (a numeric code that identifies the device)
Identifier of this device.
Object-Name Character Controller Every device must have a unique object name.
string 200
Protocol-Object- Bit string <Bit string> An internally used bit string. Indicates which BACnet
Types-Supported object types reside in the device.
Protocol- Bit string <Bit string> An internally used bit string. Indicates which BACnet
Services- services the device can process.
Supported
protocol-revision unsigned 9
Acked-Transitions bit string To-offnormal =1, Indicates whether the corresponding transitions
To-fault = 1, To- have been acknowledged. 1 indicates that the
normal = 1 transition was acknowledged. Set in the Event
Enrollment Editor at the operator workstation.
Description Yes Character Event enrollment 0 A description assigned to describe the object’s
string function.
Event-Enable Yes bit string To-offnormal =1, Indicates whether notifications are enabled for
To-fault = 1, To- these event transition types. 1 indicates that the
normal = 1 transition will be reported. Set in the Event
Enrollment Editor at the operator workstation.
Event-Type Yes Enumerated change_of_bitstring Indicates the type of event algorithm to be used
to detect events.
Notify-Type Unsigned alarm Indicates whether the object is set up for alarms
or events.
Object-Property- Yes BACnet object- FALSE Specifies the identifier of the object being
Reference property- monitored by the EEO.
reference
Object-Type Event-enrollment
Archive Yes Boolean FALSE Indicates whether the file has been saved for
backup.
Description Character string ACM-GC ROC A description assigned to describe the object’s
File function.
Modification-Date Time 07/31/20 The date and time the file was last modified.
10:22:20:00a
Ack-required Yes Bit string To offnormal = Indicates whether an acknowledgment is required for
1, to fault = 1, to event transitions. A 1 indicates that acknowledgment is
normal = 1 required. Set up at the operator workstation.
Description Yes Character Alarm Handler An editable description of the object’s location or
string function.
Object- BACnet_ Notification- This property consists of the object-type property and
Identifier Object_ class 1 the object instance, which is a numeric code that
Identifier identifies the object of interest.
Recipient-list Yes List <List of BACnet Lists the devices that will receive notification when the
Destination> notification class transitions. Set up at the operator
workstation.
priority Yes Array of Indicates the priority to be used for event notifications for
Unsigned TO-OFFNORMAL, TO-FAULT, and TO-NORMAL
events, respectively.
Instance-Of Character alerton hq alerACM-GC Header information for the file. Program 0 does not
string 0*00000000* support this property.
Object- BACnet_ program 1024 This property consists of the object-type property
Identifier Object_ and the object instance, which is a numeric code
Identifier that identifies the object of interest.
Program- Yes Enumerated READY Used to command the program state. A program
Change can be stopped using the HALT command, for
example, and started again with RESTART.
Status-Flags Bit string In alarm = 0, fault = 0, A four-position bit string that indicates the status of
overridden = 0, out of the object. If a status bit =1, that status is TRUE.
service = 0
Description Yes Character string Weekend Gym A description assigned to describe the object’s
function.
Exception- Yes Sequence <Array of BACnet Assigned in schedule setup at operator workstation.
Schedule Special
Event>
List-Of- Yes List <List of BACnet The list of objects that this schedule commands.
Object- Object
Property- Property
References Reference>
Object-Name Yes Character string schedule 000 Assigned in schedule setup at operator workstation.
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
MS/TP Instance 0
MS/TP Instance 1
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
MS/TP Instance 2
MS/TP Instance 3
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
MS/TP Instance 4
MS/TP Instance 5
Units
Description Present
Point Name Property (NOT Clearable
Property Value
BACnet)
Card Slot 0
Card Slot 1
Appendix E: Troubleshooting
ISSUE: All MS/TP networks shut down.
If you connect more than the maximum number of devices your license supports, then all MS/TP
networks shut down after approximately 10 minutes. As soon at the ACM detects more BACnet devices
on its directly connected networks than the license supports (this is the ALERTON license, and not the
Niagara license), then a License Limit Warning BV comes on and a 10 minute “grace period” timer
starts counting down.
If the number of devices remains over the license limit the timer will count down to zero and the ACM
will disable ALL directly connected networks. If the number of devices drops below the license limit
during the grace period, a 60sec dead band timer will start. If the number of connected devices remains
below the license limit for the dead band period, then the limit warning is cleared, and the grace timer is
cleared.
IMPORTANT! If there is less than 60 seconds on the grace period timer when the dead band timer
starts, the grace period will expire before the dead band timer, and the networks hosting
Alerton devices will be disabled. The ACM must be reset to re-enable the disabled
networks.
The ACM does not route IP packets. This means the ACM serves as an extra layer of isolation between
the firewall and the BAS network. The network segment between ETH0 and the firewall acts like a
DMZ.
Due to site-specific considerations, it might not be feasible to do the most preferred installation.
Implementation 2A above is not as robust in terms of security, but it is acceptable as a second choice.
If the building network has IP routers, then ETH1 must be used because it is the only port that supports
RIP.
These acceptable installations are less secure than the preferred installation because of the following
considerations:
• It may be possible to interact with the BAS protocols through the firewall if a weakness in the
firewall exists (or if it is misconfigured). The security of the BAS protocols here depends on the
firewall to block all traffic except through the “punched holes” represented by the port forwarding
(for example, in the above diagram, HTTPS could be “punched through” to the ACM).
• Because the RIPv1 protocol is enabled on ETH1, it might be possible to discover routing
information via the Internet. Doing so would also require exploiting a weakness or misconfiguration
in the firewall.
NOTE This installation information is included in the Distribution File Installer in WorkPlace AX Help.
See Workplace AX Help for this and more detailed information about working with AX
distribution files.
1. Download the ACM Niagara AX files from the ACM product page.
2. Unzip the file and save the folder at C:\Niagara\Niagara 3.8.38\sw\Inbox.
“Niagara 3.8.38” is the name of the Niagara install folder for this version. The folder structure
is important so copy the folder and not the individual files.
3. Run WorkPlace AX.
4. Using WorkPlace AX connect to the ACM Platform to update the ACM.
5. Using the Distribution File Installer choose Directory, select the new folder, click Install, and
then click through the online prompts to install the required components.
This creates a new folder that matches the folder name in the Inbox in Step 2.
6. Once the installation is complete the controller will automatically restart.
7. Reconnect to the ACM Platform, click Platform Administrator, and then verify that the Niag-
ara Runtime version shows the new version number.
Specifications
Technical Data
Storage 5°C to 25°C (41°F to 77°F) recommended storage temperature to extend life;
Temperatures 0°C to 50°C (32°F to 122°F) allowed storage temperature.
Storage Humidities RH 65% ±5% non-condensing recommended storage humidity to extend life;
RH 5% to 95%, non-condensing allowed storage humidity.
Dimensions 4.5 in. L x 2.7 in. W x 1.75 in. H (114.3 mm W x 68.6 mm W x 44.5 mm H). See Fig. 4.
Installation
See the ACM Battery installation instructions, LT-ACMBATT-II for installation details. The ACM Battery
can be mounted to the DIN rail or secured to the panel.
Charging
The ACM Battery is charged by the ACM controller. It might take up to 24 hours for the battery to reach
full charge.
Servicing
The ACM Battery is installed or replaced as a single unit, and cannot be field serviced. The cover
should only be removed to access screw holes for panel installation.