Shell - PTC Bricklet 2.0

This is the description of the Shell API bindings for the PTC Bricklet 2.0. General information and technical specifications for the PTC 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 PTC Bricklet 2.0

# Get current temperature
tinkerforge call ptc-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 PTC Bricklet 2.0

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

# Set period for temperature callback to 1s (1000ms) without a threshold
tinkerforge call ptc-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 PTC Bricklet 2.0

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

# Configure threshold for temperature "greater than 30 °C"
# with a debounce period of 1s (1000ms)
tinkerforge call ptc-v2-bricklet $uid set-temperature-callback-configuration 1000 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 ptc-v2-bricklet [<option>..] <uid> <function> [<argument>..]
Parameters:
  • <uid> – Type: String
  • <function> – Type: String

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

The dispatch command is used to dispatch a callback of the PTC 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 PTC Bricklet 2.0 and exits
tinkerforge call ptc-v2-bricklet <uid> <function> [<option>..] [<argument>..]
Parameters:
  • <uid> – Type: String
  • <function> – Type: 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 sent and errors are silently ignored, because they cannot be detected.

tinkerforge dispatch ptc-v2-bricklet <uid> <callback> [<option>..]
Parameters:
  • <uid> – Type: String
  • <callback> – Type: 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 ptc-v2-bricklet <uid> get-temperature
Output:
  • temperature – Type: Int, Unit: 1/100 °C, Range: [-24600 to 84900]

Returns the temperature of the connected sensor.

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.

tinkerforge call ptc-v2-bricklet <uid> get-resistance
Output:
  • resistance – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1]

Returns the value as measured by the MAX31865 precision delta-sigma ADC.

The value can be converted with the following formulas:

  • Pt100: resistance = (value * 390) / 32768
  • Pt1000: resistance = (value * 3900) / 32768

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

tinkerforge call ptc-v2-bricklet <uid> is-sensor-connected
Output:
  • connected – Type: Bool

Returns true if the sensor is connected correctly.

If this function returns false, there is either no Pt100 or Pt1000 sensor connected, the sensor is connected incorrectly or the sensor itself is faulty.

If you want to get the status automatically, it is recommended to use the sensor-connected callback. You can set the callback configuration with set-sensor-connected-callback-configuration.

tinkerforge call ptc-v2-bricklet <uid> set-wire-mode <mode>
Parameters:
  • <mode> – Type: Int, Range: See symbols, Default: 2
Output:
  • no output

Sets the wire mode of the sensor. Possible values are 2, 3 and 4 which correspond to 2-, 3- and 4-wire sensors. The value has to match the jumper configuration on the Bricklet.

The following symbols are available for this function:

For <mode>:

  • wire-mode-2 = 2
  • wire-mode-3 = 3
  • wire-mode-4 = 4
tinkerforge call ptc-v2-bricklet <uid> get-wire-mode
Output:
  • mode – Type: Int, Range: See symbols, Default: 2

Returns the wire mode as set by set-wire-mode

The following symbols are available for this function:

For mode:

  • wire-mode-2 = 2
  • wire-mode-3 = 3
  • wire-mode-4 = 4
tinkerforge call ptc-v2-bricklet <uid> set-moving-average-configuration <moving-average-length-resistance> <moving-average-length-temperature>
Parameters:
  • <moving-average-length-resistance> – Type: Int, Range: [1 to 1000], Default: 1
  • <moving-average-length-temperature> – Type: Int, Range: [1 to 1000], Default: 40
Output:
  • no output

Sets the length of a moving averaging for the resistance and temperature.

Setting the length to 1 will turn the averaging off. With less averaging, there is more noise on the data.

New data is gathered every 20ms. With a moving average of length 1000 the resulting averaging window has a length of 20s. If you want to do long term measurements the longest moving average will give the cleanest results.

The default values match the non-changeable averaging settings of the old PTC Bricklet 1.0

tinkerforge call ptc-v2-bricklet <uid> get-moving-average-configuration
Output:
  • moving-average-length-resistance – Type: Int, Range: [1 to 1000], Default: 1
  • moving-average-length-temperature – Type: Int, Range: [1 to 1000], Default: 40

Returns the moving average configuration as set by set-moving-average-configuration.

Advanced Functions

tinkerforge call ptc-v2-bricklet <uid> set-noise-rejection-filter <filter>
Parameters:
  • <filter> – Type: Int, Range: See symbols, Default: 0
Output:
  • no output

Sets the noise rejection filter to either 50Hz (0) or 60Hz (1). Noise from 50Hz or 60Hz power sources (including harmonics of the AC power's fundamental frequency) is attenuated by 82dB.

The following symbols are available for this function:

For <filter>:

  • filter-option-50hz = 0
  • filter-option-60hz = 1
tinkerforge call ptc-v2-bricklet <uid> get-noise-rejection-filter
Output:
  • filter – Type: Int, Range: See symbols, Default: 0

Returns the noise rejection filter option as set by set-noise-rejection-filter

The following symbols are available for this function:

For filter:

  • filter-option-50hz = 0
  • filter-option-60hz = 1
tinkerforge call ptc-v2-bricklet <uid> get-spitfp-error-count
Output:
  • error-count-ack-checksum – Type: Int, Range: [0 to 232 - 1]
  • error-count-message-checksum – Type: Int, Range: [0 to 232 - 1]
  • error-count-frame – Type: Int, Range: [0 to 232 - 1]
  • error-count-overflow – Type: Int, Range: [0 to 232 - 1]

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 ptc-v2-bricklet <uid> set-status-led-config <config>
Parameters:
  • <config> – Type: Int, Range: See symbols, Default: 3
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:

For <config>:

  • status-led-config-off = 0
  • status-led-config-on = 1
  • status-led-config-show-heartbeat = 2
  • status-led-config-show-status = 3
tinkerforge call ptc-v2-bricklet <uid> get-status-led-config
Output:
  • config – Type: Int, Range: See symbols, Default: 3

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

The following symbols are available for this function:

For config:

  • status-led-config-off = 0
  • status-led-config-on = 1
  • status-led-config-show-heartbeat = 2
  • status-led-config-show-status = 3
tinkerforge call ptc-v2-bricklet <uid> get-chip-temperature
Output:
  • temperature – Type: Int, Unit: 1 °C, Range: [-215 to 215 - 1]

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.

tinkerforge call ptc-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 ptc-v2-bricklet <uid> get-identity
Output:
  • uid – Type: String, Length: up to 8
  • connected-uid – Type: String, Length: up to 8
  • position – Type: Char, Range: [a to h, z]
  • hardware-version – Type: Int Array, Length: 3
    • 0: major – Type: Int, Range: [0 to 255]
    • 1: minor – Type: Int, Range: [0 to 255]
    • 2: revision – Type: Int, Range: [0 to 255]
  • firmware-version – Type: Int Array, Length: 3
    • 0: major – Type: Int, Range: [0 to 255]
    • 1: minor – Type: Int, Range: [0 to 255]
    • 2: revision – Type: Int, Range: [0 to 255]
  • device-identifier – Type: Int, Range: [0 to 216 - 1]

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

Callback Configuration Functions

tinkerforge call ptc-v2-bricklet <uid> set-temperature-callback-configuration <period> <value-has-to-change> <option> <min> <max>
Parameters:
  • <period> – Type: Int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • <value-has-to-change> – Type: Bool, Default: false
  • <option> – Type: Char, Range: See symbols, Default: x
  • <min> – Type: Int, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0
  • <max> – Type: Int, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0
Output:
  • no output

The period 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 following symbols are available for this function:

For <option>:

  • threshold-option-off = x
  • threshold-option-outside = o
  • threshold-option-inside = i
  • threshold-option-smaller = <
  • threshold-option-greater = >
tinkerforge call ptc-v2-bricklet <uid> get-temperature-callback-configuration
Output:
  • period – Type: Int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value-has-to-change – Type: Bool, Default: false
  • option – Type: Char, Range: See symbols, Default: x
  • min – Type: Int, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Int, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0

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

The following symbols are available for this function:

For option:

  • threshold-option-off = x
  • threshold-option-outside = o
  • threshold-option-inside = i
  • threshold-option-smaller = <
  • threshold-option-greater = >
tinkerforge call ptc-v2-bricklet <uid> set-resistance-callback-configuration <period> <value-has-to-change> <option> <min> <max>
Parameters:
  • <period> – Type: Int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • <value-has-to-change> – Type: Bool, Default: false
  • <option> – Type: Char, Range: See symbols, Default: x
  • <min> – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1], Default: 0
  • <max> – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1], Default: 0
Output:
  • no output

The period is the period with which the resistance 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 resistance 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 following symbols are available for this function:

For <option>:

  • threshold-option-off = x
  • threshold-option-outside = o
  • threshold-option-inside = i
  • threshold-option-smaller = <
  • threshold-option-greater = >
tinkerforge call ptc-v2-bricklet <uid> get-resistance-callback-configuration
Output:
  • period – Type: Int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value-has-to-change – Type: Bool, Default: false
  • option – Type: Char, Range: See symbols, Default: x
  • min – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1], Default: 0

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

The following symbols are available for this function:

For option:

  • threshold-option-off = x
  • threshold-option-outside = o
  • threshold-option-inside = i
  • threshold-option-smaller = <
  • threshold-option-greater = >
tinkerforge call ptc-v2-bricklet <uid> set-sensor-connected-callback-configuration <enabled>
Parameters:
  • <enabled> – Type: Bool, Default: false
Output:
  • no output

If you enable this callback, the sensor-connected callback is triggered every time a Pt sensor is connected/disconnected.

tinkerforge call ptc-v2-bricklet <uid> get-sensor-connected-callback-configuration
Output:
  • enabled – Type: Bool, Default: false

Returns the configuration as set by set-sensor-connected-callback-configuration.

Callbacks

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

tinkerforge dispatch ptc-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 ptc-v2-bricklet <uid> temperature
Output:
  • temperature – Type: Int, Unit: 1/100 °C, Range: [-24600 to 84900]

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 ptc-v2-bricklet <uid> resistance
Output:
  • resistance – Type: Int, Unit: ? Ω, Range: [-231 to 231 - 1]

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

The parameter is the same as get-resistance.

tinkerforge dispatch ptc-v2-bricklet <uid> sensor-connected
Output:
  • connected – Type: Bool

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

The parameter is the same as is-sensor-connected.

Internal Functions

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.

tinkerforge call ptc-v2-bricklet <uid> set-bootloader-mode <mode>
Parameters:
  • <mode> – Type: Int, Range: See symbols
Output:
  • status – Type: Int, Range: See 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:

For <mode>:

  • bootloader-mode-bootloader = 0
  • bootloader-mode-firmware = 1
  • bootloader-mode-bootloader-wait-for-reboot = 2
  • bootloader-mode-firmware-wait-for-reboot = 3
  • bootloader-mode-firmware-wait-for-erase-and-reboot = 4

For status:

  • bootloader-status-ok = 0
  • bootloader-status-invalid-mode = 1
  • bootloader-status-no-change = 2
  • bootloader-status-entry-function-not-present = 3
  • bootloader-status-device-identifier-incorrect = 4
  • bootloader-status-crc-mismatch = 5
tinkerforge call ptc-v2-bricklet <uid> get-bootloader-mode
Output:
  • mode – Type: Int, Range: See symbols

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

The following symbols are available for this function:

For mode:

  • bootloader-mode-bootloader = 0
  • bootloader-mode-firmware = 1
  • bootloader-mode-bootloader-wait-for-reboot = 2
  • bootloader-mode-firmware-wait-for-reboot = 3
  • bootloader-mode-firmware-wait-for-erase-and-reboot = 4
tinkerforge call ptc-v2-bricklet <uid> set-write-firmware-pointer <pointer>
Parameters:
  • <pointer> – Type: Int, Unit: 1 B, Range: [0 to 232 - 1]
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 ptc-v2-bricklet <uid> write-firmware <data>
Parameters:
  • <data> – Type: Int Array, Length: 64, Range: [0 to 255]
Output:
  • status – Type: Int, Range: [0 to 255]

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 ptc-v2-bricklet <uid> write-uid <uid>
Parameters:
  • <uid> – Type: Int, Range: [0 to 232 - 1]
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 ptc-v2-bricklet <uid> read-uid
Output:
  • uid – Type: Int, Range: [0 to 232 - 1]

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