This is the description of the MQTT API bindings for the One Wire Bricklet. General information and technical specifications for the One Wire Bricklet 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-read-ds18b20-temperature.txt)
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 | # Change XYZ to the UID of your One Wire Bricklet
setup:
publish '{"identifier": 0, "command": 78}' to tinkerforge/request/one_wire_bricklet/XYZ/write_command # WRITE SCRATCHPAD
publish '{"data": 0}' to tinkerforge/request/one_wire_bricklet/XYZ/write # ALARM H (unused)
publish '{"data": 0}' to tinkerforge/request/one_wire_bricklet/XYZ/write # ALARM L (unused)
publish '{"data": 127}' to tinkerforge/request/one_wire_bricklet/XYZ/write # CONFIGURATION: 12-bit mode
# Read temperature 10 times
for i in 0..9
publish '{"identifier": 0, "command": 68}' to tinkerforge/request/one_wire_bricklet/XYZ/write_command # CONVERT T (start temperature conversion)
wait for 1s # Wait for conversion to finish
publish '{"identifier": 0, "command": 190}' to tinkerforge/request/one_wire_bricklet/XYZ/write_command # READ SCRATCHPAD
subscribe to tinkerforge/response/one_wire_bricklet/XYZ/read # Subscribe to responses for read commands below
first message is t_low
second message is t_high
endsubscribe
publish '' to tinkerforge/request/one_wire_bricklet/XYZ/read # Read t_low
publish '' to tinkerforge/request/one_wire_bricklet/XYZ/read # Read t_high
set temperature to t_low | (t_high << 8)
if temperature > (1 << 12)
set temperature to temperature - (1 << 16) # Negative 12-bit values are sign-extended to 16-bit two's complement.
endif
set temperature to temperature / 16 # 12 bit mode measures in units of 1/16°C.
print temperature
endfor
|
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/
one_wire_bricklet/
<UID>/
search_bus
¶Request: |
|
---|---|
Response: |
|
Returns a list of up to 64 identifiers of the connected 1-Wire devices. Each identifier is 64-bit and consists of 8-bit family code, 48-bit ID and 8-bit CRC.
To get these identifiers the Bricklet runs the SEARCH ROM algorithm, as defined by Maxim.
The following symbols are available for this function:
For status:
request/
one_wire_bricklet/
<UID>/
reset_bus
¶Request: |
|
---|---|
Response: |
|
Resets the bus with the 1-Wire reset operation.
The following symbols are available for this function:
For status:
request/
one_wire_bricklet/
<UID>/
write
¶Request: |
|
---|---|
Response: |
|
Writes a byte of data to the 1-Wire bus.
The following symbols are available for this function:
For status:
request/
one_wire_bricklet/
<UID>/
read
¶Request: |
|
---|---|
Response: |
|
Reads a byte of data from the 1-Wire bus.
The following symbols are available for this function:
For status:
request/
one_wire_bricklet/
<UID>/
write_command
¶Request: |
|
---|---|
Response: |
|
Writes a command to the 1-Wire device with the given identifier. You can obtain
the identifier by calling request/one_wire_bricklet/<UID>/search_bus
. The MATCH ROM operation is used to
write the command.
If you only have one device connected or want to broadcast to all devices you can set the identifier to 0. In this case the SKIP ROM operation is used to write the command.
The following symbols are available for this function:
For status:
request/
one_wire_bricklet/
<UID>/
set_communication_led_config
¶Request: |
|
---|---|
Response: |
|
Sets the communication LED configuration. By default the LED shows 1-wire communication traffic by flickering.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following symbols are available for this function:
For config:
request/
one_wire_bricklet/
<UID>/
get_communication_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/one_wire_bricklet/<UID>/set_communication_led_config
The following symbols are available for this function:
For config:
request/
one_wire_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/
one_wire_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/
one_wire_bricklet/
<UID>/
get_status_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/one_wire_bricklet/<UID>/set_status_led_config
The following symbols are available for this function:
For config:
request/
one_wire_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/
one_wire_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/
one_wire_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 One Wire's name in a human readable form.
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/
one_wire_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/
one_wire_bricklet/
<UID>/
get_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Returns the current bootloader mode, see request/one_wire_bricklet/<UID>/set_bootloader_mode
.
The following symbols are available for this function:
For mode:
request/
one_wire_bricklet/
<UID>/
set_write_firmware_pointer
¶Request: |
|
---|---|
Response: |
|
Sets the firmware pointer for request/one_wire_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/
one_wire_bricklet/
<UID>/
write_firmware
¶Request: |
|
---|---|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
request/one_wire_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/
one_wire_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/
one_wire_bricklet/
<UID>/
read_uid
¶Request: |
|
---|---|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.