This is the description of the Rust API bindings for the E-Paper 296x128 Bricklet. General information and technical specifications for the E-Paper 296x128 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_hello_world.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 | use std::{error::Error, io};
use tinkerforge::{e_paper_296x128_bricklet::*, ip_connection::IpConnection};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your E-Paper 296x128 Bricklet.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let ep = EPaper296x128Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Use black background
ep.fill_display(E_PAPER_296X128_BRICKLET_COLOR_BLACK).recv()?;
// Write big white "Hello World" in the middle of the screen
ep.draw_text(
16,
48,
E_PAPER_296X128_BRICKLET_FONT_24X32,
E_PAPER_296X128_BRICKLET_COLOR_WHITE,
E_PAPER_296X128_BRICKLET_ORIENTATION_HORIZONTAL,
"Hello World".to_string(),
)
.recv()?;
ep.draw().recv()?;
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
ipcon.disconnect();
Ok(())
}
|
Download (example_load_image.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 | extern crate image; // Add 'image = "0.20"' to dependencies in Cargo.toml
use std::{error::Error, io};
use std::path::Path;
use image::RgbImage;
use tinkerforge::{e_paper_296x128_bricklet::*, ip_connection::IpConnection};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your E-Paper 296x128 Bricklet.
const WIDTH: u32 = 296;
const HEIGHT: u32 = 128;
// Convert RgbImage to matching color bool array
fn bool_array_from_image(image: &RgbImage, r: u8, g: u8, b: u8) -> Vec<bool> {
let mut pixels = vec![false; (WIDTH * HEIGHT) as usize];
for row in 0..HEIGHT-1 {
for column in 0..WIDTH-1 {
let pixel = image.get_pixel(column, row);
pixels[(row * WIDTH + column) as usize] = (pixel[0] == r) && (pixel[1] == g) && (pixel[2] == b);
}
}
pixels
}
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let ep = EPaper296x128Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Download example image here:
// https://raw.githubusercontent.com/Tinkerforge/e-paper-296x128-bricklet/master/software/examples/tf_red.png
let image = image::open(&Path::new("tf_red.png")).unwrap().to_rgb();
// Get black/white pixels from image and write them to the Bricklet buffer
let pixels_bw = bool_array_from_image(&image, 0xFF, 0xFF, 0xFF);
let _ =ep.write_black_white(0, 0, (WIDTH-1) as u16, (HEIGHT-1) as u8, &pixels_bw);
// Get red pixels from image and write them to the Bricklet buffer
let pixels_red = bool_array_from_image(&image, 0xFF, 0, 0);
let _ = ep.write_color(0, 0, (WIDTH-1) as u16, (HEIGHT-1) as u8, &pixels_red);
// Draw buffered values to the display
ep.draw();
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.
EPaper296x128Bricklet::
new
(uid: &str, ip_connection: &IpConnection) → EPaper296x128Bricklet¶Parameters: |
|
---|---|
Returns: |
|
Creates a new EPaper296x128Bricklet
object with the unique device ID uid
and adds
it to the IPConnection ip_connection
:
let e_paper_296x128 = EPaper296x128Bricklet::new("YOUR_DEVICE_UID", &ip_connection);
This device object can be used after the IP connection has been connected.
EPaper296x128Bricklet::
draw
(&self) → ConvertingReceiver<()>¶Draws the current black/white and red or gray buffer to the e-paper display.
The Bricklet does not have any double-buffering. You should not call
this function while writing to the buffer. See EPaper296x128Bricklet::get_draw_status
.
EPaper296x128Bricklet::
get_draw_status
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns one of three draw statuses:
You can write to the buffer (through one of the write or draw functions) when the status is either idle or drawing. You should not write to the buffer while it is being copied to the display. There is no double-buffering.
The following constants are available for this function:
For draw_status:
EPaper296x128Bricklet::
write_black_white
(&self, x_start: u16, y_start: u8, x_end: u16, y_end: u8, pixels: &[bool]) → Result<(), BrickletRecvTimeoutError>¶Parameters: |
|
---|
Writes black/white pixels to the specified window into the buffer.
The pixels are written into the window line by line top to bottom and each line is written from left to right.
The value 0 (false) corresponds to a black pixel and the value 1 (true) to a white pixel.
This function writes the pixels into the black/white pixel buffer, to draw the
buffer to the display use EPaper296x128Bricklet::draw
.
Use EPaper296x128Bricklet::write_color
to write red or gray pixels.
EPaper296x128Bricklet::
read_black_white
(&self, x_start: u16, y_start: u8, x_end: u16, y_end: u8) → Result<Vec<bool>, BrickletRecvTimeoutError>¶Parameters: |
|
---|---|
Returns: |
|
Returns the current content of the black/white pixel buffer for the specified window.
The pixels are read into the window line by line top to bottom and each line is read from left to right.
The current content of the buffer does not have to be the current content of the display. It is possible that the data was not drawn to the display yet and after a restart of the Bricklet the buffer will be reset to black, while the display retains its content.
EPaper296x128Bricklet::
write_color
(&self, x_start: u16, y_start: u8, x_end: u16, y_end: u8, pixels: &[bool]) → Result<(), BrickletRecvTimeoutError>¶Parameters: |
|
---|
The E-Paper 296x128 Bricklet is available with the colors black/white/red and black/white/gray. Depending on the model this function writes either red or gray pixels to the specified window into the buffer.
The pixels are written into the window line by line top to bottom and each line is written from left to right.
The value 0 (false) means that this pixel does not have color. It will be either black
or white (see EPaper296x128Bricklet::write_black_white
). The value 1 (true) corresponds to a red or gray
pixel, depending on the Bricklet model.
This function writes the pixels into the red or gray pixel buffer, to draw the buffer
to the display use EPaper296x128Bricklet::draw
.
Use EPaper296x128Bricklet::write_black_white
to write black/white pixels.
EPaper296x128Bricklet::
read_color
(&self, x_start: u16, y_start: u8, x_end: u16, y_end: u8) → Result<Vec<bool>, BrickletRecvTimeoutError>¶Parameters: |
|
---|---|
Returns: |
|
Returns the current content of the red or gray pixel buffer for the specified window.
The pixels are written into the window line by line top to bottom and each line is written from left to right.
The current content of the buffer does not have to be the current content of the display. It is possible that the data was not drawn to the display yet and after a restart of the Bricklet the buffer will be reset to black, while the display retains its content.
EPaper296x128Bricklet::
fill_display
(&self, color: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Fills the complete content of the display with the given color.
This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer
to the display use EPaper296x128Bricklet::draw
.
The following constants are available for this function:
For color:
EPaper296x128Bricklet::
draw_text
(&self, position_x: u16, position_y: u8, font: u8, color: u8, orientation: u8, text: String) → ConvertingReceiver<()>¶Parameters: |
|
---|
Draws a text with up to 50 characters at the pixel position (x, y).
You can use one of 9 different font sizes and draw the text in black/white/red|gray. The text can be drawn horizontal or vertical.
This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer
to the display use EPaper296x128Bricklet::draw
.
The font conforms to code page 437.
The following constants are available for this function:
For font:
For color:
For orientation:
EPaper296x128Bricklet::
draw_line
(&self, position_x_start: u16, position_y_start: u8, position_x_end: u16, position_y_end: u8, color: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Draws a line from (x, y)-start to (x, y)-end in the given color.
This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer
to the display use EPaper296x128Bricklet::draw
.
The following constants are available for this function:
For color:
EPaper296x128Bricklet::
draw_box
(&self, position_x_start: u16, position_y_start: u8, position_x_end: u16, position_y_end: u8, fill: bool, color: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Draws a box from (x, y)-start to (x, y)-end in the given color.
If you set fill to true, the box will be filled with the color. Otherwise only the outline will be drawn.
This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer
to the display use EPaper296x128Bricklet::draw
.
The following constants are available for this function:
For color:
EPaper296x128Bricklet::
set_update_mode
(&self, update_mode: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Note
The default update mode corresponds to the default e-paper display manufacturer settings. All of the other modes are experimental and will result in increased ghosting and possibly other long-term side effects.
If you want to know more about the inner workings of an e-paper display take a look at this excellent video from Ben Krasnow: https://www.youtube.com/watch?v=MsbiO8EAsGw.
If you are not sure about this option, leave the update mode at default.
Currently there are three update modes available:
With the black/white/red display if you use either the black/white or the delta mode, after a while of going back and forth between black and white the white color will start to appear red-ish or pink-ish.
If you use the aggressive delta mode and rapidly change the content, we recommend that you change back to the default mode every few hours and in the default mode cycle between the three available colors a few times. This will get rid of the ghosting and after that you can go back to the delta mode with flicker-free updates.
The following constants are available for this function:
For update_mode:
EPaper296x128Bricklet::
get_update_mode
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the update mode as set by EPaper296x128Bricklet::set_update_mode
.
The following constants are available for this function:
For update_mode:
EPaper296x128Bricklet::
set_display_type
(&self, display_type: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the type of the display. The e-paper display is available in black/white/red and black/white/gray. This will be factory set during the flashing and testing phase. The value is saved in non-volatile memory and will stay after a power cycle.
The following constants are available for this function:
For display_type:
EPaper296x128Bricklet::
get_display_type
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the type of the e-paper display. It can either be black/white/red or black/white/gray.
The following constants are available for this function:
For display_type:
EPaper296x128Bricklet::
set_display_driver
(&self, display_driver: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the type of display driver. The Bricklet can currently support SSD1675A and SSD1680. This will be factory set during the flashing and testing phase. The value is saved in non-volatile memory and will stay after a power cycle.
The following constants are available for this function:
For display_driver:
New in version 2.0.3 (Plugin).
EPaper296x128Bricklet::
get_display_driver
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the e-paper display driver.
The following constants are available for this function:
For display_driver:
New in version 2.0.3 (Plugin).
EPaper296x128Bricklet::
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.
EPaper296x128Bricklet::
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:
EPaper296x128Bricklet::
get_status_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by EPaper296x128Bricklet::set_status_led_config
The following constants are available for this function:
For config:
EPaper296x128Bricklet::
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.
EPaper296x128Bricklet::
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!
EPaper296x128Bricklet::
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.
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.
EPaper296x128Bricklet::
get_draw_status_callback_receiver
(&self) → ConvertingCallbackReceiver<u8>¶Event: |
|
---|
Receivers created with this function receive Draw Status events.
Callback for the current draw status. Will be called every time the
draw status changes (see EPaper296x128Bricklet::get_draw_status
).
The following constants are available for this function:
For draw_status:
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.
EPaper296x128Bricklet::
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.
EPaper296x128Bricklet::
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
EPaper296x128Bricklet::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:
EPaper296x128Bricklet::
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:
EPaper296x128Bricklet::
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.
EPaper296x128Bricklet::
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:
EPaper296x128Bricklet::
get_bootloader_mode
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the current bootloader mode, see EPaper296x128Bricklet::set_bootloader_mode
.
The following constants are available for this function:
For mode:
EPaper296x128Bricklet::
set_write_firmware_pointer
(&self, pointer: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the firmware pointer for EPaper296x128Bricklet::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.
EPaper296x128Bricklet::
write_firmware
(&self, data: [u8; 64]) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
EPaper296x128Bricklet::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.
EPaper296x128Bricklet::
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.
EPaper296x128Bricklet::
read_uid
(&self) → ConvertingReceiver<u32>¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
EPaper296x128Bricklet::
DEVICE_IDENTIFIER
¶This constant is used to identify a E-Paper 296x128 Bricklet.
The EPaper296x128Bricklet::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.
EPaper296x128Bricklet::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a E-Paper 296x128 Bricklet.