This is the description of the Ruby API bindings for the Multi Touch Bricklet. General information and technical specifications for the Multi Touch Bricklet 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 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_multi_touch'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Multi Touch Bricklet
ipcon = IPConnection.new # Create IP connection
mt = BrickletMultiTouch.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Get current touch state
state = mt.get_touch_state
s = ''
if (state & (1 << 12)) == (1 << 12)
s += 'In proximity, '
end
if (state & 0xfff) == 0
s += 'No electrodes touched'
else
s += 'Electrodes '
for i in 0..11
if (state & (1 << i)) == (1 << i)
s += i.to_s() + ' '
end
end
s += 'touched'
end
puts s
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 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_multi_touch'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Multi Touch Bricklet
ipcon = IPConnection.new # Create IP connection
mt = BrickletMultiTouch.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Register touch state callback
mt.register_callback(BrickletMultiTouch::CALLBACK_TOUCH_STATE) do |state|
s = ''
if (state & (1 << 12)) == (1 << 12)
s += 'In proximity, '
end
if (state & 0xfff) == 0
s += 'No electrodes touched'
else
s += 'Electrodes '
for i in 0..11
if (state & (1 << i)) == (1 << i)
s += i.to_s() + ' '
end
end
s += 'touched'
end
puts s
end
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
All functions listed below are thread-safe.
BrickletMultiTouch
::
new
(uid, ipcon) → multi_touch¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
multi_touch = BrickletMultiTouch.new 'YOUR_DEVICE_UID', ipcon
This object can then be used after the IP Connection is connected.
BrickletMultiTouch
#
get_touch_state
→ int¶Returns: |
|
---|
Returns the current touch state. The state is given as a bitfield.
Bits 0 to 11 represent the 12 electrodes and bit 12 represents the proximity.
If an electrode is touched, the corresponding bit is true. If a hand or similar is in proximity to the electrodes, bit 12 is true.
Example: The state 4103 = 0x1007 = 0b1000000000111 means that electrodes 0, 1 and 2 are touched and that something is in the proximity of the electrodes.
The proximity is activated with a distance of 1-2cm. An electrode is already counted as touched if a finger is nearly touching the electrode. This means that you can put a piece of paper or foil or similar on top of a electrode to build a touch panel with a professional look.
BrickletMultiTouch
#
recalibrate
→ nil¶Recalibrates the electrodes. Call this function whenever you changed or moved you electrodes.
BrickletMultiTouch
#
set_electrode_config
(enabled_electrodes) → nil¶Parameters: |
|
---|
Enables/disables electrodes with a bitfield (see #get_touch_state
).
True enables the electrode, false disables the electrode. A disabled electrode will always return false as its state. If you don't need all electrodes you can disable the electrodes that are not needed.
It is recommended that you disable the proximity bit (bit 12) if
the proximity feature is not needed. This will reduce the amount of
traffic that is produced by the ::CALLBACK_TOUCH_STATE
callback.
Disabling electrodes will also reduce power consumption.
Default: 8191 = 0x1FFF = 0b1111111111111 (all electrodes and proximity feature enabled)
BrickletMultiTouch
#
get_electrode_config
→ int¶Returns: |
|
---|
Returns the electrode configuration, as set by #set_electrode_config
.
BrickletMultiTouch
#
set_electrode_sensitivity
(sensitivity) → nil¶Parameters: |
|
---|
Sets the sensitivity of the electrodes. An electrode with a high sensitivity will register a touch earlier then an electrode with a low sensitivity.
If you build a big electrode you might need to decrease the sensitivity, since the area that can be charged will get bigger. If you want to be able to activate an electrode from further away you need to increase the sensitivity.
After a new sensitivity is set, you likely want to call #recalibrate
to calibrate the electrodes with the newly defined sensitivity.
BrickletMultiTouch
#
get_electrode_sensitivity
→ int¶Returns: |
|
---|
Returns the current sensitivity, as set by #set_electrode_sensitivity
.
BrickletMultiTouch
#
get_identity
→ [str, str, chr, [int, ...], [int, ...], int]¶Return Array: |
|
---|
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.
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:
multi_touch.register_callback BrickletMultiTouch::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.
BrickletMultiTouch
::
CALLBACK_TOUCH_STATE
¶Callback Parameters: |
|
---|
Returns the current touch state, see #get_touch_state
for
information about the state.
This callback is triggered every time the touch state changes.
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.
BrickletMultiTouch
#
get_api_version
→ [int, ...]¶Return Array: |
|
---|
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.
BrickletMultiTouch
#
get_response_expected
(function_id) → bool¶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
#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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletMultiTouch
#
set_response_expected
(function_id, response_expected) → nil¶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 function_id:
BrickletMultiTouch
#
set_response_expected_all
(response_expected) → nil¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletMultiTouch
::
DEVICE_IDENTIFIER
¶This constant is used to identify a Multi Touch Bricklet.
The #get_identity()
function and the
IPConnection::CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletMultiTouch
::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Multi Touch Bricklet.