This is the description of the Perl 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 Perl 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 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletHallEffect;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Hall Effect Bricklet
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $he = Tinkerforge::BrickletHallEffect->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Get current edge count without reset
my $count = $he->get_edge_count(0);
print "Count: $count\n";
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Download (example_callback.pl)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletHallEffect;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Hall Effect Bricklet
# Callback subroutine for edge count callback
sub cb_edge_count
{
my ($count, $value) = @_;
print "Count: $count\n";
}
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $he = Tinkerforge::BrickletHallEffect->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Register edge count callback to subroutine cb_edge_count
$he->register_callback($he->CALLBACK_EDGE_COUNT, 'cb_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!
$he->set_edge_count_callback_period(50);
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Generally, every subroutine of the Perl bindings can report an error as
Tinkerforge::Error
object via croak()
. The object has a
get_code()
and a get_message()
subroutine. There are different
error code:
All functions listed below are thread-safe.
BrickletHallEffect
->
new
($uid, $ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID $uid
:
$hall_effect = BrickletHallEffect->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected.
BrickletHallEffect
->
get_value
()¶Returns: |
|
---|
Returns true if a magnetic field of 3.5 millitesla or greater is detected.
BrickletHallEffect
->
get_edge_count
($reset_counter)¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletHallEffect
->
set_edge_count_config
($edge_type, $debounce)¶Parameters: |
|
---|---|
Returns: |
|
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 constants are available for this function:
For $edge_type:
BrickletHallEffect
->
get_edge_count_config
()¶Return Array: |
|
---|
Returns the edge type and debounce time as set by set_edge_count_config()
.
The following constants are available for this function:
For $edge_type:
BrickletHallEffect
->
get_identity
()¶Return Array: |
|
---|
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. There is also a constant for the device identifier of this Bricklet.
BrickletHallEffect
->
register_callback
($callback_id, $function)¶Parameters: |
|
---|---|
Returns: |
|
Registers the given $function
name with the given $callback_id
.
The available callback IDs with corresponding function signatures are listed below.
BrickletHallEffect
->
set_edge_interrupt
($edges)¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletHallEffect
->
get_edge_interrupt
()¶Returns: |
|
---|
Returns the edges as set by set_edge_interrupt()
.
BrickletHallEffect
->
set_edge_count_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_EDGE_COUNT
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_EDGE_COUNT
callback is only triggered if the edge count has changed
since the last triggering.
BrickletHallEffect
->
get_edge_count_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_edge_count_callback_period()
.
Callbacks can be registered to receive
time critical or recurring data from the device. The registration is done
with the register_callback()
function of
the device object. The first parameter is the callback ID and the second
parameter the callback function name:
sub my_callback
{
print "@_[0]";
}
$hall_effect->register_callback(BrickletHallEffect->CALLBACK_EXAMPLE, 'my_callback')
The callback function will be called from an internal thread of the
IP Connection. In contrast to many other programming languages, variables are
not automatically shared between threads in Perl. If you want to share a global
variable between a callback function and the rest for your program it has to be
marked as :shared
. See the documentation of the threads::shared Perl module for more details.
The available constants with inherent number and type of parameters 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.
BrickletHallEffect
->
CALLBACK_EDGE_COUNT
¶Callback Parameters: |
|
---|
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 CALLBACK_EDGE_COUNT
callback is only triggered if the count or value changed
since the last triggering.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
BrickletHallEffect
->
get_api_version
()¶Return Array: |
|
---|
Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
BrickletHallEffect
->
get_response_expected
($function_id)¶Parameters: |
|
---|---|
Returns: |
|
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled,
because those functions will always send a response. For callback configuration
functions it is enabled by default too, but can be disabled by
set_response_expected()
. For setter functions it is disabled by default
and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For $function_id:
BrickletHallEffect
->
set_response_expected
($function_id, $response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For $function_id:
BrickletHallEffect
->
set_response_expected_all
($response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletHallEffect
->
DEVICE_IDENTIFIER
¶This constant is used to identify a Hall Effect Bricklet.
The get_identity()
function and the
IPConnection->CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletHallEffect
->
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Hall Effect Bricklet.