Software / API Bindings / Delphi/Lazarus / API Reference and Examples / Bricklets / Multi Touch Bricklet 2.0

Delphi/Lazarus - Multi Touch Bricklet 2.0¶

This is the description of the Delphi/Lazarus 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 Delphi/Lazarus API bindings is part of their general description.

Examples¶

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

Simple¶

Download (ExampleSimple.pas)

program ExampleSimple;

{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}

uses
  SysUtils, IPConnection, BrickletMultiTouchV2;

type
  TExample = class
  private
    ipcon: TIPConnection;
    mt: TBrickletMultiTouchV2;
  public
    procedure Execute;
  end;

const
  HOST = 'localhost';
  PORT = 4223;
  UID = 'XYZ'; { Change XYZ to the UID of your Multi Touch Bricklet 2.0 }

var
  e: TExample;

procedure TExample.Execute;
var state: TArray0To12OfBoolean;
begin
  { Create IP connection }
  ipcon := TIPConnection.Create;

  { Create device object }
  mt := TBrickletMultiTouchV2.Create(UID, ipcon);

  { Connect to brickd }
  ipcon.Connect(HOST, PORT);
  { Don't use device before ipcon is connected }

  { Get current touch state }
  state := mt.GetTouchState;

  WriteLn(Format('Electrode 0: %d', [state[0]]));
  WriteLn(Format('Electrode 1: %d', [state[1]]));
  WriteLn(Format('Electrode 2: %d', [state[2]]));
  WriteLn(Format('Electrode 3: %d', [state[3]]));
  WriteLn(Format('Electrode 4: %d', [state[4]]));
  WriteLn(Format('Electrode 5: %d', [state[5]]));
  WriteLn(Format('Electrode 6: %d', [state[6]]));
  WriteLn(Format('Electrode 7: %d', [state[7]]));
  WriteLn(Format('Electrode 8: %d', [state[8]]));
  WriteLn(Format('Electrode 9: %d', [state[9]]));
  WriteLn(Format('Electrode 10: %d', [state[10]]));
  WriteLn(Format('Electrode 11: %d', [state[11]]));
  WriteLn(Format('Proximity: %d', [state[12]]));

  WriteLn('Press key to exit');
  ReadLn;
  ipcon.Destroy; { Calls ipcon.Disconnect internally }
end;

begin
  e := TExample.Create;
  e.Execute;
  e.Destroy;
end.

Callback¶

Download (ExampleCallback.pas)

program ExampleCallback;

{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}

uses
  SysUtils, IPConnection, BrickletMultiTouchV2;

type
  TExample = class
  private
    ipcon: TIPConnection;
    mt: TBrickletMultiTouchV2;
  public
    procedure TouchStateCB(sender: TBrickletMultiTouchV2;
                           const state: TArray0To12OfBoolean);
    procedure Execute;
  end;

const
  HOST = 'localhost';
  PORT = 4223;
  UID = 'XYZ'; { Change XYZ to the UID of your Multi Touch Bricklet 2.0 }

var
  e: TExample;

{ Callback procedure for touch state callback }
procedure TExample.TouchStateCB(sender: TBrickletMultiTouchV2;
                                const state: TArray0To12OfBoolean);
begin
  WriteLn(Format('Electrode 0: %d', [state[0]]));
  WriteLn(Format('Electrode 1: %d', [state[1]]));
  WriteLn(Format('Electrode 2: %d', [state[2]]));
  WriteLn(Format('Electrode 3: %d', [state[3]]));
  WriteLn(Format('Electrode 4: %d', [state[4]]));
  WriteLn(Format('Electrode 5: %d', [state[5]]));
  WriteLn(Format('Electrode 6: %d', [state[6]]));
  WriteLn(Format('Electrode 7: %d', [state[7]]));
  WriteLn(Format('Electrode 8: %d', [state[8]]));
  WriteLn(Format('Electrode 9: %d', [state[9]]));
  WriteLn(Format('Electrode 10: %d', [state[10]]));
  WriteLn(Format('Electrode 11: %d', [state[11]]));
  WriteLn(Format('Proximity: %d', [state[12]]));
  WriteLn('');
end;

procedure TExample.Execute;
begin
  { Create IP connection }
  ipcon := TIPConnection.Create;

  { Create device object }
  mt := TBrickletMultiTouchV2.Create(UID, ipcon);

  { Connect to brickd }
  ipcon.Connect(HOST, PORT);
  { Don't use device before ipcon is connected }

  { Register touch state callback to procedure TouchStateCB }
  mt.OnTouchState := {$ifdef FPC}@{$endif}TouchStateCB;

  { Set period for touch state callback to 0.01s (10ms) }
  mt.SetTouchStateCallbackConfiguration(10, true);

  WriteLn('Press key to exit');
  ReadLn;
  ipcon.Destroy; { Calls ipcon.Disconnect internally }
end;

begin
  e := TExample.Create;
  e.Execute;
  e.Destroy;
end.

API¶

Since Delphi does not support multiple return values directly, we use the out keyword to return multiple values from a function.

All functions and procedures listed below are thread-safe.

Basic Functions¶

constructor TBrickletMultiTouchV2.Create(const uid: string; ipcon: TIPConnection)¶

Parameters:	uid – Type: string ipcon – Type: TIPConnection
Returns:	multiTouchV2 – Type: TBrickletMultiTouchV2

Creates an object with the unique device ID uid:

multiTouchV2 := TBrickletMultiTouchV2.Create('YOUR_DEVICE_UID', ipcon);

This object can then be used after the IP Connection is connected.

function TBrickletMultiTouchV2.GetTouchState: array [0..12] of boolean¶

Returns:	state – Type: array [0..12] of boolean

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 OnTouchState callback. You can set the callback configuration with SetTouchStateCallbackConfiguration.

procedure TBrickletMultiTouchV2.Recalibrate¶: Recalibrates the electrodes. Call this function whenever you changed or moved you electrodes.

procedure TBrickletMultiTouchV2.SetElectrodeConfig(const enabledElectrodes: array [0..12] of boolean)¶

Parameters:	enabledElectrodes – Type: array [0..12] of boolean, Default: (true, true, true, true, true, true, true, true, true, true, true, true, true)

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 OnTouchState callback.

Disabling electrodes will also reduce power consumption.

function TBrickletMultiTouchV2.GetElectrodeConfig: array [0..12] of boolean¶

Returns:	enabledElectrodes – Type: array [0..12] of boolean, Default: (true, true, true, true, true, true, true, true, true, true, true, true, true)

Returns the electrode configuration, as set by SetElectrodeConfig.

procedure TBrickletMultiTouchV2.SetElectrodeSensitivity(const sensitivity: byte)¶

Parameters:	sensitivity – Type: byte, Range: [5 to 201], Default: 181

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.

function TBrickletMultiTouchV2.GetElectrodeSensitivity: byte¶

Returns:	sensitivity – Type: byte, Range: [5 to 201], Default: 181

Returns the current sensitivity, as set by SetElectrodeSensitivity.

procedure TBrickletMultiTouchV2.SetTouchLEDConfig(const config: byte)¶

Parameters:	config – Type: byte, Range: See constants, Default: 3

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

For config:

BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_OFF = 0
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_ON = 1
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_SHOW_HEARTBEAT = 2
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_SHOW_TOUCH = 3

function TBrickletMultiTouchV2.GetTouchLEDConfig: byte¶

Returns:	config – Type: byte, Range: See constants, Default: 3

Returns the LED configuration as set by SetTouchLEDConfig

The following constants are available for this function:

For config:

BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_OFF = 0
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_ON = 1
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_SHOW_HEARTBEAT = 2
BRICKLET_MULTI_TOUCH_V2_TOUCH_LED_CONFIG_SHOW_TOUCH = 3

Advanced Functions¶

procedure TBrickletMultiTouchV2.GetSPITFPErrorCount(out errorCountAckChecksum: longword; out errorCountMessageChecksum: longword; out errorCountFrame: longword; out errorCountOverflow: longword)¶

Output Parameters:	errorCountAckChecksum – Type: longword, Range: [0 to 2³² - 1] errorCountMessageChecksum – Type: longword, Range: [0 to 2³² - 1] errorCountFrame – Type: longword, Range: [0 to 2³² - 1] errorCountOverflow – Type: longword, Range: [0 to 2³² - 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.

procedure TBrickletMultiTouchV2.SetStatusLEDConfig(const config: byte)¶

Parameters:	config – Type: byte, Range: See constants, Default: 3

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:

BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_OFF = 0
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_ON = 1
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3

function TBrickletMultiTouchV2.GetStatusLEDConfig: byte¶

Returns:	config – Type: byte, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig

The following constants are available for this function:

For config:

BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_OFF = 0
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_ON = 1
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
BRICKLET_MULTI_TOUCH_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3

function TBrickletMultiTouchV2.GetChipTemperature: smallint¶

Returns:	temperature – Type: smallint, Unit: 1 °C, Range: [-2¹⁵ to 2¹⁵ - 1]

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.

procedure TBrickletMultiTouchV2.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!

procedure TBrickletMultiTouchV2.GetIdentity(out uid: string; out connectedUid: string; out position: char; out hardwareVersion: array [0..2] of byte; out firmwareVersion: array [0..2] of byte; out deviceIdentifier: word)¶

Output Parameters:

Output Parameters:	uid – Type: string, Length: up to 8 connectedUid – Type: string, Length: up to 8 position – Type: char, Range: ['a' to 'h', 'z'] hardwareVersion – Type: array [0..2] of byte 0: major – Type: byte, Range: [0 to 255] 1: minor – Type: byte, Range: [0 to 255] 2: revision – Type: byte, Range: [0 to 255] firmwareVersion – Type: array [0..2] of byte 0: major – Type: byte, Range: [0 to 255] 1: minor – Type: byte, Range: [0 to 255] 2: revision – Type: byte, Range: [0 to 255] deviceIdentifier – Type: word, Range: [0 to 2¹⁶ - 1]

uid – Type: string, Length: up to 8
connectedUid – Type: string, Length: up to 8
position – Type: char, Range: ['a' to 'h', 'z']
hardwareVersion – Type: array [0..2] of byte

0: major – Type: byte, Range: [0 to 255]
1: minor – Type: byte, Range: [0 to 255]
2: revision – Type: byte, Range: [0 to 255]

firmwareVersion – Type: array [0..2] of byte

0: major – Type: byte, Range: [0 to 255]
1: minor – Type: byte, Range: [0 to 255]
2: revision – Type: byte, Range: [0 to 255]

deviceIdentifier – Type: word, Range: [0 to 2¹⁶ - 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', '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.

Callback Configuration Functions¶

procedure TBrickletMultiTouchV2.SetTouchStateCallbackConfiguration(const period: longword; const valueHasToChange: boolean)¶

Parameters:	period – Type: longword, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 valueHasToChange – Type: boolean, Default: false

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

procedure TBrickletMultiTouchV2.GetTouchStateCallbackConfiguration(out period: longword; out valueHasToChange: boolean)¶

Output Parameters:	period – Type: longword, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 valueHasToChange – Type: boolean, Default: false

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 procedure to an callback property of the device object:

procedure TExample.MyCallback(sender: TBrickletMultiTouchV2; const value: longint);
begin
  WriteLn(Format('Value: %d', [value]));
end;

multiTouchV2.OnExample := {$ifdef FPC}@{$endif}example.MyCallback;

The available callback properties and their parameter types 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.

property TBrickletMultiTouchV2.OnTouchState¶

procedure(sender: TBrickletMultiTouchV2; const state: array [0..12] of boolean) of object;

Callback Parameters:	sender – Type: TBrickletMultiTouchV2 state – Type: array [0..12] of boolean

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)

Virtual Functions¶

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.

function TBrickletMultiTouchV2.GetAPIVersion: array [0..2] of byte¶

Output Parameters:	apiVersion – Type: array [0..2] of byte 0: major – Type: byte, Range: [0 to 255] 1: minor – Type: byte, Range: [0 to 255] 2: revision – Type: byte, Range: [0 to 255]

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.

function TBrickletMultiTouchV2.GetResponseExpected(const functionId: byte): boolean¶

Parameters:	functionId – Type: byte, Range: See constants
Returns:	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 sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For functionId:

BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_TOUCH_STATE_CALLBACK_CONFIGURATION = 2
BRICKLET_MULTI_TOUCH_V2_FUNCTION_RECALIBRATE = 5
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_ELECTRODE_CONFIG = 6
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_ELECTRODE_SENSITIVITY = 8
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_TOUCH_LED_CONFIG = 10
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
BRICKLET_MULTI_TOUCH_V2_FUNCTION_RESET = 243
BRICKLET_MULTI_TOUCH_V2_FUNCTION_WRITE_UID = 248

procedure TBrickletMultiTouchV2.SetResponseExpected(const functionId: byte; const responseExpected: boolean)¶

Parameters:	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.

The following constants are available for this function:

For functionId:

BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_TOUCH_STATE_CALLBACK_CONFIGURATION = 2
BRICKLET_MULTI_TOUCH_V2_FUNCTION_RECALIBRATE = 5
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_ELECTRODE_CONFIG = 6
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_ELECTRODE_SENSITIVITY = 8
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_TOUCH_LED_CONFIG = 10
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
BRICKLET_MULTI_TOUCH_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
BRICKLET_MULTI_TOUCH_V2_FUNCTION_RESET = 243
BRICKLET_MULTI_TOUCH_V2_FUNCTION_WRITE_UID = 248

procedure TBrickletMultiTouchV2.SetResponseExpectedAll(const responseExpected: boolean)¶

Parameters:	responseExpected – Type: boolean

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

Internal Functions¶

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.

function TBrickletMultiTouchV2.SetBootloaderMode(const mode: byte): byte¶

Parameters:	mode – Type: byte, Range: See constants
Returns:	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:

BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_BOOTLOADER = 0
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE = 1
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_OK = 0
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_INVALID_MODE = 1
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_NO_CHANGE = 2
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_STATUS_CRC_MISMATCH = 5

function TBrickletMultiTouchV2.GetBootloaderMode: byte¶

Returns:	mode – Type: byte, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode.

The following constants are available for this function:

For mode:

BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_BOOTLOADER = 0
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE = 1
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
BRICKLET_MULTI_TOUCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

procedure TBrickletMultiTouchV2.SetWriteFirmwarePointer(const pointer: longword)¶

Parameters:	pointer – Type: longword, Unit: 1 B, Range: [0 to 2³² - 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.

function TBrickletMultiTouchV2.WriteFirmware(const data: array [0..63] of byte): byte¶

Parameters:	data – Type: array [0..63] of byte, Range: [0 to 255]
Returns:	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.

procedure TBrickletMultiTouchV2.WriteUID(const uid: longword)¶

Parameters:	uid – Type: longword, Range: [0 to 2³² - 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.

function TBrickletMultiTouchV2.ReadUID: longword¶

Returns:	uid – Type: longword, Range: [0 to 2³² - 1]

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

Constants¶

const BRICKLET_MULTI_TOUCH_V2_DEVICE_IDENTIFIER¶

This constant is used to identify a Multi Touch Bricklet 2.0.

The GetIdentity function and the TIPConnection.OnEnumerate callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

const BRICKLET_MULTI_TOUCH_V2_DEVICE_DISPLAY_NAME¶: This constant represents the human readable name of a Multi Touch Bricklet 2.0.