This is the description of the Shell API bindings for the Ambient Light Bricklet 2.0. General information and technical specifications for the Ambient Light 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 Ambient Light Bricklet 2.0
# Get current illuminance
tinkerforge call ambient-light-v2-bricklet $uid get-illuminance
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Ambient Light Bricklet 2.0
# Handle incoming illuminance callbacks
tinkerforge dispatch ambient-light-v2-bricklet $uid illuminance &
# Set period for illuminance callback to 1s (1000ms)
# Note: The illuminance callback is only called every second
# if the illuminance has changed since the last call!
tinkerforge call ambient-light-v2-bricklet $uid set-illuminance-callback-period 1000
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Download (example-threshold.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Ambient Light Bricklet 2.0
# Get threshold callbacks with a debounce time of 10 seconds (10000ms)
tinkerforge call ambient-light-v2-bricklet $uid set-debounce-period 10000
# Handle incoming illuminance reached callbacks
tinkerforge dispatch ambient-light-v2-bricklet $uid illuminance-reached\
--execute "echo Illuminance: {illuminance}/100 lx. Too bright, close the curtains!" &
# Configure threshold for illuminance "greater than 500 lx"
tinkerforge call ambient-light-v2-bricklet $uid set-illuminance-callback-threshold threshold-option-greater 50000 0
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
ambient-light-v2-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Ambient Light 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 Ambient Light Bricklet 2.0 and exitsdispatch
ambient-light-v2-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Ambient Light 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 Ambient Light Bricklet 2.0 and exitsambient-light-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.
ambient-light-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)ambient-light-v2-bricklet
<uid> get-illuminance
¶Output: |
|
---|
Returns the illuminance of the ambient light sensor. The measurement range goes up to about 100000lux, but above 64000lux the precision starts to drop.
Changed in version 2.0.2 (Plugin): An illuminance of 0lux indicates an error condition where the sensor cannot
perform a reasonable measurement. This can happen with very dim or very bright
light conditions. In bright light conditions this might indicate that the sensor
is saturated and the configuration should be modified (set-configuration
)
to better match the light conditions.
If you want to get the illuminance periodically, it is recommended to use the
illuminance
callback and set the period with
set-illuminance-callback-period
.
ambient-light-v2-bricklet
<uid> set-configuration
<illuminance-range> <integration-time>¶Parameters: |
|
---|---|
Output: |
|
Sets the configuration. It is possible to configure an illuminance range between 0-600lux and 0-64000lux and an integration time between 50ms and 400ms.
New in version 2.0.2 (Plugin): The unlimited illuminance range allows to measure up to about 100000lux, but above 64000lux the precision starts to drop.
A smaller illuminance range increases the resolution of the data. A longer integration time will result in less noise on the data.
Changed in version 2.0.2 (Plugin): If the actual measure illuminance is out-of-range then the current illuminance
range maximum +0.01lux is reported by get-illuminance
and the
illuminance
callback. For example, 800001 for the 0-8000lux range.
Changed in version 2.0.2 (Plugin): With a long integration time the sensor might be saturated before the measured
value reaches the maximum of the selected illuminance range. In this case 0lux
is reported by get-illuminance
and the illuminance
callback.
If the measurement is out-of-range or the sensor is saturated then you should configure the next higher illuminance range. If the highest range is already in use, then start to reduce the integration time.
The following symbols are available for this function:
For <illuminance-range>:
For <integration-time>:
ambient-light-v2-bricklet
<uid> get-configuration
¶Output: |
|
---|
Returns the configuration as set by set-configuration
.
The following symbols are available for this function:
For illuminance-range:
For integration-time:
ambient-light-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.
ambient-light-v2-bricklet
<uid> set-illuminance-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the illuminance
callback is triggered
periodically. A value of 0 turns the callback off.
The illuminance
callback is only triggered if the illuminance has changed
since the last triggering.
ambient-light-v2-bricklet
<uid> get-illuminance-callback-period
¶Output: |
|
---|
Returns the period as set by set-illuminance-callback-period
.
ambient-light-v2-bricklet
<uid> set-illuminance-callback-threshold
<option> <min> <max>¶Parameters: |
|
---|---|
Output: |
|
Sets the thresholds for the illuminance-reached
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the illuminance is outside the min and max values |
'i' | Callback is triggered when the illuminance is inside the min and max values |
'<' | Callback is triggered when the illuminance is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the illuminance is greater than the min value (max is ignored) |
The following symbols are available for this function:
For <option>:
ambient-light-v2-bricklet
<uid> get-illuminance-callback-threshold
¶Output: |
|
---|
Returns the threshold as set by set-illuminance-callback-threshold
.
The following symbols are available for this function:
For option:
ambient-light-v2-bricklet
<uid> set-debounce-period
<debounce>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the threshold callbacks
are triggered, if the thresholds
keep being reached.
ambient-light-v2-bricklet
<uid> get-debounce-period
¶Output: |
|
---|
Returns the debounce period as set by set-debounce-period
.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch ambient-light-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.
ambient-light-v2-bricklet
<uid> illuminance
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-illuminance-callback-period
. The parameter is the illuminance of the
ambient light sensor.
The illuminance
callback is only triggered if the illuminance has changed since the
last triggering.
ambient-light-v2-bricklet
<uid> illuminance-reached
¶Output: |
|
---|
This callback is triggered when the threshold as set by
set-illuminance-callback-threshold
is reached.
The parameter is the illuminance of the ambient light sensor.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by set-debounce-period
.