Software / API Bindings / Perl / API Reference and Examples / Bricklets (Discontinued) / Thermocouple Bricklet

Perl - Thermocouple Bricklet¶

This is the description of the Perl API bindings for the Thermocouple Bricklet. General information and technical specifications for the Thermocouple 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)

#!/usr/bin/perl

use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletThermocouple;

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

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

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

# Get current temperature
my $temperature = $t->get_temperature();
print "Temperature: " . $temperature/100.0 . " °C\n";

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

Callback¶

Download (example_callback.pl)

#!/usr/bin/perl

use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletThermocouple;

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

# Callback subroutine for temperature callback
sub cb_temperature
{
    my ($temperature) = @_;

    print "Temperature: " . $temperature/100.0 . " °C\n";
}

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

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

# Register temperature callback to subroutine cb_temperature
$t->register_callback($t->CALLBACK_TEMPERATURE, 'cb_temperature');

# Set period for temperature callback to 1s (1000ms)
# Note: The temperature callback is only called every second
#       if the temperature has changed since the last call!
$t->set_temperature_callback_period(1000);

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

Threshold¶

Download (example_threshold.pl)

#!/usr/bin/perl

use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletThermocouple;

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

# Callback subroutine for temperature reached callback
sub cb_temperature_reached
{
    my ($temperature) = @_;

    print "Temperature: " . $temperature/100.0 . " °C\n";
}

my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $t = Tinkerforge::BrickletThermocouple->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)
$t->set_debounce_period(10000);

# Register temperature reached callback to subroutine cb_temperature_reached
$t->register_callback($t->CALLBACK_TEMPERATURE_REACHED, 'cb_temperature_reached');

# Configure threshold for temperature "greater than 30 °C"
$t->set_temperature_callback_threshold('>', 30*100, 0);

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
Error->STREAM_OUT_OF_SYNC = 51
Error->INVALID_UID = 61
Error->NON_ASCII_CHAR_IN_SECRET = 71
Error->WRONG_DEVICE_TYPE = 81
Error->DEVICE_REPLACED = 82
Error->WRONG_RESPONSE_LENGTH = 83

All functions listed below are thread-safe.

Basic Functions¶

BrickletThermocouple->new($uid, $ipcon)¶

Parameters:	$uid – Type: string $ipcon – Type: IPConnection
Returns:	$thermocouple – Type: BrickletThermocouple

Creates an object with the unique device ID $uid:

$thermocouple = BrickletThermocouple->new("YOUR_DEVICE_UID", $ipcon);

This object can then be used after the IP Connection is connected.

BrickletThermocouple->get_temperature()¶

Returns:	$temperature – Type: int, Unit: 1/100 °C, Range: [-21000 to 180000]

Returns the temperature of the thermocouple.

If you want to get the temperature periodically, it is recommended to use the CALLBACK_TEMPERATURE callback and set the period with set_temperature_callback_period().

Advanced Functions¶

BrickletThermocouple->set_configuration($averaging, $thermocouple_type, $filter)¶

Parameters:	$averaging – Type: int, Range: See constants, Default: 16 $thermocouple_type – Type: int, Range: See constants, Default: 3 $filter – Type: int, Range: See constants, Default: 0
Returns:	undef

You can configure averaging size, thermocouple type and frequency filtering.

Available averaging sizes are 1, 2, 4, 8 and 16 samples.

As thermocouple type you can use B, E, J, K, N, R, S and T. If you have a different thermocouple or a custom thermocouple you can also use G8 and G32. With these types the returned value will not be in °C/100, it will be calculated by the following formulas:

G8: value = 8 * 1.6 * 2^17 * Vin
G32: value = 32 * 1.6 * 2^17 * Vin

where Vin is the thermocouple input voltage.

The frequency filter can be either configured to 50Hz or to 60Hz. You should configure it according to your utility frequency.

The conversion time depends on the averaging and filter configuration, it can be calculated as follows:

60Hz: time = 82 + (samples - 1) * 16.67
50Hz: time = 98 + (samples - 1) * 20

The following constants are available for this function:

For $averaging:

BrickletThermocouple->AVERAGING_1 = 1
BrickletThermocouple->AVERAGING_2 = 2
BrickletThermocouple->AVERAGING_4 = 4
BrickletThermocouple->AVERAGING_8 = 8
BrickletThermocouple->AVERAGING_16 = 16

For $thermocouple_type:

BrickletThermocouple->TYPE_B = 0
BrickletThermocouple->TYPE_E = 1
BrickletThermocouple->TYPE_J = 2
BrickletThermocouple->TYPE_K = 3
BrickletThermocouple->TYPE_N = 4
BrickletThermocouple->TYPE_R = 5
BrickletThermocouple->TYPE_S = 6
BrickletThermocouple->TYPE_T = 7
BrickletThermocouple->TYPE_G8 = 8
BrickletThermocouple->TYPE_G32 = 9

For $filter:

BrickletThermocouple->FILTER_OPTION_50HZ = 0
BrickletThermocouple->FILTER_OPTION_60HZ = 1

BrickletThermocouple->get_configuration()¶

Return Array:	0: $averaging – Type: int, Range: See constants, Default: 16 1: $thermocouple_type – Type: int, Range: See constants, Default: 3 2: $filter – Type: int, Range: See constants, Default: 0

Returns the configuration as set by set_configuration().

The following constants are available for this function:

For $averaging:

BrickletThermocouple->AVERAGING_1 = 1
BrickletThermocouple->AVERAGING_2 = 2
BrickletThermocouple->AVERAGING_4 = 4
BrickletThermocouple->AVERAGING_8 = 8
BrickletThermocouple->AVERAGING_16 = 16

For $thermocouple_type:

BrickletThermocouple->TYPE_B = 0
BrickletThermocouple->TYPE_E = 1
BrickletThermocouple->TYPE_J = 2
BrickletThermocouple->TYPE_K = 3
BrickletThermocouple->TYPE_N = 4
BrickletThermocouple->TYPE_R = 5
BrickletThermocouple->TYPE_S = 6
BrickletThermocouple->TYPE_T = 7
BrickletThermocouple->TYPE_G8 = 8
BrickletThermocouple->TYPE_G32 = 9

For $filter:

BrickletThermocouple->FILTER_OPTION_50HZ = 0
BrickletThermocouple->FILTER_OPTION_60HZ = 1

BrickletThermocouple->get_error_state()¶

Return Array:	0: $over_under – Type: bool 1: $open_circuit – Type: bool

Returns the current error state. There are two possible errors:

Over/Under Voltage and
Open Circuit.

Over/Under Voltage happens for voltages below 0V or above 3.3V. In this case it is very likely that your thermocouple is defective. An Open Circuit error indicates that there is no thermocouple connected.

You can use the CALLBACK_ERROR_STATE callback to automatically get triggered when the error state changes.

BrickletThermocouple->get_identity()¶

Return Array:

Return Array:	0: $uid – Type: string, Length: up to 8 1: $connected_uid – Type: string, Length: up to 8 2: $position – Type: char, Range: ['a' to 'h', 'z'] 3: \@hardware_version – Type: [int, ...], Length: 3 0: $major – Type: int, Range: [0 to 255] 1: $minor – Type: int, Range: [0 to 255] 2: $revision – Type: int, Range: [0 to 255] 4: \@firmware_version – Type: [int, ...], Length: 3 0: $major – Type: int, Range: [0 to 255] 1: $minor – Type: int, Range: [0 to 255] 2: $revision – Type: int, Range: [0 to 255] 5: $device_identifier – Type: int, Range: [0 to 2¹⁶ - 1]

0: $uid – Type: string, Length: up to 8
1: $connected_uid – Type: string, Length: up to 8
2: $position – Type: char, Range: ['a' to 'h', 'z']
3: \@hardware_version – Type: [int, ...], Length: 3

0: $major – Type: int, Range: [0 to 255]
1: $minor – Type: int, Range: [0 to 255]
2: $revision – Type: int, Range: [0 to 255]

4: \@firmware_version – Type: [int, ...], Length: 3

0: $major – Type: int, Range: [0 to 255]
1: $minor – Type: int, Range: [0 to 255]
2: $revision – Type: int, Range: [0 to 255]

5: $device_identifier – Type: int, Range: [0 to 2¹⁶ - 1]

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.

Callback Configuration Functions¶

BrickletThermocouple->register_callback($callback_id, $function)¶

Parameters:	$callback_id – Type: int $function – Type: string
Returns:	undef

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

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

BrickletThermocouple->set_temperature_callback_period($period)¶

Parameters:	$period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0
Returns:	undef

Sets the period with which the CALLBACK_TEMPERATURE callback is triggered periodically. A value of 0 turns the callback off.

The CALLBACK_TEMPERATURE callback is only triggered if the temperature has changed since the last triggering.

BrickletThermocouple->get_temperature_callback_period()¶

Returns:	$period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0

Returns the period as set by set_temperature_callback_period().

BrickletThermocouple->set_temperature_callback_threshold($option, $min, $max)¶

Parameters:	$option – Type: char, Range: See constants, Default: 'x' $min – Type: int, Unit: 1/100 °C, Range: [-2³¹ to 2³¹ - 1], Default: 0 $max – Type: int, Unit: 1/100 °C, Range: [-2³¹ to 2³¹ - 1], Default: 0
Returns:	undef

Sets the thresholds for the CALLBACK_TEMPERATURE_REACHED callback.

The following options are possible:

Option	Description
'x'	Callback is turned off
'o'	Callback is triggered when the temperature is outside the min and max values
'i'	Callback is triggered when the temperature is inside the min and max values
'<'	Callback is triggered when the temperature is smaller than the min value (max is ignored)
'>'	Callback is triggered when the temperature is greater than the min value (max is ignored)

The following constants are available for this function:

For $option:

BrickletThermocouple->THRESHOLD_OPTION_OFF = 'x'
BrickletThermocouple->THRESHOLD_OPTION_OUTSIDE = 'o'
BrickletThermocouple->THRESHOLD_OPTION_INSIDE = 'i'
BrickletThermocouple->THRESHOLD_OPTION_SMALLER = '<'
BrickletThermocouple->THRESHOLD_OPTION_GREATER = '>'

BrickletThermocouple->get_temperature_callback_threshold()¶

Return Array:	0: $option – Type: char, Range: See constants, Default: 'x' 1: $min – Type: int, Unit: 1/100 °C, Range: [-2³¹ to 2³¹ - 1], Default: 0 2: $max – Type: int, Unit: 1/100 °C, Range: [-2³¹ to 2³¹ - 1], Default: 0

Returns the threshold as set by set_temperature_callback_threshold().

The following constants are available for this function:

For $option:

BrickletThermocouple->THRESHOLD_OPTION_OFF = 'x'
BrickletThermocouple->THRESHOLD_OPTION_OUTSIDE = 'o'
BrickletThermocouple->THRESHOLD_OPTION_INSIDE = 'i'
BrickletThermocouple->THRESHOLD_OPTION_SMALLER = '<'
BrickletThermocouple->THRESHOLD_OPTION_GREATER = '>'

BrickletThermocouple->set_debounce_period($debounce)¶

Parameters:	$debounce – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 100
Returns:	undef

Sets the period with which the threshold callback

CALLBACK_TEMPERATURE_REACHED

is triggered, if the threshold

set_temperature_callback_threshold()

keeps being reached.

BrickletThermocouple->get_debounce_period()¶

Returns:	$debounce – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 100

Returns the debounce period as set by set_debounce_period().

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

$thermocouple->register_callback(BrickletThermocouple->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.

BrickletThermocouple->CALLBACK_TEMPERATURE¶

Callback Parameters:	$temperature – Type: int, Unit: 1/100 °C, Range: [-21000 to 180000]

This callback is triggered periodically with the period that is set by set_temperature_callback_period(). The parameter is the temperature of the thermocouple.

The CALLBACK_TEMPERATURE callback is only triggered if the temperature has changed since the last triggering.

BrickletThermocouple->CALLBACK_TEMPERATURE_REACHED¶

Callback Parameters:	$temperature – Type: int, Unit: 1/100 °C, Range: [-21000 to 180000]

This callback is triggered when the threshold as set by set_temperature_callback_threshold() is reached. The parameter is the temperature of the thermocouple.

If the threshold keeps being reached, the callback is triggered periodically with the period as set by set_debounce_period().

BrickletThermocouple->CALLBACK_ERROR_STATE¶

Callback Parameters:	$over_under – Type: bool $open_circuit – Type: bool

This Callback is triggered every time the error state changes (see get_error_state()).

Virtual Functions¶

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.

BrickletThermocouple->get_api_version()¶

Return Array:	0: \@api_version – Type: [int, ...], Length: 3 0: $major – Type: int, Range: [0 to 255] 1: $minor – Type: int, Range: [0 to 255] 2: $revision – Type: int, Range: [0 to 255]

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.

BrickletThermocouple->get_response_expected($function_id)¶

Parameters:	$function_id – Type: int, Range: See constants
Returns:	$response_expected – 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 sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For $function_id:

BrickletThermocouple->FUNCTION_SET_TEMPERATURE_CALLBACK_PERIOD = 2
BrickletThermocouple->FUNCTION_SET_TEMPERATURE_CALLBACK_THRESHOLD = 4
BrickletThermocouple->FUNCTION_SET_DEBOUNCE_PERIOD = 6
BrickletThermocouple->FUNCTION_SET_CONFIGURATION = 10

BrickletThermocouple->set_response_expected($function_id, $response_expected)¶

Parameters:	$function_id – Type: int, Range: See constants $response_expected – Type: bool
Returns:	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.

The following constants are available for this function:

For $function_id:

BrickletThermocouple->FUNCTION_SET_TEMPERATURE_CALLBACK_PERIOD = 2
BrickletThermocouple->FUNCTION_SET_TEMPERATURE_CALLBACK_THRESHOLD = 4
BrickletThermocouple->FUNCTION_SET_DEBOUNCE_PERIOD = 6
BrickletThermocouple->FUNCTION_SET_CONFIGURATION = 10

BrickletThermocouple->set_response_expected_all($response_expected)¶

Parameters:	$response_expected – Type: bool
Returns:	undef

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

Constants¶

BrickletThermocouple->DEVICE_IDENTIFIER¶

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

BrickletThermocouple->DEVICE_DISPLAY_NAME¶: This constant represents the human readable name of a Thermocouple Bricklet.