Tipify Adio Extension
The tipAdioExt provides support for local analog and digital IO. The Adio Extension provides a connector for interpreting pulse counts as Demand and Usage.
Hardware Connectors
The 245 provides inputs on the rear of the device as shown below. The Adio Extension is responsible to interpreting pulses and signals connected through the Pulse Input, RS485, and the RS23s connectors.

NOTE: Wire connected to the Pulse Inputs should be 28 - 14 AWG.
Verify installation of the Tipify Adio Extension

Note: The "tipAdioExt" should come preinstalled in your version of Skyspark hosted by Tipify on the T-Star 245.
1. Login into the Skyspark environment through a valid Superuser or Admin account.
2. Navigate to the Host App and select the Install tab.
3. Under the Install Tab scroll down till you find the "tipAdioExt" extension under the name column.
Enabling the Tipify Adio Extension

Note: Enabling the ADIO extension is done on a per project basis in Skyspark and can not be done on the Host Level.
1. Login into the Skyspark environment through a valid Superuser or Admin account.
2. Navigate to an active project, then the Settings App.
3. Under the Exts Tab of the Settings App, highlight the "adio" extension.
4. If the "adio" extension status reads "disabled" select and highlight the "adio" extension and press the Enable button in the upper left-hand corner.
Adio Connectors
Adio connectors are specified with adioConn tag.
For local IO, the adioLocal tag is required:
- adioConn
- adioLocal
- dis: "Local IO"
Digital Inputs
Adio exposes digital inputs as Bool points:
- adioConnRef: @conn
- adioCur: "di1"
- kind: "Bool"
- curValue: false
- curStatus: "ok"
Electric Metering
For devices supporting high speed pulse counting on their digital inputs, a special subsystem is available specifically for electric meter applications. When available, the TipAdioExt will expose two additional points for each pulse counter: kw and kwh.
These points behave a bit differently then standard points in the connector framework. They handle history collection internally in order to guarantee that logging occurs exactly at the top of the minute for their configured interval (i.e. 0:15, 0:30, 0:45) regardless of when device was booted.
When the kwh point is learned into an equip with the Builder app, it will already be fully configured for use:
- adioConnRef: @conn
- adioCur: "kwh1"
- adioHisInterval: 15min
- navName: "kWh 1"
- energy
- his
- kind: "Number"
- unit: "kWh"
- tz: "New_York"

Note: You can modify the logging interval by adjusting the adioHisInterval tag, where the valid range is 1min to 60min.
The kwh logs pulse counts as deltas between its adioHisInterval range:
2014-05-09T00:15:00-04:00 New_York, 7kW
2014-05-09T00:30:00-04:00 New_York, 8kW
2014-05-09T00:45:00-04:00 New_York, 5kW
2014-05-09T01:00:00-04:00 New_York, 3kW
2014-05-09T01:15:00-04:00 New_York, 4kW
2014-05-09T01:30:00-04:00 New_York, 6kW
To calculate totalized values you will need to apply a rollup:
read(@id).hisRead(today).hisRollupAuto(1hr)
2014-05-09T01:00:00-04:00 New_York, 23kW
2014-05-09T02:00:00-04:00 New_York, 17kW
2014-05-09T03:00:00-04:00 New_York, 18kW
2014-05-09T04:00:00-04:00 New_York, 20kW
Likewise the kw point will be pre-configured when learned:
- adioConnRef: @conn
- adioCur: "kw1"
- adioKwWindow: 15min
- adioHisInterval: 15min
- navName: "kW 1"
- power
- his
- kind: "Number"
- unit: "kW"
- tz: "New_York"
The kw point has one additional tag adioKwWindow which is used to calculate the real-time instantaneous demand value. The range for this tag is also
1min to 60min. This value is calculated on a rolling 30sec sliding window over the configured window.
Both kw and kwh support directly scaling the values read from the meter. This can be configured by adding the adioScale tag (+, -, /, * operators are
supported):
adioScale: "* 1000"