Specifications
Table Of Contents
- 1.0 System Overview
- 2.0 Product Description
- 2.1 Application Software
- 2.2 Custom Software Development
- 2.2.1 SITECONFIG-SVC - SiteScan Configuration Service Agreement
- Additional Benefits
- HIGRAPHIC - Create a Graphic
- HIGRAPHICM - Modify a Graphic
- HIGRAPHICUP - Upgrade SS2000W Graphic to SSWeb Java-Based Graphic (1)
- HIGRAPHICUP-5 - Upgrade SS2000W Graphics to SSWeb Java-Based Graphics (2-5)
- TEXTMOD - Customized Modifications
- MODCONFIG-4 - Modbus Configuration
- MODCONFIG-12 - Modbus Configuration
- BACCONFIG-4 - BACnet Configuration
- BACCONFIG-12 - BACnet Configuration
- 2.2.1 SITECONFIG-SVC - SiteScan Configuration Service Agreement
- 2.3 Gateway Modules
- 2.4 SiteLink Modules
- 2.5 Site I/O Modules
- 2.6 Stand-Alone Monitoring Modules
- 2.7 Module Accessories
- 2.8 ARCnet Communication Enhancement Devices
- 2.8.1 ARC156-KIT - ARCnet Kit
- 2.8.2 Other ARCnet Parts
- ARCDIAG485 - ARCnet156 Diagnostics Board
- ARCDIAG485WO - ARCnet156 Diagnostics Board Without Enclosure
- ARCPROT485 - ARCnet156 Surge Protection Board
- ARCPROT485WO - ARCnet156 Surge Protection Board Without Enclosure
- ARCREP485 - ARCnet156 Repeater Board (Signal Booster)
- ARCREP485WO - ARCnet156 Repeater Board Without Enclosure
- 2.9 Third-Party Interfaces
- 3.0 Application and Configuration
- 4.0 Upgrading SiteScan 2000 Systems to SiteScan Web
- 5.0 Third-Party and Building Management Interfaces
- 5.1 SiteScan Web and BACnet/IP to BMS
- 5.2 BACnet/IP to BMS Without a SiteScan Web Front-End
- 5.3 BMS Front-End Interfacing to Liebert Equipment by EIA-485 Modbus
- 5.4 SiteTPI-E with OpenComms NIC (or OpenComms 485)
- 5.5 Basic SiteTPI-E with Third-Party Equipment
- 5.6 SiteTPI-E and Third-Party Equipment with Different Modbus Protocol
- 6.0 ARCnet156
- 7.0 Wiring Guidelines
- Appendix A - Terminology

ARCnet156
34
6.7 Upgrading to ARC156
Before upgrading a legacy CMnet to ARC156, you must:
• Ensure adequate wiring. See 6.4 - Wiring Recommendations for details.
• Verify the network configuration is acceptable. See 6.2 - Segment Requirements.
• Use the appropriate network accessories—for example, 120 Ohm terminators and REP485
repeaters.
• Make sure all modules are capable of using Exec 6.0 or later. Refer to the Technical Instructions
for each module or to the Technical Handbook to determine this.
Follow these steps to upgrade the CMnet to ARC156:
1. While the CMnet is running at 38.4 Kbps or 9600 bps, transfer an Exec 6.0 (or higher) driver into
every module.
This can be done over a Direct Connection through a gateway module, or by setting the module for
38.4 Kbps or 9600 bps and Direct Network connecting to the module’s Access Port using an APT
in 485 mode.
2. Add a 120 Ohm terminator to each end of the network segment.
3. Add at least one ARC156-KIT to the middle of the network segment. Set the bias jumper to add
bias.
You can have more than one ARC156-KIT per network segment, but no more than one
ARC156-KIT should have the bias jumper set to add bias.
4. Go to each module and set the CMnet baud rate jumper for 156 Kbps communication.
Once you change the module’s baud rate, the module can no longer communicate on the CMnet.
When all modules are set to use 156 Kbps communications, a network reconfiguration is required
to start the ARC156 CMnet.
5. To reconfigure the CMnet immediately, remove and then restore power to one of the modules.
Otherwise, wait up to 30 minutes for the modules to reconfigure themselves.
6. Add other devices (like a REP485 or PROT485) to the CMnet as necessary to improve the signal
quality.
NOTE
A CMnet divided into segments may experience several reconfigurations until all the segments
are synchronized.