This is the description of the Shell API bindings for the Thermocouple Bricklet. General information and technical specifications for the Thermocouple Bricklet are summarized in its hardware description.
An installation guide for the Shell API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 6 7 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Thermocouple Bricklet
# Get current temperature
tinkerforge call thermocouple-bricklet $uid get-temperature
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Thermocouple Bricklet
# Handle incoming temperature callbacks
tinkerforge dispatch thermocouple-bricklet $uid temperature &
# Set period for temperature callback to 1s (1000ms)
# Note: The temperature callback is only called every second
# if the temperature has changed since the last call!
tinkerforge call thermocouple-bricklet $uid set-temperature-callback-period 1000
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Download (example-threshold.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Thermocouple Bricklet
# Get threshold callbacks with a debounce time of 10 seconds (10000ms)
tinkerforge call thermocouple-bricklet $uid set-debounce-period 10000
# Handle incoming temperature reached callbacks
tinkerforge dispatch thermocouple-bricklet $uid temperature-reached &
# Configure threshold for temperature "greater than 30 °C"
tinkerforge call thermocouple-bricklet $uid set-temperature-callback-threshold threshold-option-greater 3000 0
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Possible exit codes for all tinkerforge
commands are:
argparse
module is missingThe common options of the call
and dispatch
commands are documented
here. The specific command structure is shown below.
call
thermocouple-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Thermocouple Bricklet. It can take several
options:
--help
shows help for the specific call
command and exits--list-functions
shows a list of known functions of the Thermocouple Bricklet and exitsdispatch
thermocouple-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Thermocouple Bricklet. It can
take several options:
--help
shows help for the specific dispatch
command and exits--list-callbacks
shows a list of known callbacks of the Thermocouple Bricklet and exitsthermocouple-bricklet
<uid> <function>
[<option>..] [<argument>..]¶Parameters: |
|
---|
The <function>
to be called can take different options depending of its
kind. All functions can take the following options:
--help
shows help for the specific function and exitsGetter functions can take the following options:
--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response
requests response and waits for itThe --expect-response
option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
thermocouple-bricklet
<uid> <callback>
[<option>..]¶Parameters: |
|
---|
The <callback>
to be dispatched can take several options:
--help
shows help for the specific callback and exits--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)thermocouple-bricklet
<uid> get-temperature
¶Output: |
|
---|
Returns the temperature of the thermocouple.
If you want to get the temperature periodically, it is recommended
to use the temperature
callback and set the period with
set-temperature-callback-period
.
thermocouple-bricklet
<uid> set-configuration
<averaging> <thermocouple-type> <filter>¶Parameters: |
|
---|---|
Output: |
|
You can configure averaging size, thermocouple type and frequency filtering.
Available averaging sizes are 1, 2, 4, 8 and 16 samples.
As thermocouple type you can use B, E, J, K, N, R, S and T. If you have a different thermocouple or a custom thermocouple you can also use G8 and G32. With these types the returned value will not be in °C/100, it will be calculated by the following formulas:
value = 8 * 1.6 * 2^17 * Vin
value = 32 * 1.6 * 2^17 * Vin
where Vin is the thermocouple input voltage.
The frequency filter can be either configured to 50Hz or to 60Hz. You should configure it according to your utility frequency.
The conversion time depends on the averaging and filter configuration, it can be calculated as follows:
time = 82 + (samples - 1) * 16.67
time = 98 + (samples - 1) * 20
The following symbols are available for this function:
For <averaging>:
For <thermocouple-type>:
For <filter>:
thermocouple-bricklet
<uid> get-configuration
¶Output: |
|
---|
Returns the configuration as set by set-configuration
.
The following symbols are available for this function:
For averaging:
For thermocouple-type:
For filter:
thermocouple-bricklet
<uid> get-error-state
¶Output: |
|
---|
Returns the current error state. There are two possible errors:
Over/Under Voltage happens for voltages below 0V or above 3.3V. In this case it is very likely that your thermocouple is defective. An Open Circuit error indicates that there is no thermocouple connected.
You can use the error-state
callback to automatically get triggered
when the error state changes.
thermocouple-bricklet
<uid> get-identity
¶Output: |
|
---|
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.
thermocouple-bricklet
<uid> set-temperature-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the temperature
callback is triggered
periodically. A value of 0 turns the callback off.
The temperature
callback is only triggered if the temperature has changed
since the last triggering.
thermocouple-bricklet
<uid> get-temperature-callback-period
¶Output: |
|
---|
Returns the period as set by set-temperature-callback-period
.
thermocouple-bricklet
<uid> set-temperature-callback-threshold
<option> <min> <max>¶Parameters: |
|
---|---|
Output: |
|
Sets the thresholds for the temperature-reached
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the temperature is outside the min and max values |
'i' | Callback is triggered when the temperature is inside the min and max values |
'<' | Callback is triggered when the temperature is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the temperature is greater than the min value (max is ignored) |
The following symbols are available for this function:
For <option>:
thermocouple-bricklet
<uid> get-temperature-callback-threshold
¶Output: |
|
---|
Returns the threshold as set by set-temperature-callback-threshold
.
The following symbols are available for this function:
For option:
thermocouple-bricklet
<uid> set-debounce-period
<debounce>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the threshold callback
is triggered, if the threshold
keeps being reached.
thermocouple-bricklet
<uid> get-debounce-period
¶Output: |
|
---|
Returns the debounce period as set by set-debounce-period
.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch thermocouple-bricklet <uid> example
The available callbacks are described below.
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.
thermocouple-bricklet
<uid> temperature
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-temperature-callback-period
. The parameter is the
temperature of the thermocouple.
The temperature
callback is only triggered if the temperature has
changed since the last triggering.
thermocouple-bricklet
<uid> temperature-reached
¶Output: |
|
---|
This callback is triggered when the threshold as set by
set-temperature-callback-threshold
is reached.
The parameter is the temperature of the thermocouple.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by set-debounce-period
.
thermocouple-bricklet
<uid> error-state
¶Output: |
|
---|
This Callback is triggered every time the error state changes
(see get-error-state
).