Visual Basic .NET - Dual Button Bricklet 2.0¶

Callback¶

Download (ExampleCallback.vb)

 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

Imports System
Imports Tinkerforge

Module ExampleCallback
    Const HOST As String = "localhost"
    Const PORT As Integer = 4223
    Const UID As String = "XYZ" ' Change XYZ to the UID of your Dual Button Bricklet 2.0

    ' Callback subroutine for state changed callback
    Sub StateChangedCB(ByVal sender As BrickletDualButtonV2, ByVal buttonL As Byte, _
                       ByVal buttonR As Byte, ByVal ledL As Byte, ByVal ledR As Byte)
        If buttonL = BrickletDualButtonV2.BUTTON_STATE_PRESSED Then
            Console.WriteLine("Left Button: Pressed")
        Else If buttonL = BrickletDualButtonV2.BUTTON_STATE_RELEASED Then
            Console.WriteLine("Left Button: Released")
        End If

        If buttonR = BrickletDualButtonV2.BUTTON_STATE_PRESSED Then
            Console.WriteLine("Right Button: Pressed")
        Else If buttonR = BrickletDualButtonV2.BUTTON_STATE_RELEASED Then
            Console.WriteLine("Right Button: Released")
        End If

        Console.WriteLine("")
    End Sub

    Sub Main()
        Dim ipcon As New IPConnection() ' Create IP connection
        Dim db As New BrickletDualButtonV2(UID, ipcon) ' Create device object

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

        ' Register state changed callback to subroutine StateChangedCB
        AddHandler db.StateChangedCallback, AddressOf StateChangedCB

        ' Enable state changed callback
        db.SetStateChangedCallbackConfiguration(True)

        Console.WriteLine("Press key to exit")
        Console.ReadLine()
        ipcon.Disconnect()
    End Sub
End Module

Basic Functions¶

Class BrickletDualButtonV2(ByVal uid As String, ByVal ipcon As IPConnection)¶

Creates an object with the unique device ID uid:

Dim dualButtonV2 As New BrickletDualButtonV2("YOUR_DEVICE_UID", ipcon)

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

Sub BrickletDualButtonV2.SetLEDState(ByVal ledL As Byte, ByVal ledR As 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:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

For ledR:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

Sub BrickletDualButtonV2.GetLEDState(ByRef ledL As Byte, ByRef ledR As 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:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

For ledR:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

Sub BrickletDualButtonV2.GetButtonState(ByRef buttonL As Byte, ByRef buttonR As 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:

• BrickletDualButtonV2.BUTTON_STATE_PRESSED = 0
• BrickletDualButtonV2.BUTTON_STATE_RELEASED = 1

For buttonR:

• BrickletDualButtonV2.BUTTON_STATE_PRESSED = 0
• BrickletDualButtonV2.BUTTON_STATE_RELEASED = 1

Advanced Functions¶

Sub BrickletDualButtonV2.SetSelectedLEDState(ByVal led As Byte, ByVal state As Byte)¶

Parameters:	led – Type: Byte, Range: See constants state – Type: Byte, 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.LED_LEFT = 0
• BrickletDualButtonV2.LED_RIGHT = 1

For state:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

Sub BrickletDualButtonV2.GetSPITFPErrorCount(ByRef errorCountAckChecksum As Long, ByRef errorCountMessageChecksum As Long, ByRef errorCountFrame As Long, ByRef errorCountOverflow As Long)¶

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

Sub BrickletDualButtonV2.SetStatusLEDConfig(ByVal config As 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:

• BrickletDualButtonV2.STATUS_LED_CONFIG_OFF = 0
• BrickletDualButtonV2.STATUS_LED_CONFIG_ON = 1
• BrickletDualButtonV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletDualButtonV2.STATUS_LED_CONFIG_SHOW_STATUS = 3

Function BrickletDualButtonV2.GetStatusLEDConfig() As 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:

• BrickletDualButtonV2.STATUS_LED_CONFIG_OFF = 0
• BrickletDualButtonV2.STATUS_LED_CONFIG_ON = 1
• BrickletDualButtonV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletDualButtonV2.STATUS_LED_CONFIG_SHOW_STATUS = 3

Function BrickletDualButtonV2.GetChipTemperature() As Short¶

Returns:	temperature – Type: Short, 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.

Sub BrickletDualButtonV2.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!

Sub BrickletDualButtonV2.GetIdentity(ByRef uid As String, ByRef connectedUid As String, ByRef position As Char, ByRef hardwareVersion() As Byte, ByRef firmwareVersion() As Byte, ByRef deviceIdentifier As Integer)¶

Output Parameters:

uid – Type: String, Length: up to 8 connectedUid – Type: String, Length: up to 8 position – Type: Char, Range: ["a"C to "h"C, "z"C] hardwareVersion – Type: Byte Array, Length: 3 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: Byte Array, Length: 3 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: 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). 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¶

Sub BrickletDualButtonV2.SetStateChangedCallbackConfiguration(ByVal enabled As Boolean)¶

Parameters:	enabled – Type: Boolean, Default: false

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

Function BrickletDualButtonV2.GetStateChangedCallbackConfiguration() As Boolean¶

Returns:	enabled – Type: Boolean, 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 procedure to an callback property of the device object:

Sub MyCallback(ByVal sender As BrickletDualButtonV2, ByVal value As Short)
    Console.WriteLine("Value: {0}", value)
End Sub

AddHandler dualButtonV2.ExampleCallback, AddressOf MyCallback

The available callback property and their type of parameters are described below.

Event BrickletDualButtonV2.StateChangedCallback(ByVal sender As BrickletDualButtonV2, ByVal buttonL As Byte, ByVal buttonR As Byte, ByVal ledL As Byte, ByVal ledR As Byte)¶

Callback Parameters:	sender – Type: BrickletDualButtonV2 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).

This callback can be enabled with SetStateChangedCallbackConfiguration().

The following constants are available for this function:

For buttonL:

• BrickletDualButtonV2.BUTTON_STATE_PRESSED = 0
• BrickletDualButtonV2.BUTTON_STATE_RELEASED = 1

For buttonR:

• BrickletDualButtonV2.BUTTON_STATE_PRESSED = 0
• BrickletDualButtonV2.BUTTON_STATE_RELEASED = 1

For ledL:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.LED_STATE_OFF = 3

For ledR:

• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_ON = 0
• BrickletDualButtonV2.LED_STATE_AUTO_TOGGLE_OFF = 1
• BrickletDualButtonV2.LED_STATE_ON = 2
• BrickletDualButtonV2.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 BrickletDualButtonV2.GetAPIVersion() As Byte()¶

Output Parameters:	apiVersion – Type: Byte Array, Length: 3 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 BrickletDualButtonV2.GetResponseExpected(ByVal functionId As Byte) As 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:

• BrickletDualButtonV2.FUNCTION_SET_LED_STATE = 1
• BrickletDualButtonV2.FUNCTION_SET_SELECTED_LED_STATE = 5
• BrickletDualButtonV2.FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
• BrickletDualButtonV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletDualButtonV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletDualButtonV2.FUNCTION_RESET = 243
• BrickletDualButtonV2.FUNCTION_WRITE_UID = 248

Sub BrickletDualButtonV2.SetResponseExpected(ByVal functionId As Byte, ByVal responseExpected As 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:

• BrickletDualButtonV2.FUNCTION_SET_LED_STATE = 1
• BrickletDualButtonV2.FUNCTION_SET_SELECTED_LED_STATE = 5
• BrickletDualButtonV2.FUNCTION_SET_STATE_CHANGED_CALLBACK_CONFIGURATION = 6
• BrickletDualButtonV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletDualButtonV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletDualButtonV2.FUNCTION_RESET = 243
• BrickletDualButtonV2.FUNCTION_WRITE_UID = 248

Sub BrickletDualButtonV2.SetResponseExpectedAll(ByVal responseExpected As 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 BrickletDualButtonV2.SetBootloaderMode(ByVal mode As Byte) As 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:

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

For status:

• BrickletDualButtonV2.BOOTLOADER_STATUS_OK = 0
• BrickletDualButtonV2.BOOTLOADER_STATUS_INVALID_MODE = 1
• BrickletDualButtonV2.BOOTLOADER_STATUS_NO_CHANGE = 2
• BrickletDualButtonV2.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
• BrickletDualButtonV2.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
• BrickletDualButtonV2.BOOTLOADER_STATUS_CRC_MISMATCH = 5

Function BrickletDualButtonV2.GetBootloaderMode() As 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:

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

Sub BrickletDualButtonV2.SetWriteFirmwarePointer(ByVal pointer As Long)¶

Parameters:	pointer – Type: Long, 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.

Function BrickletDualButtonV2.WriteFirmware(ByVal data() As Byte) As Byte¶

Parameters:	data – Type: Byte Array, Length: 64, 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.

Sub BrickletDualButtonV2.WriteUID(ByVal uid As Long)¶

Parameters:	uid – Type: Long, 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.

Function BrickletDualButtonV2.ReadUID() As Long¶

Returns:	uid – Type: Long, Range: [0 to 232 - 1]

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

Constants¶

Const BrickletDualButtonV2.DEVICE_IDENTIFIER¶

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.

Const BrickletDualButtonV2.DEVICE_DISPLAY_NAME¶

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