This is the description of the Rust API bindings for the RS232 Bricklet. General information and technical specifications for the RS232 Bricklet 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 | use std::{error::Error, io, thread};
use tinkerforge::{ip_connection::IpConnection, rs232_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.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let rs232 = Rs232Bricklet::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 {
let message: String = read.message.iter().collect();
println!("Message (Length: {}) {}", read.length, message);
}
});
// Enable read callback
rs232.enable_read_callback();
let mut chars = ['\0'; 60];
let test_chars = ['t', 'e', 's', 't'];
chars[0..4].copy_from_slice(&test_chars);
// Write "test" string
rs232.write(chars, 4);
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
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.
Rs232Bricklet::
new
(uid: &str, ip_connection: &IpConnection) → Rs232Bricklet¶Parameters: |
|
---|---|
Returns: |
|
Creates a new Rs232Bricklet
object with the unique device ID uid
and adds
it to the IPConnection ip_connection
:
let rs232 = Rs232Bricklet::new("YOUR_DEVICE_UID", &ip_connection);
This device object can be used after the IP connection has been connected.
Rs232Bricklet::
write
(&self, message: [char; 60], length: u8) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Writes a string of up to 60 characters to the RS232 interface. The string can be binary data, ASCII or similar is not necessary.
The length of the string has to be given as an additional parameter.
The return value is the number of bytes that could be written.
See Rs232Bricklet::set_configuration
for configuration possibilities
regarding baudrate, parity and so on.
Rs232Bricklet::
read
(&self) → ConvertingReceiver<Read>¶Return Object: |
|
---|
Returns the currently buffered message. The maximum length of message is 60. If the returned length is 0, no new data was available.
Instead of polling with this function, you can also use
callbacks. See Rs232Bricklet::enable_read_callback
and Rs232Bricklet::get_read_callback_receiver
callback.
Rs232Bricklet::
set_configuration
(&self, baudrate: u8, parity: u8, stopbits: u8, wordlength: u8, hardware_flowcontrol: u8, software_flowcontrol: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the configuration for the RS232 communication.
Hard-/Software flow control can either be on or off but not both simultaneously on.
The following constants are available for this function:
For baudrate:
For parity:
For stopbits:
For wordlength:
For hardware_flowcontrol:
For software_flowcontrol:
Rs232Bricklet::
get_configuration
(&self) → ConvertingReceiver<Configuration>¶Return Object: |
|
---|
Returns the configuration as set by Rs232Bricklet::set_configuration
.
The following constants are available for this function:
For baudrate:
For parity:
For stopbits:
For wordlength:
For hardware_flowcontrol:
For software_flowcontrol:
Rs232Bricklet::
set_break_condition
(&self, break_time: u16) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets a break condition (the TX output is forced to a logic 0 state). The parameter sets the hold-time of the break condition.
New in version 2.0.2 (Plugin).
Rs232Bricklet::
read_frame
(&self) → ConvertingReceiver<ReadFrame>¶Return Object: |
|
---|
Returns up to one frame of bytes from the read buffer.
The frame size is configured with Rs232Bricklet::set_frame_readable_callback_configuration
.
If the returned length is 0, no new data was available.
New in version 2.0.4 (Plugin).
Rs232Bricklet::
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.
Rs232Bricklet::
enable_read_callback
(&self) → ConvertingReceiver<()>¶Enables the Rs232Bricklet::get_read_callback_receiver
callback. This will disable the Rs232Bricklet::get_frame_readable_callback_receiver
callback.
By default the callback is disabled.
Rs232Bricklet::
disable_read_callback
(&self) → ConvertingReceiver<()>¶Disables the Rs232Bricklet::get_read_callback_receiver
callback.
By default the callback is disabled.
Rs232Bricklet::
is_read_callback_enabled
(&self) → ConvertingReceiver<bool>¶Returns: |
|
---|
Returns true if the Rs232Bricklet::get_read_callback_receiver
callback is enabled,
false otherwise.
Rs232Bricklet::
set_frame_readable_callback_configuration
(&self, frame_size: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Configures the Rs232Bricklet::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 Rs232Bricklet::get_read_callback_receiver
callback.
By default the callback is disabled.
New in version 2.0.4 (Plugin).
Rs232Bricklet::
get_frame_readable_callback_configuration
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the callback configuration as set by Rs232Bricklet::set_frame_readable_callback_configuration
.
New in version 2.0.4 (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.
Rs232Bricklet::
get_read_callback_receiver
(&self) → ConvertingCallbackReceiver<ReadEvent>¶Event Object: |
|
---|
Receivers created with this function receive Read events.
This callback is called if new data is available. The message has a maximum size of 60 characters. The actual length of the message is given in addition.
To enable this callback, use Rs232Bricklet::enable_read_callback
.
Rs232Bricklet::
get_error_callback_receiver
(&self) → ConvertingCallbackReceiver<u8>¶Event: |
|
---|
Receivers created with this function receive Error events.
This callback is called if an error occurs. Possible errors are overrun, parity or framing error.
The following constants are available for this function:
For error:
New in version 2.0.1 (Plugin).
Rs232Bricklet::
get_frame_readable_callback_receiver
(&self) → ConvertingCallbackReceiver<u8>¶Event: |
|
---|
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 Rs232Bricklet::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 Rs232Bricklet::read
or Rs232Bricklet::read_frame
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the Rs232Bricklet::read_frame
function, every time the callback triggers without checking the frame count received variable.
New in version 2.0.4 (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.
Rs232Bricklet::
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.
Rs232Bricklet::
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
Rs232Bricklet::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:
Rs232Bricklet::
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:
Rs232Bricklet::
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.
Rs232Bricklet::
DEVICE_IDENTIFIER
¶This constant is used to identify a RS232 Bricklet.
The Rs232Bricklet::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.
Rs232Bricklet::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a RS232 Bricklet.