This is the description of the Shell API bindings for the Multi Touch Bricklet. General information and technical specifications for the Multi Touch 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 Multi Touch Bricklet
# Get current touch state
tinkerforge call multi-touch-bricklet $uid get-touch-state
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Multi Touch Bricklet
# Handle incoming touch state callbacks
tinkerforge dispatch multi-touch-bricklet $uid touch-state &
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
multi-touch-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Multi Touch 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 Multi Touch Bricklet and exitsdispatch
multi-touch-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Multi Touch 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 Multi Touch Bricklet and exitsmulti-touch-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.
multi-touch-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)multi-touch-bricklet
<uid> get-touch-state
¶Output: |
|
---|
Returns the current touch state. The state is given as a bitfield.
Bits 0 to 11 represent the 12 electrodes and bit 12 represents the proximity.
If an electrode is touched, the corresponding bit is true. If a hand or similar is in proximity to the electrodes, bit 12 is true.
Example: The state 4103 = 0x1007 = 0b1000000000111 means that electrodes 0, 1 and 2 are touched and that something is in the proximity of the electrodes.
The proximity is activated with a distance of 1-2cm. An electrode is already counted as touched if a finger is nearly touching the electrode. This means that you can put a piece of paper or foil or similar on top of a electrode to build a touch panel with a professional look.
multi-touch-bricklet
<uid> recalibrate
¶Output: |
|
---|
Recalibrates the electrodes. Call this function whenever you changed or moved you electrodes.
multi-touch-bricklet
<uid> set-electrode-config
<enabled-electrodes>¶Parameters: |
|
---|---|
Output: |
|
Enables/disables electrodes with a bitfield (see get-touch-state
).
True enables the electrode, false disables the electrode. A disabled electrode will always return false as its state. If you don't need all electrodes you can disable the electrodes that are not needed.
It is recommended that you disable the proximity bit (bit 12) if
the proximity feature is not needed. This will reduce the amount of
traffic that is produced by the touch-state
callback.
Disabling electrodes will also reduce power consumption.
Default: 8191 = 0x1FFF = 0b1111111111111 (all electrodes and proximity feature enabled)
multi-touch-bricklet
<uid> get-electrode-config
¶Output: |
|
---|
Returns the electrode configuration, as set by set-electrode-config
.
multi-touch-bricklet
<uid> set-electrode-sensitivity
<sensitivity>¶Parameters: |
|
---|---|
Output: |
|
Sets the sensitivity of the electrodes. An electrode with a high sensitivity will register a touch earlier then an electrode with a low sensitivity.
If you build a big electrode you might need to decrease the sensitivity, since the area that can be charged will get bigger. If you want to be able to activate an electrode from further away you need to increase the sensitivity.
After a new sensitivity is set, you likely want to call recalibrate
to calibrate the electrodes with the newly defined sensitivity.
multi-touch-bricklet
<uid> get-electrode-sensitivity
¶Output: |
|
---|
Returns the current sensitivity, as set by set-electrode-sensitivity
.
multi-touch-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 multi-touch-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.
multi-touch-bricklet
<uid> touch-state
¶Output: |
|
---|
Returns the current touch state, see get-touch-state
for
information about the state.
This callback is triggered every time the touch state changes.