This is the description of the Rust API bindings for the CAN Bricklet 2.0. General information and technical specifications for the CAN 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.
The example code below is Public Domain (CC0 1.0).
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 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 | use std::{error::Error, io, thread};
use tinkerforge::{can_v2_bricklet::*, ip_connection::IpConnection};
// FIXME: This example is incomplete
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your CAN Bricklet 2.0.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let can = CanV2Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Configure transceiver for loopback mode
can.set_transceiver_configuration(1000000, 625, CAN_V2_BRICKLET_TRANSCEIVER_MODE_LOOPBACK);
let frame_read_receiver = can.get_frame_read_callback_receiver();
// Spawn thread to handle received callback messages.
// This thread ends when the `can` object
// is dropped, so there is no need for manual cleanup.
thread::spawn(move || {
for frame_read in frame_read_receiver {
match frame_read {
Some((payload, result)) => {
if result.frame_type == CAN_V2_BRICKLET_FRAME_TYPE_STANDARD_DATA {
println!("Frame Type: Standard Data");
} else if result.frame_type == CAN_V2_BRICKLET_FRAME_TYPE_STANDARD_REMOTE {
println!("Frame Type: Standard Remote");
} else if result.frame_type == CAN_V2_BRICKLET_FRAME_TYPE_EXTENDED_DATA {
println!("Frame Type: Extended Data");
} else if result.frame_type == CAN_V2_BRICKLET_FRAME_TYPE_EXTENDED_REMOTE {
println!("Frame Type: Extended Remote");
}
println!("Identifier: {}", result.identifier);
print!("Data (Length: {}):", payload.len());
for item in payload.iter() {
print!(" {}", item);
}
println!();
println!();
}
None => println!("Stream was out of sync."),
}
}
});
// Enable frame read callback
can.set_frame_read_callback_configuration(true);
// Write standard data frame with identifier 1742 and 3 bytes of data
can.write_frame(CAN_V2_BRICKLET_FRAME_TYPE_STANDARD_DATA, 1742, &[42, 23, 17])?;
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
can.set_frame_read_callback_configuration(false);
ipcon.disconnect();
Ok(())
}
|
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.
CanV2Bricklet::
new
(uid: &str, ip_connection: &IpConnection) → CanV2Bricklet¶Parameters: |
|
---|---|
Returns: |
|
Creates a new CanV2Bricklet
object with the unique device ID uid
and adds
it to the IPConnection ip_connection
:
let can_v2 = CanV2Bricklet::new("YOUR_DEVICE_UID", &ip_connection);
This device object can be used after the IP connection has been connected.
CanV2Bricklet::
write_frame
(&self, frame_type: u8, identifier: u32, data: &[u8]) → Result<bool, BrickletRecvTimeoutError>¶Parameters: |
|
---|---|
Returns: |
|
Writes a data or remote frame to the write queue to be transmitted over the CAN transceiver.
The Bricklet supports the standard 11-bit (CAN 2.0A) and the additional extended
29-bit (CAN 2.0B) identifiers. For standard frames the Bricklet uses bit 0 to 10
from the identifier
parameter as standard 11-bit identifier. For extended
frames the Bricklet uses bit 0 to 28 from the identifier
parameter as
extended 29-bit identifier.
The data
parameter can be up to 15 bytes long. For data frames up to 8 bytes
will be used as the actual data. The length (DLC) field in the data or remote
frame will be set to the actual length of the data
parameter. This allows
to transmit data and remote frames with excess length. For remote frames only
the length of the data
parameter is used. The actual data
bytes are
ignored.
Returns true if the frame was successfully added to the write queue. Returns
false if the frame could not be added because write queue is already full or
because the write buffer or the write backlog are configured with a size of
zero (see CanV2Bricklet::set_queue_configuration
).
The write queue can overflow if frames are written to it at a higher rate
than the Bricklet can transmitted them over the CAN transceiver. This may
happen if the CAN transceiver is configured as read-only or is using a low baud
rate (see CanV2Bricklet::set_transceiver_configuration
). It can also happen if the CAN
bus is congested and the frame cannot be transmitted because it constantly loses
arbitration or because the CAN transceiver is currently disabled due to a high
write error level (see CanV2Bricklet::get_error_log
).
The following constants are available for this function:
For frame_type:
CanV2Bricklet::
read_frame
(&self) → Result<(Vec<u8>, ReadFrameResult), BrickletRecvTimeoutError>¶Return Object: |
|
---|
Tries to read the next data or remote frame from the read queue and returns it.
If a frame was successfully read, then the success
return value is set to
true and the other return values contain the frame. If the read queue is
empty and no frame could be read, then the success
return value is set to
false and the other return values contain invalid data.
The identifier
return value follows the identifier format described for
CanV2Bricklet::write_frame
.
The data
return value can be up to 15 bytes long. For data frames up to the
first 8 bytes are the actual received data. All bytes after the 8th byte are
always zero and only there to indicate the length of a data or remote frame
with excess length. For remote frames the length of the data
return value
represents the requested length. The actual data
bytes are always zero.
A configurable read filter can be used to define which frames should be
received by the CAN transceiver and put into the read queue (see
CanV2Bricklet::set_read_filter_configuration
).
Instead of polling with this function, you can also use callbacks. See the
CanV2Bricklet::set_frame_read_callback_configuration
function and the CanV2Bricklet::get_frame_read_callback_receiver
callback.
The following constants are available for this function:
For frame_type:
CanV2Bricklet::
set_transceiver_configuration
(&self, baud_rate: u32, sample_point: u16, transceiver_mode: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the transceiver configuration for the CAN bus communication.
The CAN transceiver has three different modes:
The following constants are available for this function:
For transceiver_mode:
CanV2Bricklet::
get_transceiver_configuration
(&self) → ConvertingReceiver<TransceiverConfiguration>¶Return Object: |
|
---|
Returns the configuration as set by CanV2Bricklet::set_transceiver_configuration
.
The following constants are available for this function:
For transceiver_mode:
CanV2Bricklet::
set_queue_configuration
(&self, write_buffer_size: u8, write_buffer_timeout: i32, write_backlog_size: u16, read_buffer_sizes: &[i8], read_backlog_size: u16) → Result<(), BrickletRecvTimeoutError>¶Parameters: |
|
---|
Sets the write and read queue configuration.
The CAN transceiver has 32 buffers in total in hardware for transmitting and receiving frames. Additionally, the Bricklet has a backlog for 768 frames in total in software. The buffers and the backlog can be freely assigned to the write and read queues.
CanV2Bricklet::write_frame
writes a frame into the write backlog. The Bricklet moves
the frame from the backlog into a free write buffer. The CAN transceiver then
transmits the frame from the write buffer to the CAN bus. If there are no
write buffers (write_buffer_size
is zero) or there is no write backlog
(write_backlog_size
is zero) then no frames can be transmitted and
CanV2Bricklet::write_frame
returns always false.
The CAN transceiver receives a frame from the CAN bus and stores it into a
free read buffer. The Bricklet moves the frame from the read buffer into the
read backlog. CanV2Bricklet::read_frame
reads the frame from the read backlog and
returns it. If there are no read buffers (read_buffer_sizes
is empty) or
there is no read backlog (read_backlog_size
is zero) then no frames can be
received and CanV2Bricklet::read_frame
returns always false.
There can be multiple read buffers, because the CAN transceiver cannot receive
data and remote frames into the same read buffer. A positive read buffer size
represents a data frame read buffer and a negative read buffer size represents
a remote frame read buffer. A read buffer size of zero is not allowed. By
default the first read buffer is configured for data frames and the second read
buffer is configured for remote frame. There can be up to 32 different read
buffers, assuming that no write buffer is used. Each read buffer has its own
filter configuration (see CanV2Bricklet::set_read_filter_configuration
).
A valid queue configuration fulfills these conditions:
write_buffer_size + abs(read_buffer_size_0) + abs(read_buffer_size_1) + ... + abs(read_buffer_size_31) <= 32
write_backlog_size + read_backlog_size <= 768
The write buffer timeout has three different modes that define how a failed frame transmission should be handled:
The current content of the queues is lost when this function is called.
CanV2Bricklet::
get_queue_configuration
(&self) → Result<(Vec<i8>, QueueConfigurationResult), BrickletRecvTimeoutError>¶Return Object: |
|
---|
Returns the queue configuration as set by CanV2Bricklet::set_queue_configuration
.
CanV2Bricklet::
set_read_filter_configuration
(&self, buffer_index: u8, filter_mode: u8, filter_mask: u32, filter_identifier: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
Set the read filter configuration for the given read buffer index. This can be used to define which frames should be received by the CAN transceiver and put into the read buffer.
The read filter has four different modes that define if and how the filter mask and the filter identifier are applied:
The filter mask and filter identifier are used as bit masks. Their usage depends on the mode:
The filter mask and filter identifier are applied in this way: The filter mask is used to select the frame identifier bits that should be compared to the corresponding filter identifier bits. All unselected bits are automatically accepted. All selected bits have to match the filter identifier to be accepted. If all bits for the selected mode are accepted then the frame is accepted and is added to the read buffer.
Filter Mask Bit | Filter Identifier Bit | Frame Identifier Bit | Result |
---|---|---|---|
0 | X | X | Accept |
1 | 0 | 0 | Accept |
1 | 0 | 1 | Reject |
1 | 1 | 0 | Reject |
1 | 1 | 1 | Accept |
For example, to receive standard frames with identifier 0x123 only, the mode can be set to Match-Standard-Only with 0x7FF as mask and 0x123 as identifier. The mask of 0x7FF selects all 11 identifier bits for matching so that the identifier has to be exactly 0x123 to be accepted.
To accept identifier 0x123 and identifier 0x456 at the same time, just set filter 2 to 0x456 and keep mask and filter 1 unchanged.
There can be up to 32 different read filters configured at the same time,
because there can be up to 32 read buffer (see CanV2Bricklet::set_queue_configuration
).
The default mode is accept-all for all read buffers.
The following constants are available for this function:
For filter_mode:
CanV2Bricklet::
get_read_filter_configuration
(&self, buffer_index: u8) → ConvertingReceiver<ReadFilterConfiguration>¶Parameters: |
|
---|---|
Return Object: |
|
Returns the read filter configuration as set by CanV2Bricklet::set_read_filter_configuration
.
The following constants are available for this function:
For filter_mode:
CanV2Bricklet::
get_error_log
(&self) → Result<(Vec<bool>, ErrorLogResult), BrickletRecvTimeoutError>¶Return Object: |
|
---|
Returns information about different kinds of errors.
The write and read error levels indicate the current level of stuffing, form, acknowledgement, bit and checksum errors during CAN bus write and read operations. For each of this error kinds there is also an individual counter.
When the write error level extends 255 then the CAN transceiver gets disabled and no frames can be transmitted or received anymore. The CAN transceiver will automatically be activated again after the CAN bus is idle for a while.
The write buffer timeout, read buffer and backlog overflow counts represents the number of these errors:
CanV2Bricklet::set_queue_configuration
).CanV2Bricklet::set_read_filter_configuration
) can help to reduce the amount of
received frames. This count is not exact, but a lower bound, because the
Bricklet might not able detect all overflows if they occur in rapid succession.CanV2Bricklet::read_frame
function. Using the CanV2Bricklet::get_frame_read_callback_receiver
callback ensures that the read backlog
can not overflow.The read buffer overflow counter counts the overflows of all configured read
buffers. Which read buffer exactly suffered from an overflow can be figured
out from the read buffer overflow occurrence list
(read_buffer_overflow_error_occurred
). Reading the error log clears the
occurence list.
The following constants are available for this function:
For transceiver_state:
CanV2Bricklet::
set_communication_led_config
(&self, config: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the communication LED configuration. By default the LED shows CAN-Bus traffic, it flickers once for every 40 transmitted or received frames.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
CanV2Bricklet::
get_communication_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by CanV2Bricklet::set_communication_led_config
The following constants are available for this function:
For config:
CanV2Bricklet::
set_error_led_config
(&self, config: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the error LED configuration.
By default (show-transceiver-state) the error LED turns on if the CAN
transceiver is passive or disabled state (see CanV2Bricklet::get_error_log
). If
the CAN transceiver is in active state the LED turns off.
If the LED is configured as show-error then the error LED turns on if any error occurs. If you call this function with the show-error option again, the LED will turn off until the next error occurs.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
CanV2Bricklet::
get_error_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by CanV2Bricklet::set_error_led_config
.
The following constants are available for this function:
For config:
CanV2Bricklet::
get_spitfp_error_count
(&self) → ConvertingReceiver<SpitfpErrorCount>¶Return Object: |
|
---|
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.
CanV2Bricklet::
set_status_led_config
(&self, config: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
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:
CanV2Bricklet::
get_status_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by CanV2Bricklet::set_status_led_config
The following constants are available for this function:
For config:
CanV2Bricklet::
get_chip_temperature
(&self) → ConvertingReceiver<i16>¶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.
CanV2Bricklet::
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!
CanV2Bricklet::
get_identity
(&self) → ConvertingReceiver<Identity>¶Return Object: |
|
---|
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.
CanV2Bricklet::
set_frame_read_callback_configuration
(&self, enabled: bool) → ConvertingReceiver<()>¶Parameters: |
|
---|
Enables and disables the CanV2Bricklet::get_frame_read_callback_receiver
callback.
By default the callback is disabled. Enabling this callback will disable the CanV2Bricklet::get_frame_readable_callback_receiver
callback.
CanV2Bricklet::
get_frame_read_callback_configuration
(&self) → ConvertingReceiver<bool>¶Returns: |
|
---|
Returns true if the CanV2Bricklet::get_frame_read_callback_receiver
callback is enabled, false otherwise.
CanV2Bricklet::
set_frame_readable_callback_configuration
(&self, enabled: bool) → ConvertingReceiver<()>¶Parameters: |
|
---|
Enables and disables the CanV2Bricklet::get_frame_readable_callback_receiver
callback.
By default the callback is disabled. Enabling this callback will disable the CanV2Bricklet::get_frame_read_callback_receiver
callback.
New in version 2.0.3 (Plugin).
CanV2Bricklet::
get_frame_readable_callback_configuration
(&self) → ConvertingReceiver<bool>¶Returns: |
|
---|
Returns true if the CanV2Bricklet::get_frame_readable_callback_receiver
callback is enabled, false otherwise.
New in version 2.0.3 (Plugin).
CanV2Bricklet::
set_error_occurred_callback_configuration
(&self, enabled: bool) → ConvertingReceiver<()>¶Parameters: |
|
---|
Enables and disables the CanV2Bricklet::get_error_occurred_callback_receiver
callback.
By default the callback is disabled.
New in version 2.0.3 (Plugin).
CanV2Bricklet::
get_error_occurred_callback_configuration
(&self) → ConvertingReceiver<bool>¶Returns: |
|
---|
Returns true if the CanV2Bricklet::get_error_occurred_callback_receiver
callback is enabled, false otherwise.
New in version 2.0.3 (Plugin).
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.
CanV2Bricklet::
get_frame_read_callback_receiver
(&self) → ConvertingHighLevelCallbackReceiver<u8, FrameReadResult, FrameReadLowLevelEvent>¶Event Object: |
|
---|
Receivers created with this function receive Frame Read events.
This callback is triggered if a data or remote frame was received by the CAN transceiver.
The identifier
return value follows the identifier format described for
CanV2Bricklet::write_frame
.
For details on the data
return value see CanV2Bricklet::read_frame
.
A configurable read filter can be used to define which frames should be
received by the CAN transceiver and put into the read queue (see
CanV2Bricklet::set_read_filter_configuration
).
To enable this callback, use CanV2Bricklet::set_frame_read_callback_configuration
.
The following constants are available for this function:
For frame_type:
CanV2Bricklet::
get_frame_readable_callback_receiver
(&self) → ConvertingCallbackReceiver<()>¶Receivers created with this function receive Frame Readable events.
This callback is triggered if a data or remote frame was received by the CAN
transceiver. The received frame can be read with CanV2Bricklet::read_frame
.
If additional frames are received, but CanV2Bricklet::read_frame
was not called yet, the callback
will not trigger again.
A configurable read filter can be used to define which frames should be
received by the CAN transceiver and put into the read queue (see
CanV2Bricklet::set_read_filter_configuration
).
To enable this callback, use CanV2Bricklet::set_frame_readable_callback_configuration
.
New in version 2.0.3 (Plugin).
CanV2Bricklet::
get_error_occurred_callback_receiver
(&self) → ConvertingCallbackReceiver<()>¶Receivers created with this function receive Error Occurred events.
This callback is triggered if any error occurred while writing, reading or transmitting CAN frames.
The callback is only triggered once until CanV2Bricklet::get_error_log
is called. That function will return
details abount the error(s) occurred.
To enable this callback, use CanV2Bricklet::set_error_occurred_callback_configuration
.
New in version 2.0.3 (Plugin).
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.
CanV2Bricklet::
get_api_version
(&self) → [u8; 3]¶Return Object: |
|
---|
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.
CanV2Bricklet::
get_response_expected
(&mut self, function_id: u8) → bool¶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
CanV2Bricklet::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:
CanV2Bricklet::
set_response_expected
(&mut self, function_id: u8, response_expected: bool) → ()¶Parameters: |
|
---|
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:
CanV2Bricklet::
set_response_expected_all
(&mut self, response_expected: bool) → ()¶Parameters: |
|
---|
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.
CanV2Bricklet::
set_bootloader_mode
(&self, mode: u8) → ConvertingReceiver<u8>¶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:
CanV2Bricklet::
get_bootloader_mode
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the current bootloader mode, see CanV2Bricklet::set_bootloader_mode
.
The following constants are available for this function:
For mode:
CanV2Bricklet::
set_write_firmware_pointer
(&self, pointer: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the firmware pointer for CanV2Bricklet::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.
CanV2Bricklet::
write_firmware
(&self, data: [u8; 64]) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
CanV2Bricklet::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.
CanV2Bricklet::
write_uid
(&self, uid: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
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.
CanV2Bricklet::
read_uid
(&self) → ConvertingReceiver<u32>¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
CanV2Bricklet::
DEVICE_IDENTIFIER
¶This constant is used to identify a CAN Bricklet 2.0.
The CanV2Bricklet::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.
CanV2Bricklet::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a CAN Bricklet 2.0.