This is the description of the Shell API bindings for the LED Strip Bricklet. General information and technical specifications for the LED Strip Bricklet 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 LED Strip Bricklet
# Set first 10 LEDs to green
tinkerforge call led-strip-bricklet $uid set-rgb-values 0 10 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 255,255,255,255,255,255,255,255,255,255,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
|
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
led-strip-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the LED Strip Bricklet. 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 LED Strip Bricklet and exitsdispatch
led-strip-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the LED Strip Bricklet. 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 LED Strip Bricklet and exitsled-strip-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.
led-strip-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)led-strip-bricklet
<uid> set-rgb-values
<index> <length> <r> <g> <b>¶Parameters: |
|
---|---|
Output: |
|
Sets length RGB values for the LEDs starting from index.
To make the colors show correctly you need to configure the chip type
(set-chip-type
) and a 3-channel channel mapping (set-channel-mapping
)
according to the connected LEDs.
Example: If you set
the LED with index 5 will be red, 6 will be green and 7 will be blue.
Note
Depending on the LED circuitry colors can be permuted.
The colors will be transfered to actual LEDs when the next
frame duration ends, see set-frame-duration
.
Generic approach:
frame-rendered
callback.frame-rendered
callback.This approach ensures that you can change the LED colors with a fixed frame rate.
The actual number of controllable LEDs depends on the number of free
Bricklet ports. See here for more
information. A call of set-rgb-values
with index + length above the
bounds is ignored completely.
led-strip-bricklet
<uid> get-rgb-values
<index> <length>¶Parameters: |
|
---|---|
Output: |
|
Returns length R, G and B values starting from the given LED index.
The values are the last values that were set by set-rgb-values
.
led-strip-bricklet
<uid> set-frame-duration
<duration>¶Parameters: |
|
---|---|
Output: |
|
Sets the frame duration.
Example: If you want to achieve 20 frames per second, you should set the frame duration to 50ms (50ms * 20 = 1 second).
For an explanation of the general approach see set-rgb-values
.
led-strip-bricklet
<uid> get-frame-duration
¶Output: |
|
---|
Returns the frame duration as set by set-frame-duration
.
led-strip-bricklet
<uid> get-supply-voltage
¶Output: |
|
---|
Returns the current supply voltage of the LEDs.
led-strip-bricklet
<uid> set-clock-frequency
<frequency>¶Parameters: |
|
---|---|
Output: |
|
Sets the frequency of the clock.
The Bricklet will choose the nearest achievable frequency, which may
be off by a few Hz. You can get the exact frequency that is used by
calling get-clock-frequency
.
If you have problems with flickering LEDs, they may be bits flipping. You can fix this by either making the connection between the LEDs and the Bricklet shorter or by reducing the frequency.
With a decreasing frequency your maximum frames per second will decrease too.
Note
The frequency in firmware version 2.0.0 is fixed at 2MHz.
New in version 2.0.1 (Plugin).
led-strip-bricklet
<uid> get-clock-frequency
¶Output: |
|
---|
Returns the currently used clock frequency as set by set-clock-frequency
.
New in version 2.0.1 (Plugin).
led-strip-bricklet
<uid> set-chip-type
<chip>¶Parameters: |
|
---|---|
Output: |
|
Sets the type of the LED driver chip. We currently support the chips
The following symbols are available for this function:
For <chip>:
New in version 2.0.2 (Plugin).
led-strip-bricklet
<uid> get-chip-type
¶Output: |
|
---|
Returns the currently used chip type as set by set-chip-type
.
The following symbols are available for this function:
For chip:
New in version 2.0.2 (Plugin).
led-strip-bricklet
<uid> set-rgbw-values
<index> <length> <r> <g> <b> <w>¶Parameters: |
|
---|---|
Output: |
|
Sets length RGBW values for the LEDs starting from index.
To make the colors show correctly you need to configure the chip type
(set-chip-type
) and a 4-channel channel mapping (set-channel-mapping
)
according to the connected LEDs.
The maximum length is 12, the index goes from 0 to 239 and the rgbw values have 8 bits each.
Example: If you set
the LED with index 5 will be red, 6 will be green, 7 will be blue and 8 will be white.
Note
Depending on the LED circuitry colors can be permuted.
The colors will be transfered to actual LEDs when the next
frame duration ends, see set-frame-duration
.
Generic approach:
frame-rendered
callback.frame-rendered
callback.This approach ensures that you can change the LED colors with a fixed frame rate.
The actual number of controllable LEDs depends on the number of free
Bricklet ports. See here for more
information. A call of set-rgbw-values
with index + length above the
bounds is ignored completely.
The LPD8806 LED driver chips have 7-bit channels for RGB. Internally the LED Strip Bricklets divides the 8-bit values set using this function by 2 to make them 7-bit. Therefore, you can just use the normal value range (0-255) for LPD8806 LEDs.
The brightness channel of the APA102 LED driver chips has 5-bit. Internally the LED Strip Bricklets divides the 8-bit values set using this function by 8 to make them 5-bit. Therefore, you can just use the normal value range (0-255) for the brightness channel of APA102 LEDs.
New in version 2.0.6 (Plugin).
led-strip-bricklet
<uid> get-rgbw-values
<index> <length>¶Parameters: |
|
---|---|
Output: |
|
Returns length RGBW values starting from the given index.
The values are the last values that were set by set-rgbw-values
.
New in version 2.0.6 (Plugin).
led-strip-bricklet
<uid> set-channel-mapping
<mapping>¶Parameters: |
|
---|---|
Output: |
|
Sets the channel mapping for the connected LEDs.
set-rgb-values
and set-rgbw-values
take the data in RGB(W) order.
But the connected LED driver chips might have their 3 or 4 channels in a
different order. For example, the WS2801 chips typically use BGR order, the
WS2812 chips typically use GRB order and the APA102 chips typically use WBGR
order.
The APA102 chips are special. They have three 8-bit channels for RGB and an additional 5-bit channel for the overall brightness of the RGB LED making them 4-channel chips. Internally the brightness channel is the first channel, therefore one of the Wxyz channel mappings should be used. Then the W channel controls the brightness.
If a 3-channel mapping is selected then set-rgb-values
has to be used.
Calling set-rgbw-values
with a 3-channel mapping will produce incorrect
results. Vice-versa if a 4-channel mapping is selected then
set-rgbw-values
has to be used. Calling set-rgb-values
with a
4-channel mapping will produce incorrect results.
The following symbols are available for this function:
For <mapping>:
New in version 2.0.6 (Plugin).
led-strip-bricklet
<uid> get-channel-mapping
¶Output: |
|
---|
Returns the currently used channel mapping as set by set-channel-mapping
.
The following symbols are available for this function:
For mapping:
New in version 2.0.6 (Plugin).
led-strip-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.
led-strip-bricklet
<uid> enable-frame-rendered-callback
¶Output: |
|
---|
Enables the frame-rendered
callback.
By default the callback is enabled.
New in version 2.0.6 (Plugin).
led-strip-bricklet
<uid> disable-frame-rendered-callback
¶Output: |
|
---|
Disables the frame-rendered
callback.
By default the callback is enabled.
New in version 2.0.6 (Plugin).
led-strip-bricklet
<uid> is-frame-rendered-callback-enabled
¶Output: |
|
---|
Returns true if the frame-rendered
callback is enabled, false otherwise.
New in version 2.0.6 (Plugin).
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch led-strip-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.
led-strip-bricklet
<uid> frame-rendered
¶Output: |
|
---|
This callback is triggered directly after a new frame is rendered. The parameter is the number of RGB or RGBW LEDs in that frame.
You should send the data for the next frame directly after this callback was triggered.
For an explanation of the general approach see set-rgb-values
.