This is the description of the Perl API bindings for the Remote Switch Bricklet. General information and technical specifications for the Remote Switch 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).
Download (example_switch_socket.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 | #!/usr/bin/perl
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletRemoteSwitch;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'ufe'; # Change to your UID
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $rs = Tinkerforge::BrickletRemoteSwitch->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Switch on a type A socket with house code 17 and receiver code 1.
# House code 17 is 10001 in binary (least-significant bit first)
# and means that the DIP switches 1 and 5 are on and 2-4 are off.
# Receiver code 1 is 10000 in binary (least-significant bit first)
# and means that the DIP switch A is on and B-E are off.
$rs->switch_socket_a(17, 1, $rs->SWITCH_TO_ON);
print "Press any 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.
Parameters: |
|
---|---|
Return type: | BrickletRemoteSwitch |
Creates an object with the unique device ID $uid:
$remote_switch = BrickletRemoteSwitch->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected (see examples above).
Parameters: |
|
---|---|
Return type: | undef |
This function is deprecated, use switch_socket_a() instead.
The following constants are available for this function:
Return type: | int |
---|
Returns the current switching state. If the current state is busy, the Bricklet is currently sending a code to switch a socket. It will not accept any calls of switch_socket() until the state changes to ready.
How long the switching takes is dependent on the number of repeats, see set_repeats().
The following constants are available for this function:
Parameters: |
|
---|---|
Return type: | undef |
To switch a type A socket you have to give the house code, receiver code and the state (on or off) you want to switch to.
The house code and receiver code have a range of 0 to 31 (5bit).
A detailed description on how you can figure out the house and receiver code can be found here.
The following constants are available for this function:
New in version 2.0.1 (Plugin).
Parameters: |
|
---|---|
Return type: | undef |
To switch a type B socket you have to give the address, unit and the state (on or off) you want to switch to.
The address has a range of 0 to 67108863 (26bit) and the unit has a range of 0 to 15 (4bit). To switch all devices with the same address use 255 for the unit.
A detailed description on how you can teach a socket the address and unit can be found here.
The following constants are available for this function:
New in version 2.0.1 (Plugin).
Parameters: |
|
---|---|
Return type: | undef |
To control a type B dimmer you have to give the address, unit and the dim value you want to set the dimmer to.
The address has a range of 0 to 67108863 (26bit), the unit and the dim value has a range of 0 to 15 (4bit).
A detailed description on how you can teach a dimmer the address and unit can be found here.
New in version 2.0.1 (Plugin).
Parameters: |
|
---|---|
Return type: | undef |
To switch a type C socket you have to give the system code, device code and the state (on or off) you want to switch to.
The system code has a range of 'A' to 'P' (4bit) and the device code has a range of 1 to 16 (4bit).
A detailed description on how you can figure out the system and device code can be found here.
The following constants are available for this function:
New in version 2.0.1 (Plugin).
Parameters: | $repeats -- int |
---|---|
Return type: | undef |
Sets the number of times the code is send when of the switch_socket() functions is called. The repeats basically correspond to the amount of time that a button of the remote is pressed.
Some dimmers are controlled by the length of a button pressed, this can be simulated by increasing the repeats.
The default value is 5.
Return type: | int |
---|
Returns the number of repeats as set by set_repeats().
Return type: | [int, int, int] |
---|
Returns the version of the API definition (major, minor, revision) 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.
Parameters: | $function_id -- int |
---|---|
Return type: | bool |
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 send and errors are silently ignored, because they cannot be detected.
See set_response_expected() for the list of function ID constants available for this function.
Parameters: |
|
---|---|
Return type: | undef |
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 and callbacks it is always disabled.
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 send and errors are silently ignored, because they cannot be detected.
The following function ID constants are available for this function:
Parameters: | $response_expected -- bool |
---|---|
Return type: | undef |
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Return type: | [string, string, char, [int, int, int], [int, int, int], int] |
---|
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' or 'd'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
The returned array contains the elements uid, connected_uid, position, hardware_version, firmware_version and device_identifier.
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]";
}
$remote_switch->register_callback(BrickletRemoteSwitch->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.
This callback is called whenever the switching state changes from busy to ready, see get_switching_state().
This constant is used to identify a Remote Switch Bricklet.
The get_identity() function and the CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.