This is the description of the Ruby API bindings for the Color Bricklet 2.0. General information and technical specifications for the Color Bricklet 2.0 are summarized in its hardware description.
An installation guide for the Ruby API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
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 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_color_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Color Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
c = BrickletColorV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Get current color as [r, g, b, c]
color = c.get_color
puts "Color [R]: #{color[0]}"
puts "Color [G]: #{color[1]}"
puts "Color [B]: #{color[2]}"
puts "Color [C]: #{color[3]}"
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
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 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_color_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Color Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
c = BrickletColorV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Register color callback
c.register_callback(BrickletColorV2::CALLBACK_COLOR) do |r, g, b, c_|
puts "Color [R]: #{r}"
puts "Color [G]: #{g}"
puts "Color [B]: #{b}"
puts "Color [C]: #{c_}"
puts ''
end
# Set period for color callback to 0.1s (100ms)
c.set_color_callback_configuration 100, false
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
All functions listed below are thread-safe.
BrickletColorV2
::
new
(uid, ipcon) → color_v2¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
color_v2 = BrickletColorV2.new 'YOUR_DEVICE_UID', ipcon
This object can then be used after the IP Connection is connected.
BrickletColorV2
#
get_color
→ [int, int, int, int]¶Return Array: |
|
---|
Returns the measured color of the sensor.
The red (r), green (g), blue (b) and clear (c) colors are measured with four different photodiodes that are responsive at different wavelengths:
If you want to get the color periodically, it is recommended
to use the ::CALLBACK_COLOR
callback and set the period with
#set_color_callback_configuration
.
BrickletColorV2
#
get_illuminance
→ int¶Returns: |
|
---|
Returns the illuminance affected by the gain and integration time as
set by #set_configuration
. To get the illuminance in Lux apply this formula:
lux = illuminance * 700 / gain / integration_time
To get a correct illuminance measurement make sure that the color
values themselves are not saturated. The color value (R, G or B)
is saturated if it is equal to the maximum value of 65535.
In that case you have to reduce the gain, see #set_configuration
.
If you want to get the value periodically, it is recommended to use the
::CALLBACK_ILLUMINANCE
callback. You can set the callback configuration
with #set_illuminance_callback_configuration
.
BrickletColorV2
#
get_color_temperature
→ int¶Returns: |
|
---|
Returns the color temperature.
To get a correct color temperature measurement make sure that the color
values themselves are not saturated. The color value (R, G or B)
is saturated if it is equal to the maximum value of 65535.
In that case you have to reduce the gain, see #set_configuration
.
If you want to get the value periodically, it is recommended to use the
::CALLBACK_COLOR_TEMPERATURE
callback. You can set the callback configuration
with #set_color_temperature_callback_configuration
.
BrickletColorV2
#
set_light
(enable) → nil¶Parameters: |
|
---|
Turns the white LED on the Bricklet on/off.
BrickletColorV2
#
get_light
→ bool¶Returns: |
|
---|
Returns the value as set by #set_light
.
BrickletColorV2
#
set_configuration
(gain, integration_time) → nil¶Parameters: |
|
---|
Sets the configuration of the sensor. Gain and integration time can be configured this way.
For configuring the gain:
For configuring the integration time:
Increasing the gain enables the sensor to detect a color from a higher distance.
The integration time provides a trade-off between conversion time and accuracy. With a longer integration time the values read will be more accurate but it will take longer to get the conversion results.
The following constants are available for this function:
For gain:
For integration_time:
BrickletColorV2
#
get_configuration
→ [int, int]¶Return Array: |
|
---|
Returns the configuration as set by #set_configuration
.
The following constants are available for this function:
For gain:
For integration_time:
BrickletColorV2
#
get_spitfp_error_count
→ [int, int, int, int]¶Return Array: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
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.
BrickletColorV2
#
set_status_led_config
(config) → nil¶Parameters: |
|
---|
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:
For config:
BrickletColorV2
#
get_status_led_config
→ int¶Returns: |
|
---|
Returns the configuration as set by #set_status_led_config
The following constants are available for this function:
For config:
BrickletColorV2
#
get_chip_temperature
→ int¶Returns: |
|
---|
Returns the temperature 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.
BrickletColorV2
#
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!
BrickletColorV2
#
get_identity
→ [str, str, chr, [int, ...], [int, ...], int]¶Return Array: |
|
---|
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', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
BrickletColorV2
#
register_callback
(callback_id) { |param [, ...]| block } → nil¶Parameters: |
|
---|
Registers the given block
with the given callback_id
.
The available callback IDs with corresponding function signatures are listed below.
BrickletColorV2
#
set_color_callback_configuration
(period, value_has_to_change) → nil¶Parameters: |
|
---|
The period is the period with which the ::CALLBACK_COLOR
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.
BrickletColorV2
#
get_color_callback_configuration
→ [int, bool]¶Return Array: |
|
---|
Returns the callback configuration as set by
#set_color_callback_configuration
.
BrickletColorV2
#
set_illuminance_callback_configuration
(period, value_has_to_change, option, min, max) → nil¶Parameters: |
|
---|
The period is the period with which the ::CALLBACK_ILLUMINANCE
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.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the ::CALLBACK_ILLUMINANCE
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following constants are available for this function:
For option:
BrickletColorV2
#
get_illuminance_callback_configuration
→ [int, bool, chr, int, int]¶Return Array: |
|
---|
Returns the callback configuration as set by #set_illuminance_callback_configuration
.
The following constants are available for this function:
For option:
BrickletColorV2
#
set_color_temperature_callback_configuration
(period, value_has_to_change, option, min, max) → nil¶Parameters: |
|
---|
The period is the period with which the ::CALLBACK_COLOR_TEMPERATURE
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.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the ::CALLBACK_COLOR_TEMPERATURE
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following constants are available for this function:
For option:
BrickletColorV2
#
get_color_temperature_callback_configuration
→ [int, bool, chr, int, int]¶Return Array: |
|
---|
Returns the callback configuration as set by #set_color_temperature_callback_configuration
.
The following constants are available for this function:
For option:
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:
color_v2.register_callback BrickletColorV2::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.
BrickletColorV2
::
CALLBACK_COLOR
¶Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
#set_color_callback_configuration
. The parameter is the color
of the sensor as RGBC.
The ::CALLBACK_COLOR
callback is only triggered if the color has changed since the
last triggering.
BrickletColorV2
::
CALLBACK_ILLUMINANCE
¶Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
#set_illuminance_callback_configuration
.
The parameter is the same as #get_illuminance
.
BrickletColorV2
::
CALLBACK_COLOR_TEMPERATURE
¶Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
#set_color_temperature_callback_configuration
.
The parameter is the same as #get_color_temperature
.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
BrickletColorV2
#
get_api_version
→ [int, ...]¶Return Array: |
|
---|
Returns the version of the API definition 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.
BrickletColorV2
#
get_response_expected
(function_id) → bool¶Parameters: |
|
---|---|
Returns: |
|
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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletColorV2
#
set_response_expected
(function_id, response_expected) → nil¶Parameters: |
|
---|
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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletColorV2
#
set_response_expected_all
(response_expected) → nil¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletColorV2
#
set_bootloader_mode
(mode) → int¶Parameters: |
|
---|---|
Returns: |
|
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:
For mode:
For status:
BrickletColorV2
#
get_bootloader_mode
→ int¶Returns: |
|
---|
Returns the current bootloader mode, see #set_bootloader_mode
.
The following constants are available for this function:
For mode:
BrickletColorV2
#
set_write_firmware_pointer
(pointer) → nil¶Parameters: |
|
---|
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.
BrickletColorV2
#
write_firmware
(data) → int¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletColorV2
#
write_uid
(uid) → nil¶Parameters: |
|
---|
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.
BrickletColorV2
#
read_uid
→ int¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletColorV2
::
DEVICE_IDENTIFIER
¶This constant is used to identify a Color Bricklet 2.0.
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.
BrickletColorV2
::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Color Bricklet 2.0.