This is the description of the MQTT API bindings for the Load Cell Bricklet. General information and technical specifications for the Load Cell 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).
1 2 3 4 5 6 | # Change XYZ to the UID of your Load Cell Bricklet
setup:
# Get current weight
subscribe to tinkerforge/response/load_cell_bricklet/XYZ/get_weight
publish '' to tinkerforge/request/load_cell_bricklet/XYZ/get_weight
|
Download (example-callback.txt)
1 2 3 4 5 6 7 8 9 10 11 | # Change XYZ to the UID of your Load Cell Bricklet
setup:
# Handle incoming weight callbacks
subscribe to tinkerforge/callback/load_cell_bricklet/XYZ/weight
publish '{"register": true}' to tinkerforge/register/load_cell_bricklet/XYZ/weight # Register weight callback
# Set period for weight callback to 1s (1000ms)
# Note: The weight callback is only called every second
# if the weight has changed since the last call!
publish '{"period": 1000}' to tinkerforge/request/load_cell_bricklet/XYZ/set_weight_callback_period
|
Download (example-threshold.txt)
1 2 3 4 5 6 7 8 9 10 11 12 | # Change XYZ to the UID of your Load Cell Bricklet
setup:
# Get threshold callbacks with a debounce time of 1 second (1000ms)
publish '{"debounce": 1000}' to tinkerforge/request/load_cell_bricklet/XYZ/set_debounce_period
# Handle incoming weight reached callbacks
subscribe to tinkerforge/callback/load_cell_bricklet/XYZ/weight_reached
publish '{"register": true}' to tinkerforge/register/load_cell_bricklet/XYZ/weight_reached # Register weight_reached callback
# Configure threshold for weight "greater than 200 g"
publish '{"option": "greater", "min": 200, "max": 0}' to tinkerforge/request/load_cell_bricklet/XYZ/set_weight_callback_threshold
|
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/
load_cell_bricklet/
<UID>/
get_weight
¶Request: |
|
---|---|
Response: |
|
Returns the currently measured weight.
If you want to get the weight periodically, it is recommended
to use the register/load_cell_bricklet/<UID>/weight
callback and set the period with
request/load_cell_bricklet/<UID>/set_weight_callback_period
.
request/
load_cell_bricklet/
<UID>/
led_on
¶Request: |
|
---|---|
Response: |
|
Turns the LED on.
request/
load_cell_bricklet/
<UID>/
led_off
¶Request: |
|
---|---|
Response: |
|
Turns the LED off.
request/
load_cell_bricklet/
<UID>/
is_led_on
¶Request: |
|
---|---|
Response: |
|
Returns true if the led is on, false otherwise.
request/
load_cell_bricklet/
<UID>/
tare
¶Request: |
|
---|---|
Response: |
|
Sets the currently measured weight as tare weight.
request/
load_cell_bricklet/
<UID>/
set_moving_average
¶Request: |
|
---|---|
Response: |
|
Sets the length of a moving averaging for the weight value.
Setting the length to 1 will turn the averaging off. With less averaging, there is more noise on the data.
request/
load_cell_bricklet/
<UID>/
get_moving_average
¶Request: |
|
---|---|
Response: |
|
Returns the length moving average as set by request/load_cell_bricklet/<UID>/set_moving_average
.
request/
load_cell_bricklet/
<UID>/
calibrate
¶Request: |
|
---|---|
Response: |
|
To calibrate your Load Cell Bricklet you have to
The calibration is saved in the EEPROM of the Bricklet and only needs to be done once.
We recommend to use the Brick Viewer for calibration, you don't need to call this function in your source code.
request/
load_cell_bricklet/
<UID>/
set_configuration
¶Request: |
|
---|---|
Response: |
|
The measurement rate and gain are configurable.
The rate can be either 10Hz or 80Hz. A faster rate will produce more noise.
It is additionally possible to add a moving average
(see request/load_cell_bricklet/<UID>/set_moving_average
) to the measurements.
The gain can be 128x, 64x or 32x. It represents a measurement range of ±20mV, ±40mV and ±80mV respectively. The Load Cell Bricklet uses an excitation voltage of 5V and most load cells use an output of 2mV/V. That means the voltage range is ±15mV for most load cells (i.e. gain of 128x is best). If you don't know what all of this means you should keep it at 128x, it will most likely be correct.
The configuration is saved in the EEPROM of the Bricklet and only needs to be done once.
We recommend to use the Brick Viewer for configuration, you don't need to call this function in your source code.
The following symbols are available for this function:
For rate:
For gain:
request/
load_cell_bricklet/
<UID>/
get_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/load_cell_bricklet/<UID>/set_configuration
.
The following symbols are available for this function:
For rate:
For gain:
request/
load_cell_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 Load Cell's name in a human readable form.
request/
load_cell_bricklet/
<UID>/
set_weight_callback_period
¶Request: |
|
---|---|
Response: |
|
Sets the period with which the register/load_cell_bricklet/<UID>/weight
callback is triggered
periodically. A value of 0 turns the callback off.
The register/load_cell_bricklet/<UID>/weight
callback is only triggered if the weight has changed since the
last triggering.
request/
load_cell_bricklet/
<UID>/
get_weight_callback_period
¶Request: |
|
---|---|
Response: |
|
Returns the period as set by request/load_cell_bricklet/<UID>/set_weight_callback_period
.
request/
load_cell_bricklet/
<UID>/
set_weight_callback_threshold
¶Request: |
|
---|---|
Response: |
|
Sets the thresholds for the register/load_cell_bricklet/<UID>/weight_reached
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the weight is outside the min and max values |
'i' | Callback is triggered when the weight is inside the min and max values |
'<' | Callback is triggered when the weight is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the weight is greater than the min value (max is ignored) |
The following symbols are available for this function:
For option:
request/
load_cell_bricklet/
<UID>/
get_weight_callback_threshold
¶Request: |
|
---|---|
Response: |
|
Returns the threshold as set by request/load_cell_bricklet/<UID>/set_weight_callback_threshold
.
The following symbols are available for this function:
For option:
request/
load_cell_bricklet/
<UID>/
set_debounce_period
¶Request: |
|
---|---|
Response: |
|
Sets the period with which the threshold callback
is triggered, if the threshold
keeps being reached.
request/
load_cell_bricklet/
<UID>/
get_debounce_period
¶Request: |
|
---|---|
Response: |
|
Returns the debounce period as set by request/load_cell_bricklet/<UID>/set_debounce_period
.
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/
load_cell_bricklet/
<UID>/
weight
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/load_cell_bricklet/<UID>/weight[/<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/load_cell_bricklet/<UID>/weight[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically with the period that is set by
request/load_cell_bricklet/<UID>/set_weight_callback_period
. The callback payload is the weight
as measured by the load cell.
The register/load_cell_bricklet/<UID>/weight
callback is only triggered if the weight has changed since the
last triggering.
register/
load_cell_bricklet/
<UID>/
weight_reached
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/load_cell_bricklet/<UID>/weight_reached[/<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/load_cell_bricklet/<UID>/weight_reached[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered when the threshold as set by
request/load_cell_bricklet/<UID>/set_weight_callback_threshold
is reached.
The callback payload is the weight as measured by the load cell.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by request/load_cell_bricklet/<UID>/set_debounce_period
.