Rust - Dual Button Bricklet 2.0¶

Callback¶

Download (example_callback.rs)

 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

use std::{error::Error, io, thread};
use tinkerforge::{dual_button_v2_bricklet::*, ip_connection::IpConnection};

const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your Dual Button Bricklet 2.0.

fn main() -> Result<(), Box<dyn Error>> {
    let ipcon = IpConnection::new(); // Create IP connection.
    let db = DualButtonV2Bricklet::new(UID, &ipcon); // Create device object.

    ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
                                          // Don't use device before ipcon is connected.

    let state_changed_receiver = db.get_state_changed_callback_receiver();

    // Spawn thread to handle received callback messages.
    // This thread ends when the `db` object
    // is dropped, so there is no need for manual cleanup.
    thread::spawn(move || {
        for state_changed in state_changed_receiver {
            if state_changed.button_l == DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED {
                println!("Left Button: Pressed");
            } else if state_changed.button_l == DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED {
                println!("Left Button: Released");
            }

            if state_changed.button_r == DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED {
                println!("Right Button: Pressed");
            } else if state_changed.button_r == DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED {
                println!("Right Button: Released");
            }

            println!();
        }
    });

    // Enable state changed callback
    db.set_state_changed_callback_configuration(true).recv()?;

    println!("Press enter to exit.");
    let mut _input = String::new();
    io::stdin().read_line(&mut _input)?;
    ipcon.disconnect();
    Ok(())
}

Basic Functions¶

pub fn DualButtonV2Bricklet::new(uid: &str, ip_connection: &IpConnection) → DualButtonV2Bricklet¶

Parameters:	uid – Type: &str ip_connection – Type: &IPConnection
Returns:	dual_button_v2 – Type: DualButtonV2Bricklet

Creates a new DualButtonV2Bricklet object with the unique device ID uid and adds it to the IPConnection ip_connection:

let dual_button_v2 = DualButtonV2Bricklet::new("YOUR_DEVICE_UID", &ip_connection);

This device object can be used after the IP connection has been connected.

pub fn DualButtonV2Bricklet::set_led_state(&self, led_l: u8, led_r: u8) → ConvertingReceiver<()>¶

Parameters:	led_l – Type: u8, Range: See constants, Default: 1 led_r – Type: u8, Range: See constants, Default: 1

Sets the state of the LEDs. Possible states are:

• 0 = AutoToggleOn: Enables auto toggle with initially enabled LED.
• 1 = AutoToggleOff: Activates auto toggle with initially disabled LED.
• 2 = On: Enables LED (auto toggle is disabled).
• 3 = Off: Disables LED (auto toggle is disabled).

In auto toggle mode the LED is toggled automatically at each press of a button.

If you just want to set one of the LEDs and don't know the current state of the other LED, you can get the state with DualButtonV2Bricklet::get_led_state or you can use DualButtonV2Bricklet::set_selected_led_state.

The following constants are available for this function:

For led_l:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

For led_r:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

pub fn DualButtonV2Bricklet::get_led_state(&self) → ConvertingReceiver<LedState>¶

Return Object:	led_l – Type: u8, Range: See constants, Default: 1 led_r – Type: u8, Range: See constants, Default: 1

Returns the current state of the LEDs, as set by DualButtonV2Bricklet::set_led_state.

The following constants are available for this function:

For led_l:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

For led_r:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

pub fn DualButtonV2Bricklet::get_button_state(&self) → ConvertingReceiver<ButtonState>¶

Return Object:	button_l – Type: u8, Range: See constants button_r – Type: u8, Range: See constants

Returns the current state for both buttons. Possible states are:

• 0 = pressed
• 1 = released

The following constants are available for this function:

For button_l:

• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED = 0
• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED = 1

For button_r:

• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED = 0
• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED = 1

Advanced Functions¶

pub fn DualButtonV2Bricklet::set_selected_led_state(&self, led: u8, state: u8) → ConvertingReceiver<()>¶

Parameters:	led – Type: u8, Range: See constants state – Type: u8, Range: See constants

Sets the state of the selected LED.

The other LED remains untouched.

The following constants are available for this function:

For led:

• DUAL_BUTTON_V2_BRICKLET_LED_LEFT = 0
• DUAL_BUTTON_V2_BRICKLET_LED_RIGHT = 1

For state:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

pub fn DualButtonV2Bricklet::get_spitfp_error_count(&self) → ConvertingReceiver<SpitfpErrorCount>¶

Return Object:	error_count_ack_checksum – Type: u32, Range: [0 to 232 - 1] error_count_message_checksum – Type: u32, Range: [0 to 232 - 1] error_count_frame – Type: u32, Range: [0 to 232 - 1] error_count_overflow – Type: u32, 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.

pub fn DualButtonV2Bricklet::set_status_led_config(&self, config: u8) → ConvertingReceiver<()>¶

Parameters:	config – Type: u8, 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:

• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_OFF = 0
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_ON = 1
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3

pub fn DualButtonV2Bricklet::get_status_led_config(&self) → ConvertingReceiver<u8>¶

Returns:	config – Type: u8, Range: See constants, Default: 3

Returns the configuration as set by DualButtonV2Bricklet::set_status_led_config

The following constants are available for this function:

For config:

• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_OFF = 0
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_ON = 1
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• DUAL_BUTTON_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3

pub fn DualButtonV2Bricklet::get_chip_temperature(&self) → ConvertingReceiver<i16>¶

Returns:	temperature – Type: i16, 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.

pub fn DualButtonV2Bricklet::reset(&self) → ConvertingReceiver<()>¶

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!

pub fn DualButtonV2Bricklet::get_identity(&self) → ConvertingReceiver<Identity>¶

Return Object:

uid – Type: String, Length: up to 8 connected_uid – Type: String, Length: up to 8 position – Type: char, Range: ['a' to 'h', 'z'] hardware_version – Type: [u8; 3] 0: major – Type: u8, Range: [0 to 255] 1: minor – Type: u8, Range: [0 to 255] 2: revision – Type: u8, Range: [0 to 255] firmware_version – Type: [u8; 3] 0: major – Type: u8, Range: [0 to 255] 1: minor – Type: u8, Range: [0 to 255] 2: revision – Type: u8, Range: [0 to 255] device_identifier – Type: u16, 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¶

pub fn DualButtonV2Bricklet::set_state_changed_callback_configuration(&self, enabled: bool) → ConvertingReceiver<()>¶

Parameters:	enabled – Type: bool, Default: false

If you enable this callback, the DualButtonV2Bricklet::get_state_changed_callback_receiver callback is triggered every time a button is pressed/released

pub fn DualButtonV2Bricklet::get_state_changed_callback_configuration(&self) → ConvertingReceiver<bool>¶

Returns:	enabled – Type: bool, Default: false

Returns the configuration as set by DualButtonV2Bricklet::set_state_changed_callback_configuration.

Callbacks¶

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding get_*_callback_receiver function, which returns a receiver for callback events.

pub fn DualButtonV2Bricklet::get_state_changed_callback_receiver(&self) → ConvertingCallbackReceiver<StateChangedEvent>¶

Event Object:	button_l – Type: u8, Range: See constants button_r – Type: u8, Range: See constants led_l – Type: u8, Range: See constants led_r – Type: u8, Range: See constants

Receivers created with this function receive State Changed events.

This callback is called whenever a button is pressed.

Possible states for buttons are:

• 0 = pressed
• 1 = released

Possible states for LEDs are:

• 0 = AutoToggleOn: Auto toggle enabled and LED on.
• 1 = AutoToggleOff: Auto toggle enabled and LED off.
• 2 = On: LED on (auto toggle is disabled).
• 3 = Off: LED off (auto toggle is disabled).

This callback can be enabled with DualButtonV2Bricklet::set_state_changed_callback_configuration.

The following constants are available for this function:

For button_l:

• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED = 0
• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED = 1

For button_r:

• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_PRESSED = 0
• DUAL_BUTTON_V2_BRICKLET_BUTTON_STATE_RELEASED = 1

For led_l:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

For led_r:

• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_ON = 0
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_AUTO_TOGGLE_OFF = 1
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_ON = 2
• DUAL_BUTTON_V2_BRICKLET_LED_STATE_OFF = 3

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.

pub fn DualButtonV2Bricklet::get_api_version(&self) → [u8; 3]¶

Return Object:	api_version – Type: [u8; 3] 0: major – Type: u8, Range: [0 to 255] 1: minor – Type: u8, Range: [0 to 255] 2: revision – Type: u8, 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.

pub fn DualButtonV2Bricklet::get_response_expected(&mut self, function_id: u8) → bool¶

Parameters:	function_id – Type: u8, 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 DualButtonV2Bricklet::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:

• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_LED_STATE = 1
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_SELECTED_LED_STATE = 5
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_RESET = 243
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_WRITE_UID = 248

pub fn DualButtonV2Bricklet::set_response_expected(&mut self, function_id: u8, response_expected: bool) → ()¶

Parameters:	function_id – Type: u8, 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:

• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_LED_STATE = 1
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_SELECTED_LED_STATE = 5
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_RESET = 243
• DUAL_BUTTON_V2_BRICKLET_FUNCTION_WRITE_UID = 248

pub fn DualButtonV2Bricklet::set_response_expected_all(&mut self, response_expected: bool) → ()¶

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.

pub fn DualButtonV2Bricklet::set_bootloader_mode(&self, mode: u8) → ConvertingReceiver<u8>¶

Parameters:	mode – Type: u8, Range: See constants
Returns:	status – Type: u8, 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:

• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_OK = 0
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_INVALID_MODE = 1
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_NO_CHANGE = 2
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_STATUS_CRC_MISMATCH = 5

pub fn DualButtonV2Bricklet::get_bootloader_mode(&self) → ConvertingReceiver<u8>¶

Returns:	mode – Type: u8, Range: See constants

Returns the current bootloader mode, see DualButtonV2Bricklet::set_bootloader_mode.

The following constants are available for this function:

For mode:

• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• DUAL_BUTTON_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

pub fn DualButtonV2Bricklet::set_write_firmware_pointer(&self, pointer: u32) → ConvertingReceiver<()>¶

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

Sets the firmware pointer for DualButtonV2Bricklet::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.

pub fn DualButtonV2Bricklet::write_firmware(&self, data: [u8; 64]) → ConvertingReceiver<u8>¶

Parameters:	data – Type: [u8; 64], Range: [0 to 255]
Returns:	status – Type: u8, Range: [0 to 255]

Writes 64 Bytes of firmware at the position as written by DualButtonV2Bricklet::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.

pub fn DualButtonV2Bricklet::write_uid(&self, uid: u32) → ConvertingReceiver<()>¶

Parameters:	uid – Type: u32, 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.

pub fn DualButtonV2Bricklet::read_uid(&self) → ConvertingReceiver<u32>¶

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

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

Constants¶

pub const DualButtonV2Bricklet::DEVICE_IDENTIFIER¶

This constant is used to identify a Dual Button Bricklet 2.0.

The DualButtonV2Bricklet::get_identity function and the IpConnection::get_enumerate_callback_receiver callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.

pub const DualButtonV2Bricklet::DEVICE_DISPLAY_NAME¶

This constant represents the human readable name of a Dual Button Bricklet 2.0.