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
31
6.0 ARCNET156
6.1 ARCnet156 CMnet Components
The SSWEB-Liebert gateways and control modules communicate using ARCnet156, a token-passing
protocol running at 156 Kbps. ARCnet156 requires network boards to properly terminate, bias, pro-
tect and repeat data transmitted over the twisted pair EIA-485 segment.
An ARC156-Kit should be used for every gateway module. The kit filters out some signal noise and
provides diagnostic information about the ARCnet156 network. Two 120 ohm terminators are
included with each ARC156-Kit.
6.2 Segment Requirements
An ARCnet156 segment is an arrangement of gateways, control modules and ARCnet156 devices up
to 2,000 ft. (610m) long.
A segment must:
• Be wired in a daisy chain (see Figure 20).
• Have an ARC156-KIT installed in the middle of the segment.
• Have a PROT485 installed at each building entrance and exit.
• Have one ARC156-KIT for every 32 modules and each 2,000 ft. (610m) of equipment and cabling.
• Not exceed 50 modules including ARCnet enhancement devices.
• Have a 120 ohm terminator at each end unless the segment is less than 10 ft. (3m) long.
Figure 20 Acceptable daisy chain configurations
NOTE
Each segment must use a Magnum ARC cable.
Term
Term
Term
Term
Configuration A Configuration B