Ruby - Isolator Bricklet¶

Simple¶

Download (example_simple.rb)

 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

#!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-

require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_isolator'

include Tinkerforge

HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Isolator Bricklet

ipcon = IPConnection.new # Create IP connection
i = BrickletIsolator.new UID, ipcon # Create device object

ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected

# Get current statistics as [messages_from_brick, messages_from_bricklet,
#                            connected_bricklet_device_identifier, connected_bricklet_uid]
statistics = i.get_statistics

puts "Messages From Brick: #{statistics[0]}"
puts "Messages From Bricklet: #{statistics[1]}"
puts "Connected Bricklet Device Identifier: #{statistics[2]}"
puts "Connected Bricklet UID: #{statistics[3]}"

puts 'Press key to exit'
$stdin.gets
ipcon.disconnect

Basic Functions¶

BrickletIsolator::new(uid, ipcon) → isolator¶

Parameters:	uid – Type: str ipcon – Type: IPConnection
Returns:	isolator – Type: BrickletIsolator

Creates an object with the unique device ID uid:

isolator = BrickletIsolator.new 'YOUR_DEVICE_UID', ipcon

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

BrickletIsolator#get_statistics → [int, int, int, str]¶

Return Array:	0: messages_from_brick – Type: int, Range: [0 to 232 - 1] 1: messages_from_bricklet – Type: int, Range: [0 to 232 - 1] 2: connected_bricklet_device_identifier – Type: int, Range: [0 to 216 - 1] 3: connected_bricklet_uid – Type: str, Length: up to 8

Returns statistics for the Isolator Bricklet.

Advanced Functions¶

BrickletIsolator#set_spitfp_baudrate_config(enable_dynamic_baudrate, minimum_dynamic_baudrate) → nil¶

Parameters:	enable_dynamic_baudrate – Type: bool, Default: true minimum_dynamic_baudrate – Type: int, Unit: 1 Bd, Range: [400000 to 2000000], Default: 400000

The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Isolator Bricklet will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.

The baudrate for communication config between Brick and Isolator Bricklet can be set through the API of the Brick.

The baudrate will be increased exponentially if lots of data is sent/received and decreased linearly if little data is sent/received.

This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.

In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.

The maximum value of the baudrate can be set per port with the function #set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate as set by #set_spitfp_baudrate will be used statically.

BrickletIsolator#get_spitfp_baudrate_config → [bool, int]¶

Return Array:	0: enable_dynamic_baudrate – Type: bool, Default: true 1: minimum_dynamic_baudrate – Type: int, Unit: 1 Bd, Range: [400000 to 2000000], Default: 400000

Returns the baudrate config, see #set_spitfp_baudrate_config.

BrickletIsolator#set_spitfp_baudrate(baudrate) → nil¶

Parameters:	baudrate – Type: int, Unit: 1 Bd, Range: [400000 to 2000000], Default: 1400000

Sets the baudrate for a the communication between Isolator Bricklet and the connected Bricklet. The baudrate for communication between Brick and Isolator Bricklet can be set through the API of the Brick.

If you want to increase the throughput of Bricklets you can increase the baudrate. If you get a high error count because of high interference (see #get_spitfp_error_count) you can decrease the baudrate.

If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see #set_spitfp_baudrate_config).

Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.

BrickletIsolator#get_spitfp_baudrate → int¶

Returns:	baudrate – Type: int, Unit: 1 Bd, Range: [400000 to 2000000], Default: 1400000

Returns the baudrate, see #set_spitfp_baudrate.

BrickletIsolator#get_isolator_spitfp_error_count → [int, int, int, int]¶

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 Isolator Bricklet and the connected Bricklet. Call #get_spitfp_error_count to get the error count between Isolator Bricklet and Brick.

The errors are divided into

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

BrickletIsolator#get_spitfp_error_count → [int, int, int, int]¶

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.

BrickletIsolator#set_status_led_config(config) → nil¶

Parameters:	config – Type: int, Range: See constants, Default: 3

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:

• BrickletIsolator::STATUS_LED_CONFIG_OFF = 0
• BrickletIsolator::STATUS_LED_CONFIG_ON = 1
• BrickletIsolator::STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletIsolator::STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletIsolator#get_status_led_config → int¶

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:

• BrickletIsolator::STATUS_LED_CONFIG_OFF = 0
• BrickletIsolator::STATUS_LED_CONFIG_ON = 1
• BrickletIsolator::STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletIsolator::STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletIsolator#get_chip_temperature → int¶

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.

BrickletIsolator#reset → nil¶

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!

BrickletIsolator#get_identity → [str, str, chr, [int, ...], [int, ...], int]¶

Return Array:

0: uid – Type: str, Length: up to 8 1: connected_uid – Type: str, Length: up to 8 2: position – Type: chr, 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.

Callback Configuration Functions¶

BrickletIsolator#register_callback(callback_id) { |param [, ...]| block } → nil¶

Parameters:	callback_id – Type: int

Registers the given block with the given callback_id.

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

BrickletIsolator#set_statistics_callback_configuration(period, value_has_to_change) → nil¶

Parameters:	period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0 value_has_to_change – Type: bool, Default: false

The period is the period with which the ::CALLBACK_STATISTICS callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

New in version 2.0.2 (Plugin).

BrickletIsolator#get_statistics_callback_configuration → [int, bool]¶

Return Array:	0: period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0 1: value_has_to_change – Type: bool, Default: false

Returns the callback configuration as set by #set_statistics_callback_configuration.

New in version 2.0.2 (Plugin).

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 is a block:

isolator.register_callback BrickletIsolator::CALLBACK_EXAMPLE, do |param|
  puts "#{param}"
end

The available constants with inherent number and type of parameters are described below.

BrickletIsolator::CALLBACK_STATISTICS¶

Callback Parameters:	messages_from_brick – Type: int, Range: [0 to 232 - 1] messages_from_bricklet – Type: int, Range: [0 to 232 - 1] connected_bricklet_device_identifier – Type: int, Range: [0 to 216 - 1] connected_bricklet_uid – Type: str, Length: up to 8

This callback is triggered periodically according to the configuration set by #set_statistics_callback_configuration.

The parameters are the same as #get_statistics.

New in version 2.0.2 (Plugin).

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.

BrickletIsolator#get_api_version → [int, ...]¶

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.

BrickletIsolator#get_response_expected(function_id) → bool¶

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:

• BrickletIsolator::FUNCTION_SET_SPITFP_BAUDRATE_CONFIG = 2
• BrickletIsolator::FUNCTION_SET_SPITFP_BAUDRATE = 4
• BrickletIsolator::FUNCTION_SET_STATISTICS_CALLBACK_CONFIGURATION = 7
• BrickletIsolator::FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletIsolator::FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletIsolator::FUNCTION_RESET = 243
• BrickletIsolator::FUNCTION_WRITE_UID = 248

BrickletIsolator#set_response_expected(function_id, response_expected) → nil¶

Parameters:	function_id – Type: int, Range: See constants response_expected – Type: bool

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:

• BrickletIsolator::FUNCTION_SET_SPITFP_BAUDRATE_CONFIG = 2
• BrickletIsolator::FUNCTION_SET_SPITFP_BAUDRATE = 4
• BrickletIsolator::FUNCTION_SET_STATISTICS_CALLBACK_CONFIGURATION = 7
• BrickletIsolator::FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletIsolator::FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletIsolator::FUNCTION_RESET = 243
• BrickletIsolator::FUNCTION_WRITE_UID = 248

BrickletIsolator#set_response_expected_all(response_expected) → nil¶

Parameters:	response_expected – Type: bool

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.

BrickletIsolator#set_bootloader_mode(mode) → int¶

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:

• BrickletIsolator::BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE = 1
• BrickletIsolator::BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

• BrickletIsolator::BOOTLOADER_STATUS_OK = 0
• BrickletIsolator::BOOTLOADER_STATUS_INVALID_MODE = 1
• BrickletIsolator::BOOTLOADER_STATUS_NO_CHANGE = 2
• BrickletIsolator::BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
• BrickletIsolator::BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
• BrickletIsolator::BOOTLOADER_STATUS_CRC_MISMATCH = 5

BrickletIsolator#get_bootloader_mode → int¶

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:

• BrickletIsolator::BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE = 1
• BrickletIsolator::BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletIsolator::BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

BrickletIsolator#set_write_firmware_pointer(pointer) → nil¶

Parameters:	pointer – Type: int, Unit: 1 B, Range: [0 to 232 - 1]

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.

BrickletIsolator#write_firmware(data) → int¶

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.

BrickletIsolator#write_uid(uid) → nil¶

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

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.

BrickletIsolator#read_uid → int¶

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¶

BrickletIsolator::DEVICE_IDENTIFIER¶

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

BrickletIsolator::DEVICE_DISPLAY_NAME¶

This constant represents the human readable name of a Isolator Bricklet.