This is the description of the Perl API bindings for the Industrial Analog Out Bricklet 2.0. General information and technical specifications for the Industrial Analog Out Bricklet 2.0 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_simple_current.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 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletIndustrialAnalogOutV2;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Industrial Analog Out Bricklet 2.0
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $iao = Tinkerforge::BrickletIndustrialAnalogOutV2->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Set output current to 4.5mA
$iao->set_current(4500);
$iao->set_enabled(1);
print "Press key to exit\n";
<STDIN>;
$iao->set_enabled(0);
$ipcon->disconnect();
|
Download (example_simple_voltage.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 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletIndustrialAnalogOutV2;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your Industrial Analog Out Bricklet 2.0
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $iao = Tinkerforge::BrickletIndustrialAnalogOutV2->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Set output voltage to 3.3V
$iao->set_voltage(3300);
$iao->set_enabled(1);
print "Press key to exit\n";
<STDIN>;
$iao->set_enabled(0);
$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.
BrickletIndustrialAnalogOutV2
->
new
($uid, $ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID $uid
:
$industrial_analog_out_v2 = BrickletIndustrialAnalogOutV2->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected.
BrickletIndustrialAnalogOutV2
->
set_enabled
($enabled)¶Parameters: |
|
---|---|
Returns: |
|
Enables/disables the output of voltage and current.
BrickletIndustrialAnalogOutV2
->
get_enabled
()¶Returns: |
|
---|
Returns true if output of voltage and current is enabled, false otherwise.
BrickletIndustrialAnalogOutV2
->
set_voltage
($voltage)¶Parameters: |
|
---|---|
Returns: |
|
Sets the output voltage.
The output voltage and output current are linked. Changing the output voltage also changes the output current.
BrickletIndustrialAnalogOutV2
->
get_voltage
()¶Returns: |
|
---|
Returns the voltage as set by set_voltage()
.
BrickletIndustrialAnalogOutV2
->
set_current
($current)¶Parameters: |
|
---|---|
Returns: |
|
Sets the output current.
The output current and output voltage are linked. Changing the output current also changes the output voltage.
BrickletIndustrialAnalogOutV2
->
get_current
()¶Returns: |
|
---|
Returns the current as set by set_current()
.
BrickletIndustrialAnalogOutV2
->
set_out_led_config
($config)¶Parameters: |
|
---|---|
Returns: |
|
You can turn the Out LED off, on or show a heartbeat. You can also set the LED to "Out Status". In this mode the LED can either be turned on with a pre-defined threshold or the intensity of the LED can change with the output value (voltage or current).
You can configure the channel status behavior with set_out_led_status_config()
.
The following constants are available for this function:
For $config:
BrickletIndustrialAnalogOutV2
->
get_out_led_config
()¶Returns: |
|
---|
Returns the Out LED configuration as set by set_out_led_config()
The following constants are available for this function:
For $config:
BrickletIndustrialAnalogOutV2
->
set_out_led_status_config
($min, $max, $config)¶Parameters: |
|
---|---|
Returns: |
|
Sets the Out LED status config. This config is used if the Out LED is
configured as "Out Status", see set_out_led_config()
.
For each channel you can choose between threshold and intensity mode.
In threshold mode you can define a positive or a negative threshold. For a positive threshold set the "min" parameter to the threshold value in mV or µA above which the LED should turn on and set the "max" parameter to 0. Example: If you set a positive threshold of 5V, the LED will turn on as soon as the output value exceeds 5V and turn off again if it goes below 5V. For a negative threshold set the "max" parameter to the threshold value in mV or µA below which the LED should turn on and set the "min" parameter to 0. Example: If you set a negative threshold of 5V, the LED will turn on as soon as the output value goes below 5V and the LED will turn off when the output value exceeds 5V.
In intensity mode you can define a range mV or µA that is used to scale the brightness of the LED. Example with min=2V, max=8V: The LED is off at 2V and below, on at 8V and above and the brightness is linearly scaled between the values 2V and 8V. If the min value is greater than the max value, the LED brightness is scaled the other way around.
The following constants are available for this function:
For $config:
BrickletIndustrialAnalogOutV2
->
get_out_led_status_config
()¶Return Array: |
|
---|
Returns the Out LED status configuration as set by set_out_led_status_config()
.
The following constants are available for this function:
For $config:
BrickletIndustrialAnalogOutV2
->
set_configuration
($voltage_range, $current_range)¶Parameters: |
|
---|---|
Returns: |
|
Configures the voltage and current range.
Possible voltage ranges are:
Possible current ranges are:
The resolution will always be 12 bit. This means, that the precision is higher with a smaller range.
The following constants are available for this function:
For $voltage_range:
For $current_range:
BrickletIndustrialAnalogOutV2
->
get_configuration
()¶Return Array: |
|
---|
Returns the configuration as set by set_configuration()
.
The following constants are available for this function:
For $voltage_range:
For $current_range:
BrickletIndustrialAnalogOutV2
->
get_spitfp_error_count
()¶Return Array: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
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.
BrickletIndustrialAnalogOutV2
->
set_status_led_config
($config)¶Parameters: |
|
---|---|
Returns: |
|
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:
For $config:
BrickletIndustrialAnalogOutV2
->
get_status_led_config
()¶Returns: |
|
---|
Returns the configuration as set by set_status_led_config()
The following constants are available for this function:
For $config:
BrickletIndustrialAnalogOutV2
->
get_chip_temperature
()¶Returns: |
|
---|
Returns the temperature 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.
BrickletIndustrialAnalogOutV2
->
reset
()¶Returns: |
|
---|
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!
BrickletIndustrialAnalogOutV2
->
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.
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.
BrickletIndustrialAnalogOutV2
->
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.
BrickletIndustrialAnalogOutV2
->
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:
BrickletIndustrialAnalogOutV2
->
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:
BrickletIndustrialAnalogOutV2
->
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.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletIndustrialAnalogOutV2
->
set_bootloader_mode
($mode)¶Parameters: |
|
---|---|
Returns: |
|
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:
For $mode:
For $status:
BrickletIndustrialAnalogOutV2
->
get_bootloader_mode
()¶Returns: |
|
---|
Returns the current bootloader mode, see set_bootloader_mode()
.
The following constants are available for this function:
For $mode:
BrickletIndustrialAnalogOutV2
->
set_write_firmware_pointer
($pointer)¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletIndustrialAnalogOutV2
->
write_firmware
(\@data)¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletIndustrialAnalogOutV2
->
write_uid
($uid)¶Parameters: |
|
---|---|
Returns: |
|
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.
BrickletIndustrialAnalogOutV2
->
read_uid
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletIndustrialAnalogOutV2
->
DEVICE_IDENTIFIER
¶This constant is used to identify a Industrial Analog Out Bricklet 2.0.
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.
BrickletIndustrialAnalogOutV2
->
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Industrial Analog Out Bricklet 2.0.