NAME
Tinkerforge::BrickletPTCV2 - Reads temperatures from Pt100 und Pt1000 sensors
CONSTANTS
- DEVICE_IDENTIFIER
-
This constant is used to identify a PTC Bricklet 2.0.
The get_identity() subroutine and the CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.
- DEVICE_DISPLAY_NAME
-
This constant represents the display name of a PTC Bricklet 2.0.
- CALLBACK_TEMPERATURE
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_TEMPERATURE callback.
- CALLBACK_RESISTANCE
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_RESISTANCE callback.
- CALLBACK_SENSOR_CONNECTED
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_SENSOR_CONNECTED callback.
- FUNCTION_GET_TEMPERATURE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_TEMPERATURE_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_TEMPERATURE_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_RESISTANCE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_RESISTANCE_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_RESISTANCE_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_NOISE_REJECTION_FILTER
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_NOISE_REJECTION_FILTER
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_IS_SENSOR_CONNECTED
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_WIRE_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_WIRE_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_MOVING_AVERAGE_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_MOVING_AVERAGE_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_SENSOR_CONNECTED_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_SENSOR_CONNECTED_CALLBACK_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_SPITFP_ERROR_COUNT
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_BOOTLOADER_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_BOOTLOADER_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_WRITE_FIRMWARE_POINTER
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_WRITE_FIRMWARE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_STATUS_LED_CONFIG
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_STATUS_LED_CONFIG
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_CHIP_TEMPERATURE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_RESET
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_WRITE_UID
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_READ_UID
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_IDENTITY
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
FUNCTIONS
- new()
-
Creates an object with the unique device ID *uid* and adds it to the IP Connection *ipcon*.
- get_temperature()
-
Returns the temperature of the connected sensor. The value has a range of -246 to 849 °C and 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 value periodically, it is recommended to use the :cb:`Temperature` callback. You can set the callback configuration with :func:`Set Temperature Callback Configuration`.
- set_temperature_callback_configuration()
-
The period in ms is the period with which the :cb:`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 :cb:`Temperature` callback.
The following options are possible:
.. csv-table:: :header: "Option", "Description" :widths: 10, 100
"'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).
- get_temperature_callback_configuration()
-
Returns the callback configuration as set by :func:`Set Temperature Callback Configuration`.
- get_resistance()
-
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 :cb:`Resistance` callback. You can set the callback configuration with :func:`Set Resistance Callback Configuration`.
- set_resistance_callback_configuration()
-
The period in ms is the period with which the :cb:`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 :cb:`Resistance` callback.
The following options are possible:
.. csv-table:: :header: "Option", "Description" :widths: 10, 100
"'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).
- get_resistance_callback_configuration()
-
Returns the callback configuration as set by :func:`Set Resistance Callback Configuration`.
- set_noise_rejection_filter()
-
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.
Default value is 0 = 50Hz.
- get_noise_rejection_filter()
-
Returns the noise rejection filter option as set by :func:`Set Noise Rejection Filter`
- is_sensor_connected()
-
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 :cb:`Sensor Connected` callback. You can set the callback configuration with :func:`Set Sensor Connected Callback Configuration`.
- set_wire_mode()
-
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 default value is 2 = 2-wire.
- get_wire_mode()
-
Returns the wire mode as set by :func:`Set Wire Mode`
- set_moving_average_configuration()
-
Sets the length of a `moving averaging <https://en.wikipedia.org/wiki/Moving_average>`__ 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.
The range for the averaging is 1-1000.
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 value is 1 for resistance and 40 for temperature. The default values match the non-changeable averaging settings of the old PTC Bricklet 1.0
- get_moving_average_configuration()
-
Returns the moving average configuration as set by :func:`Set Moving Average Configuration`.
- set_sensor_connected_callback_configuration()
-
If you enable this callback, the :cb:`Sensor Connected` callback is triggered every time a Pt sensor is connected/disconnected.
By default this callback is disabled.
- get_sensor_connected_callback_configuration()
-
Returns the configuration as set by :func:`Set Sensor Connected Callback Configuration`.
- get_spitfp_error_count()
-
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
* ack checksum errors, * message checksum errors, * frameing 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.
- set_bootloader_mode()
-
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 und 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.
- get_bootloader_mode()
-
Returns the current bootloader mode, see :func:`Set Bootloader Mode`.
- set_write_firmware_pointer()
-
Sets the firmware pointer for :func:`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.
- write_firmware()
-
Writes 64 Bytes of firmware at the position as written by :func:`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.
- set_status_led_config()
-
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.
- get_status_led_config()
-
Returns the configuration as set by :func:`Set Status LED Config`
- get_chip_temperature()
-
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.
- reset()
-
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!
- write_uid()
-
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.
- read_uid()
-
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
- get_identity()
-
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 :ref:`here <device_identifier>`. |device_identifier_constant|