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

Third-Party and Building Management Interfaces
30
5.6 SiteTPI-E and Third-Party Equipment with Different Modbus Protocol
Customer wants to monitor third-party equipment with SiteScan Web. The third-party equipment
supports Modbus, but each type supports a different Modbus interface. The Modbus protocol on the
UPS supports 2-wire interface; the air equipment supports 4-wire Modbus interface.
5.6.1 Target Application
A typical application might be:
• Third-party equipment with different Modbus interfaces
• Existing system is SiteScan Web
• 5 third-party UPSs that support 2-wire Modbus interface
• 10 third-party air units that support 4-wire Modbus interface
5.6.2 Description
It is important to determine what type of Modbus interface the third-party equipment supports. For
this configuration, one SiteTPI-E will be used for the 2-wire Modbus devices and a separate SiteTPI-E
will be used for the 4-wire Modbus equipment. The order requires five TPICONFIGs, two for the UPS
equipment and three for the third-party environmental equipment.
Note: This order requires HIGRAPHIC-M to add the third-party equipment to the existing SiteScan
Web graphics.
5.6.3 Bill of Materials
Figure 19 Example of SiteTPI-E and third-party equipment with different Modbus protocol
Table 20 Bill of materials: SiteTPI-E and third-party equipment with different Modbus protocol
Qty. Mktg. P/N Description
2 SiteTPI-E TPI to integrate Modbus device into SiteScan Web
5 TPICONFIG Includes custom programming of up to 100 mapped Modbus data points
2 XFMR24 External power supply - 120VAC/24VAC
2 HIGRAPHIC-M Modification to an existing floor plan or graphic
Note: The bill of materials does not include LGS startup part numbers. Most LGS startup part numbers are added automatically
when ordering.
Customer Network
SiteScan Web
Server
2 – Wire Modbus
4 – Wire Modbus