Shell - Thermocouple Bricklet 2.0

This is the description of the Shell API bindings for the Thermocouple Bricklet 2.0. General information and technical specifications for the Thermocouple Bricklet 2.0 are summarized in its hardware description.

An installation guide for the Shell API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (example-simple.sh)

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 2.0

# Get current temperature
tinkerforge call thermocouple-v2-bricklet $uid get-temperature

Callback

Download (example-callback.sh)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
#!/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 2.0

# Handle incoming temperature callbacks
tinkerforge dispatch thermocouple-v2-bricklet $uid temperature &

# Set period for temperature callback to 1s (1000ms) without a threshold
tinkerforge call thermocouple-v2-bricklet $uid set-temperature-callback-configuration 1000 false threshold-option-off 0 0

echo "Press key to exit"; read dummy

kill -- -$$ # Stop callback dispatch in background

Threshold

Download (example-threshold.sh)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
#!/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 2.0

# Handle incoming temperature callbacks
tinkerforge dispatch thermocouple-v2-bricklet $uid temperature &

# Configure threshold for temperature "greater than 30 °C"
# with a debounce period of 10s (10000ms)
tinkerforge call thermocouple-v2-bricklet $uid set-temperature-callback-configuration 10000 false threshold-option-greater 3000 0

echo "Press key to exit"; read dummy

kill -- -$$ # Stop callback dispatch in background

API

Possible exit codes for all tinkerforge commands are:

  • 1: interrupted (ctrl+c)
  • 2: syntax error
  • 21: Python 2.5 or newer is required
  • 22: Python argparse module is missing
  • 23: socket error
  • 24: other exception
  • 25: invalid placeholder in format string
  • 26: authentication error
  • 201: timeout occurred
  • 209: invalid argument value
  • 210: function is not supported
  • 211: unknown error

Command Structure

The common options of the call and dispatch commands are documented here. The specific command structure is shown below.

tinkerforge call thermocouple-v2-bricklet [<option>..] <uid> <function> [<argument>..]
Parameters:
  • <uid> -- string
  • <function> -- string

The call command is used to call a function of the Thermocouple Bricklet 2.0. 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 2.0 and exits
tinkerforge dispatch thermocouple-v2-bricklet [<option>..] <uid> <callback>
Parameters:
  • <uid> -- string
  • <callback> -- string

The dispatch command is used to dispatch a callback of the Thermocouple Bricklet 2.0. 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 2.0 and exits
tinkerforge call thermocouple-v2-bricklet <uid> <function> [<option>..] [<argument>..]
Parameters:
  • <uid> -- string
  • <function> -- string

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 exits

Getter 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 it

The --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 send and errors are silently ignored, because they cannot be detected.

tinkerforge dispatch thermocouple-v2-bricklet <uid> <callback> [<option>..]
Parameters:
  • <uid> -- string
  • <callback> -- string

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)

Basic Functions

tinkerforge call thermocouple-v2-bricklet <uid> get-temperature
Output:
  • temperature -- int

Returns the temperature of the thermocouple. The value is given in °C/100, e.g. a value of 4223 means that a temperature of 42.23 °C is measured.

If you want to get the temperature periodically, it is recommended to use the temperature callback and set the period with set-temperature-callback-configuration.

If you want to get the value periodically, it is recommended to use the temperature callback. You can set the callback configuration with set-temperature-callback-configuration.

Advanced Functions

tinkerforge call thermocouple-v2-bricklet <uid> set-configuration <averaging> <thermocouple-type> <filter>
Parameters:
  • <averaging> -- int (has symbols)
  • <thermocouple-type> -- int (has symbols)
  • <filter> -- int (has symbols)
Output:

no 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:

  • G8: value = 8 * 1.6 * 2^17 * Vin
  • G32: 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:

  • 60Hz: time = 82 + (samples - 1) * 16.67
  • 50Hz: time = 98 + (samples - 1) * 20

The default configuration is 16 samples, K type and 50Hz.

The following symbols are available for this function:

  • averaging-1 = 1, for <averaging>
  • averaging-2 = 2, for <averaging>
  • averaging-4 = 4, for <averaging>
  • averaging-8 = 8, for <averaging>
  • averaging-16 = 16, for <averaging>
  • type-b = 0, for <thermocouple-type>
  • type-e = 1, for <thermocouple-type>
  • type-j = 2, for <thermocouple-type>
  • type-k = 3, for <thermocouple-type>
  • type-n = 4, for <thermocouple-type>
  • type-r = 5, for <thermocouple-type>
  • type-s = 6, for <thermocouple-type>
  • type-t = 7, for <thermocouple-type>
  • type-g8 = 8, for <thermocouple-type>
  • type-g32 = 9, for <thermocouple-type>
  • filter-option-50hz = 0, for <filter>
  • filter-option-60hz = 1, for <filter>
tinkerforge call thermocouple-v2-bricklet <uid> get-configuration
Output:
  • averaging -- int (has symbols)
  • thermocouple-type -- int (has symbols)
  • filter -- int (has symbols)

Returns the configuration as set by set-configuration.

The following symbols are available for this function:

  • averaging-1 = 1, for averaging
  • averaging-2 = 2, for averaging
  • averaging-4 = 4, for averaging
  • averaging-8 = 8, for averaging
  • averaging-16 = 16, for averaging
  • type-b = 0, for thermocouple-type
  • type-e = 1, for thermocouple-type
  • type-j = 2, for thermocouple-type
  • type-k = 3, for thermocouple-type
  • type-n = 4, for thermocouple-type
  • type-r = 5, for thermocouple-type
  • type-s = 6, for thermocouple-type
  • type-t = 7, for thermocouple-type
  • type-g8 = 8, for thermocouple-type
  • type-g32 = 9, for thermocouple-type
  • filter-option-50hz = 0, for filter
  • filter-option-60hz = 1, for filter
tinkerforge call thermocouple-v2-bricklet <uid> get-error-state
Output:
  • over-under -- bool
  • open-circuit -- bool

Returns the current error state. There are two possible errors:

  • Over/Under Voltage and
  • Open Circuit.

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.

tinkerforge call thermocouple-v2-bricklet <uid> get-spitfp-error-count
Output:
  • error-count-ack-checksum -- int
  • error-count-message-checksum -- int
  • error-count-frame -- int
  • error-count-overflow -- int

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

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.

tinkerforge call thermocouple-v2-bricklet <uid> set-bootloader-mode <mode>
Parameters:
  • <mode> -- int (has symbols)
Output:
  • status -- int (has symbols)

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:

  • bootloader-mode-bootloader = 0, for <mode>
  • bootloader-mode-firmware = 1, for <mode>
  • bootloader-mode-bootloader-wait-for-reboot = 2, for <mode>
  • bootloader-mode-firmware-wait-for-reboot = 3, for <mode>
  • bootloader-mode-firmware-wait-for-erase-and-reboot = 4, for <mode>
  • bootloader-status-ok = 0, for status
  • bootloader-status-invalid-mode = 1, for status
  • bootloader-status-no-change = 2, for status
  • bootloader-status-entry-function-not-present = 3, for status
  • bootloader-status-device-identifier-incorrect = 4, for status
  • bootloader-status-crc-mismatch = 5, for status
tinkerforge call thermocouple-v2-bricklet <uid> get-bootloader-mode
Output:
  • mode -- int (has symbols)

Returns the current bootloader mode, see set-bootloader-mode.

The following symbols are available for this function:

  • bootloader-mode-bootloader = 0, for mode
  • bootloader-mode-firmware = 1, for mode
  • bootloader-mode-bootloader-wait-for-reboot = 2, for mode
  • bootloader-mode-firmware-wait-for-reboot = 3, for mode
  • bootloader-mode-firmware-wait-for-erase-and-reboot = 4, for mode
tinkerforge call thermocouple-v2-bricklet <uid> set-write-firmware-pointer <pointer>
Parameters:
  • <pointer> -- int
Output:

no output

Sets the firmware pointer for 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.

tinkerforge call thermocouple-v2-bricklet <uid> write-firmware <data>
Parameters:
  • <data> -- int,int,..61x..,int
Output:
  • status -- int

Writes 64 Bytes of firmware at the position as written by 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.

tinkerforge call thermocouple-v2-bricklet <uid> set-status-led-config <config>
Parameters:
  • <config> -- int (has symbols)
Output:

no output

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:

  • status-led-config-off = 0, for <config>
  • status-led-config-on = 1, for <config>
  • status-led-config-show-heartbeat = 2, for <config>
  • status-led-config-show-status = 3, for <config>
tinkerforge call thermocouple-v2-bricklet <uid> get-status-led-config
Output:
  • config -- int (has symbols)

Returns the configuration as set by set-status-led-config

The following symbols are available for this function:

  • status-led-config-off = 0, for config
  • status-led-config-on = 1, for config
  • status-led-config-show-heartbeat = 2, for config
  • status-led-config-show-status = 3, for config
tinkerforge call thermocouple-v2-bricklet <uid> get-chip-temperature
Output:
  • temperature -- int

Returns the temperature in °C 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.

tinkerforge call thermocouple-v2-bricklet <uid> reset
Output:no output

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!

tinkerforge call thermocouple-v2-bricklet <uid> write-uid <uid>
Parameters:
  • <uid> -- int
Output:

no output

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.

tinkerforge call thermocouple-v2-bricklet <uid> read-uid
Output:
  • uid -- int

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

tinkerforge call thermocouple-v2-bricklet <uid> get-identity
Output:
  • uid -- string
  • connected-uid -- string
  • position -- char
  • hardware-version -- int,int,int
  • firmware-version -- int,int,int
  • device-identifier -- int (has symbols)

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' or 'd'.

The device identifier numbers can be found here

Callback Configuration Functions

tinkerforge call thermocouple-v2-bricklet <uid> set-temperature-callback-configuration <period> <value-has-to-change> <option> <min> <max>
Parameters:
  • <period> -- int
  • <value-has-to-change> -- bool
  • <option> -- char (has symbols)
  • <min> -- int
  • <max> -- int
Output:

no output

The period in ms is the period with which the temperature callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

It is furthermore possible to constrain the callback with thresholds.

The option-parameter together with min/max sets a threshold for the temperature callback.

The following options are possible:

Option Description
'x' Threshold is turned off
'o' Threshold is triggered when the value is outside the min and max values
'i' Threshold is triggered when the value is inside or equal to the min and max values
'<' Threshold is triggered when the value is smaller than the min value (max is ignored)
'>' Threshold is triggered when the value is greater than the min value (max is ignored)

If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.

The default value is (0, false, 'x', 0, 0).

The following symbols are available for this function:

  • threshold-option-off = x, for <option>
  • threshold-option-outside = o, for <option>
  • threshold-option-inside = i, for <option>
  • threshold-option-smaller = <, for <option>
  • threshold-option-greater = >, for <option>
tinkerforge call thermocouple-v2-bricklet <uid> get-temperature-callback-configuration
Output:
  • period -- int
  • value-has-to-change -- bool
  • option -- char (has symbols)
  • min -- int
  • max -- int

Returns the callback configuration as set by set-temperature-callback-configuration.

The following symbols are available for this function:

  • threshold-option-off = x, for option
  • threshold-option-outside = o, for option
  • threshold-option-inside = i, for option
  • threshold-option-smaller = <, for option
  • threshold-option-greater = >, for option

Callbacks

Callbacks can be used to receive time critical or recurring data from the device:

tinkerforge dispatch thermocouple-v2-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.

tinkerforge dispatch thermocouple-v2-bricklet <uid> temperature
Output:
  • temperature -- int

This callback is triggered periodically according to the configuration set by set-temperature-callback-configuration.

The parameter is the same as get-temperature.

tinkerforge dispatch thermocouple-v2-bricklet <uid> error-state
Output:
  • over-under -- bool
  • open-circuit -- bool

This Callback is triggered every time the error state changes (see get-error-state).