This is the description of the Perl API bindings for the Distance US Bricklet. General information and technical specifications for the Distance US 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::BrickletDistanceUS;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Distance US Bricklet
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $dus = Tinkerforge::BrickletDistanceUS->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Get current distance value
my $distance = $dus->get_distance_value();
print "Distance Value: $distance\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::BrickletDistanceUS;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Distance US Bricklet
# Callback subroutine for distance value callback
sub cb_distance
{
my ($distance) = @_;
print "Distance Value: $distance\n";
}
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $dus = Tinkerforge::BrickletDistanceUS->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Register distance value callback to subroutine cb_distance
$dus->register_callback($dus->CALLBACK_DISTANCE, 'cb_distance');
# Set period for distance value callback to 0.2s (200ms)
# Note: The distance value callback is only called every 0.2 seconds
# if the distance value has changed since the last call!
$dus->set_distance_callback_period(200);
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Download (example_threshold.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 36 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletDistanceUS;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Distance US Bricklet
# Callback subroutine for distance value reached callback
sub cb_distance_reached
{
my ($distance) = @_;
print "Distance Value: $distance\n";
}
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $dus = Tinkerforge::BrickletDistanceUS->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Get threshold callbacks with a debounce time of 10 seconds (10000ms)
$dus->set_debounce_period(10000);
# Register distance value reached callback to subroutine cb_distance_reached
$dus->register_callback($dus->CALLBACK_DISTANCE_REACHED, 'cb_distance_reached');
# Configure threshold for distance value "smaller than 200"
$dus->set_distance_callback_threshold('<', 200, 0);
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.
BrickletDistanceUS
->
new
($uid, $ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID $uid
:
$distance_us = BrickletDistanceUS->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected.
BrickletDistanceUS
->
get_distance_value
()¶Returns: |
|
---|
Returns the current distance value measured by the sensor. A small value corresponds to a small distance, a big value corresponds to a big distance. The relation between the measured distance value and the actual distance is affected by the 5V supply voltage (deviations in the supply voltage result in deviations in the distance values) and is non-linear (resolution is bigger at close range).
If you want to get the distance value periodically, it is recommended to
use the CALLBACK_DISTANCE
callback and set the period with
set_distance_callback_period()
.
BrickletDistanceUS
->
set_moving_average
($average)¶Parameters: |
|
---|---|
Returns: |
|
Sets the length of a moving averaging for the distance value.
Setting the length to 0 will turn the averaging completely off. With less averaging, there is more noise on the data.
BrickletDistanceUS
->
get_moving_average
()¶Returns: |
|
---|
Returns the length moving average as set by set_moving_average()
.
BrickletDistanceUS
->
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.
BrickletDistanceUS
->
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.
BrickletDistanceUS
->
set_distance_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_DISTANCE
callback is triggered
periodically. A value of 0 turns the callback off.
Der CALLBACK_DISTANCE
callback is only triggered if the distance value has changed
since the last triggering.
BrickletDistanceUS
->
get_distance_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_distance_callback_period()
.
BrickletDistanceUS
->
set_distance_callback_threshold
($option, $min, $max)¶Parameters: |
|
---|---|
Returns: |
|
Sets the thresholds for the CALLBACK_DISTANCE_REACHED
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the distance value is outside the min and max values |
'i' | Callback is triggered when the distance value is inside the min and max values |
'<' | Callback is triggered when the distance value is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the distance value is greater than the min value (max is ignored) |
The following constants are available for this function:
For $option:
BrickletDistanceUS
->
get_distance_callback_threshold
()¶Return Array: |
|
---|
Returns the threshold as set by set_distance_callback_threshold()
.
The following constants are available for this function:
For $option:
BrickletDistanceUS
->
set_debounce_period
($debounce)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the threshold callbacks
are triggered, if the thresholds
keep being reached.
BrickletDistanceUS
->
get_debounce_period
()¶Returns: |
|
---|
Returns the debounce period as set by set_debounce_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]";
}
$distance_us->register_callback(BrickletDistanceUS->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.
BrickletDistanceUS
->
CALLBACK_DISTANCE
¶Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
set_distance_callback_period()
. The parameter is the distance value
of the sensor.
The CALLBACK_DISTANCE
callback is only triggered if the distance value has changed
since the last triggering.
BrickletDistanceUS
->
CALLBACK_DISTANCE_REACHED
¶Callback Parameters: |
|
---|
This callback is triggered when the threshold as set by
set_distance_callback_threshold()
is reached.
The parameter is the distance value of the sensor.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by set_debounce_period()
.
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.
BrickletDistanceUS
->
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.
BrickletDistanceUS
->
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:
BrickletDistanceUS
->
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:
BrickletDistanceUS
->
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.
BrickletDistanceUS
->
DEVICE_IDENTIFIER
¶This constant is used to identify a Distance US 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.
BrickletDistanceUS
->
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Distance US Bricklet.