Mathematica - Thermocouple Bricklet

This is the description of the Mathematica 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 Mathematica API bindings is part of their general description.

Examples

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

Simple

Download (ExampleSimple.nb)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Thermocouple Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
t=NETNew["Tinkerforge.BrickletThermocouple",uid,ipcon]
ipcon@Connect[host,port]

(*Get current temperature*)
Print["Temperature: "<>ToString[N[Quantity[t@GetTemperature[],"°C/100"]]]]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[t]
ReleaseNETObject[ipcon]

Callback

Download (ExampleCallback.nb)

 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
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Thermocouple Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
t=NETNew["Tinkerforge.BrickletThermocouple",uid,ipcon]
ipcon@Connect[host,port]

(*Callback function for temperature callback*)
TemperatureCB[sender_,temperature_]:=
 Print["Temperature: "<>ToString[N[Quantity[temperature,"°C/100"]]]]
AddEventHandler[t@TemperatureCallback,TemperatureCB]

(*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@SetTemperatureCallbackPeriod[1000]

Input["Click OK to exit"]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[t]
ReleaseNETObject[ipcon]

Threshold

Download (ExampleThreshold.nb)

 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
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Thermocouple Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
t=NETNew["Tinkerforge.BrickletThermocouple",uid,ipcon]
ipcon@Connect[host,port]

(*Get threshold callbacks with a debounce time of 10 seconds (10000ms)*)
t@SetDebouncePeriod[10000]

(*Callback function for temperature reached callback*)
TemperatureReachedCB[sender_,temperature_]:=
 Print["Temperature: "<>ToString[N[Quantity[temperature,"°C/100"]]]]
AddEventHandler[t@TemperatureReachedCallback,TemperatureReachedCB]

(*Configure threshold for temperature "greater than 30 °C"*)
option=Tinkerforge`BrickletThermocouple`THRESHOLDUOPTIONUGREATER
t@SetTemperatureCallbackThreshold[option,30*100,0]

Input["Click OK to exit"]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[t]
ReleaseNETObject[ipcon]

API

Generally, every function of the Mathematica bindings that returns a value can throw a Tinkerforge.TimeoutException. This exception gets thrown if the device did not respond. If a cable based connection is used, it is unlikely that this exception gets thrown (assuming nobody plugs the device out). However, if a wireless connection is used, timeouts will occur if the distance to the device gets too big.

Since .NET/Link does not support multiple return values directly, we use the out keyword to return multiple values from a function. For further information about the out keyword in .NET/Link see the corresponding Mathematica .NET/Link documentation.

The namespace for all Brick/Bricklet bindings and the IPConnection is Tinkerforge.*.

Basic Functions

BrickletThermocouple[uid, ipcon] → thermocouple
Parameters:
  • uid – Type: String
  • ipcon – Type: NETObject[IPConnection]
Returns:
  • thermocouple – Type: NETObject[BrickletThermocouple]

Creates an object with the unique device ID uid:

thermocouple=NETNew["Tinkerforge.BrickletThermocouple","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected (see examples above).

The .NET runtime has built-in garbage collection that frees objects that are no longer in use by a program. But because Mathematica can not automatically tell when a Mathematica "program" doesn't use a .NET object anymore, this has to be done by the program. For this the ReleaseNETObject[] function is used in the examples.

For further information about object management in .NET/Link see the corresponding Mathematica .NET/Link documentation.

BrickletThermocouple@GetTemperature[] → temperature
Returns:
  • temperature – Type: Integer, Unit: 1/100 °C, Range: [-21000 to 180000]

Returns the temperature of the thermocouple.

If you want to get the temperature periodically, it is recommended to use the TemperatureCallback callback and set the period with SetTemperatureCallbackPeriod[].

Advanced Functions

BrickletThermocouple@SetConfiguration[averaging, thermocoupleType, filter] → Null
Parameters:
  • averaging – Type: Integer, Range: See constants, Default: 16
  • thermocoupleType – Type: Integer, Range: See constants, Default: 3
  • filter – Type: Integer, Range: See constants, Default: 0

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 following constants are available for this function:

For averaging:

  • BrickletThermocouple`AVERAGINGU1 = 1
  • BrickletThermocouple`AVERAGINGU2 = 2
  • BrickletThermocouple`AVERAGINGU4 = 4
  • BrickletThermocouple`AVERAGINGU8 = 8
  • BrickletThermocouple`AVERAGINGU16 = 16

For thermocoupleType:

  • BrickletThermocouple`TYPEUB = 0
  • BrickletThermocouple`TYPEUE = 1
  • BrickletThermocouple`TYPEUJ = 2
  • BrickletThermocouple`TYPEUK = 3
  • BrickletThermocouple`TYPEUN = 4
  • BrickletThermocouple`TYPEUR = 5
  • BrickletThermocouple`TYPEUS = 6
  • BrickletThermocouple`TYPEUT = 7
  • BrickletThermocouple`TYPEUG8 = 8
  • BrickletThermocouple`TYPEUG32 = 9

For filter:

  • BrickletThermocouple`FILTERUOPTIONU50HZ = 0
  • BrickletThermocouple`FILTERUOPTIONU60HZ = 1
BrickletThermocouple@GetConfiguration[out averaging, out thermocoupleType, out filter] → Null
Output Parameters:
  • averaging – Type: Integer, Range: See constants, Default: 16
  • thermocoupleType – Type: Integer, Range: See constants, Default: 3
  • filter – Type: Integer, Range: See constants, Default: 0

Returns the configuration as set by SetConfiguration[].

The following constants are available for this function:

For averaging:

  • BrickletThermocouple`AVERAGINGU1 = 1
  • BrickletThermocouple`AVERAGINGU2 = 2
  • BrickletThermocouple`AVERAGINGU4 = 4
  • BrickletThermocouple`AVERAGINGU8 = 8
  • BrickletThermocouple`AVERAGINGU16 = 16

For thermocoupleType:

  • BrickletThermocouple`TYPEUB = 0
  • BrickletThermocouple`TYPEUE = 1
  • BrickletThermocouple`TYPEUJ = 2
  • BrickletThermocouple`TYPEUK = 3
  • BrickletThermocouple`TYPEUN = 4
  • BrickletThermocouple`TYPEUR = 5
  • BrickletThermocouple`TYPEUS = 6
  • BrickletThermocouple`TYPEUT = 7
  • BrickletThermocouple`TYPEUG8 = 8
  • BrickletThermocouple`TYPEUG32 = 9

For filter:

  • BrickletThermocouple`FILTERUOPTIONU50HZ = 0
  • BrickletThermocouple`FILTERUOPTIONU60HZ = 1
BrickletThermocouple@GetErrorState[out overUnder, out openCircuit] → Null
Output Parameters:
  • overUnder – Type: True/False
  • openCircuit – Type: True/False

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 ErrorStateCallback callback to automatically get triggered when the error state changes.

BrickletThermocouple@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Output Parameters:
  • uid – Type: String, Length: up to 8
  • connectedUid – Type: String, Length: up to 8
  • position – Type: Integer, Range: [ToCharacterCode["a"][[0]] to ToCharacterCode["h"][[0]], ToCharacterCode["i"][[0]], ToCharacterCode["z"][[0]]]
  • hardwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • firmwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • deviceIdentifier – Type: Integer, 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). The Raspberry Pi HAT (Zero) Brick is always at position 'i' and the Bricklet connected to an Isolator Bricklet is always as position 'z'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions

BrickletThermocouple@SetTemperatureCallbackPeriod[period] → Null
Parameters:
  • period – Type: Integer, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0

Sets the period with which the TemperatureCallback callback is triggered periodically. A value of 0 turns the callback off.

The TemperatureCallback callback is only triggered if the temperature has changed since the last triggering.

BrickletThermocouple@GetTemperatureCallbackPeriod[] → period
Returns:
  • period – Type: Integer, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0

Returns the period as set by SetTemperatureCallbackPeriod[].

BrickletThermocouple@SetTemperatureCallbackThreshold[option, min, max] → Null
Parameters:
  • option – Type: Integer, Range: See constants, Default: ToCharacterCode["x"][[0]]
  • min – Type: Integer, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Integer, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0

Sets the thresholds for the TemperatureReachedCallback 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`THRESHOLDUOPTIONUOFF = ToCharacterCode["x"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUOUTSIDE = ToCharacterCode["o"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUINSIDE = ToCharacterCode["i"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUSMALLER = ToCharacterCode["<"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUGREATER = ToCharacterCode[">"][[0]]
BrickletThermocouple@GetTemperatureCallbackThreshold[out option, out min, out max] → Null
Output Parameters:
  • option – Type: Integer, Range: See constants, Default: ToCharacterCode["x"][[0]]
  • min – Type: Integer, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Integer, Unit: 1/100 °C, Range: [-231 to 231 - 1], Default: 0

Returns the threshold as set by SetTemperatureCallbackThreshold[].

The following constants are available for this function:

For option:

  • BrickletThermocouple`THRESHOLDUOPTIONUOFF = ToCharacterCode["x"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUOUTSIDE = ToCharacterCode["o"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUINSIDE = ToCharacterCode["i"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUSMALLER = ToCharacterCode["<"][[0]]
  • BrickletThermocouple`THRESHOLDUOPTIONUGREATER = ToCharacterCode[">"][[0]]
BrickletThermocouple@SetDebouncePeriod[debounce] → Null
Parameters:
  • debounce – Type: Integer, Unit: 1 ms, Range: [0 to 232 - 1], Default: 100

Sets the period with which the threshold callback

is triggered, if the threshold

keeps being reached.

BrickletThermocouple@GetDebouncePeriod[] → debounce
Returns:
  • debounce – Type: Integer, Unit: 1 ms, Range: [0 to 232 - 1], Default: 100

Returns the debounce period as set by SetDebouncePeriod[].

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a function to a callback property of the device object:

MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]]

AddEventHandler[thermocouple@ExampleCallback,MyCallback]

For further information about event handling using .NET/Link see the corresponding Mathematica .NET/Link documentation.

The available callback property and their 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.

event BrickletThermocouple@TemperatureCallback[sender, temperature]
Callback Parameters:
  • sender – Type: NETObject[BrickletThermocouple]
  • temperature – Type: Integer, Unit: 1/100 °C, Range: [-21000 to 180000]

This callback is triggered periodically with the period that is set by SetTemperatureCallbackPeriod[]. The parameter is the temperature of the thermocouple.

The TemperatureCallback callback is only triggered if the temperature has changed since the last triggering.

event BrickletThermocouple@TemperatureReachedCallback[sender, temperature]
Callback Parameters:
  • sender – Type: NETObject[BrickletThermocouple]
  • temperature – Type: Integer, Unit: 1/100 °C, Range: [-21000 to 180000]

This callback is triggered when the threshold as set by SetTemperatureCallbackThreshold[] 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 SetDebouncePeriod[].

event BrickletThermocouple@ErrorStateCallback[sender, overUnder, openCircuit]
Callback Parameters:
  • sender – Type: NETObject[BrickletThermocouple]
  • overUnder – Type: True/False
  • openCircuit – Type: True/False

This Callback is triggered every time the error state changes (see GetErrorState[]).

Virtual Functions

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@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Output Parameters:
  • apiVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]

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@GetResponseExpected[functionId] → responseExpected
Parameters:
  • functionId – Type: Integer, Range: See constants
Returns:
  • responseExpected – Type: True/False

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 SetResponseExpected[]. 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 functionId:

  • BrickletThermocouple`FUNCTIONUSETUTEMPERATUREUCALLBACKUPERIOD = 2
  • BrickletThermocouple`FUNCTIONUSETUTEMPERATUREUCALLBACKUTHRESHOLD = 4
  • BrickletThermocouple`FUNCTIONUSETUDEBOUNCEUPERIOD = 6
  • BrickletThermocouple`FUNCTIONUSETUCONFIGURATION = 10
BrickletThermocouple@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId – Type: Integer, Range: See constants
  • responseExpected – Type: True/False

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

  • BrickletThermocouple`FUNCTIONUSETUTEMPERATUREUCALLBACKUPERIOD = 2
  • BrickletThermocouple`FUNCTIONUSETUTEMPERATUREUCALLBACKUTHRESHOLD = 4
  • BrickletThermocouple`FUNCTIONUSETUDEBOUNCEUPERIOD = 6
  • BrickletThermocouple`FUNCTIONUSETUCONFIGURATION = 10
BrickletThermocouple@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected – Type: True/False

Changes the response expected flag for all setter and callback configuration functions of this device at once.

Constants

BrickletThermocouple`DEVICEUIDENTIFIER

This constant is used to identify a Thermocouple Bricklet.

The GetIdentity[] function and the IPConnection@EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickletThermocouple`DEVICEDISPLAYNAME

This constant represents the human readable name of a Thermocouple Bricklet.