Mathematica - Dual Button Bricklet 2.0

This is the description of the Mathematica API bindings for the Dual Button Bricklet 2.0. General information and technical specifications for the Dual Button Bricklet 2.0 are summarized in its hardware description.

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

Examples

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

Callback

Download (ExampleCallback.nb)

 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
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Dual Button Bricklet 2.0*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
db=NETNew["Tinkerforge.BrickletDualButtonV2",uid,ipcon]
ipcon@Connect[host,port]

(*Callback function for state changed callback*)
StateChangedCB[sender_,buttonL_,buttonR_,ledL_,ledR_]:=
 Module[{},
  If[buttonL==Tinkerforge`BrickletDualButtonV2`BUTTONUSTATEUPRESSED,Print["Left Button: Pressed"]];
  If[buttonL==Tinkerforge`BrickletDualButtonV2`BUTTONUSTATEURELEASED,Print["Left Button: Released"]];
  If[buttonR==Tinkerforge`BrickletDualButtonV2`BUTTONUSTATEUPRESSED,Print["Right Button: Pressed"]];
  If[buttonR==Tinkerforge`BrickletDualButtonV2`BUTTONUSTATEURELEASED,Print["Right Button: Released"]]
 ]

AddEventHandler[db@StateChangedCallback,StateChangedCB]

(*Enable state changed callback*)
db@SetStateChangedCallbackConfiguration[True]

Input["Click OK to exit"]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[db]
ReleaseNETObject[ipcon]

API

Generally, every function of the Mathematica bindings that returns a value can throw a Tinkerforge.TimeoutException. This exception gets thrown 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.

Since .NET/Link does not support multiple return values directly, we use the out keyword to return multiple values from a function. For further information about the out keyword in .NET/Link see the corresponding Mathematica .NET/Link documentation.

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

Basic Functions

BrickletDualButtonV2[uid, ipcon] → dualButtonV2
Parameters:
  • uid – Type: String
  • ipcon – Type: NETObject[IPConnection]
Returns:
  • dualButtonV2 – Type: NETObject[BrickletDualButtonV2]

Creates an object with the unique device ID uid:

dualButtonV2=NETNew["Tinkerforge.BrickletDualButtonV2","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected (see examples above).

The .NET runtime has built-in garbage collection that frees objects that are no longer in use by a program. But because Mathematica can not automatically tell when a Mathematica "program" doesn't use a .NET object anymore, this has to be done by the program. For this the ReleaseNETObject[] function is used in the examples.

For further information about object management in .NET/Link see the corresponding Mathematica .NET/Link documentation.

BrickletDualButtonV2@SetLEDState[ledL, ledR] → Null
Parameters:
  • ledL – Type: Integer, Range: See constants, Default: 1
  • ledR – Type: Integer, 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:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3

For ledR:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3
BrickletDualButtonV2@GetLEDState[out ledL, out ledR] → Null
Output Parameters:
  • ledL – Type: Integer, Range: See constants, Default: 1
  • ledR – Type: Integer, 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:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3

For ledR:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3
BrickletDualButtonV2@GetButtonState[out buttonL, out buttonR] → Null
Output Parameters:
  • buttonL – Type: Integer, Range: See constants
  • buttonR – Type: Integer, 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:

  • BrickletDualButtonV2`BUTTONUSTATEUPRESSED = 0
  • BrickletDualButtonV2`BUTTONUSTATEURELEASED = 1

For buttonR:

  • BrickletDualButtonV2`BUTTONUSTATEUPRESSED = 0
  • BrickletDualButtonV2`BUTTONUSTATEURELEASED = 1

Advanced Functions

BrickletDualButtonV2@SetSelectedLEDState[led, state] → Null
Parameters:
  • led – Type: Integer, Range: See constants
  • state – Type: Integer, Range: See constants

Sets the state of the selected LED.

The other LED remains untouched.

The following constants are available for this function:

For led:

  • BrickletDualButtonV2`LEDULEFT = 0
  • BrickletDualButtonV2`LEDURIGHT = 1

For state:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3
BrickletDualButtonV2@GetSPITFPErrorCount[out errorCountAckChecksum, out errorCountMessageChecksum, out errorCountFrame, out errorCountOverflow] → Null
Output Parameters:
  • errorCountAckChecksum – Type: Integer, Range: [0 to 232 - 1]
  • errorCountMessageChecksum – Type: Integer, Range: [0 to 232 - 1]
  • errorCountFrame – Type: Integer, Range: [0 to 232 - 1]
  • errorCountOverflow – Type: Integer, 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.

BrickletDualButtonV2@SetBootloaderMode[mode] → status
Parameters:
  • mode – Type: Integer, Range: See constants
Returns:
  • status – Type: Integer, 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:

  • BrickletDualButtonV2`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletDualButtonV2`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4

For status:

  • BrickletDualButtonV2`BOOTLOADERUSTATUSUOK = 0
  • BrickletDualButtonV2`BOOTLOADERUSTATUSUINVALIDUMODE = 1
  • BrickletDualButtonV2`BOOTLOADERUSTATUSUNOUCHANGE = 2
  • BrickletDualButtonV2`BOOTLOADERUSTATUSUENTRYUFUNCTIONUNOTUPRESENT = 3
  • BrickletDualButtonV2`BOOTLOADERUSTATUSUDEVICEUIDENTIFIERUINCORRECT = 4
  • BrickletDualButtonV2`BOOTLOADERUSTATUSUCRCUMISMATCH = 5
BrickletDualButtonV2@GetBootloaderMode[] → mode
Returns:
  • mode – Type: Integer, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode[].

The following constants are available for this function:

For mode:

  • BrickletDualButtonV2`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletDualButtonV2`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletDualButtonV2`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
BrickletDualButtonV2@SetWriteFirmwarePointer[pointer] → Null
Parameters:
  • pointer – Type: Integer, Unit: 1 B, 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.

BrickletDualButtonV2@WriteFirmware[{data1, data2, ..., data64}] → status
Parameters:
  • datai – Type: Integer, Range: [0 to 255]
Returns:
  • status – Type: Integer, 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.

BrickletDualButtonV2@SetStatusLEDConfig[config] → Null
Parameters:
  • config – Type: Integer, 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:

  • BrickletDualButtonV2`STATUSULEDUCONFIGUOFF = 0
  • BrickletDualButtonV2`STATUSULEDUCONFIGUON = 1
  • BrickletDualButtonV2`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDualButtonV2`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletDualButtonV2@GetStatusLEDConfig[] → config
Returns:
  • config – Type: Integer, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig[]

The following constants are available for this function:

For config:

  • BrickletDualButtonV2`STATUSULEDUCONFIGUOFF = 0
  • BrickletDualButtonV2`STATUSULEDUCONFIGUON = 1
  • BrickletDualButtonV2`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDualButtonV2`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletDualButtonV2@GetChipTemperature[] → temperature
Returns:
  • temperature – Type: Integer, Unit: 1 °C, Range: [-215 to 215 - 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.

BrickletDualButtonV2@Reset[] → Null

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!

BrickletDualButtonV2@WriteUID[uid] → Null
Parameters:
  • uid – Type: Integer, 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.

BrickletDualButtonV2@ReadUID[] → uid
Returns:
  • uid – Type: Integer, Range: [0 to 232 - 1]

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

BrickletDualButtonV2@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Output Parameters:
  • uid – Type: String, Length: up to 8
  • connectedUid – Type: String, Length: up to 8
  • position – Type: Integer, Range: [ToCharacterCode["a"][[0]] to ToCharacterCode["h"][[0]], ToCharacterCode["i"][[0]], ToCharacterCode["z"][[0]]]
  • hardwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • firmwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • deviceIdentifier – Type: Integer, 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). The Raspberry Pi HAT (Zero) Brick is always at position 'i' and the Bricklet connected to an Isolator Bricklet is always as 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

BrickletDualButtonV2@SetStateChangedCallbackConfiguration[enabled] → Null
Parameters:
  • enabled – Type: True/False, Default: False

If you enable this callback, the StateChangedCallback callback is triggered every time a button is pressed/released

BrickletDualButtonV2@GetStateChangedCallbackConfiguration[] → enabled
Returns:
  • enabled – Type: True/False, Default: False

Returns the configuration as set by SetStateChangedCallbackConfiguration[].

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:

MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]]

AddEventHandler[dualButtonV2@ExampleCallback,MyCallback]

For further information about event handling using .NET/Link see the corresponding Mathematica .NET/Link documentation.

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 BrickletDualButtonV2@StateChangedCallback[sender, buttonL, buttonR, ledL, ledR]
Callback Parameters:
  • sender – Type: NETObject[BrickletDualButtonV2]
  • buttonL – Type: Integer, Range: See constants
  • buttonR – Type: Integer, Range: See constants
  • ledL – Type: Integer, Range: See constants
  • ledR – Type: Integer, 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).

This callback can be enabled with SetStateChangedCallbackConfiguration[].

The following constants are available for this function:

For buttonL:

  • BrickletDualButtonV2`BUTTONUSTATEUPRESSED = 0
  • BrickletDualButtonV2`BUTTONUSTATEURELEASED = 1

For buttonR:

  • BrickletDualButtonV2`BUTTONUSTATEUPRESSED = 0
  • BrickletDualButtonV2`BUTTONUSTATEURELEASED = 1

For ledL:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 3

For ledR:

  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUON = 0
  • BrickletDualButtonV2`LEDUSTATEUAUTOUTOGGLEUOFF = 1
  • BrickletDualButtonV2`LEDUSTATEUON = 2
  • BrickletDualButtonV2`LEDUSTATEUOFF = 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.

BrickletDualButtonV2@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Output Parameters:
  • apiVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, 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.

BrickletDualButtonV2@GetResponseExpected[functionId] → responseExpected
Parameters:
  • functionId – Type: Integer, Range: See constants
Returns:
  • responseExpected – Type: True/False

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:

  • BrickletDualButtonV2`FUNCTIONUSETULEDUSTATE = 1
  • BrickletDualButtonV2`FUNCTIONUSETUSELECTEDULEDUSTATE = 5
  • BrickletDualButtonV2`FUNCTIONUSETUSTATEUCHANGEDUCALLBACKUCONFIGURATION = 6
  • BrickletDualButtonV2`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletDualButtonV2`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletDualButtonV2`FUNCTIONURESET = 243
  • BrickletDualButtonV2`FUNCTIONUWRITEUUID = 248
BrickletDualButtonV2@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId – Type: Integer, Range: See constants
  • responseExpected – Type: True/False

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:

  • BrickletDualButtonV2`FUNCTIONUSETULEDUSTATE = 1
  • BrickletDualButtonV2`FUNCTIONUSETUSELECTEDULEDUSTATE = 5
  • BrickletDualButtonV2`FUNCTIONUSETUSTATEUCHANGEDUCALLBACKUCONFIGURATION = 6
  • BrickletDualButtonV2`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletDualButtonV2`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletDualButtonV2`FUNCTIONURESET = 243
  • BrickletDualButtonV2`FUNCTIONUWRITEUUID = 248
BrickletDualButtonV2@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected – Type: True/False

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

Constants

BrickletDualButtonV2`DEVICEUIDENTIFIER

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

BrickletDualButtonV2`DEVICEDISPLAYNAME

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