This is the description of the Shell API bindings for the Motion Detector Bricklet. General information and technical specifications for the Motion Detector 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).
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 Motion Detector Bricklet
# Handle incoming motion detected callbacks
tinkerforge dispatch motion-detector-bricklet $uid motion-detected\
--execute "echo Motion Detected" &
# Handle incoming detection cycle ended callbacks
tinkerforge dispatch motion-detector-bricklet $uid detection-cycle-ended\
--execute "echo Detection Cycle Ended (next detection possible in ~3 seconds)" &
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
motion-detector-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Motion Detector 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 Motion Detector Bricklet and exitsdispatch
motion-detector-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Motion Detector 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 Motion Detector Bricklet and exitsmotion-detector-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.
motion-detector-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)motion-detector-bricklet
<uid> get-motion-detected
¶Output: |
|
---|
Returns 1 if a motion was detected. How long this returns 1 after a motion was detected can be adjusted with one of the small potentiometers on the Motion Detector Bricklet, see here.
There is also a blue LED on the Bricklet that is on as long as the Bricklet is in the "motion detected" state.
The following symbols are available for this function:
For motion:
motion-detector-bricklet
<uid> set-status-led-config
<config>¶Parameters: |
|
---|---|
Output: |
|
Sets the status led configuration.
By default the status LED turns on if a motion is detected and off is no motion is detected.
You can also turn the LED permanently on/off.
The following symbols are available for this function:
For <config>:
New in version 2.0.1 (Plugin).
motion-detector-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:
New in version 2.0.1 (Plugin).
motion-detector-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.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch motion-detector-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.
motion-detector-bricklet
<uid> motion-detected
¶Output: |
|
---|
This callback is called after a motion was detected.
motion-detector-bricklet
<uid> detection-cycle-ended
¶Output: |
|
---|
This callback is called when the detection cycle ended. When this callback is called, a new motion can be detected again after approximately 2 seconds.