This is the description of the Perl API bindings for the IP Connection. The IP Connection manages the communication between the API bindings and the Brick Daemon or a WIFI/Ethernet Extension. Before Bricks and Bricklets can be controlled using their API an IP Connection has to be created and its TCP/IP connection has to be established.
An installation guide for the Perl API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example_enumerate.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 37 38 39 40 41 42 43 44 45 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use constant HOST => 'localhost';
use constant PORT => 4223;
# Create connection and connect to brickd
my $ipcon = Tinkerforge::IPConnection->new();
# Print incoming enumeration
sub cb_enumerate
{
my ($uid, $connected_uid, $position, $hardware_version,
$firmware_version, $device_identifier, $enumeration_type) = @_;
print "UID: $uid\n";
print "Enumeration Type: $enumeration_type\n";
if ($enumeration_type == Tinkerforge::IPConnection->ENUMERATION_TYPE_DISCONNECTED)
{
print "\n";
return;
}
print "Connected UID: $connected_uid\n";
print "Position: $position\n";
print "Hardware Version: ".join('.', @$hardware_version)."\n";
print "Firmware Version: ".join('.', @$firmware_version)."\n";
print "Device Identifier: $device_identifier\n";
print "\n";
}
$ipcon->connect(&HOST, &PORT);
# Register Enumerate Callback
$ipcon->register_callback($ipcon->CALLBACK_ENUMERATE, 'cb_enumerate');
# Trigger Enumerate
$ipcon->enumerate();
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Download (example_authenticate.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 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant SECRET => 'My Authentication Secret!';
# Create IPConnection
our $ipcon = Tinkerforge::IPConnection->new();
# Disable auto reconnect mechanism, in case we have the wrong secret.
# If the authentication is successful, reenable it.
$ipcon->set_auto_reconnect(0);
# Authenticate each time the connection got (re-)established
sub cb_connected
{
my ($connect_reason) = @_;
if ($connect_reason == $ipcon->CONNECT_REASON_REQUEST)
{
print "Connected by request\n";
}
elsif ($connect_reason == $ipcon->CONNECT_REASON_AUTO_RECONNECT)
{
print "Auto-Reconnect\n";
}
# Authenticate first...
eval
{
$ipcon->authenticate(&SECRET);
print "Authentication succeeded\n";
};
if ($!)
{
print "Could not authenticate: $!\n";
return;
}
# ...reenable auto reconnect mechanism, as described above...
$ipcon->set_auto_reconnect(1);
# ...then trigger Enumerate
$ipcon->enumerate();
}
# Print incoming enumeration
sub cb_enumerate
{
my ($uid, $connected_uid, $position, $hardware_version,
$firmware_version, $device_identifier, $enumeration_type) = @_;
print "UID: $uid, Enumeration Type: $enumeration_type\n";
}
# Register Connected Callback
$ipcon->register_callback($ipcon->CALLBACK_CONNECTED, 'cb_connected');
# Register Enumerate Callback
$ipcon->register_callback($ipcon->CALLBACK_ENUMERATE, 'cb_enumerate');
# Connect to brickd
$ipcon->connect(&HOST, &PORT);
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 methods listed below are thread-safe.
IPConnection
->
new
()¶Creates an IP Connection object that can be used to enumerate the available devices. It is also required for the constructor of Bricks and Bricklets.
IPConnection
->
connect
($host, $port)¶Parameters: |
|
---|---|
Return type: | undef |
Creates a TCP/IP connection to the given $host
and $port
. The host and port
can refer to a Brick Daemon or to a WIFI/Ethernet Extension.
Devices can only be controlled when the connection was established successfully.
Blocks until the connection is established and throws an exception if there is no Brick Daemon or WIFI/Ethernet Extension listening at the given host and port.
IPConnection
->
disconnect
()¶Return type: | undef |
---|
Disconnects the TCP/IP connection from the Brick Daemon or the WIFI/Ethernet Extension.
IPConnection
->
authenticate
($secret)¶Parameters: | $host -- string |
---|---|
Return type: | undef |
Performs an authentication handshake with the connected Brick Daemon or WIFI/Ethernet Extension. If the handshake succeeds the connection switches from non-authenticated to authenticated state and communication can continue as normal. If the handshake fails then the connection gets closed. Authentication can fail if the wrong secret was used or if authentication is not enabled at all on the Brick Daemon or the WIFI/Ethernet Extension.
See the authentication tutorial for more information.
New in version 2.1.0.
IPConnection
->
get_connection_state
()¶Return type: | int |
---|
Can return the following states:
IPConnection
->
set_auto_reconnect
($auto_reconnect)¶Parameters: | $auto_reconnect -- bool |
---|---|
Return type: | undef |
Enables or disables auto-reconnect. If auto-reconnect is enabled,
the IP Connection will try to reconnect to the previously given
host and port, if the currently existing connection is lost.
Therefore, auto-reconnect only does something after a successful
connect()
call.
Default value is 1.
IPConnection
->
get_auto_reconnect
()¶Return type: | bool |
---|
Returns 1 if auto-reconnect is enabled, 0 otherwise.
IPConnection
->
set_timeout
($timeout)¶Parameters: | $timeout -- float |
---|---|
Return type: | undef |
Sets the timeout in seconds for getters and for setters for which the response expected flag is activated.
Default timeout is 2.5.
IPConnection
->
get_timeout
()¶Return type: | float |
---|
Returns the timeout as set by set_timeout()
.
IPConnection
->
enumerate
()¶Return type: | undef |
---|
Broadcasts an enumerate request. All devices will respond with an enumerate callback.
IPConnection
->
register_callback
($callback_id, $function)¶Parameters: |
|
---|---|
Return type: | undef |
Registers the given $function
name with the given $callback_id
.
The available callback IDs with corresponding function signatures are described below.
Callbacks can be registered to be notified about events. The registration is
done with the register_callback()
function. The first parameter is the callback ID and the second
parameter the callback function:
sub my_callback
{
print "@_[0]";
}
$ipcon->register_callback(IPConnection->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.
IPConnection
->
CALLBACK_ENUMERATE
¶Parameters: |
|
---|
The callback has seven parameters:
$uid
: The UID of the device.$connected_uid
: UID where the device is connected to. For a Bricklet this
is the UID of the Brick or Bricklet it is connected to. For a Brick it is
the UID of the bottommost Brick in the stack. For the bottommost Brick
in a stack it is "0". With this information it is possible to
reconstruct the complete network topology.$position
: For Bricks: '0' - '8' (position in stack). For Bricklets:
'a' - 'h' (position on Brick) or 'i' (position of the Raspberry Pi (Zero) HAT)
or 'z' (Bricklet on Isolator Bricklet).@hardware_version
: Major, minor and release number for hardware version.@firmware_version
: Major, minor and release number for firmware version.$device_identifier
: A number that represents the device.$enumeration_type
: Type of enumeration.Possible enumeration types are:
enumerate()
). This enumeration type can occur multiple times
for the same device.$uid
and
$enumeration_type
are valid.It should be possible to implement plug-and-play functionality with this (as is done in Brick Viewer).
The device identifier numbers can be found here. There are also constants for these numbers named following this pattern:
<device-class>->DEVICE_IDENTIFIER
For example: BrickMaster->DEVICE_IDENTIFIER
or BrickletAmbientLight->DEVICE_IDENTIFIER
.
IPConnection
->
CALLBACK_CONNECTED
¶Parameters: | $connect_reason -- int |
---|
This callback is called whenever the IP Connection got connected to a Brick Daemon or to a WIFI/Ethernet Extension, possible reasons are:
IPConnection
->
CALLBACK_DISCONNECTED
¶Parameters: | $disconnect_reason -- int |
---|
This callback is called whenever the IP Connection got disconnected from a Brick Daemon or from a WIFI/Ethernet Extension, possible reasons are: