Perl - Industrial Dual Relay Bricklet

This is the description of the Perl API bindings for the Industrial Dual Relay Bricklet. General information and technical specifications for the Industrial Dual Relay Bricklet are summarized in its hardware description.

An installation guide for the Perl API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (example_simple.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
#!/usr/bin/perl

use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletIndustrialDualRelay;

use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Industrial Dual Relay Bricklet

my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $idr = Tinkerforge::BrickletIndustrialDualRelay->new(&UID, $ipcon); # Create device object

$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected

# Turn relays alternating on/off 10 times with 1 second delay
for (my $i = 0; $i < 5; $i++)
{
    sleep(1);
    $idr->set_value(1, 0);
    sleep(1);
    $idr->set_value(0, 1);
}

print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();

API

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:

  • Error->ALREADY_CONNECTED = 11
  • Error->NOT_CONNECTED = 12
  • Error->CONNECT_FAILED = 13
  • Error->INVALID_FUNCTION_ID = 21
  • Error->TIMEOUT = 31
  • Error->INVALID_PARAMETER = 41
  • Error->FUNCTION_NOT_SUPPORTED = 42
  • Error->UNKNOWN_ERROR = 43

All methods listed below are thread-safe.

Basic Functions

BrickletIndustrialDualRelay->new($uid, $ipcon)
Parameters:
  • $uid -- string
  • $ipcon -- IPConnection
Return type:

BrickletIndustrialDualRelay

Creates an object with the unique device ID $uid:

$industrial_dual_relay = BrickletIndustrialDualRelay->new("YOUR_DEVICE_UID", $ipcon);

This object can then be used after the IP Connection is connected (see examples above).

BrickletIndustrialDualRelay->set_value($channel0, $channel1)
Parameters:
  • $channel0 -- bool
  • $channel1 -- bool
Return type:

undef

Sets the state of the relays, true means on and false means off. For example: (true, false) turns relay 0 on and relay 1 off.

If you just want to set one of the relays and don't know the current state of the other relay, you can get the state with get_value() or you can use set_selected_value().

Running monoflop timers will be overwritten if this function is called.

The default value is (false, false).

BrickletIndustrialDualRelay->get_value()
Return type:[bool, bool]

Returns the state of the relays, true means on and false means off.

The returned array contains the elements channel0 and channel1.

Advanced Functions

BrickletIndustrialDualRelay->set_monoflop($channel, $value, $time)
Parameters:
  • $channel -- int
  • $value -- bool
  • $time -- int
Return type:

undef

The first parameter can be 0 or 1 (relay 0 or relay 1). The second parameter is the desired state of the relay (true means on and false means off). The third parameter indicates the time (in ms) that the relay should hold the state.

If this function is called with the parameters (1, true, 1500): Relay 1 will turn on and in 1.5s it will turn off again.

A monoflop can be used as a failsafe mechanism. For example: Lets assume you have a RS485 bus and a Industrial Dual Relay Bricklet connected to one of the slave stacks. You can now call this function every second, with a time parameter of two seconds. The relay will be on all the time. If now the RS485 connection is lost, the relay will turn off in at most two seconds.

BrickletIndustrialDualRelay->get_monoflop($channel)
Parameters:$channel -- int
Return type:[bool, int, int]

Returns (for the given relay) the current state and the time as set by set_monoflop() as well as the remaining time until the state flips.

If the timer is not running currently, the remaining time will be returned as 0.

The returned array contains the elements value, time and time_remaining.

BrickletIndustrialDualRelay->set_selected_value($channel, $value)
Parameters:
  • $channel -- int
  • $value -- bool
Return type:

undef

Sets the state of the selected relay (0 or 1), true means on and false means off.

The other relay remains untouched.

BrickletIndustrialDualRelay->get_api_version()
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.

BrickletIndustrialDualRelay->get_response_expected($function_id)
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.

BrickletIndustrialDualRelay->set_response_expected($function_id, $response_expected)
Parameters:
  • $function_id -- int
  • $response_expected -- bool
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.

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:

  • BrickletIndustrialDualRelay->FUNCTION_SET_VALUE = 1
  • BrickletIndustrialDualRelay->FUNCTION_SET_MONOFLOP = 3
  • BrickletIndustrialDualRelay->FUNCTION_SET_SELECTED_VALUE = 6
  • BrickletIndustrialDualRelay->FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletIndustrialDualRelay->FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletIndustrialDualRelay->FUNCTION_RESET = 243
  • BrickletIndustrialDualRelay->FUNCTION_WRITE_UID = 248
BrickletIndustrialDualRelay->set_response_expected_all($response_expected)
Parameters:$response_expected -- bool
Return type:undef

Changes the response expected flag for all setter and callback configuration functions of this device at once.

BrickletIndustrialDualRelay->get_spitfp_error_count()
Return type:[int, int, int, int]

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

The returned array contains the elements error_count_ack_checksum, error_count_message_checksum, error_count_frame and error_count_overflow.

BrickletIndustrialDualRelay->set_bootloader_mode($mode)
Parameters:$mode -- int
Return type:int

Sets the bootloader mode and returns the status after the requested mode change was instigated.

You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

The following constants are available for this function:

  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_OK = 0
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_INVALID_MODE = 1
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_NO_CHANGE = 2
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BrickletIndustrialDualRelay->BOOTLOADER_STATUS_CRC_MISMATCH = 5
BrickletIndustrialDualRelay->get_bootloader_mode()
Return type:int

Returns the current bootloader mode, see set_bootloader_mode().

The following constants are available for this function:

  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletIndustrialDualRelay->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
BrickletIndustrialDualRelay->set_write_firmware_pointer($pointer)
Parameters:$pointer -- int
Return type:undef

Sets the firmware pointer for write_firmware(). The pointer has to be increased by chunks of size 64. The data is written to flash every 4 chunks (which equals to one page of size 256).

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

BrickletIndustrialDualRelay->write_firmware(@data)
Parameters:@data -- [int, int, ..61x.., int]
Return type:int

Writes 64 Bytes of firmware at the position as written by set_write_firmware_pointer() before. The firmware is written to flash every 4 chunks.

You can only write firmware in bootloader mode.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

BrickletIndustrialDualRelay->set_status_led_config($config)
Parameters:$config -- int
Return type:undef

Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.

The following constants are available for this function:

  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_OFF = 0
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_ON = 1
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletIndustrialDualRelay->get_status_led_config()
Return type:int

Returns the configuration as set by set_status_led_config()

The following constants are available for this function:

  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_OFF = 0
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_ON = 1
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletIndustrialDualRelay->STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletIndustrialDualRelay->get_chip_temperature()
Return type:int

Returns the temperature in °C as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.

BrickletIndustrialDualRelay->reset()
Return type:undef

Calling this function will reset the Bricklet. All configurations will be lost.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

BrickletIndustrialDualRelay->write_uid($uid)
Parameters:$uid -- int
Return type:undef

Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.

We recommend that you use Brick Viewer to change the UID.

BrickletIndustrialDualRelay->read_uid()
Return type:int

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

BrickletIndustrialDualRelay->get_identity()
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.

Callback Configuration Functions

BrickletIndustrialDualRelay->register_callback($id, $callback)
Parameters:
  • $id -- int
  • $callback -- string
Return type:

undef

Registers the given $function name with the given $callback_id.

The available callback IDs with corresponding function signatures are listed below.

Callbacks

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]";
}

$industrial_dual_relay->register_callback(BrickletIndustrialDualRelay->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.

BrickletIndustrialDualRelay->CALLBACK_MONOFLOP_DONE
Parameters:
  • $channel -- int
  • $value -- bool

This callback is triggered whenever a monoflop timer reaches 0. The parameter contain the relay (0 or 1) and the current state of the relay (the state after the monoflop).

Constants

BrickletIndustrialDualRelay->DEVICE_IDENTIFIER

This constant is used to identify a Industrial Dual Relay 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.

BrickletIndustrialDualRelay->DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Industrial Dual Relay Bricklet.