This is the description of the Python 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 Python 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 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your Thermocouple Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_thermocouple import BrickletThermocouple
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
t = BrickletThermocouple(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Get current temperature
temperature = t.get_temperature()
print("Temperature: " + str(temperature/100.0) + " °C")
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
Download (example_callback.py)
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 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your Thermocouple Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_thermocouple import BrickletThermocouple
# Callback function for temperature callback
def cb_temperature(temperature):
print("Temperature: " + str(temperature/100.0) + " °C")
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
t = BrickletThermocouple(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Register temperature callback to function cb_temperature
t.register_callback(t.CALLBACK_TEMPERATURE, cb_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!
t.set_temperature_callback_period(1000)
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
Download (example_threshold.py)
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 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your Thermocouple Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_thermocouple import BrickletThermocouple
# Callback function for temperature reached callback
def cb_temperature_reached(temperature):
print("Temperature: " + str(temperature/100.0) + " °C")
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
t = BrickletThermocouple(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Get threshold callbacks with a debounce time of 10 seconds (10000ms)
t.set_debounce_period(10000)
# Register temperature reached callback to function cb_temperature_reached
t.register_callback(t.CALLBACK_TEMPERATURE_REACHED, cb_temperature_reached)
# Configure threshold for temperature "greater than 30 °C"
t.set_temperature_callback_threshold(">", 30*100, 0)
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
Generally, every function of the Python bindings can throw an
tinkerforge.ip_connection.Error
exception that has a value
and a
description
property. value
can have different values:
All functions listed below are thread-safe.
BrickletThermocouple
(uid, ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
thermocouple = BrickletThermocouple("YOUR_DEVICE_UID", ipcon)
This object can then be used after the IP Connection is connected.
BrickletThermocouple.
get_temperature
()¶Returns: |
|
---|
Returns the temperature of the thermocouple.
If you want to get the temperature periodically, it is recommended
to use the CALLBACK_TEMPERATURE
callback and set the period with
set_temperature_callback_period()
.
BrickletThermocouple.
set_configuration
(averaging, thermocouple_type, filter)¶Parameters: |
|
---|---|
Returns: |
|
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 constants are available for this function:
For averaging:
For thermocouple_type:
For filter:
BrickletThermocouple.
get_configuration
()¶Return Object: |
|
---|
Returns the configuration as set by set_configuration()
.
The following constants are available for this function:
For averaging:
For thermocouple_type:
For filter:
BrickletThermocouple.
get_error_state
()¶Return Object: |
|
---|
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 CALLBACK_ERROR_STATE
callback to automatically get triggered
when the error state changes.
BrickletThermocouple.
get_identity
()¶Return Object: |
|
---|
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. There is also a constant for the device identifier of this Bricklet.
BrickletThermocouple.
register_callback
(callback_id, function)¶Parameters: |
|
---|---|
Returns: |
|
Registers the given function
with the given callback_id
.
The available callback IDs with corresponding function signatures are listed below.
BrickletThermocouple.
set_temperature_callback_period
(period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_TEMPERATURE
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_TEMPERATURE
callback is only triggered if the temperature has changed
since the last triggering.
BrickletThermocouple.
get_temperature_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_temperature_callback_period()
.
BrickletThermocouple.
set_temperature_callback_threshold
(option, min, max)¶Parameters: |
|
---|---|
Returns: |
|
Sets the thresholds for the CALLBACK_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 constants are available for this function:
For option:
BrickletThermocouple.
get_temperature_callback_threshold
()¶Return Object: |
|
---|
Returns the threshold as set by set_temperature_callback_threshold()
.
The following constants are available for this function:
For option:
BrickletThermocouple.
set_debounce_period
(debounce)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the threshold callback
is triggered, if the threshold
keeps being reached.
BrickletThermocouple.
get_debounce_period
()¶Returns: |
|
---|
Returns the debounce period as set by set_debounce_period()
.
Callbacks can be registered to receive
time critical or recurring data from the device. The registration is done
with the register_callback()
function of
the device object. The first parameter is the callback ID and the second
parameter the callback function:
def my_callback(param):
print(param)
thermocouple.register_callback(BrickletThermocouple.CALLBACK_EXAMPLE, my_callback)
The available constants with inherent number and type of parameters 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.
BrickletThermocouple.
CALLBACK_TEMPERATURE
¶Callback Parameters: |
|
---|
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 CALLBACK_TEMPERATURE
callback is only triggered if the temperature has
changed since the last triggering.
BrickletThermocouple.
CALLBACK_TEMPERATURE_REACHED
¶Callback Parameters: |
|
---|
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()
.
BrickletThermocouple.
CALLBACK_ERROR_STATE
¶Callback Parameters: |
|
---|
This Callback is triggered every time the error state changes
(see get_error_state()
).
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
BrickletThermocouple.
get_api_version
()¶Return Object: |
|
---|
Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
BrickletThermocouple.
get_response_expected
(function_id)¶Parameters: |
|
---|---|
Returns: |
|
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled,
because those functions will always send a response. For callback configuration
functions it is enabled by default too, but can be disabled by
set_response_expected()
. For setter functions it is disabled by default
and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletThermocouple.
set_response_expected
(function_id, response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletThermocouple.
set_response_expected_all
(response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletThermocouple.
DEVICE_IDENTIFIER
¶This constant is used to identify a Thermocouple Bricklet.
The get_identity()
function and the
IPConnection.CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletThermocouple.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Thermocouple Bricklet.