LabVIEW - Multi Touch Bricklet 2.0

This is the description of the LabVIEW API bindings for the Multi Touch Bricklet 2.0. General information and technical specifications for the Multi Touch Bricklet 2.0 are summarized in its hardware description.

An installation guide for the LabVIEW API bindings is part of their general description.

Examples

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

API

Generally, every method of the LabVIEW bindings that outputs a value can report a Tinkerforge.TimeoutException. This error gets reported 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.

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

Basic Functions

BrickletMultiTouchV2(uid, ipcon) → multiTouchV2
Input:
  • uid – Type: String
  • ipcon – Type: .NET Refnum (IPConnection)
Output:
  • multiTouchV2 – Type: .NET Refnum (BrickletMultiTouchV2)

Creates an object with the unique device ID uid. This object can then be used after the IP Connection is connected (see examples above).

BrickletMultiTouchV2.GetTouchState() → state
Output:
  • state – Type: Boolean[13]

Returns the current touch state. The state is given as a array of bools.

Element 0 to 11 represent the 12 electrodes and element 12 represents the proximity.

If an electrode is touched, the corresponding element is true. If a hand or similar is in proximity to the electrodes, element 12 is true.

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.

If you want to get the value periodically, it is recommended to use the TouchStateCallback callback. You can set the callback configuration with SetTouchStateCallbackConfiguration().

BrickletMultiTouchV2.Recalibrate()

Recalibrates the electrodes. Call this function whenever you changed or moved you electrodes.

BrickletMultiTouchV2.SetElectrodeConfig(enabledElectrodes)
Input:
  • enabledElectrodes – Type: Boolean[13]

Enables/disables electrodes with a bool array (see GetTouchState()).

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 electrode (element 12) if the proximity feature is not needed. This will reduce the amount of traffic that is produced by the TouchStateCallback callback.

Disabling electrodes will also reduce power consumption.

Default: All electrodes enabled.

BrickletMultiTouchV2.GetElectrodeConfig() → enabledElectrodes
Output:
  • enabledElectrodes – Type: Boolean[13]

Returns the electrode configuration, as set by SetElectrodeConfig().

BrickletMultiTouchV2.SetElectrodeSensitivity(sensitivity)
Input:
  • sensitivity – Type: Byte, Range: [0 to 255]

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.

The valid sensitivity value range is 5-201.

The default sensitivity value is 181.

BrickletMultiTouchV2.GetElectrodeSensitivity() → sensitivity
Output:
  • sensitivity – Type: Byte, Range: [0 to 255]

Returns the current sensitivity, as set by SetElectrodeSensitivity().

BrickletMultiTouchV2.SetTouchLEDConfig(config)
Input:
  • config – Type: Byte, Range: See constants

Configures the touch LED to be either turned off, turned on, blink in heartbeat mode or show the touch state (electrode touched = LED on).

The default value is 3 (show touch state).

The following constants are available for this function:

For config:

  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_OFF = 0
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_ON = 1
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_SHOW_TOUCH = 3
BrickletMultiTouchV2.GetTouchLEDConfig() → config
Output:
  • config – Type: Byte, Range: See constants

Returns the LED configuration as set by SetTouchLEDConfig()

The following constants are available for this function:

For config:

  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_OFF = 0
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_ON = 1
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletMultiTouchV2.TOUCH_LED_CONFIG_SHOW_TOUCH = 3

Advanced Functions

BrickletMultiTouchV2.GetAPIVersion() → apiVersion
Output:
  • apiVersion – Type: Byte[3], Range: [0 to 255]

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.

BrickletMultiTouchV2.GetResponseExpected(functionId) → responseExpected
Input:
  • functionId – Type: Byte, Range: See constants
Output:
  • responseExpected – Type: Boolean

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 send and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For functionId:

  • BrickletMultiTouchV2.FUNCTION_SET_TOUCH_STATE_CALLBACK_CONFIGURATION = 2
  • BrickletMultiTouchV2.FUNCTION_RECALIBRATE = 5
  • BrickletMultiTouchV2.FUNCTION_SET_ELECTRODE_CONFIG = 6
  • BrickletMultiTouchV2.FUNCTION_SET_ELECTRODE_SENSITIVITY = 8
  • BrickletMultiTouchV2.FUNCTION_SET_TOUCH_LED_CONFIG = 10
  • BrickletMultiTouchV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletMultiTouchV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletMultiTouchV2.FUNCTION_RESET = 243
  • BrickletMultiTouchV2.FUNCTION_WRITE_UID = 248
BrickletMultiTouchV2.SetResponseExpected(functionId, responseExpected)
Input:
  • functionId – Type: Byte, Range: See constants
  • responseExpected – Type: Boolean

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

For functionId:

  • BrickletMultiTouchV2.FUNCTION_SET_TOUCH_STATE_CALLBACK_CONFIGURATION = 2
  • BrickletMultiTouchV2.FUNCTION_RECALIBRATE = 5
  • BrickletMultiTouchV2.FUNCTION_SET_ELECTRODE_CONFIG = 6
  • BrickletMultiTouchV2.FUNCTION_SET_ELECTRODE_SENSITIVITY = 8
  • BrickletMultiTouchV2.FUNCTION_SET_TOUCH_LED_CONFIG = 10
  • BrickletMultiTouchV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletMultiTouchV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletMultiTouchV2.FUNCTION_RESET = 243
  • BrickletMultiTouchV2.FUNCTION_WRITE_UID = 248
BrickletMultiTouchV2.SetResponseExpectedAll(responseExpected)
Input:
  • responseExpected – Type: Boolean

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

BrickletMultiTouchV2.GetSPITFPErrorCount() → errorCountAckChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow
Output:
  • errorCountAckChecksum – Type: Int64, Range: [0 to 232 - 1]
  • errorCountMessageChecksum – Type: Int64, Range: [0 to 232 - 1]
  • errorCountFrame – Type: Int64, Range: [0 to 232 - 1]
  • errorCountOverflow – Type: Int64, Range: [0 to 232 - 1]

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing 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.

BrickletMultiTouchV2.SetBootloaderMode(mode) → status
Input:
  • mode – Type: Byte, Range: See constants
Output:
  • status – Type: Byte, Range: See constants

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:

  • BrickletMultiTouchV2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletMultiTouchV2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

  • BrickletMultiTouchV2.BOOTLOADER_STATUS_OK = 0
  • BrickletMultiTouchV2.BOOTLOADER_STATUS_INVALID_MODE = 1
  • BrickletMultiTouchV2.BOOTLOADER_STATUS_NO_CHANGE = 2
  • BrickletMultiTouchV2.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BrickletMultiTouchV2.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BrickletMultiTouchV2.BOOTLOADER_STATUS_CRC_MISMATCH = 5
BrickletMultiTouchV2.GetBootloaderMode() → mode
Output:
  • mode – Type: Byte, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode().

The following constants are available for this function:

For mode:

  • BrickletMultiTouchV2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletMultiTouchV2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletMultiTouchV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
BrickletMultiTouchV2.SetWriteFirmwarePointer(pointer)
Input:
  • pointer – Type: Int64, Range: [0 to 232 - 1]

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.

BrickletMultiTouchV2.WriteFirmware(data) → status
Input:
  • data – Type: Byte[64], Range: [0 to 255]
Output:
  • status – Type: Byte, Range: [0 to 255]

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.

BrickletMultiTouchV2.SetStatusLEDConfig(config)
Input:
  • config – Type: Byte, Range: See constants

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:

  • BrickletMultiTouchV2.STATUS_LED_CONFIG_OFF = 0
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_ON = 1
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletMultiTouchV2.GetStatusLEDConfig() → config
Output:
  • config – Type: Byte, Range: See constants

Returns the configuration as set by SetStatusLEDConfig()

The following constants are available for this function:

For config:

  • BrickletMultiTouchV2.STATUS_LED_CONFIG_OFF = 0
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_ON = 1
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletMultiTouchV2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletMultiTouchV2.GetChipTemperature() → temperature
Output:
  • temperature – Type: Int16, Range: [-215 to 215 - 1]

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.

BrickletMultiTouchV2.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!

BrickletMultiTouchV2.WriteUID(uid)
Input:
  • uid – Type: Int64, Range: [0 to 232 - 1]

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.

BrickletMultiTouchV2.ReadUID() → uid
Output:
  • uid – Type: Int64, Range: [0 to 232 - 1]

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

BrickletMultiTouchV2.GetIdentity() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier
Output:
  • uid – Type: String, Length: up to 8
  • connectedUid – Type: String, Length: up to 8
  • position – Type: Char
  • hardwareVersion – Type: Byte[3], Range: [0 to 255]
  • firmwareVersion – Type: Byte[3], Range: [0 to 255]
  • deviceIdentifier – Type: Int32, 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' or 'd'.

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

Callback Configuration Functions

BrickletMultiTouchV2.SetTouchStateCallbackConfiguration(period, valueHasToChange)
Input:
  • period – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • valueHasToChange – Type: Boolean, Default: F

The period is the period with which the TouchStateCallback 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.

BrickletMultiTouchV2.GetTouchStateCallbackConfiguration() → period, valueHasToChange
Output:
  • period – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • valueHasToChange – Type: Boolean, Default: F

Returns the callback configuration as set by SetTouchStateCallbackConfiguration().

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. 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 BrickletMultiTouchV2.TouchStateCallback → sender, state
Callback Output:
  • sender – Type: .NET Refnum (BrickletMultiTouchV2)
  • state – Type: Boolean[13]

Returns the current touch state, see GetTouchState() for information about the state.

This callback is triggered every time the touch state changes with a given period (see SetTouchStateCallbackConfiguration())

Constants

BrickletMultiTouchV2.DEVICE_IDENTIFIER

This constant is used to identify a Multi Touch 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.

BrickletMultiTouchV2.DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Multi Touch Bricklet 2.0.