Perl - RGB LED Bricklet 2.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

#!/usr/bin/perl

use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletRGBLEDV2;

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

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

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

# Set light blue color
$rl->set_rgb_value(0, 170, 234);

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

Basic Functions¶

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

Parameters:	$uid – Type: string $ipcon – Type: IPConnection
Returns:	$rgb_led_v2 – Type: BrickletRGBLEDV2

Creates an object with the unique device ID $uid:

$rgb_led_v2 = BrickletRGBLEDV2->new("YOUR_DEVICE_UID", $ipcon);

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

BrickletRGBLEDV2->set_rgb_value($r, $g, $b)¶

Parameters:	$r – Type: int, Range: [0 to 255] $g – Type: int, Range: [0 to 255] $b – Type: int, Range: [0 to 255]
Returns:	undef

Sets the r, g and b values for the LED.

BrickletRGBLEDV2->get_rgb_value()¶

Return Array:	0: $r – Type: int, Range: [0 to 255] 1: $g – Type: int, Range: [0 to 255] 2: $b – Type: int, Range: [0 to 255]

Returns the r, g and b values of the LED as set by set_rgb_value().

Advanced Functions¶

BrickletRGBLEDV2->get_spitfp_error_count()¶

Return Array:	0: $error_count_ack_checksum – Type: int, Range: [0 to 232 - 1] 1: $error_count_message_checksum – Type: int, Range: [0 to 232 - 1] 2: $error_count_frame – Type: int, Range: [0 to 232 - 1] 3: $error_count_overflow – Type: int, Range: [0 to 232 - 1]

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.

BrickletRGBLEDV2->set_status_led_config($config)¶

Parameters:	$config – Type: int, Range: See constants, Default: 3
Returns:	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:

For $config:

• BrickletRGBLEDV2->STATUS_LED_CONFIG_OFF = 0
• BrickletRGBLEDV2->STATUS_LED_CONFIG_ON = 1
• BrickletRGBLEDV2->STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRGBLEDV2->STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRGBLEDV2->get_status_led_config()¶

Returns:	$config – Type: int, Range: See constants, Default: 3

Returns the configuration as set by set_status_led_config()

The following constants are available for this function:

For $config:

• BrickletRGBLEDV2->STATUS_LED_CONFIG_OFF = 0
• BrickletRGBLEDV2->STATUS_LED_CONFIG_ON = 1
• BrickletRGBLEDV2->STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRGBLEDV2->STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRGBLEDV2->get_chip_temperature()¶

Returns:	$temperature – Type: int, Unit: 1 °C, Range: [-215 to 215 - 1]

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.

BrickletRGBLEDV2->reset()¶

Returns:	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!

BrickletRGBLEDV2->get_identity()¶

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 216 - 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.

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.

BrickletRGBLEDV2->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.

BrickletRGBLEDV2->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:

• BrickletRGBLEDV2->FUNCTION_SET_RGB_VALUE = 1
• BrickletRGBLEDV2->FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletRGBLEDV2->FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletRGBLEDV2->FUNCTION_RESET = 243
• BrickletRGBLEDV2->FUNCTION_WRITE_UID = 248

BrickletRGBLEDV2->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.

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:

• BrickletRGBLEDV2->FUNCTION_SET_RGB_VALUE = 1
• BrickletRGBLEDV2->FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletRGBLEDV2->FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletRGBLEDV2->FUNCTION_RESET = 243
• BrickletRGBLEDV2->FUNCTION_WRITE_UID = 248

BrickletRGBLEDV2->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.

Internal Functions¶

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.

BrickletRGBLEDV2->set_bootloader_mode($mode)¶

Parameters:	$mode – Type: int, Range: See constants
Returns:	$status – Type: int, Range: See constants

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:

• BrickletRGBLEDV2->BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE = 1
• BrickletRGBLEDV2->BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For $status:

• BrickletRGBLEDV2->BOOTLOADER_STATUS_OK = 0
• BrickletRGBLEDV2->BOOTLOADER_STATUS_INVALID_MODE = 1
• BrickletRGBLEDV2->BOOTLOADER_STATUS_NO_CHANGE = 2
• BrickletRGBLEDV2->BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
• BrickletRGBLEDV2->BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
• BrickletRGBLEDV2->BOOTLOADER_STATUS_CRC_MISMATCH = 5

BrickletRGBLEDV2->get_bootloader_mode()¶

Returns:	$mode – Type: int, Range: See constants

Returns the current bootloader mode, see set_bootloader_mode().

The following constants are available for this function:

For $mode:

• BrickletRGBLEDV2->BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE = 1
• BrickletRGBLEDV2->BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletRGBLEDV2->BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

BrickletRGBLEDV2->set_write_firmware_pointer($pointer)¶

Parameters:	$pointer – Type: int, Unit: 1 B, Range: [0 to 232 - 1]
Returns:	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.

BrickletRGBLEDV2->write_firmware(\@data)¶

Parameters:	\@data – Type: [int, ...], Length: 64, Range: [0 to 255]
Returns:	$status – Type: int, Range: [0 to 255]

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.

BrickletRGBLEDV2->write_uid($uid)¶

Parameters:	$uid – Type: int, Range: [0 to 232 - 1]
Returns:	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.

BrickletRGBLEDV2->read_uid()¶

Returns:	$uid – Type: int, Range: [0 to 232 - 1]

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

Constants¶

BrickletRGBLEDV2->DEVICE_IDENTIFIER¶

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

BrickletRGBLEDV2->DEVICE_DISPLAY_NAME¶

This constant represents the human readable name of a RGB LED Bricklet 2.0.