This is the description of the Ruby 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 Ruby 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 20 21 22 23 24 25 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_ptc_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your PTC Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
ptc = BrickletPTCV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Get current temperature
temperature = ptc.get_temperature
puts "Temperature: #{temperature/100.0} °C"
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
Download (example_callback.rb)
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 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_ptc_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your PTC Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
ptc = BrickletPTCV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Register temperature callback
ptc.register_callback(BrickletPTCV2::CALLBACK_TEMPERATURE) do |temperature|
puts "Temperature: #{temperature/100.0} °C"
end
# Set period for temperature callback to 1s (1000ms) without a threshold
ptc.set_temperature_callback_configuration 1000, false, 'x', 0, 0
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
Download (example_threshold.rb)
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 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_ptc_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your PTC Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
ptc = BrickletPTCV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Register temperature callback
ptc.register_callback(BrickletPTCV2::CALLBACK_TEMPERATURE) do |temperature|
puts "Temperature: #{temperature/100.0} °C"
end
# Configure threshold for temperature "greater than 30 °C"
# with a debounce period of 1s (1000ms)
ptc.set_temperature_callback_configuration 1000, false, '>', 30*100, 0
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
All methods listed below are thread-safe.
Parameters: |
|
---|
Creates an object with the unique device ID uid:
ptc_v2 = BrickletPTCV2.new 'YOUR_DEVICE_UID', ipcon
This object can then be used after the IP Connection is connected (see examples above).
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 ::CALLBACK_TEMPERATURE callback. You can set the callback configuration with #set_temperature_callback_configuration.
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 ::CALLBACK_RESISTANCE callback. You can set the callback configuration with #set_resistance_callback_configuration.
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 ::CALLBACK_SENSOR_CONNECTED callback. You can set the callback configuration with #set_sensor_connected_callback_configuration.
Parameters: | mode -- int |
---|
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.
The following constants are available for this function:
Returns the wire mode as set by #set_wire_mode
The following constants are available for this function:
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.
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
Returns the moving average configuration as set by #set_moving_average_configuration.
The returned array has the values moving_average_length_resistance and moving_average_length_temperature.
Parameters: | filter -- int |
---|
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.
The following constants are available for this function:
Returns the noise rejection filter option as set by #set_noise_rejection_filter
The following constants are available for this function:
Returns the version of the API definition (major, minor, revision) 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.
Parameters: | function_id -- int |
---|
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 #set_response_expected. 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 send and errors are silently ignored, because they cannot be detected.
See #set_response_expected for the list of function ID constants available for this function.
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 send and errors are silently ignored, because they cannot be detected.
The following function ID constants are available for this function:
Parameters: | response_expected -- bool |
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
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.
The returned array has the values error_count_ack_checksum, error_count_message_checksum, error_count_frame and error_count_overflow.
Parameters: | mode -- int |
---|
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:
Returns the current bootloader mode, see #set_bootloader_mode.
The following constants are available for this function:
Parameters: | pointer -- int |
---|
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.
Parameters: | data -- [int, int, ..61x.., 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.
Parameters: | config -- int |
---|
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:
Returns the configuration as set by #set_status_led_config
The following constants are available for this function:
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.
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!
Parameters: | uid -- int |
---|
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.
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
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. There is also a constant for the device identifier of this Bricklet.
The returned array has the values uid, connected_uid, position, hardware_version, firmware_version and device_identifier.
Parameters: | callback_id -- int |
---|
Registers the given block with the given callback_id.
The available callback IDs with corresponding function signatures are listed below.
Parameters: |
|
---|
The period in ms is the period with which the ::CALLBACK_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 ::CALLBACK_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 constants are available for this function:
Returns the callback configuration as set by #set_temperature_callback_configuration.
The following constants are available for this function:
The returned array has the values period, value_has_to_change, option, min and max.
Parameters: |
|
---|
The period in ms is the period with which the ::CALLBACK_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 ::CALLBACK_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 default value is (0, false, 'x', 0, 0).
The following constants are available for this function:
Returns the callback configuration as set by #set_resistance_callback_configuration.
The following constants are available for this function:
The returned array has the values period, value_has_to_change, option, min and max.
Parameters: | enabled -- bool |
---|
If you enable this callback, the ::CALLBACK_SENSOR_CONNECTED callback is triggered every time a Pt sensor is connected/disconnected.
By default this callback is disabled.
Returns the configuration as set by #set_sensor_connected_callback_configuration.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the #register_callback function of the device object. The first parameter is the callback ID and the second parameter is a block:
ptc_v2.register_callback BrickletPTCV2::CALLBACK_EXAMPLE, do |param|
puts "#{param}"
end
The available constants with inherent number and 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.
Parameters: | 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.
Parameters: | resistance -- int |
---|
This callback is triggered periodically according to the configuration set by #set_resistance_callback_configuration.
The parameter is the same as #get_resistance.
Parameters: | connected -- 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.
This constant is used to identify a PTC Bricklet 2.0.
The #get_identity() function and the ::CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.
This constant represents the human readable name of a PTC Bricklet 2.0.