Ruby - Energy Monitor Bricklet

This is the description of the Ruby API bindings for the Energy Monitor Bricklet. General information and technical specifications for the Energy Monitor Bricklet are summarized in its hardware description.

An installation guide for the Ruby API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (example_simple.rb)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
#!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-

require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_energy_monitor'

include Tinkerforge

HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Energy Monitor Bricklet

ipcon = IPConnection.new # Create IP connection
em = BrickletEnergyMonitor.new UID, ipcon # Create device object

ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected

# Get current Energy Data as [voltage, current, energy, real_power, apparent_power,
#                             reactive_power, power_factor, frequency]
energy_data = em.get_energy_data

puts "Voltage: #{energy_data[0]/100.0} V"
puts "Current: #{energy_data[1]/100.0} A"
puts "Energy: #{energy_data[2]/100.0} Wh"
puts "Real Power: #{energy_data[3]/100.0} h"
puts "Apparent Power: #{energy_data[4]/100.0} VA"
puts "Reactive Power: #{energy_data[5]/100.0} VAR"
puts "Power Factor: #{energy_data[6]/1000.0}"
puts "Frequency: #{energy_data[7]/100.0} Hz"

puts 'Press key to exit'
$stdin.gets
ipcon.disconnect

Callback

Download (example_callback.rb)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
#!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-

require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_energy_monitor'

include Tinkerforge

HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Energy Monitor Bricklet

ipcon = IPConnection.new # Create IP connection
em = BrickletEnergyMonitor.new UID, ipcon # Create device object

ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected

# Register Energy Data callback
em.register_callback(BrickletEnergyMonitor::CALLBACK_ENERGY_DATA) do |voltage, current,
                                                                      energy, real_power,
                                                                      apparent_power,
                                                                      reactive_power,
                                                                      power_factor,
                                                                      frequency|
  puts "Voltage: #{voltage/100.0} V"
  puts "Current: #{current/100.0} A"
  puts "Energy: #{energy/100.0} Wh"
  puts "Real Power: #{real_power/100.0} h"
  puts "Apparent Power: #{apparent_power/100.0} VA"
  puts "Reactive Power: #{reactive_power/100.0} VAR"
  puts "Power Factor: #{power_factor/1000.0}"
  puts "Frequency: #{frequency/100.0} Hz"
  puts ''
end

# Set period for Energy Data callback to 1s (1000ms)
em.set_energy_data_callback_configuration 1000, false

puts 'Press key to exit'
$stdin.gets
ipcon.disconnect

API

All methods listed below are thread-safe.

Basic Functions

BrickletEnergyMonitor::new(uid, ipcon) → energy_monitor
Parameters:
  • uid -- str
  • ipcon -- IPConnection

Creates an object with the unique device ID uid:

energy_monitor = BrickletEnergyMonitor.new 'YOUR_DEVICE_UID', ipcon

This object can then be used after the IP Connection is connected (see examples above).

BrickletEnergyMonitor#get_energy_data → [int, int, int, int, int, int, int, int]

Returns all of the measurements that are done by the Energy Monitor Bricklet.

  • Voltage (V): Voltage RMS with a resolution of 10mV (example: 230.05V = 23005)
  • Current (A): Current RMS with a resolution of 10mA (example: 1.42A = 142)
  • Energy (Wh): Energy (integrated over time) with a resolution of 10mWh (example: 1.1kWh = 110000)
  • Real Power (W): Real Power with a resolution of 10mW (example: 1234.56W = 123456)
  • Apparent Power (VA): Apparent Power with a resolution of 10mVA (example: 1234.56VA = 123456)
  • Reactive Power (VAR): Reactive Power with a resolution of 10mVAR (example: 1234.56VAR = 123456)
  • Power Factor: Power Factor with a resolution of 1/1000 (example: PF 0.995 = 995)
  • Frequency (Hz): AC Frequency of the mains voltage with a resolution of 1/100 Hz (example: 50Hz = 5000)

The frequency is recalculated every 6 seconds.

All other values are integrated over 10 zero-crossings of the voltage sine wave. With a standard AC mains voltage frequency of 50Hz this results in a 5 measurements per second (or an integration time of 200ms per measurement).

If no voltage transformer is connected, the Bricklet will use the current waveform to calculate the frequency and it will use an integration time of 10 zero-crossings of the current waveform.

The returned array has the values voltage, current, energy, real_power, apparent_power, reactive_power, power_factor and frequency.

BrickletEnergyMonitor#reset_energy → nil

Sets the energy value (see #get_energy_data) back to 0Wh.

BrickletEnergyMonitor#get_waveform → [int, int, ..1533x.., int]

Returns a snapshot of the voltage and current waveform. The values in the returned array alternate between voltage and current. The data from one getter call contains 768 data points for voltage and current, which correspond to about 3 full sine waves.

The voltage is given with a resolution of 100mV and the current is given with a resolution of 10mA.

This data is meant to be used for a non-realtime graphical representation of the voltage and current waveforms.

BrickletEnergyMonitor#get_transformer_status → [bool, bool]

Returns true if a voltage/current transformer is connected to the Bricklet.

The returned array has the values voltage_transformer_connected and current_transformer_connected.

BrickletEnergyMonitor#set_transformer_calibration(voltage_ratio, current_ratio, phase_shift) → nil
Parameters:
  • voltage_ratio -- int
  • current_ratio -- int
  • phase_shift -- int

Sets the transformer ratio for the voltage and current transformer in 1/100 form.

Example: If your mains voltage is 230V, you use 9V voltage transformer and a 1V:30A current clamp your voltage ratio is 230/9 = 25.56 and your current ratio is 30/1 = 30.

In this case you have to set the values 2556 and 3000 for voltage ratio and current ratio.

The calibration is saved in non-volatile memory, you only have to set it once.

By default the voltage ratio is set to 1923 and the current ratio is set to 3000.

Set the phase shift to 0. It is for future use and currently not supported by the Bricklet.

BrickletEnergyMonitor#get_transformer_calibration → [int, int, int]

Returns the transformer calibration as set by #set_transformer_calibration.

The returned array has the values voltage_ratio, current_ratio and phase_shift.

BrickletEnergyMonitor#calibrate_offset → nil

Calling this function will start an offset calibration. The offset calibration will integrate the voltage and current waveform over a longer time period to find the 0 transition point in the sine wave.

The Bricklet comes with a factory-calibrated offset value, you should not have to call this function.

If you want to re-calibrate the offset we recommend that you connect a load that has a smooth sinusoidal voltage and current waveform. Alternatively you can also short both inputs.

The calibration is saved in non-volatile memory, you only have to set it once.

Advanced Functions

BrickletEnergyMonitor#get_api_version → [int, int, int]

Returns the version of the API definition (major, minor, revision) implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.

BrickletEnergyMonitor#get_response_expected(function_id) → bool
Parameters:function_id -- int

Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.

For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by #set_response_expected. For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

  • BrickletEnergyMonitor::FUNCTION_RESET_ENERGY = 2
  • BrickletEnergyMonitor::FUNCTION_SET_TRANSFORMER_CALIBRATION = 5
  • BrickletEnergyMonitor::FUNCTION_CALIBRATE_OFFSET = 7
  • BrickletEnergyMonitor::FUNCTION_SET_ENERGY_DATA_CALLBACK_CONFIGURATION = 8
  • BrickletEnergyMonitor::FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletEnergyMonitor::FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletEnergyMonitor::FUNCTION_RESET = 243
  • BrickletEnergyMonitor::FUNCTION_WRITE_UID = 248
BrickletEnergyMonitor#set_response_expected(function_id, response_expected) → nil
Parameters:
  • function_id -- int
  • response_expected -- bool

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

  • BrickletEnergyMonitor::FUNCTION_RESET_ENERGY = 2
  • BrickletEnergyMonitor::FUNCTION_SET_TRANSFORMER_CALIBRATION = 5
  • BrickletEnergyMonitor::FUNCTION_CALIBRATE_OFFSET = 7
  • BrickletEnergyMonitor::FUNCTION_SET_ENERGY_DATA_CALLBACK_CONFIGURATION = 8
  • BrickletEnergyMonitor::FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletEnergyMonitor::FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletEnergyMonitor::FUNCTION_RESET = 243
  • BrickletEnergyMonitor::FUNCTION_WRITE_UID = 248
BrickletEnergyMonitor#set_response_expected_all(response_expected) → nil
Parameters:response_expected -- bool

Changes the response expected flag for all setter and callback configuration functions of this device at once.

BrickletEnergyMonitor#get_spitfp_error_count → [int, int, int, int]

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

The returned array has the values error_count_ack_checksum, error_count_message_checksum, error_count_frame and error_count_overflow.

BrickletEnergyMonitor#set_bootloader_mode(mode) → int
Parameters:mode -- int

Sets the bootloader mode and returns the status after the requested mode change was instigated.

You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

The following constants are available for this function:

  • BrickletEnergyMonitor::BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletEnergyMonitor::BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_OK = 0
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_INVALID_MODE = 1
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_NO_CHANGE = 2
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BrickletEnergyMonitor::BOOTLOADER_STATUS_CRC_MISMATCH = 5
BrickletEnergyMonitor#get_bootloader_mode → int

Returns the current bootloader mode, see #set_bootloader_mode.

The following constants are available for this function:

  • BrickletEnergyMonitor::BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletEnergyMonitor::BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletEnergyMonitor::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
BrickletEnergyMonitor#set_write_firmware_pointer(pointer) → nil
Parameters:pointer -- int

Sets the firmware pointer for #write_firmware. The pointer has to be increased by chunks of size 64. The data is written to flash every 4 chunks (which equals to one page of size 256).

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

BrickletEnergyMonitor#write_firmware(data) → int
Parameters:data -- [int, int, ..61x.., int]

Writes 64 Bytes of firmware at the position as written by #set_write_firmware_pointer before. The firmware is written to flash every 4 chunks.

You can only write firmware in bootloader mode.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

BrickletEnergyMonitor#set_status_led_config(config) → nil
Parameters:config -- int

Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.

The following constants are available for this function:

  • BrickletEnergyMonitor::STATUS_LED_CONFIG_OFF = 0
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_ON = 1
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletEnergyMonitor#get_status_led_config → int

Returns the configuration as set by #set_status_led_config

The following constants are available for this function:

  • BrickletEnergyMonitor::STATUS_LED_CONFIG_OFF = 0
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_ON = 1
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletEnergyMonitor::STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletEnergyMonitor#get_chip_temperature → int

Returns the temperature in °C as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.

BrickletEnergyMonitor#reset → nil

Calling this function will reset the Bricklet. All configurations will be lost.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

BrickletEnergyMonitor#write_uid(uid) → nil
Parameters:uid -- int

Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.

We recommend that you use Brick Viewer to change the UID.

BrickletEnergyMonitor#read_uid → int

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

BrickletEnergyMonitor#get_identity → [str, str, str, [int, int, int], [int, int, int], int]

Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.

The position can be 'a', 'b', 'c' or 'd'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

The returned array has the values uid, connected_uid, position, hardware_version, firmware_version and device_identifier.

Callback Configuration Functions

BrickletEnergyMonitor#register_callback(callback_id) { |param [, ...]| block } → nil
Parameters:callback_id -- int

Registers the given block with the given callback_id.

The available callback IDs with corresponding function signatures are listed below.

BrickletEnergyMonitor#set_energy_data_callback_configuration(period, value_has_to_change) → nil
Parameters:
  • period -- int
  • value_has_to_change -- bool

The period in ms is the period with which the ::CALLBACK_ENERGY_DATA callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

The default value is (0, false).

BrickletEnergyMonitor#get_energy_data_callback_configuration → [int, bool]

Returns the callback configuration as set by #set_energy_data_callback_configuration.

The returned array has the values period and value_has_to_change.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the #register_callback function of the device object. The first parameter is the callback ID and the second parameter is a block:

energy_monitor.register_callback BrickletEnergyMonitor::CALLBACK_EXAMPLE, do |param|
  puts "#{param}"
end

The available constants with inherent number and type of parameters are described below.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

BrickletEnergyMonitor::CALLBACK_ENERGY_DATA
Parameters:
  • voltage -- int
  • current -- int
  • energy -- int
  • real_power -- int
  • apparent_power -- int
  • reactive_power -- int
  • power_factor -- int
  • frequency -- int

This callback is triggered periodically according to the configuration set by #set_energy_data_callback_configuration.

The parameters are the same as #get_energy_data.

Constants

BrickletEnergyMonitor::DEVICE_IDENTIFIER

This constant is used to identify a Energy Monitor Bricklet.

The #get_identity() function and the IPConnection::CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.

BrickletEnergyMonitor::DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Energy Monitor Bricklet.