Rust - RS232 Bricklet 2.0

This is the description of the Rust API bindings for the RS232 Bricklet 2.0. General information and technical specifications for the RS232 Bricklet 2.0 are summarized in its hardware description.

An installation guide for the Rust API bindings is part of their general description. Additional documentation can be found on docs.rs.

Examples

The example code below is Public Domain (CC0 1.0).

Loopback

Download (example_loopback.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
use std::{error::Error, io, thread};
use tinkerforge::{ip_connection::IpConnection, rs232_v2_bricklet::*};

// For this example connect the RX1 and TX pin to receive the send message

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

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

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

    let read_receiver = rs232.get_read_callback_receiver();

    // Spawn thread to handle received callback messages.
    // This thread ends when the `rs232` object
    // is dropped, so there is no need for manual cleanup.
    thread::spawn(move || {
        for read in read_receiver {
            match read {
                Some((payload, _)) => {
                    let message: String = payload.iter().collect();
                    println!("Message (Length: {}) {}", message.len(), message);
                }
                None => println!("Stream was out of sync."),
            }
        }
    });

    // Enable read callback
    rs232.enable_read_callback();

    // Write "test" string
    rs232.write(&['t', 'e', 's', 't'])?;

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

API

To allow non-blocking usage, nearly every function of the Rust bindings returns a wrapper around a mpsc::Receiver. To block until the function has finished and get your result, call one of the receiver's recv variants. Those return either the result sent by the device, or any error occurred.

Functions returning a result directly will block until the device has finished processing the request.

All functions listed below are thread-safe, those which return a receiver are lock-free.

Basic Functions

pub fn Rs232V2Bricklet::new(uid: &str, ip_connection: &IpConnection) → Rs232V2Bricklet
Parameters:
  • uid – Type: &str
  • ip_connection – Type: &IPConnection
Returns:
  • rs232_v2 – Type: Rs232V2Bricklet

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

let rs232_v2 = Rs232V2Bricklet::new("YOUR_DEVICE_UID", &ip_connection);

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

pub fn Rs232V2Bricklet::write(&self, message: &[char]) → Result<usize, BrickletRecvTimeoutError>
Parameters:
  • message – Type: &[char]
Returns:
  • message_written – Type: u16, Range: [0 to 216 - 1]

Writes characters to the RS232 interface. The characters can be binary data, ASCII or similar is not necessary.

The return value is the number of characters that were written.

See Rs232V2Bricklet::set_configuration for configuration possibilities regarding baud rate, parity and so on.

pub fn Rs232V2Bricklet::read(&self, length: u16) → Result<Vec<char>, BrickletRecvTimeoutError>
Parameters:
  • length – Type: u16, Range: [0 to 216 - 1]
Returns:
  • message – Type: Vec<char>

Returns up to length characters from receive buffer.

Instead of polling with this function, you can also use callbacks. But note that this function will return available data only when the read callback is disabled. See Rs232V2Bricklet::enable_read_callback and Rs232V2Bricklet::get_read_callback_receiver callback.

pub fn Rs232V2Bricklet::set_configuration(&self, baudrate: u32, parity: u8, stopbits: u8, wordlength: u8, flowcontrol: u8) → ConvertingReceiver<()>
Parameters:
  • baudrate – Type: u32, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200
  • parity – Type: u8, Range: See constants, Default: 0
  • stopbits – Type: u8, Range: See constants, Default: 1
  • wordlength – Type: u8, Range: See constants, Default: 8
  • flowcontrol – Type: u8, Range: See constants, Default: 0

Sets the configuration for the RS232 communication.

The following constants are available for this function:

For parity:

  • RS232_V2_BRICKLET_PARITY_NONE = 0
  • RS232_V2_BRICKLET_PARITY_ODD = 1
  • RS232_V2_BRICKLET_PARITY_EVEN = 2

For stopbits:

  • RS232_V2_BRICKLET_STOPBITS_1 = 1
  • RS232_V2_BRICKLET_STOPBITS_2 = 2

For wordlength:

  • RS232_V2_BRICKLET_WORDLENGTH_5 = 5
  • RS232_V2_BRICKLET_WORDLENGTH_6 = 6
  • RS232_V2_BRICKLET_WORDLENGTH_7 = 7
  • RS232_V2_BRICKLET_WORDLENGTH_8 = 8

For flowcontrol:

  • RS232_V2_BRICKLET_FLOWCONTROL_OFF = 0
  • RS232_V2_BRICKLET_FLOWCONTROL_SOFTWARE = 1
  • RS232_V2_BRICKLET_FLOWCONTROL_HARDWARE = 2
pub fn Rs232V2Bricklet::get_configuration(&self) → ConvertingReceiver<Configuration>
Return Object:
  • baudrate – Type: u32, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200
  • parity – Type: u8, Range: See constants, Default: 0
  • stopbits – Type: u8, Range: See constants, Default: 1
  • wordlength – Type: u8, Range: See constants, Default: 8
  • flowcontrol – Type: u8, Range: See constants, Default: 0

Returns the configuration as set by Rs232V2Bricklet::set_configuration.

The following constants are available for this function:

For parity:

  • RS232_V2_BRICKLET_PARITY_NONE = 0
  • RS232_V2_BRICKLET_PARITY_ODD = 1
  • RS232_V2_BRICKLET_PARITY_EVEN = 2

For stopbits:

  • RS232_V2_BRICKLET_STOPBITS_1 = 1
  • RS232_V2_BRICKLET_STOPBITS_2 = 2

For wordlength:

  • RS232_V2_BRICKLET_WORDLENGTH_5 = 5
  • RS232_V2_BRICKLET_WORDLENGTH_6 = 6
  • RS232_V2_BRICKLET_WORDLENGTH_7 = 7
  • RS232_V2_BRICKLET_WORDLENGTH_8 = 8

For flowcontrol:

  • RS232_V2_BRICKLET_FLOWCONTROL_OFF = 0
  • RS232_V2_BRICKLET_FLOWCONTROL_SOFTWARE = 1
  • RS232_V2_BRICKLET_FLOWCONTROL_HARDWARE = 2

Advanced Functions

pub fn Rs232V2Bricklet::set_buffer_config(&self, send_buffer_size: u16, receive_buffer_size: u16) → ConvertingReceiver<()>
Parameters:
  • send_buffer_size – Type: u16, Unit: 1 B, Range: [210 to 9216], Default: 5120
  • receive_buffer_size – Type: u16, Unit: 1 B, Range: [210 to 9216], Default: 5120

Sets the send and receive buffer size in byte. In total the buffers have to be 10240 byte (10KiB) in size, the minimum buffer size is 1024 byte (1KiB) for each.

The current buffer content is lost if this function is called.

The send buffer holds data that is given by Rs232V2Bricklet::write and can not be written yet. The receive buffer holds data that is received through RS232 but could not yet be send to the user, either by Rs232V2Bricklet::read or through Rs232V2Bricklet::get_read_callback_receiver callback.

pub fn Rs232V2Bricklet::get_buffer_config(&self) → ConvertingReceiver<BufferConfig>
Return Object:
  • send_buffer_size – Type: u16, Unit: 1 B, Range: [210 to 9216], Default: 5120
  • receive_buffer_size – Type: u16, Unit: 1 B, Range: [210 to 9216], Default: 5120

Returns the buffer configuration as set by Rs232V2Bricklet::set_buffer_config.

pub fn Rs232V2Bricklet::get_buffer_status(&self) → ConvertingReceiver<BufferStatus>
Return Object:
  • send_buffer_used – Type: u16, Unit: 1 B, Range: [0 to 9216]
  • receive_buffer_used – Type: u16, Unit: 1 B, Range: [0 to 9216]

Returns the currently used bytes for the send and received buffer.

See Rs232V2Bricklet::set_buffer_config for buffer size configuration.

pub fn Rs232V2Bricklet::get_error_count(&self) → ConvertingReceiver<ErrorCount>
Return Object:
  • error_count_overrun – Type: u32, Range: [0 to 232 - 1]
  • error_count_parity – Type: u32, Range: [0 to 232 - 1]

Returns the current number of overrun and parity errors.

pub fn Rs232V2Bricklet::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 Rs232V2Bricklet::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:

  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_OFF = 0
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_ON = 1
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3
pub fn Rs232V2Bricklet::get_status_led_config(&self) → ConvertingReceiver<u8>
Returns:
  • config – Type: u8, Range: See constants, Default: 3

Returns the configuration as set by Rs232V2Bricklet::set_status_led_config

The following constants are available for this function:

For config:

  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_OFF = 0
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_ON = 1
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • RS232_V2_BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS = 3
pub fn Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::enable_read_callback(&self) → ConvertingReceiver<()>

Enables the Rs232V2Bricklet::get_read_callback_receiver callback. This will disable the Rs232V2Bricklet::get_frame_readable_callback_receiver callback.

By default the callback is disabled.

pub fn Rs232V2Bricklet::disable_read_callback(&self) → ConvertingReceiver<()>

Disables the Rs232V2Bricklet::get_read_callback_receiver callback.

By default the callback is disabled.

pub fn Rs232V2Bricklet::is_read_callback_enabled(&self) → ConvertingReceiver<bool>
Returns:
  • enabled – Type: bool, Default: false

Returns true if the Rs232V2Bricklet::get_read_callback_receiver callback is enabled, false otherwise.

pub fn Rs232V2Bricklet::set_frame_readable_callback_configuration(&self, frame_size: u16) → ConvertingReceiver<()>
Parameters:
  • frame_size – Type: u16, Unit: 1 B, Range: [0 to 9216], Default: 0

Configures the Rs232V2Bricklet::get_frame_readable_callback_receiver 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 Rs232V2Bricklet::get_read_callback_receiver callback.

By default the callback is disabled.

New in version 2.0.3 (Plugin).

pub fn Rs232V2Bricklet::get_frame_readable_callback_configuration(&self) → ConvertingReceiver<u16>
Returns:
  • frame_size – Type: u16, Unit: 1 B, Range: [0 to 9216], Default: 0

Returns the callback configuration as set by Rs232V2Bricklet::set_frame_readable_callback_configuration.

New in version 2.0.3 (Plugin).

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.

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.

pub fn Rs232V2Bricklet::get_read_callback_receiver(&self) → ConvertingHighLevelCallbackReceiver<char, ReadResult, ReadLowLevelEvent>
Event:
  • message – Type: Vec<char>

Receivers created with this function receive Read events.

This callback is called if new data is available.

To enable this callback, use Rs232V2Bricklet::enable_read_callback.

pub fn Rs232V2Bricklet::get_error_count_callback_receiver(&self) → ConvertingCallbackReceiver<ErrorCountEvent>
Event Object:
  • error_count_overrun – Type: u32, Range: [0 to 232 - 1]
  • error_count_parity – Type: u32, Range: [0 to 232 - 1]

Receivers created with this function receive Error Count events.

This callback is called if a new error occurs. It returns the current overrun and parity error count.

pub fn Rs232V2Bricklet::get_frame_readable_callback_receiver(&self) → ConvertingCallbackReceiver<u16>
Event:
  • frame_count – Type: u16, Range: [0 to 216 - 1]

Receivers created with this function receive Frame Readable events.

This callback is called if at least one frame of data is readable. The frame size is configured with Rs232V2Bricklet::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 Rs232V2Bricklet::read is called. This means, that if you have configured a frame size of X bytes, you can read exactly X bytes using the Rs232V2Bricklet::read function, every time the callback triggers without checking the frame count received variable.

New in version 2.0.3 (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.

pub fn Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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:

  • RS232_V2_BRICKLET_FUNCTION_ENABLE_READ_CALLBACK = 3
  • RS232_V2_BRICKLET_FUNCTION_DISABLE_READ_CALLBACK = 4
  • RS232_V2_BRICKLET_FUNCTION_SET_CONFIGURATION = 6
  • RS232_V2_BRICKLET_FUNCTION_SET_BUFFER_CONFIG = 8
  • RS232_V2_BRICKLET_FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 14
  • RS232_V2_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • RS232_V2_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • RS232_V2_BRICKLET_FUNCTION_RESET = 243
  • RS232_V2_BRICKLET_FUNCTION_WRITE_UID = 248
pub fn Rs232V2Bricklet::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:

  • RS232_V2_BRICKLET_FUNCTION_ENABLE_READ_CALLBACK = 3
  • RS232_V2_BRICKLET_FUNCTION_DISABLE_READ_CALLBACK = 4
  • RS232_V2_BRICKLET_FUNCTION_SET_CONFIGURATION = 6
  • RS232_V2_BRICKLET_FUNCTION_SET_BUFFER_CONFIG = 8
  • RS232_V2_BRICKLET_FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 14
  • RS232_V2_BRICKLET_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • RS232_V2_BRICKLET_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • RS232_V2_BRICKLET_FUNCTION_RESET = 243
  • RS232_V2_BRICKLET_FUNCTION_WRITE_UID = 248
pub fn Rs232V2Bricklet::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 Rs232V2Bricklet::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:

  • RS232_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_OK = 0
  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_INVALID_MODE = 1
  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_NO_CHANGE = 2
  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • RS232_V2_BRICKLET_BOOTLOADER_STATUS_CRC_MISMATCH = 5
pub fn Rs232V2Bricklet::get_bootloader_mode(&self) → ConvertingReceiver<u8>
Returns:
  • mode – Type: u8, Range: See constants

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

The following constants are available for this function:

For mode:

  • RS232_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER = 0
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE = 1
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • RS232_V2_BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
pub fn Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::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 Rs232V2Bricklet::DEVICE_IDENTIFIER

This constant is used to identify a RS232 Bricklet 2.0.

The Rs232V2Bricklet::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 Rs232V2Bricklet::DEVICE_DISPLAY_NAME

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