MQTT - E-Paper 296x128 Bricklet

This is the description of the MQTT 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 MQTT API bindings is part of their general description.

Examples

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

Hello World

Download (example-hello-world.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
# Change XYZ to the UID of your E-Paper 296x128 Bricklet

setup:
    # Use black background
    publish '{"color": "black"}' to tinkerforge/request/e_paper_296x128_bricklet/XYZ/fill_display

    # Write big white "Hello World" in the middle of the screen
    publish '{"position_x": 16, "position_y": 48, "font": "24x32", "color": "white", "orientation": "horizontal", "text": "Hello World"}' to tinkerforge/request/e_paper_296x128_bricklet/XYZ/draw_text

    publish '' to tinkerforge/request/e_paper_296x128_bricklet/XYZ/draw

API

All published payloads to and from the MQTT bindings are in JSON format.

If an error occures, the bindings publish a JSON object containing the error message as member _ERROR. It is published on the corresponding response topic: .../response/... for .../request/... and .../callback/... for .../register/....

Basic Functions

request/e_paper_296x128_bricklet/<UID>/draw
Request:
  • empty payload
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/get_draw_status.

request/e_paper_296x128_bricklet/<UID>/get_draw_status
Request:
  • empty payload
Response:
  • draw_status – Type: int, Range: See symbols

Returns one of three draw statuses:

  • Idle
  • Copying: Data is being copied from the buffer of the Bricklet to the buffer of the display.
  • Drawing: The display is updating its content (during this phase the flickering etc happens).

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 symbols are available for this function:

For draw_status:

  • "idle" = 0
  • "copying" = 1
  • "drawing" = 2
request/e_paper_296x128_bricklet/<UID>/write_black_white
Request:
  • x_start – Type: int, Range: [0 to 295]
  • y_start – Type: int, Range: [0 to 127]
  • x_end – Type: int, Range: [0 to 295]
  • y_end – Type: int, Range: [0 to 127]
  • pixels – Type: [bool, ...], Length: variable
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/draw.

Use request/e_paper_296x128_bricklet/<UID>/write_color to write red or gray pixels.

request/e_paper_296x128_bricklet/<UID>/read_black_white
Request:
  • x_start – Type: int, Range: [0 to 295]
  • y_start – Type: int, Range: [0 to 127]
  • x_end – Type: int, Range: [0 to 295]
  • y_end – Type: int, Range: [0 to 127]
Response:
  • pixels – Type: [bool, ...], Length: variable

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.

request/e_paper_296x128_bricklet/<UID>/write_color
Request:
  • x_start – Type: int, Range: [0 to 295]
  • y_start – Type: int, Range: [0 to 127]
  • x_end – Type: int, Range: [0 to 295]
  • y_end – Type: int, Range: [0 to 127]
  • pixels – Type: [bool, ...], Length: variable
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/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 request/e_paper_296x128_bricklet/<UID>/draw.

Use request/e_paper_296x128_bricklet/<UID>/write_black_white to write black/white pixels.

request/e_paper_296x128_bricklet/<UID>/read_color
Request:
  • x_start – Type: int, Range: [0 to 295]
  • y_start – Type: int, Range: [0 to 127]
  • x_end – Type: int, Range: [0 to 295]
  • y_end – Type: int, Range: [0 to 127]
Response:
  • pixels – Type: [bool, ...], Length: variable

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.

request/e_paper_296x128_bricklet/<UID>/fill_display
Request:
  • color – Type: int, Range: See symbols
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/draw.

The following symbols are available for this function:

For color:

  • "black" = 0
  • "white" = 1
  • "red" = 2
  • "gray" = 2
request/e_paper_296x128_bricklet/<UID>/draw_text
Request:
  • position_x – Type: int, Range: [0 to 295]
  • position_y – Type: int, Range: [0 to 127]
  • font – Type: int, Range: See symbols
  • color – Type: int, Range: See symbols
  • orientation – Type: int, Range: See symbols
  • text – Type: string, Length: up to 50
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/draw.

The following symbols are available for this function:

For font:

  • "6x8" = 0
  • "6x16" = 1
  • "6x24" = 2
  • "6x32" = 3
  • "12x16" = 4
  • "12x24" = 5
  • "12x32" = 6
  • "18x24" = 7
  • "18x32" = 8
  • "24x32" = 9

For color:

  • "black" = 0
  • "white" = 1
  • "red" = 2
  • "gray" = 2

For orientation:

  • "horizontal" = 0
  • "vertical" = 1
request/e_paper_296x128_bricklet/<UID>/draw_line
Request:
  • position_x_start – Type: int, Range: [0 to 295]
  • position_y_start – Type: int, Range: [0 to 127]
  • position_x_end – Type: int, Range: [0 to 295]
  • position_y_end – Type: int, Range: [0 to 127]
  • color – Type: int, Range: See symbols
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/draw.

The following symbols are available for this function:

For color:

  • "black" = 0
  • "white" = 1
  • "red" = 2
  • "gray" = 2
request/e_paper_296x128_bricklet/<UID>/draw_box
Request:
  • position_x_start – Type: int, Range: [0 to 295]
  • position_y_start – Type: int, Range: [0 to 127]
  • position_x_end – Type: int, Range: [0 to 295]
  • position_y_end – Type: int, Range: [0 to 127]
  • fill – Type: bool
  • color – Type: int, Range: See symbols
Response:
  • no response

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 request/e_paper_296x128_bricklet/<UID>/draw.

The following symbols are available for this function:

For color:

  • "black" = 0
  • "white" = 1
  • "red" = 2
  • "gray" = 2

Advanced Functions

request/e_paper_296x128_bricklet/<UID>/set_update_mode
Request:
  • update_mode – Type: int, Range: See symbols, Default: 0
Response:
  • no response

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:

  • Default: Settings as given by the manufacturer. An update will take about 7.5 seconds and during the update the screen will flicker several times.
  • Black/White: This will only update the black/white pixel. It uses the manufacturer settings for black/white and ignores the red or gray pixel buffer. With this mode the display will flicker once and it takes about 2.5 seconds. Compared to the default settings there is more ghosting.
  • Delta: This will only update the black/white pixel. It uses an aggressive method where the changes are not applied for a whole buffer but only for the delta between the last and the next buffer. With this mode the display will not flicker during an update and it takes about 900-950ms. Compared to the other two settings there is more ghosting. This mode can be used for something like a flicker-free live update of a text.

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 symbols are available for this function:

For update_mode:

  • "default" = 0
  • "black_white" = 1
  • "delta" = 2
request/e_paper_296x128_bricklet/<UID>/get_update_mode
Request:
  • empty payload
Response:
  • update_mode – Type: int, Range: See symbols, Default: 0

Returns the update mode as set by request/e_paper_296x128_bricklet/<UID>/set_update_mode.

The following symbols are available for this function:

For update_mode:

  • "default" = 0
  • "black_white" = 1
  • "delta" = 2
request/e_paper_296x128_bricklet/<UID>/set_display_type
Request:
  • display_type – Type: int, Range: See symbols
Response:
  • no response

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 symbols are available for this function:

For display_type:

  • "black_white_red" = 0
  • "black_white_gray" = 1
request/e_paper_296x128_bricklet/<UID>/get_display_type
Request:
  • empty payload
Response:
  • display_type – Type: int, Range: See symbols

Returns the type of the e-paper display. It can either be black/white/red or black/white/gray.

The following symbols are available for this function:

For display_type:

  • "black_white_red" = 0
  • "black_white_gray" = 1
request/e_paper_296x128_bricklet/<UID>/set_display_driver
Request:
  • display_driver – Type: int, Range: See symbols
Response:
  • no response

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 symbols are available for this function:

For display_driver:

  • "ssd1675a" = 0
  • "ssd1680" = 1

New in version 2.0.3 (Plugin).

request/e_paper_296x128_bricklet/<UID>/get_display_driver
Request:
  • empty payload
Response:
  • display_driver – Type: int, Range: See symbols

Returns the e-paper display driver.

The following symbols are available for this function:

For display_driver:

  • "ssd1675a" = 0
  • "ssd1680" = 1

New in version 2.0.3 (Plugin).

request/e_paper_296x128_bricklet/<UID>/get_spitfp_error_count
Request:
  • empty payload
Response:
  • error_count_ack_checksum – Type: int, Range: [0 to 232 - 1]
  • error_count_message_checksum – Type: int, Range: [0 to 232 - 1]
  • error_count_frame – Type: int, Range: [0 to 232 - 1]
  • error_count_overflow – Type: int, 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.

request/e_paper_296x128_bricklet/<UID>/set_status_led_config
Request:
  • config – Type: int, Range: See symbols, Default: 3
Response:
  • no response

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 symbols are available for this function:

For config:

  • "off" = 0
  • "on" = 1
  • "show_heartbeat" = 2
  • "show_status" = 3
request/e_paper_296x128_bricklet/<UID>/get_status_led_config
Request:
  • empty payload
Response:
  • config – Type: int, Range: See symbols, Default: 3

Returns the configuration as set by request/e_paper_296x128_bricklet/<UID>/set_status_led_config

The following symbols are available for this function:

For config:

  • "off" = 0
  • "on" = 1
  • "show_heartbeat" = 2
  • "show_status" = 3
request/e_paper_296x128_bricklet/<UID>/get_chip_temperature
Request:
  • empty payload
Response:
  • temperature – Type: int, 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.

request/e_paper_296x128_bricklet/<UID>/reset
Request:
  • empty payload
Response:
  • no response

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!

request/e_paper_296x128_bricklet/<UID>/get_identity
Request:
  • empty payload
Response:
  • 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: [int, ...], Length: 3
    • 0: major – Type: int, Range: [0 to 255]
    • 1: minor – Type: int, Range: [0 to 255]
    • 2: revision – Type: int, Range: [0 to 255]
  • firmware_version – Type: [int, ...], Length: 3
    • 0: major – Type: int, Range: [0 to 255]
    • 1: minor – Type: int, Range: [0 to 255]
    • 2: revision – Type: int, Range: [0 to 255]
  • device_identifier – Type: int, Range: [0 to 216 - 1]
  • _display_name – Type: string

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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.

The display name contains the E-Paper 296x128's name in a human readable form.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding .../register/... topic and an optional suffix. This suffix can be used to deregister the callback later.

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.

register/e_paper_296x128_bricklet/<UID>/draw_status
Register Request:
  • register – Type: bool
Callback Response:
  • draw_status – Type: int, Range: See symbols

A callback can be registered for this event by publishing to the .../register/e_paper_296x128_bricklet/<UID>/draw_status[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/e_paper_296x128_bricklet/<UID>/draw_status[/<SUFFIX>] topic for each registered suffix.

Callback for the current draw status. Will be called every time the draw status changes (see request/e_paper_296x128_bricklet/<UID>/get_draw_status).

The following symbols are available for this function:

For draw_status:

  • "idle" = 0
  • "copying" = 1
  • "drawing" = 2

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.

request/e_paper_296x128_bricklet/<UID>/set_bootloader_mode
Request:
  • mode – Type: int, Range: See symbols
Response:
  • status – Type: int, Range: See symbols

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 symbols are available for this function:

For mode:

  • "bootloader" = 0
  • "firmware" = 1
  • "bootloader_wait_for_reboot" = 2
  • "firmware_wait_for_reboot" = 3
  • "firmware_wait_for_erase_and_reboot" = 4

For status:

  • "ok" = 0
  • "invalid_mode" = 1
  • "no_change" = 2
  • "entry_function_not_present" = 3
  • "device_identifier_incorrect" = 4
  • "crc_mismatch" = 5
request/e_paper_296x128_bricklet/<UID>/get_bootloader_mode
Request:
  • empty payload
Response:
  • mode – Type: int, Range: See symbols

Returns the current bootloader mode, see request/e_paper_296x128_bricklet/<UID>/set_bootloader_mode.

The following symbols are available for this function:

For mode:

  • "bootloader" = 0
  • "firmware" = 1
  • "bootloader_wait_for_reboot" = 2
  • "firmware_wait_for_reboot" = 3
  • "firmware_wait_for_erase_and_reboot" = 4
request/e_paper_296x128_bricklet/<UID>/set_write_firmware_pointer
Request:
  • pointer – Type: int, Unit: 1 B, Range: [0 to 232 - 1]
Response:
  • no response

Sets the firmware pointer for request/e_paper_296x128_bricklet/<UID>/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.

request/e_paper_296x128_bricklet/<UID>/write_firmware
Request:
  • data – Type: [int, ...], Length: 64, Range: [0 to 255]
Response:
  • status – Type: int, Range: [0 to 255]

Writes 64 Bytes of firmware at the position as written by request/e_paper_296x128_bricklet/<UID>/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.

request/e_paper_296x128_bricklet/<UID>/write_uid
Request:
  • uid – Type: int, Range: [0 to 232 - 1]
Response:
  • no response

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.

request/e_paper_296x128_bricklet/<UID>/read_uid
Request:
  • empty payload
Response:
  • uid – Type: int, Range: [0 to 232 - 1]

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