This is the description of the Shell 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 Shell 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 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Color Bricklet 2.0
# Get current color
tinkerforge call color-v2-bricklet $uid get-color
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Color Bricklet 2.0
# Handle incoming color callbacks
tinkerforge dispatch color-v2-bricklet $uid color &
# Set period for color callback to 0.1s (100ms)
tinkerforge call color-v2-bricklet $uid set-color-callback-configuration 100 false
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Possible exit codes for all tinkerforge
commands are:
argparse
module is missingThe common options of the call
and dispatch
commands are documented
here. The specific command structure is shown below.
call
color-v2-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Color Bricklet 2.0. It can take several
options:
--help
shows help for the specific call
command and exits--list-functions
shows a list of known functions of the Color Bricklet 2.0 and exitsdispatch
color-v2-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Color Bricklet 2.0. It can
take several options:
--help
shows help for the specific dispatch
command and exits--list-callbacks
shows a list of known callbacks of the Color Bricklet 2.0 and exitscolor-v2-bricklet
<uid> <function>
[<option>..] [<argument>..]¶Parameters: |
|
---|
The <function>
to be called can take different options depending of its
kind. All functions can take the following options:
--help
shows help for the specific function and exitsGetter functions can take the following options:
--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response
requests response and waits for itThe --expect-response
option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
color-v2-bricklet
<uid> <callback>
[<option>..]¶Parameters: |
|
---|
The <callback>
to be dispatched can take several options:
--help
shows help for the specific callback and exits--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)color-v2-bricklet
<uid> get-color
¶Output: |
|
---|
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 color
callback and set the period with
set-color-callback-configuration
.
color-v2-bricklet
<uid> get-illuminance
¶Output: |
|
---|
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
illuminance
callback. You can set the callback configuration
with set-illuminance-callback-configuration
.
color-v2-bricklet
<uid> get-color-temperature
¶Output: |
|
---|
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
color-temperature
callback. You can set the callback configuration
with set-color-temperature-callback-configuration
.
color-v2-bricklet
<uid> set-light
<enable>¶Parameters: |
|
---|---|
Output: |
|
Turns the white LED on the Bricklet on/off.
color-v2-bricklet
<uid> get-light
¶Output: |
|
---|
Returns the value as set by set-light
.
color-v2-bricklet
<uid> set-configuration
<gain> <integration-time>¶Parameters: |
|
---|---|
Output: |
|
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 symbols are available for this function:
For <gain>:
For <integration-time>:
color-v2-bricklet
<uid> get-configuration
¶Output: |
|
---|
Returns the configuration as set by set-configuration
.
The following symbols are available for this function:
For gain:
For integration-time:
color-v2-bricklet
<uid> get-spitfp-error-count
¶Output: |
|
---|
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.
color-v2-bricklet
<uid> set-status-led-config
<config>¶Parameters: |
|
---|---|
Output: |
|
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 symbols are available for this function:
For <config>:
color-v2-bricklet
<uid> get-status-led-config
¶Output: |
|
---|
Returns the configuration as set by set-status-led-config
The following symbols are available for this function:
For config:
color-v2-bricklet
<uid> get-chip-temperature
¶Output: |
|
---|
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.
color-v2-bricklet
<uid> reset
¶Output: |
|
---|
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!
color-v2-bricklet
<uid> get-identity
¶Output: |
|
---|
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.
color-v2-bricklet
<uid> set-color-callback-configuration
<period> <value-has-to-change>¶Parameters: |
|
---|---|
Output: |
|
The period is the period with which the 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.
color-v2-bricklet
<uid> get-color-callback-configuration
¶Output: |
|
---|
Returns the callback configuration as set by
set-color-callback-configuration
.
color-v2-bricklet
<uid> set-illuminance-callback-configuration
<period> <value-has-to-change> <option> <min> <max>¶Parameters: |
|
---|---|
Output: |
|
The period is the period with which the 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 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 symbols are available for this function:
For <option>:
color-v2-bricklet
<uid> get-illuminance-callback-configuration
¶Output: |
|
---|
Returns the callback configuration as set by set-illuminance-callback-configuration
.
The following symbols are available for this function:
For option:
color-v2-bricklet
<uid> set-color-temperature-callback-configuration
<period> <value-has-to-change> <option> <min> <max>¶Parameters: |
|
---|---|
Output: |
|
The period is the period with which the 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 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 symbols are available for this function:
For <option>:
color-v2-bricklet
<uid> get-color-temperature-callback-configuration
¶Output: |
|
---|
Returns the callback configuration as set by set-color-temperature-callback-configuration
.
The following symbols are available for this function:
For option:
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch color-v2-bricklet <uid> example
The available callbacks 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.
color-v2-bricklet
<uid> color
¶Output: |
|
---|
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 color
callback is only triggered if the color has changed since the
last triggering.
color-v2-bricklet
<uid> illuminance
¶Output: |
|
---|
This callback is triggered periodically according to the configuration set by
set-illuminance-callback-configuration
.
The parameter is the same as get-illuminance
.
color-v2-bricklet
<uid> color-temperature
¶Output: |
|
---|
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
.
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.
color-v2-bricklet
<uid> set-bootloader-mode
<mode>¶Parameters: |
|
---|---|
Output: |
|
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 symbols are available for this function:
For <mode>:
For status:
color-v2-bricklet
<uid> get-bootloader-mode
¶Output: |
|
---|
Returns the current bootloader mode, see set-bootloader-mode
.
The following symbols are available for this function:
For mode:
color-v2-bricklet
<uid> set-write-firmware-pointer
<pointer>¶Parameters: |
|
---|---|
Output: |
|
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.
color-v2-bricklet
<uid> write-firmware
<data>¶Parameters: |
|
---|---|
Output: |
|
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.
color-v2-bricklet
<uid> write-uid
<uid>¶Parameters: |
|
---|---|
Output: |
|
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.
color-v2-bricklet
<uid> read-uid
¶Output: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.