MQTT - LCD 16x2 Bricklet¶

Hello World¶

Download (example-hello-world.txt)

1
2
3
4
5
6
7
8

# Change XYZ to the UID of your LCD 16x2 Bricklet

setup:
    # Turn backlight on
    publish '' to tinkerforge/request/lcd_16x2_bricklet/XYZ/backlight_on

    # Write "Hello World"
    publish '{"line": 0, "position": 0, "text": "Hello World"}' to tinkerforge/request/lcd_16x2_bricklet/XYZ/write_line

Button Callback¶

Download (example-button-callback.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

# Change XYZ to the UID of your LCD 16x2 Bricklet

setup:
    # Handle incoming button pressed callbacks
    subscribe to tinkerforge/callback/lcd_16x2_bricklet/XYZ/button_pressed
    publish '{"register": true}' to tinkerforge/register/lcd_16x2_bricklet/XYZ/button_pressed # Register button_pressed callback

    # Handle incoming button released callbacks
    subscribe to tinkerforge/callback/lcd_16x2_bricklet/XYZ/button_released
    publish '{"register": true}' to tinkerforge/register/lcd_16x2_bricklet/XYZ/button_released # Register button_released callback

Unicode¶

Download (example-unicode.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

# Change XYZ to the UID of your LCD 16x2 Bricklet

setup:
    # Turn backlight on
    publish '' to tinkerforge/request/lcd_16x2_bricklet/XYZ/backlight_on

    function UTF8ToKS006U # This function should convert strings from UTF-8 to the LCD charset. See examples for other languages.

    # Write a string using the FIXME function to map to the LCD charset
    publish '{"line": 0, "position": 0, "text": UTF8ToKS0066U("Stromstärke: 5µA")}' to tinkerforge/request/lcd_16x2_bricklet/XYZ/write_line

    # Write a string directly including characters from the LCD charset
    publish '{"line": 1, "position": 0, "text": "Drehzahl: 1000s\u00e9"}' to tinkerforge/request/lcd_16x2_bricklet/XYZ/write_line

Basic Functions¶

request/lcd_16x2_bricklet/<UID>/write_line¶

Request:	line – Type: int, Range: [0 to 1] position – Type: int, Range: [0 to 15] text – Type: string, Length: up to 16
Response:	no response

Writes text to a specific line with a specific position. The text can have a maximum of 16 characters.

For example: (0, 5, "Hello") will write Hello in the middle of the first line of the display.

The display uses a special charset that includes all ASCII characters except backslash and tilde. The LCD charset also includes several other non-ASCII characters, see the charset specification for details. The Unicode example above shows how to specify non-ASCII characters and how to translate from Unicode to the LCD charset.

request/lcd_16x2_bricklet/<UID>/clear_display¶

Request:	empty payload
Response:	no response

Deletes all characters from the display.

request/lcd_16x2_bricklet/<UID>/backlight_on¶

Request:	empty payload
Response:	no response

Turns the backlight on.

request/lcd_16x2_bricklet/<UID>/backlight_off¶

Request:	empty payload
Response:	no response

Turns the backlight off.

request/lcd_16x2_bricklet/<UID>/is_backlight_on¶

Request:	empty payload
Response:	backlight – Type: bool

Returns true if the backlight is on and false otherwise.

Advanced Functions¶

request/lcd_16x2_bricklet/<UID>/set_config¶

Request:	cursor – Type: bool, Default: false blinking – Type: bool, Default: false
Response:	no response

Configures if the cursor (shown as "_") should be visible and if it should be blinking (shown as a blinking block). The cursor position is one character behind the the last text written with request/lcd_16x2_bricklet/<UID>/write_line.

request/lcd_16x2_bricklet/<UID>/get_config¶

Request:	empty payload
Response:	cursor – Type: bool, Default: false blinking – Type: bool, Default: false

Returns the configuration as set by request/lcd_16x2_bricklet/<UID>/set_config.

request/lcd_16x2_bricklet/<UID>/is_button_pressed¶

Request:	button – Type: int, Range: [0 to 2]
Response:	pressed – Type: bool

Returns true if the button is pressed.

If you want to react on button presses and releases it is recommended to use the register/lcd_16x2_bricklet/<UID>/button_pressed and register/lcd_16x2_bricklet/<UID>/button_released callbacks.

request/lcd_16x2_bricklet/<UID>/set_custom_character¶

Request:	index – Type: int, Range: [0 to 7] character – Type: [int, ...], Length: 8, Range: [0 to 31]
Response:	no response

The LCD 16x2 Bricklet can store up to 8 custom characters. The characters consist of 5x8 pixels and can be addressed with the index 0-7. To describe the pixels, the first 5 bits of 8 bytes are used. For example, to make a custom character "H", you should transfer the following:

• character[0] = 0b00010001 (decimal value 17)
• character[1] = 0b00010001 (decimal value 17)
• character[2] = 0b00010001 (decimal value 17)
• character[3] = 0b00011111 (decimal value 31)
• character[4] = 0b00010001 (decimal value 17)
• character[5] = 0b00010001 (decimal value 17)
• character[6] = 0b00010001 (decimal value 17)
• character[7] = 0b00000000 (decimal value 0)

The characters can later be written with request/lcd_16x2_bricklet/<UID>/write_line by using the characters with the byte representation 8 ("\x08" or "\u0008") to 15 ("\x0F" or "\u000F").

You can play around with the custom characters in Brick Viewer since version 2.0.1.

Custom characters are stored by the LCD in RAM, so they have to be set after each startup.

New in version 2.0.1 (Plugin).

request/lcd_16x2_bricklet/<UID>/get_custom_character¶

Request:	index – Type: int, Range: [0 to 7]
Response:	character – Type: [int, ...], Length: 8, Range: [0 to 31]

Returns the custom character for a given index, as set with request/lcd_16x2_bricklet/<UID>/set_custom_character.

New in version 2.0.1 (Plugin).

request/lcd_16x2_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 LCD 16x2'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.

register/lcd_16x2_bricklet/<UID>/button_pressed¶

Register Request:	register – Type: bool
Callback Response:	button – Type: int, Range: [0 to 2]

A callback can be registered for this event by publishing to the .../register/lcd_16x2_bricklet/<UID>/button_pressed[/<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/lcd_16x2_bricklet/<UID>/button_pressed[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when a button is pressed. The callback payload is the number of the button.

register/lcd_16x2_bricklet/<UID>/button_released¶

Register Request:	register – Type: bool
Callback Response:	button – Type: int, Range: [0 to 2]

A callback can be registered for this event by publishing to the .../register/lcd_16x2_bricklet/<UID>/button_released[/<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/lcd_16x2_bricklet/<UID>/button_released[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when a button is released. The callback payload is the number of the button.