Delphi/Lazarus - Dual Button Bricklet¶

Callback¶

Download (ExampleCallback.pas)

 1program ExampleCallback;
 2
 3{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
 4{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}
 5
 6uses
 7  SysUtils, IPConnection, BrickletDualButton;
 8
 9type
10  TExample = class
11  private
12    ipcon: TIPConnection;
13    db: TBrickletDualButton;
14  public
15    procedure StateChangedCB(sender: TBrickletDualButton; const buttonL: byte;
16                             const buttonR: byte; const ledL: byte; const ledR: byte);
17    procedure Execute;
18  end;
19
20const
21  HOST = 'localhost';
22  PORT = 4223;
23  UID = 'XYZ'; { Change XYZ to the UID of your Dual Button Bricklet }
24
25var
26  e: TExample;
27
28{ Callback procedure for state changed callback }
29procedure TExample.StateChangedCB(sender: TBrickletDualButton; const buttonL: byte;
30                                  const buttonR: byte; const ledL: byte;
31                                  const ledR: byte);
32begin
33  if (buttonL = BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED) then begin
34    WriteLn('Left Button: Pressed');
35  end
36  else if (buttonL = BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED) then begin
37    WriteLn('Left Button: Released');
38  end;
39
40  if (buttonR = BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED) then begin
41    WriteLn('Right Button: Pressed');
42  end
43  else if (buttonR = BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED) then begin
44    WriteLn('Right Button: Released');
45  end;
46
47  WriteLn('');
48end;
49
50procedure TExample.Execute;
51begin
52  { Create IP connection }
53  ipcon := TIPConnection.Create;
54
55  { Create device object }
56  db := TBrickletDualButton.Create(UID, ipcon);
57
58  { Connect to brickd }
59  ipcon.Connect(HOST, PORT);
60  { Don't use device before ipcon is connected }
61
62  { Register state changed callback to procedure StateChangedCB }
63  db.OnStateChanged := {$ifdef FPC}@{$endif}StateChangedCB;
64
65  WriteLn('Press key to exit');
66  ReadLn;
67  ipcon.Destroy; { Calls ipcon.Disconnect internally }
68end;
69
70begin
71  e := TExample.Create;
72  e.Execute;
73  e.Destroy;
74end.

Basic Functions¶

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

Parameters:	uid – Type: string ipcon – Type: TIPConnection
Returns:	dualButton – Type: TBrickletDualButton

Creates an object with the unique device ID uid:

dualButton := TBrickletDualButton.Create('YOUR_DEVICE_UID', ipcon);

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

procedure TBrickletDualButton.SetLEDState(const ledL: byte; const ledR: byte)¶

Parameters:	ledL – Type: byte, Range: See constants, Default: 1 ledR – Type: byte, Range: See constants, Default: 1

Sets the state of the LEDs. Possible states are:

• 0 = AutoToggleOn: Enables auto toggle with initially enabled LED.

• 1 = AutoToggleOff: Activates auto toggle with initially disabled LED.

• 2 = On: Enables LED (auto toggle is disabled).

• 3 = Off: Disables LED (auto toggle is disabled).

In auto toggle mode the LED is toggled automatically at each press of a button.

If you just want to set one of the LEDs and don't know the current state of the other LED, you can get the state with GetLEDState or you can use SetSelectedLEDState.

The following constants are available for this function:

For ledL:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

For ledR:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

procedure TBrickletDualButton.GetLEDState(out ledL: byte; out ledR: byte)¶

Output Parameters:	ledL – Type: byte, Range: See constants, Default: 1 ledR – Type: byte, Range: See constants, Default: 1

Returns the current state of the LEDs, as set by SetLEDState.

The following constants are available for this function:

For ledL:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

For ledR:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

procedure TBrickletDualButton.GetButtonState(out buttonL: byte; out buttonR: byte)¶

Output Parameters:	buttonL – Type: byte, Range: See constants buttonR – Type: byte, Range: See constants

Returns the current state for both buttons. Possible states are:

• 0 = pressed

• 1 = released

The following constants are available for this function:

For buttonL:

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED = 0

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED = 1

For buttonR:

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED = 0

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED = 1

Advanced Functions¶

procedure TBrickletDualButton.SetSelectedLEDState(const led: byte; const state: byte)¶

Parameters:	led – Type: byte, Range: See constants state – Type: byte, Range: See constants

Sets the state of the selected LED (0 or 1).

The other LED remains untouched.

The following constants are available for this function:

For led:

• BRICKLET_DUAL_BUTTON_LED_LEFT = 0

• BRICKLET_DUAL_BUTTON_LED_RIGHT = 1

For state:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

procedure TBrickletDualButton.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:

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 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', '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¶

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: TBrickletDualButton; const value: longint);
begin
  WriteLn(Format('Value: %d', [value]));
end;

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

The available callback properties and their parameter types are described below.

property TBrickletDualButton.OnStateChanged¶

procedure(sender: TBrickletDualButton; const buttonL: byte; const buttonR: byte; const ledL: byte; const ledR: byte) of object;

Callback Parameters:	sender – Type: TBrickletDualButton buttonL – Type: byte, Range: See constants buttonR – Type: byte, Range: See constants ledL – Type: byte, Range: See constants ledR – Type: byte, Range: See constants

This callback is called whenever a button is pressed.

Possible states for buttons are:

• 0 = pressed

• 1 = released

Possible states for LEDs are:

• 0 = AutoToggleOn: Auto toggle enabled and LED on.

• 1 = AutoToggleOff: Auto toggle enabled and LED off.

• 2 = On: LED on (auto toggle is disabled).

• 3 = Off: LED off (auto toggle is disabled).

The following constants are available for this function:

For buttonL:

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED = 0

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED = 1

For buttonR:

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_PRESSED = 0

• BRICKLET_DUAL_BUTTON_BUTTON_STATE_RELEASED = 1

For ledL:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

For ledR:

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_ON = 0

• BRICKLET_DUAL_BUTTON_LED_STATE_AUTO_TOGGLE_OFF = 1

• BRICKLET_DUAL_BUTTON_LED_STATE_ON = 2

• BRICKLET_DUAL_BUTTON_LED_STATE_OFF = 3

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 TBrickletDualButton.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 TBrickletDualButton.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_DUAL_BUTTON_FUNCTION_SET_LED_STATE = 1

• BRICKLET_DUAL_BUTTON_FUNCTION_SET_SELECTED_LED_STATE = 5

procedure TBrickletDualButton.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.

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_DUAL_BUTTON_FUNCTION_SET_LED_STATE = 1

• BRICKLET_DUAL_BUTTON_FUNCTION_SET_SELECTED_LED_STATE = 5

procedure TBrickletDualButton.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.

Constants¶

const BRICKLET_DUAL_BUTTON_DEVICE_IDENTIFIER¶

This constant is used to identify a Dual Button Bricklet.

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_DUAL_BUTTON_DEVICE_DISPLAY_NAME¶

This constant represents the human readable name of a Dual Button Bricklet.