Overview

This section of our web site provides a list of auxiliary devices known to be compatible with eGauge and gives some detail on available measurements and how to configure them in eGauge.


Introduction


While the eGauge supports direct measurement of electrical power, voltage, current, and properties derived from those measurements (such as power factor or THD), many other physical quantities can be measured and recorded by the eGauge with the help of auxiliary devices. For example, there are auxiliary devices to measure and report temperature, humidity, CO2 level, solar irradiance level, volumetric flow rates, pulse counts from water meters, etc. The eGauge can read data from compatible auxiliary devices via the local network using hardwired Ethernet or powerline communication (HomePlug) as the physical media. External sensor data is then recorded on the eGauge internal memory in the same manner as direct measurements. Typically, each recorded quantity (for example, outdoor temperature) occupies one register in the eGauge and as such the number of quantities that can be recorded is limited only by the number of registers available on the eGauge.

Auxiliary devices with only a serial interface (typically RS-485 or RS-232) cannot directly communicate with an Ethernet network. However, such devices can be accommodated with a BF-430 serial-to-Ethernet converter (see below for more details).

Some auxiliary devices require configuration before they can be used. The extent of configuration depends on the nature of the device and the variables being measured. In particular, RS-485 devices need to have a unique address assigned. The installing party should be familiar with how to configure these devices; the device manufacturer should be contacted for configuration support.


Disclaimer

eGauge Systems cannot guarantee compatibility and support for documented or undocumented devices. Many factors, including network environment, changes to third-party device hardware or software, and other unforeseen issues will affect the compatibility and stability of communication. Any third-party hardware to be used with the eGauge should be tested and confirmed before assuming expected functionality. Direct eGauge troubleshooting is limited to eGauges available via the proxy-server.

The eGauge is configured to read from remote devices in SettingsInstallationRemote Devices. A remote device entry consists of a device name (typically descriptive of the remote device), protocol (for example, RS-485 or Modbus TCP) and a device address (IP address or MAC of the remote device, and may contain other information about the remote device). Examples and descriptions for these entries can be found along with the specific device information in this section of the website.

Please see the Remote Devices section in the eGauge configuration guide for additional information on configuring the eGauge for remote devices.


BF-430: RS-485 to Ethernet Converter


The Chiyu BF-430 is an RS-485/RS-232 to Ethernet converter that is required for serial communication to third-party devices (for example, Modbus RTU). The eGauge sends data to the BF-430 over the Ethernet network, and the BF-430 in turn sends the data to the third-party device over the serial line. When the device on the serial line responds, the BF-430 relays that data to the eGauge.

The BF-430 can accommodate one RS-232 slave device, or multiple RS-485 slave devices. If there are multiple slave devices on the RS-485 line, all devices must communicate using the same protocol and bus settings (including but not limited to: baud rate, parity, data bits, and stop bits). The RS-232 and RS-485 ports cannot be used simultaneously. Only one master unit (i.e., the eGauge) may request data from the BF-430 at a time.

The BF-430 is powered by 9–30Vdc, via power terminals or a standard barrel jack plug. The Chiyu BF-430 contains an embedded web server that is used for configuration and diagnostics.

The Chiyu BF-430 image is currently unavailable

The most common attributes that must be adjusted on the BF-430 are:

  • Baud rate
  • Data bits
  • Stop bits
  • Parity check

These attributes can be adjusted from the Serial Type menu under Advanced Setup, or the settings can be pre-set for specified devices prior to shipping when ordered from eGauge Systems. Please specify the device type(s) when ordering.

Some troubleshooting and verification can be done on the web interface of the BF-430. For example, verification of the correct serial settings from the Serial Type menu, and verification of communication on the serial port from the System Status menu. The full manual for the Chiyu BF-430 can be found here.


Modbus


The eGauge can read data via Modbus TCP and Modbus RTU. Modbus RTU is a serial protocol and requires an RS-485 to Ethernet converter as described in the previous section. Modbus TCP communicates directly on the TCP/IP network. Modbus RTU via a serial-to-Ethernet converter is not the same as Modbus TCP, and the eGauge must be configured appropriately.

Supported Modbus devices listed in the Third-Party device section have Modbus maps built into the eGauge device. If a Modbus RTU or Modbus TCP device is not listed, in-line definitions can be used to manually specify the Modbus map. See section Modbus Syntax below for more information.

To request implementation of a map, please email support@egauge.net . To expedite new device implementation, an eGauge with at least one functional in-line definition should be available on the proxy server for eGauge support to test.


Important

Device implementation by eGauge Systems is not guaranteed, and implementation time will vary.


Modbus Syntax


Modbus remote devices are defined by the address:
  DEVTYPE.SLAVE_ADDR@ADDR[:PORT]
Note: Modbus RTU requires prefixing the address with modbus://


The following table describes the full Modbus address format and syntax. In-line definitions may be used to allow the eGauge to read from arbitrary or unsupported Modbus devices.

VariableDefinition
DEVTYPE Remote device type or inline Modbus register definitions using the following syntax to define the following elements:
name=addr,[!]type[+offset] [*scale][,unit];
nameregister name
addrregister address
!indicates a read-only register
typeregister type ?
offsetadditive offset for register value
scalemultiplicative scale value for register value
unitphysical unit ?
SLAVE_ADDRThe Modbus address (0-255) of the device
ADDR RS-485 to Ethernet adapter MAC address, or IP address of host
PORT The port-number of the RS-485 to Ethernet adapter or host
Register TypeDescription
bit1-bit
s16signed 16-bit integer
u16unsigned 16-bit integer
s32signed 32-bit integer
s32llittle-endian signed 32-bit integer
u32unsigned 32-bit integer
u32llittle-endian unsigned 32-bit integer
s64signed 64-bit integer
u64unsigned 64-bit integer
floatfloat value
floatllittle-endian float value
doubledouble value
Unit CodePhysical Quantity
OhmResistance (Ω)
WPower (watt)
kWhEnergy (kWh)
degCTemperature (degrees Celsius)
m/sSpeed (meters per second)
mmLength (millimeter)
W/m^2Irradiance (watts per square meter)
msTime (millisecond)
sTime (seconds)
hTime (hour)
VVoltage (volt)
mVVoltage (millivolt)
ACurrent (ampere)
mACurrent (milliampere)
AsCharge (ampere-second)
AhCharge (ampere-hour)
mAhCharge (milliampere-hour)
HzFrequency (hertz)
%Percentage (%)
m3/s Volumetric flow (cubic meters per second)
m3Volume (cubic meters)
PaPressure (pascal)
kPaPressure (kilopascal)
degAngle (degree)
RHRelative humidity (%)

Examples:

Modbus TCP:

  • badger3050.1@192.168.1.21
  • volume=101,u32,m3.1@192.168.1.21

Modbus RTU:

  • modbus://badger3050.1@000ee3026a50
  • modbus://volume=101,u32,m3.1@000ee3026a50:50001

Analog/Digital Input Devices


Product Device

Configuration

Device NameProtocolDevice Address ?
ControlByWeb X-320ControlByWebIP_ADDR
Device Address Configuration
VariableDescription
IP_ADDRIP address of ControlByWeb X-320
PORTPort to use for ControlByWeb (default: 80)
Device Address Example(s)
192.168.1.21
192.168.1.21:8080

Environmental Sensors


Product Device

Configuration

Device NameProtocolDevice Address ?
IMT Solar Irradiance SensorRS485modbus://imt_si.SLAVE_ADDR@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
SLAVE_ADDRSlave (serial) address of Modbus device
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
modbus://imt_si.2@000ee325a6f4
Product Device

Configuration

Device NameProtocolDevice Address ?
Temperature @lert WiFi Editiontemperature @lertIP_ADDR
Device Address Configuration
VariableDescription
IP_ADDRIP Address of Temperature @lert device
Device Address Example(s)
192.168.1.21
Notes
The eGauge will only fetch registers for sensors configured on the Temperature @lert device.
Product Device

Configuration

Device NameProtocolDevice Address ?
Tempco CO2 SensorRS485modbus://temco_co2_e.SLAVE_ADDR@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
SLAVE_ADDRSlave (serial) address of Modbus device
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
modbus://temco_co2_e.1@000ee325a6f4
modbus://temco_co2_e.3@000ee325a6f4:10000
Notes
Ethernet communication on the Tempco CO2 Sensor is not yet supported.
Product Device

Configuration

Device NameProtocolDevice Address ?
SMA Sunny SensorBoxRS485sma://@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
sma://@000ee325a6f4
sma://@192.168.1.21
Notes
The SMA SunnySensorbox has been discontinued in 2015.

Ambient temperature and wind speed measurements require add-on sensors.

Available measurements are fetched live from the SensorBox, so additional unsupported measurements may show up based on the SensorBox version.
Product Device

Configuration

Device NameProtocolDevice Address ?
Lufft WS501-UMBRS485modbus://lufft.SLAVE_ADDR@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
SLAVE_ADDRSlave (serial) address of Modbus device
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
modbus://lufft.1@000ee325a6f4

Flow Meters


Product Device

Configuration

Device NameProtocolDevice Address ?
badger3050RS485modbus://badger3050.SLAVE_ADDR@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
SLAVE_ADDRSlave (serial) address of Modbus device
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
modbus://badger3050.1@000ee325a6f4
modbus://badger3050.1@000ee325a6f4:10000

Heating Systems


Product Device

Configuration

Device NameProtocolDevice Address ?
Alpha-Innotec Luxtronik 2Alpha-Innotec Luxtronik 2DEV_ADDR
Device Address Configuration
VariableDescription
DEV_ADDRHostname or IP address of device
Device Address Example(s)
192.168.1.21

Inverters


Product Device

Configuration

Device NameProtocolDevice Address ?
ABB Aurora InvertersRS485po://SER_ADDR@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
SER_ADDRSerial address of inverter
CONV_ADDRSerial-to-Ethernet converter MAC or IP address
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
po://@000ee325a6f4
po://2@000ee325a6f4
Notes
ABB Power-One inverters with RS-485 serial output are supported.

If SER_ADDR is omitted, the eGauge will auto-enumerate to locate all inverters. If this fails, try specifying the SER_ADDR option and creating one remote device entry for each inverter.
Product Device

Configuration

Device NameProtocolDevice Address ?
SMA InvertersRS485sma://@CONV_ADDR[:PORT]
Device Address Configuration
VariableDescription
CONV_ADDRSerial-to-Ethernet converter MAC or IP addres
PORTTCP port to use on serial-to-Ethernet converter (default: 50000)
Device Address Example(s)
sma://@000ee325a6f4
Notes
SMA inverters with RS-485 serial output are supported.

Available measurements are fetched from the inverter, and will vary based on inverter model. Consult the SMA inverter manual for available parameters.

Remote eGauge


Product Device

Configuration

Device NameProtocolDevice Address ?
Remote eGauge via TCPremote eGauge via TCPDEV_ADDR
Device Address Configuration
VariableDescription
DEV_ADDRHostname or IP address of eGauge device
Device Address Example(s)
eGauge9999
192.168.1.88
Notes
TCP communication between eGauges is slower than UDP, but may be the chosen option if UDP communication is unavailable between the devices. Remote TCP communication over the eGauge proxy server is not recommended due to significantly higher lag times. Remote eGauge via TCP will not work if the slave eGauge has site-wide password protection.

The available measurements an eGauge has to offer will vary based on the installation configuration.
Product Device

Configuration

Device NameProtocolDevice Address ?
Remote eGauge via UDPremote eGauge via UDPDEV_ADDR
Device Address Configuration
VariableDescription
DEV_ADDRHostname or IP address of eGauge device
Device Address Example(s)
eGauge9999
192.168.1.88
Notes
UDP communication is the preferred method between eGauge devices. UDP communication is faster than TCP. eGauges communicating via UDP typically must be on the same local area network, or allow UDP communication to pass between the two.

The available measurements an eGauge has to offer will vary based on the installation configuration.