This is the description of the Mathematica 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 Mathematica 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 | Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]
host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your PTC Bricklet 2.0*)
(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
ptc=NETNew["Tinkerforge.BrickletPTCV2",uid,ipcon]
ipcon@Connect[host,port]
(*Get current temperature*)
Print["Temperature: "<>ToString[N[Quantity[ptc@GetTemperature[],"°C/100"]]]]
(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[ptc]
ReleaseNETObject[ipcon]
|
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 | Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]
host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your PTC Bricklet 2.0*)
(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
ptc=NETNew["Tinkerforge.BrickletPTCV2",uid,ipcon]
ipcon@Connect[host,port]
(*Callback function for temperature callback*)
TemperatureCB[sender_,temperature_]:=
Print["Temperature: "<>ToString[N[Quantity[temperature,"°C/100"]]]]
AddEventHandler[ptc@TemperatureCallback,TemperatureCB]
(*Set period for temperature callback to 1s (1000ms) without a threshold*)
option=Tinkerforge`BrickletPTCV2`THRESHOLDUOPTIONUOFF
ptc@SetTemperatureCallbackConfiguration[1000,False,option,0,0]
Input["Click OK to exit"]
(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[ptc]
ReleaseNETObject[ipcon]
|
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 | Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]
host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your PTC Bricklet 2.0*)
(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
ptc=NETNew["Tinkerforge.BrickletPTCV2",uid,ipcon]
ipcon@Connect[host,port]
(*Callback function for temperature callback*)
TemperatureCB[sender_,temperature_]:=
Print["Temperature: "<>ToString[N[Quantity[temperature,"°C/100"]]]]
AddEventHandler[ptc@TemperatureCallback,TemperatureCB]
(*Configure threshold for temperature "greater than 30 °C"*)
(*with a debounce period of 1s (1000ms)*)
option=Tinkerforge`BrickletPTCV2`THRESHOLDUOPTIONUGREATER
ptc@SetTemperatureCallbackConfiguration[1000,False,option,30*100,0]
Input["Click OK to exit"]
(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[ptc]
ReleaseNETObject[ipcon]
|
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.*
.
BrickletPTCV2
[uid, ipcon] → ptcV2¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
ptcV2=NETNew["Tinkerforge.BrickletPTCV2","YOUR_DEVICE_UID",ipcon]
This object can then be used after the IP Connection is connected.
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.
BrickletPTCV2
@
GetTemperature
[] → temperature¶Returns: |
|
---|
Returns the temperature of the connected sensor.
If you want to get the value periodically, it is recommended to use the
TemperatureCallback
callback. You can set the callback configuration
with SetTemperatureCallbackConfiguration[]
.
BrickletPTCV2
@
GetResistance
[] → resistance¶Returns: |
|
---|
Returns the value as measured by the MAX31865 precision delta-sigma ADC.
The value can be converted with the following formulas:
If you want to get the value periodically, it is recommended to use the
ResistanceCallback
callback. You can set the callback configuration
with SetResistanceCallbackConfiguration[]
.
BrickletPTCV2
@
IsSensorConnected
[] → connected¶Returns: |
|
---|
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
SensorConnectedCallback
callback. You can set the callback configuration
with SetSensorConnectedCallbackConfiguration[]
.
BrickletPTCV2
@
SetWireMode
[mode] → Null¶Parameters: |
|
---|
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 constants are available for this function:
For mode:
BrickletPTCV2
@
GetWireMode
[] → mode¶Returns: |
|
---|
Returns the wire mode as set by SetWireMode[]
The following constants are available for this function:
For mode:
BrickletPTCV2
@
SetMovingAverageConfiguration
[movingAverageLengthResistance, movingAverageLengthTemperature] → Null¶Parameters: |
|
---|
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
BrickletPTCV2
@
GetMovingAverageConfiguration
[out movingAverageLengthResistance, out movingAverageLengthTemperature] → Null¶Output Parameters: |
|
---|
Returns the moving average configuration as set by SetMovingAverageConfiguration[]
.
BrickletPTCV2
@
SetNoiseRejectionFilter
[filter] → Null¶Parameters: |
|
---|
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 constants are available for this function:
For filter:
BrickletPTCV2
@
GetNoiseRejectionFilter
[] → filter¶Returns: |
|
---|
Returns the noise rejection filter option as set by
SetNoiseRejectionFilter[]
The following constants are available for this function:
For filter:
BrickletPTCV2
@
GetSPITFPErrorCount
[out errorCountAckChecksum, out errorCountMessageChecksum, out errorCountFrame, out errorCountOverflow] → Null¶Output Parameters: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
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.
BrickletPTCV2
@
SetStatusLEDConfig
[config] → Null¶Parameters: |
|
---|
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 constants are available for this function:
For config:
BrickletPTCV2
@
GetStatusLEDConfig
[] → config¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig[]
The following constants are available for this function:
For config:
BrickletPTCV2
@
GetChipTemperature
[] → temperature¶Returns: |
|
---|
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.
BrickletPTCV2
@
Reset
[] → Null¶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!
BrickletPTCV2
@
GetIdentity
[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null¶Output Parameters: |
|
---|
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.
BrickletPTCV2
@
SetTemperatureCallbackConfiguration
[period, valueHasToChange, option, min, max] → Null¶Parameters: |
|
---|
The period is the period with which the TemperatureCallback
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 TemperatureCallback
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 constants are available for this function:
For option:
BrickletPTCV2
@
GetTemperatureCallbackConfiguration
[out period, out valueHasToChange, out option, out min, out max] → Null¶Output Parameters: |
|
---|
Returns the callback configuration as set by SetTemperatureCallbackConfiguration[]
.
The following constants are available for this function:
For option:
BrickletPTCV2
@
SetResistanceCallbackConfiguration
[period, valueHasToChange, option, min, max] → Null¶Parameters: |
|
---|
The period is the period with which the ResistanceCallback
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 ResistanceCallback
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 constants are available for this function:
For option:
BrickletPTCV2
@
GetResistanceCallbackConfiguration
[out period, out valueHasToChange, out option, out min, out max] → Null¶Output Parameters: |
|
---|
Returns the callback configuration as set by SetResistanceCallbackConfiguration[]
.
The following constants are available for this function:
For option:
BrickletPTCV2
@
SetSensorConnectedCallbackConfiguration
[enabled] → Null¶Parameters: |
|
---|
If you enable this callback, the SensorConnectedCallback
callback is triggered
every time a Pt sensor is connected/disconnected.
BrickletPTCV2
@
GetSensorConnectedCallbackConfiguration
[] → enabled¶Returns: |
|
---|
Returns the configuration as set by SetSensorConnectedCallbackConfiguration[]
.
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[ptcV2@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.
BrickletPTCV2
@
TemperatureCallback
[sender, temperature]¶Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
SetTemperatureCallbackConfiguration[]
.
The parameter is the same as GetTemperature[]
.
BrickletPTCV2
@
ResistanceCallback
[sender, resistance]¶Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
SetResistanceCallbackConfiguration[]
.
The parameter is the same as GetResistance[]
.
BrickletPTCV2
@
SensorConnectedCallback
[sender, connected]¶Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
SetSensorConnectedCallbackConfiguration[]
.
The parameter is the same as IsSensorConnected[]
.
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.
BrickletPTCV2
@
GetAPIVersion
[] → {apiVersion1, apiVersion2, apiVersion3}¶Output Parameters: |
|
---|
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.
BrickletPTCV2
@
GetResponseExpected
[functionId] → responseExpected¶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
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:
BrickletPTCV2
@
SetResponseExpected
[functionId, responseExpected] → Null¶Parameters: |
|
---|
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:
BrickletPTCV2
@
SetResponseExpectedAll
[responseExpected] → Null¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
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.
BrickletPTCV2
@
SetBootloaderMode
[mode] → status¶Parameters: |
|
---|---|
Returns: |
|
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 constants are available for this function:
For mode:
For status:
BrickletPTCV2
@
GetBootloaderMode
[] → mode¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode[]
.
The following constants are available for this function:
For mode:
BrickletPTCV2
@
SetWriteFirmwarePointer
[pointer] → Null¶Parameters: |
|
---|
Sets the firmware pointer for WriteFirmware[]
. 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.
BrickletPTCV2
@
WriteFirmware
[{data1, data2, ..., data64}] → status¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
SetWriteFirmwarePointer[]
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.
BrickletPTCV2
@
WriteUID
[uid] → Null¶Parameters: |
|
---|
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.
BrickletPTCV2
@
ReadUID
[] → uid¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletPTCV2
`
DEVICEUIDENTIFIER
¶This constant is used to identify a PTC Bricklet 2.0.
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.
BrickletPTCV2
`
DEVICEDISPLAYNAME
¶This constant represents the human readable name of a PTC Bricklet 2.0.