This is the description of the Perl API bindings for the RS232 Bricklet. General information and technical specifications for the RS232 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_loopback.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 | #!/usr/bin/perl
# For this example connect the RX1 and TX pin to receive the send message
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletRS232;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your RS232 Bricklet
# Convert string to char array with length 60, as needed by write
sub string_to_char_array
{
my ($message) = @_;
my @chars = split('', $message);
my @array = ("\0") x 60;
for my $i (0..(scalar(@chars) - 1)) {
$array[$i] = $chars[$i];
}
return \@array;
}
# Assume that the message consists of ASCII characters and
# convert it from an array of chars to a string
sub char_array_to_string
{
my ($message, $length) = @_;
return substr(join('', @{$message}), 0, $length);
}
# Callback subroutine for read callback
sub cb_read
{
my ($message, $length) = @_;
my $str = char_array_to_string($message, $length);
print "Message (Length: " . $length . "): \"" . $str . "\"\n";
}
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $rs232 = Tinkerforge::BrickletRS232->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Register read callback to subroutine cb_read
$rs232->register_callback($rs232->CALLBACK_READ, 'cb_read');
# Enable read callback
$rs232->enable_read_callback();
# Write "test" string
my $message = string_to_char_array('test');
$rs232->write($message, 4);
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.
BrickletRS232
->
new
($uid, $ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID $uid
:
$rs232 = BrickletRS232->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected.
BrickletRS232
->
write
(\@message, $length)¶Parameters: |
|
---|---|
Returns: |
|
Writes a string of up to 60 characters to the RS232 interface. The string can be binary data, ASCII or similar is not necessary.
The length of the string has to be given as an additional parameter.
The return value is the number of bytes that could be written.
See set_configuration()
for configuration possibilities
regarding baudrate, parity and so on.
BrickletRS232
->
read
()¶Return Array: |
|
---|
Returns the currently buffered message. The maximum length of message is 60. If the returned length is 0, no new data was available.
Instead of polling with this function, you can also use
callbacks. See enable_read_callback()
and CALLBACK_READ
callback.
BrickletRS232
->
set_configuration
($baudrate, $parity, $stopbits, $wordlength, $hardware_flowcontrol, $software_flowcontrol)¶Parameters: |
|
---|---|
Returns: |
|
Sets the configuration for the RS232 communication.
Hard-/Software flow control can either be on or off but not both simultaneously on.
The following constants are available for this function:
For $baudrate:
For $parity:
For $stopbits:
For $wordlength:
For $hardware_flowcontrol:
For $software_flowcontrol:
BrickletRS232
->
get_configuration
()¶Return Array: |
|
---|
Returns the configuration as set by set_configuration()
.
The following constants are available for this function:
For $baudrate:
For $parity:
For $stopbits:
For $wordlength:
For $hardware_flowcontrol:
For $software_flowcontrol:
BrickletRS232
->
set_break_condition
($break_time)¶Parameters: |
|
---|---|
Returns: |
|
Sets a break condition (the TX output is forced to a logic 0 state). The parameter sets the hold-time of the break condition.
New in version 2.0.2 (Plugin).
BrickletRS232
->
read_frame
()¶Return Array: |
|
---|
Returns up to one frame of bytes from the read buffer.
The frame size is configured with set_frame_readable_callback_configuration()
.
If the returned length is 0, no new data was available.
New in version 2.0.4 (Plugin).
BrickletRS232
->
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.
BrickletRS232
->
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.
BrickletRS232
->
enable_read_callback
()¶Returns: |
|
---|
Enables the CALLBACK_READ
callback. This will disable the CALLBACK_FRAME_READABLE
callback.
By default the callback is disabled.
BrickletRS232
->
disable_read_callback
()¶Returns: |
|
---|
Disables the CALLBACK_READ
callback.
By default the callback is disabled.
BrickletRS232
->
is_read_callback_enabled
()¶Returns: |
|
---|
Returns true if the CALLBACK_READ
callback is enabled,
false otherwise.
BrickletRS232
->
set_frame_readable_callback_configuration
($frame_size)¶Parameters: |
|
---|---|
Returns: |
|
Configures the CALLBACK_FRAME_READABLE
callback. The frame size is the number of bytes, that have to be readable to trigger the callback.
A frame size of 0 disables the callback. A frame size greater than 0 enables the callback and disables the CALLBACK_READ
callback.
By default the callback is disabled.
New in version 2.0.4 (Plugin).
BrickletRS232
->
get_frame_readable_callback_configuration
()¶Returns: |
|
---|
Returns the callback configuration as set by set_frame_readable_callback_configuration()
.
New in version 2.0.4 (Plugin).
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]";
}
$rs232->register_callback(BrickletRS232->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.
BrickletRS232
->
CALLBACK_READ
¶Callback Parameters: |
|
---|
This callback is called if new data is available. The message has a maximum size of 60 characters. The actual length of the message is given in addition.
To enable this callback, use enable_read_callback()
.
BrickletRS232
->
CALLBACK_ERROR
¶Callback Parameters: |
|
---|
This callback is called if an error occurs. Possible errors are overrun, parity or framing error.
The following constants are available for this function:
For $error:
New in version 2.0.1 (Plugin).
BrickletRS232
->
CALLBACK_FRAME_READABLE
¶Callback Parameters: |
|
---|
This callback is called if at least one frame of data is readable. The frame size is configured with set_frame_readable_callback_configuration()
.
The frame count parameter is the number of frames that can be read.
This callback is triggered only once until read()
or read_frame()
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the read_frame()
function, every time the callback triggers without checking the frame count parameter.
New in version 2.0.4 (Plugin).
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.
BrickletRS232
->
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.
BrickletRS232
->
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:
BrickletRS232
->
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:
BrickletRS232
->
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.
BrickletRS232
->
DEVICE_IDENTIFIER
¶This constant is used to identify a RS232 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.
BrickletRS232
->
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a RS232 Bricklet.