This is the description of the MQTT API bindings for the RS232 Bricklet 2.0. General information and technical specifications for the RS232 Bricklet 2.0 are summarized in its hardware description.
An installation guide for the MQTT API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example-loopback.txt)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | # For this example connect the RX1 and TX pin to receive the send message
# Change XYZ to the UID of your RS232 Bricklet 2.0
setup:
# Handle incoming read callbacks
subscribe to tinkerforge/callback/rs232_v2_bricklet/XYZ/read # Received messages contain the message as string
publish '{"register": true}' to tinkerforge/register/rs232_v2_bricklet/XYZ/read # Register read callback
# Enable read callback
publish '' to tinkerforge/request/rs232_v2_bricklet/XYZ/enable_read_callback
# Write "test" string
publish '{"message": "test"}' to tinkerforge/request/rs232_v2_bricklet/XYZ/write
|
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/...
.
request/
rs232_v2_bricklet/
<UID>/
write
¶Request: |
|
---|---|
Response: |
|
Writes characters to the RS232 interface. The characters can be binary data, ASCII or similar is not necessary.
The return value is the number of characters that were written.
See request/rs232_v2_bricklet/<UID>/set_configuration
for configuration possibilities
regarding baud rate, parity and so on.
request/
rs232_v2_bricklet/
<UID>/
read
¶Request: |
|
---|---|
Response: |
|
Returns up to length characters from receive buffer.
Instead of polling with this function, you can also use
callbacks. But note that this function will return available
data only when the read callback is disabled.
See request/rs232_v2_bricklet/<UID>/enable_read_callback
and register/rs232_v2_bricklet/<UID>/read
callback.
request/
rs232_v2_bricklet/
<UID>/
set_configuration
¶Request: |
|
---|---|
Response: |
|
Sets the configuration for the RS232 communication.
The following symbols are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
request/
rs232_v2_bricklet/
<UID>/
get_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/rs232_v2_bricklet/<UID>/set_configuration
.
The following symbols are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
request/
rs232_v2_bricklet/
<UID>/
set_buffer_config
¶Request: |
|
---|---|
Response: |
|
Sets the send and receive buffer size in byte. In total the buffers have to be 10240 byte (10KiB) in size, the minimum buffer size is 1024 byte (1KiB) for each.
The current buffer content is lost if this function is called.
The send buffer holds data that is given by request/rs232_v2_bricklet/<UID>/write
and
can not be written yet. The receive buffer holds data that is
received through RS232 but could not yet be send to the
user, either by request/rs232_v2_bricklet/<UID>/read
or through register/rs232_v2_bricklet/<UID>/read
callback.
request/
rs232_v2_bricklet/
<UID>/
get_buffer_config
¶Request: |
|
---|---|
Response: |
|
Returns the buffer configuration as set by request/rs232_v2_bricklet/<UID>/set_buffer_config
.
request/
rs232_v2_bricklet/
<UID>/
get_buffer_status
¶Request: |
|
---|---|
Response: |
|
Returns the currently used bytes for the send and received buffer.
See request/rs232_v2_bricklet/<UID>/set_buffer_config
for buffer size configuration.
request/
rs232_v2_bricklet/
<UID>/
get_error_count
¶Request: |
|
---|---|
Response: |
|
Returns the current number of overrun and parity errors.
request/
rs232_v2_bricklet/
<UID>/
get_spitfp_error_count
¶Request: |
|
---|---|
Response: |
|
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.
request/
rs232_v2_bricklet/
<UID>/
set_status_led_config
¶Request: |
|
---|---|
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:
request/
rs232_v2_bricklet/
<UID>/
get_status_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/rs232_v2_bricklet/<UID>/set_status_led_config
The following symbols are available for this function:
For config:
request/
rs232_v2_bricklet/
<UID>/
get_chip_temperature
¶Request: |
|
---|---|
Response: |
|
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/
rs232_v2_bricklet/
<UID>/
reset
¶Request: |
|
---|---|
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/
rs232_v2_bricklet/
<UID>/
get_identity
¶Request: |
|
---|---|
Response: |
|
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 RS232 2.0's name in a human readable form.
request/
rs232_v2_bricklet/
<UID>/
enable_read_callback
¶Request: |
|
---|---|
Response: |
|
Enables the register/rs232_v2_bricklet/<UID>/read
callback. This will disable the register/rs232_v2_bricklet/<UID>/frame_readable
callback.
By default the callback is disabled.
request/
rs232_v2_bricklet/
<UID>/
disable_read_callback
¶Request: |
|
---|---|
Response: |
|
Disables the register/rs232_v2_bricklet/<UID>/read
callback.
By default the callback is disabled.
request/
rs232_v2_bricklet/
<UID>/
is_read_callback_enabled
¶Request: |
|
---|---|
Response: |
|
Returns true if the register/rs232_v2_bricklet/<UID>/read
callback is enabled,
false otherwise.
request/
rs232_v2_bricklet/
<UID>/
set_frame_readable_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Configures the register/rs232_v2_bricklet/<UID>/frame_readable
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 register/rs232_v2_bricklet/<UID>/read
callback.
By default the callback is disabled.
New in version 2.0.3 (Plugin).
request/
rs232_v2_bricklet/
<UID>/
get_frame_readable_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by request/rs232_v2_bricklet/<UID>/set_frame_readable_callback_configuration
.
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 .../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/
rs232_v2_bricklet/
<UID>/
read
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/rs232_v2_bricklet/<UID>/read[/<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/rs232_v2_bricklet/<UID>/read[/<SUFFIX>]
topic for each registered suffix.
This callback is called if new data is available.
To enable this callback, use request/rs232_v2_bricklet/<UID>/enable_read_callback
.
Note
If reconstructing the value fails, the callback is triggered with null for message.
register/
rs232_v2_bricklet/
<UID>/
error_count
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/rs232_v2_bricklet/<UID>/error_count[/<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/rs232_v2_bricklet/<UID>/error_count[/<SUFFIX>]
topic for each registered suffix.
This callback is called if a new error occurs. It returns the current overrun and parity error count.
register/
rs232_v2_bricklet/
<UID>/
frame_readable
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/rs232_v2_bricklet/<UID>/frame_readable[/<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/rs232_v2_bricklet/<UID>/frame_readable[/<SUFFIX>]
topic for each registered suffix.
This callback is called if at least one frame of data is readable. The frame size is configured with request/rs232_v2_bricklet/<UID>/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 request/rs232_v2_bricklet/<UID>/read
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the request/rs232_v2_bricklet/<UID>/read
function, every time the callback triggers without checking the frame count callback payload.
New in version 2.0.3 (Plugin).
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/
rs232_v2_bricklet/
<UID>/
set_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
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:
For status:
request/
rs232_v2_bricklet/
<UID>/
get_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Returns the current bootloader mode, see request/rs232_v2_bricklet/<UID>/set_bootloader_mode
.
The following symbols are available for this function:
For mode:
request/
rs232_v2_bricklet/
<UID>/
set_write_firmware_pointer
¶Request: |
|
---|---|
Response: |
|
Sets the firmware pointer for request/rs232_v2_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/
rs232_v2_bricklet/
<UID>/
write_firmware
¶Request: |
|
---|---|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
request/rs232_v2_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/
rs232_v2_bricklet/
<UID>/
write_uid
¶Request: |
|
---|---|
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/
rs232_v2_bricklet/
<UID>/
read_uid
¶Request: |
|
---|---|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.