This is the description of the Shell API bindings for the Hall Effect Bricklet. General information and technical specifications for the Hall Effect 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 Hall Effect Bricklet
# Get current edge count without reset
tinkerforge call hall-effect-bricklet $uid get-edge-count false
|
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 Hall Effect Bricklet
# Handle incoming edge count callbacks
tinkerforge dispatch hall-effect-bricklet $uid edge-count &
# Set period for edge count callback to 0.05s (50ms)
# Note: The edge count callback is only called every 0.05 seconds
# if the edge count has changed since the last call!
tinkerforge call hall-effect-bricklet $uid set-edge-count-callback-period 50
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
hall-effect-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Hall Effect 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 Hall Effect Bricklet and exitsdispatch
hall-effect-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Hall Effect 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 Hall Effect Bricklet and exitshall-effect-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.
hall-effect-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)hall-effect-bricklet
<uid> get-value
¶Output: |
|
---|
Returns true if a magnetic field of 3.5 millitesla or greater is detected.
hall-effect-bricklet
<uid> get-edge-count
<reset-counter>¶Parameters: |
|
---|---|
Output: |
|
Returns the current value of the edge counter. You can configure
edge type (rising, falling, both) that is counted with
set-edge-count-config
.
If you set the reset counter to true, the count is set back to 0 directly after it is read.
hall-effect-bricklet
<uid> set-edge-count-config
<edge-type> <debounce>¶Parameters: |
|
---|---|
Output: |
|
The edge type parameter configures if rising edges, falling edges or both are counted. Possible edge types are:
A magnetic field of 3.5 millitesla or greater causes a falling edge and a magnetic field of 2.5 millitesla or smaller causes a rising edge.
If a magnet comes near the Bricklet the signal goes low (falling edge), if a magnet is removed from the vicinity the signal goes high (rising edge).
Configuring an edge counter resets its value to 0.
If you don't know what any of this means, just leave it at default. The default configuration is very likely OK for you.
The following symbols are available for this function:
For <edge-type>:
hall-effect-bricklet
<uid> get-edge-count-config
¶Output: |
|
---|
Returns the edge type and debounce time as set by set-edge-count-config
.
The following symbols are available for this function:
For edge-type:
hall-effect-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.
hall-effect-bricklet
<uid> set-edge-interrupt
<edges>¶Parameters: |
|
---|---|
Output: |
|
Sets the number of edges until an interrupt is invoked.
If edges is set to n, an interrupt is invoked for every n-th detected edge.
If edges is set to 0, the interrupt is disabled.
hall-effect-bricklet
<uid> get-edge-interrupt
¶Output: |
|
---|
Returns the edges as set by set-edge-interrupt
.
hall-effect-bricklet
<uid> set-edge-count-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the edge-count
callback is triggered
periodically. A value of 0 turns the callback off.
The edge-count
callback is only triggered if the edge count has changed
since the last triggering.
hall-effect-bricklet
<uid> get-edge-count-callback-period
¶Output: |
|
---|
Returns the period as set by set-edge-count-callback-period
.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch hall-effect-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.
hall-effect-bricklet
<uid> edge-count
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-edge-count-callback-period
. The parameters are the
current count and the current value (see get-value
and
get-edge-count
).
The edge-count
callback is only triggered if the count or value changed
since the last triggering.