1. ICC's ETH-1000 GatewayICC's ETH-1000 Gateway
●
Problem: client needs to integrate vendor'sProblem: client needs to integrate vendor's
energy monitoring platform intoenergy monitoring platform into
homegrown data acquisition systemhomegrown data acquisition system
●
One approach: directly connect databasesOne approach: directly connect databases
– Vendor reluctant to assist with proprietaryVendor reluctant to assist with proprietary
DB implementationDB implementation
●
Solution: multi-protocol gatewaySolution: multi-protocol gateway
– BACnetBACnet
– ModbusModbus

2. Gateway OverviewGateway Overview
●
Support for myriad protocolsSupport for myriad protocols
●
Single Ethernet portSingle Ethernet port
●
Mature productMature product

3. Config BasicsConfig Basics
●
Gateway configured with 2 “sides”Gateway configured with 2 “sides”
– BACnet: object mapped to database locationsBACnet: object mapped to database locations
– Modbus: registers mapped to database locationsModbus: registers mapped to database locations
BACnet config
AI5 =
DB location 2
AI6 =
DB location 4
...
Gateway DB
Loc2 =
Loc4 =
...
Modbus config
R100 =
DB location 2
R101 =
DB location 4
...

4. Data Flow: BACnet SideData Flow: BACnet Side
●
At set intervals, gateway pollsAt set intervals, gateway polls
BACnet devicesBACnet devices
– 1. REQ: what is AI5's value1. REQ: what is AI5's value
– 2. ACK: AI5 = 852. ACK: AI5 = 85
Vendor
Platform
(BACnet)
1. What is
Analog Input #5
(Outside Air)?
2. AI5 =
85

5. Data Flow: Storing ValuesData Flow: Storing Values
●
Results are stored in local DBResults are stored in local DB
– 3. AI5 points to Location 23. AI5 points to Location 2
BACnet config
AI5 =
DB location 2
AI6 =
DB location 4
...
Gateway DB
Loc2 = 85
Loc4 = x
...
Modbus config
R100 =
DB location 2
R101 =
DB location 4
...
3.

6. Data Flow: Modbus QueriesData Flow: Modbus Queries
●
At regular intervals, logger pollsAt regular intervals, logger polls
gateway devicegateway device
– 4. Query: what is Register 100's4. Query: what is Register 100's
valuevalue
eGauge
Logger
(Modbus)
4. What is
Register 100?

7. Data Flow: Returning ValuesData Flow: Returning Values
●
Modbus process executes database lookupModbus process executes database lookup
– 5. Location 2 returns 855. Location 2 returns 85
BACnet config
AI5 =
DB location 2
AI6 =
DB location 4
...
Gateway DB
Loc2 = 85
Loc4 = x
...
.
Modbus config
R100 =
DB location 2
R101 =
DB location 4
...
5.

8. Data Flow: Modbus ResponsesData Flow: Modbus Responses
●
Modbus process sends valueModbus process sends value
– 6. Register 100 = 856. Register 100 = 85
●
Logger values can be viewedLogger values can be viewed
with dashboard and/or insertedwith dashboard and/or inserted
into SQL databaseinto SQL database
– eGauge XML-based APIeGauge XML-based API
enables SQL integrationenables SQL integration
eGauge
Logger
(Modbus)
6. R100 = 85.
To SQL
database

9. Gateway Value PropositionGateway Value Proposition
●
Can be used in many environmentsCan be used in many environments
●
Disparate monitoring systems can be integratedDisparate monitoring systems can be integrated
for more effective business intelligencefor more effective business intelligence
●
Automated processes create efficient data flowAutomated processes create efficient data flow
●
Need for expensive custom programmingNeed for expensive custom programming
mitigatedmitigated
●
Quick configuration and deploymentQuick configuration and deployment