This is the description of the MQTT 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 MQTT API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 6 | # Change XYZ to the UID of your Color Bricklet 2.0
setup:
# Get current color
subscribe to tinkerforge/response/color_v2_bricklet/XYZ/get_color
publish '' to tinkerforge/request/color_v2_bricklet/XYZ/get_color
|
Download (example-callback.txt)
1 2 3 4 5 6 7 8 9 | # Change XYZ to the UID of your Color Bricklet 2.0
setup:
# Handle incoming color callbacks
subscribe to tinkerforge/callback/color_v2_bricklet/XYZ/color
publish '{"register": true}' to tinkerforge/register/color_v2_bricklet/XYZ/color # Register color callback
# Set period for color callback to 0.1s (100ms)
publish '{"period": 100, "value_has_to_change": false}' to tinkerforge/request/color_v2_bricklet/XYZ/set_color_callback_configuration
|
All published payloads to and from the MQTT bindings are in JSON format.
If an error occures, the bindings publish a JSON object containing the error message as member _ERROR
.
It is published on the corresponding response topic: .../response/...
for .../request/...
and .../callback/...
for .../register/...
.
request/
color_v2_bricklet/
<UID>/
get_color
¶Request: |
|
---|---|
Response: |
|
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 register/color_v2_bricklet/<UID>/color
callback and set the period with
request/color_v2_bricklet/<UID>/set_color_callback_configuration
.
request/
color_v2_bricklet/
<UID>/
get_illuminance
¶Request: |
|
---|---|
Response: |
|
Returns the illuminance affected by the gain and integration time as
set by request/color_v2_bricklet/<UID>/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 request/color_v2_bricklet/<UID>/set_configuration
.
If you want to get the value periodically, it is recommended to use the
register/color_v2_bricklet/<UID>/illuminance
callback. You can set the callback configuration
with request/color_v2_bricklet/<UID>/set_illuminance_callback_configuration
.
request/
color_v2_bricklet/
<UID>/
get_color_temperature
¶Request: |
|
---|---|
Response: |
|
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 request/color_v2_bricklet/<UID>/set_configuration
.
If you want to get the value periodically, it is recommended to use the
register/color_v2_bricklet/<UID>/color_temperature
callback. You can set the callback configuration
with request/color_v2_bricklet/<UID>/set_color_temperature_callback_configuration
.
request/
color_v2_bricklet/
<UID>/
set_light
¶Request: |
|
---|---|
Response: |
|
Turns the white LED on the Bricklet on/off.
request/
color_v2_bricklet/
<UID>/
get_light
¶Request: |
|
---|---|
Response: |
|
Returns the value as set by request/color_v2_bricklet/<UID>/set_light
.
request/
color_v2_bricklet/
<UID>/
set_configuration
¶Request: |
|
---|---|
Response: |
|
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:
request/
color_v2_bricklet/
<UID>/
get_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/color_v2_bricklet/<UID>/set_configuration
.
The following symbols are available for this function:
For gain:
For integration_time:
request/
color_v2_bricklet/
<UID>/
get_spitfp_error_count
¶Request: |
|
---|---|
Response: |
|
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.
request/
color_v2_bricklet/
<UID>/
set_status_led_config
¶Request: |
|
---|---|
Response: |
|
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:
request/
color_v2_bricklet/
<UID>/
get_status_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/color_v2_bricklet/<UID>/set_status_led_config
The following symbols are available for this function:
For config:
request/
color_v2_bricklet/
<UID>/
get_chip_temperature
¶Request: |
|
---|---|
Response: |
|
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.
request/
color_v2_bricklet/
<UID>/
reset
¶Request: |
|
---|---|
Response: |
|
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!
request/
color_v2_bricklet/
<UID>/
get_identity
¶Request: |
|
---|---|
Response: |
|
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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.
The display name contains the Color 2.0's name in a human readable form.
request/
color_v2_bricklet/
<UID>/
set_color_callback_configuration
¶Request: |
|
---|---|
Response: |
|
The period is the period with which the register/color_v2_bricklet/<UID>/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.
request/
color_v2_bricklet/
<UID>/
get_color_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by
request/color_v2_bricklet/<UID>/set_color_callback_configuration
.
request/
color_v2_bricklet/
<UID>/
set_illuminance_callback_configuration
¶Request: |
|
---|---|
Response: |
|
The period is the period with which the register/color_v2_bricklet/<UID>/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 register/color_v2_bricklet/<UID>/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:
request/
color_v2_bricklet/
<UID>/
get_illuminance_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by request/color_v2_bricklet/<UID>/set_illuminance_callback_configuration
.
The following symbols are available for this function:
For option:
request/
color_v2_bricklet/
<UID>/
set_color_temperature_callback_configuration
¶Request: |
|
---|---|
Response: |
|
The period is the period with which the register/color_v2_bricklet/<UID>/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 register/color_v2_bricklet/<UID>/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:
request/
color_v2_bricklet/
<UID>/
get_color_temperature_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by request/color_v2_bricklet/<UID>/set_color_temperature_callback_configuration
.
The following symbols 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 corresponding .../register/...
topic and an optional suffix.
This suffix can be used to deregister the callback later.
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.
register/
color_v2_bricklet/
<UID>/
color
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/color_v2_bricklet/<UID>/color[/<SUFFIX>]
topic with the payload "true".
An added callback can be removed by publishing to the same topic with the payload "false".
To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.
If the callback is triggered, a message with it's payload is published under the corresponding .../callback/color_v2_bricklet/<UID>/color[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically with the period that is set by
request/color_v2_bricklet/<UID>/set_color_callback_configuration
. The callback payload is the color
of the sensor as RGBC.
The register/color_v2_bricklet/<UID>/color
callback is only triggered if the color has changed since the
last triggering.
register/
color_v2_bricklet/
<UID>/
illuminance
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/color_v2_bricklet/<UID>/illuminance[/<SUFFIX>]
topic with the payload "true".
An added callback can be removed by publishing to the same topic with the payload "false".
To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.
If the callback is triggered, a message with it's payload is published under the corresponding .../callback/color_v2_bricklet/<UID>/illuminance[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically according to the configuration set by
request/color_v2_bricklet/<UID>/set_illuminance_callback_configuration
.
The callback payload is the same as request/color_v2_bricklet/<UID>/get_illuminance
.
register/
color_v2_bricklet/
<UID>/
color_temperature
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/color_v2_bricklet/<UID>/color_temperature[/<SUFFIX>]
topic with the payload "true".
An added callback can be removed by publishing to the same topic with the payload "false".
To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.
If the callback is triggered, a message with it's payload is published under the corresponding .../callback/color_v2_bricklet/<UID>/color_temperature[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically according to the configuration set by
request/color_v2_bricklet/<UID>/set_color_temperature_callback_configuration
.
The callback payload is the same as request/color_v2_bricklet/<UID>/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.
request/
color_v2_bricklet/
<UID>/
set_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
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:
request/
color_v2_bricklet/
<UID>/
get_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Returns the current bootloader mode, see request/color_v2_bricklet/<UID>/set_bootloader_mode
.
The following symbols are available for this function:
For mode:
request/
color_v2_bricklet/
<UID>/
set_write_firmware_pointer
¶Request: |
|
---|---|
Response: |
|
Sets the firmware pointer for request/color_v2_bricklet/<UID>/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.
request/
color_v2_bricklet/
<UID>/
write_firmware
¶Request: |
|
---|---|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
request/color_v2_bricklet/<UID>/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.
request/
color_v2_bricklet/
<UID>/
write_uid
¶Request: |
|
---|---|
Response: |
|
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.
request/
color_v2_bricklet/
<UID>/
read_uid
¶Request: |
|
---|---|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.