This is the description of the Go API bindings for the Dual Button Bricklet. General information and technical specifications for the Dual Button Bricklet are summarized in its hardware description.
An installation guide for the Go API bindings is part of their general description. Additional documentation can be found on godoc.org.
The example code below is Public Domain (CC0 1.0).
Download (example_callback.go)
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 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/dual_button_bricklet"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
)
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your Dual Button Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
db, _ := dual_button_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
db.RegisterStateChangedCallback(func(buttonL dual_button_bricklet.ButtonState, buttonR dual_button_bricklet.ButtonState, ledL dual_button_bricklet.LEDState, ledR dual_button_bricklet.LEDState) {
if buttonL == dual_button_bricklet.ButtonStatePressed {
fmt.Println("Left Button: Pressed")
} else if buttonL == dual_button_bricklet.ButtonStateReleased {
fmt.Println("Left Button: Released")
}
if buttonR == dual_button_bricklet.ButtonStatePressed {
fmt.Println("Right Button: Pressed")
} else if buttonR == dual_button_bricklet.ButtonStateReleased {
fmt.Println("Right Button: Released")
}
fmt.Println()
})
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
The Dual Button Bricklet API is defined in the package github.com/Tinkerforge/go-api-bindings/dual_button_bricklet
Nearly every function of the Go bindings can return an
ipconnection.DeviceError
, implementing the error interface. The error can have one of the following values:
which correspond to the values returned from Bricks and Bricklets.
All functions listed below are thread-safe.
dual_button_bricklet.
New
(uid string, ipcon *IPConnection) (device DualButtonBricklet, err error)¶Parameters: |
|
---|---|
Returns: |
|
Creates a new DualButtonBricklet
object with the unique device ID uid
and adds
it to the IPConnection ipcon
:
device, err := dual_button_bricklet.New("YOUR_DEVICE_UID", &ipcon)
This device object can be used after the IPConnection has been connected.
(*DualButtonBricklet)
SetLEDState
(ledL uint8, ledR uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the state of the LEDs. Possible states are:
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:
For ledR:
(*DualButtonBricklet)
GetLEDState
() (ledL uint8, ledR uint8, err error)¶Returns: |
|
---|
Returns the current state of the LEDs, as set by SetLEDState()
.
The following constants are available for this function:
For ledL:
For ledR:
(*DualButtonBricklet)
GetButtonState
() (buttonL uint8, buttonR uint8, err error)¶Returns: |
|
---|
Returns the current state for both buttons. Possible states are:
The following constants are available for this function:
For buttonL:
For buttonR:
(*DualButtonBricklet)
SetSelectedLEDState
(led uint8, state uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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:
For state:
(*DualButtonBricklet)
GetIdentity
() (uid string, connectedUid string, position rune, hardwareVersion [3]uint8, firmwareVersion [3]uint8, deviceIdentifier uint16, err error)¶Returns: |
|
---|
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 can be registered to receive
time critical or recurring data from the device. The registration is done
with the corresponding Register*Callback
function, which returns a unique callback ID.
This ID can be used to deregister the callback later with the corresponding Deregister*Callback
function.
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.
(*DualButtonBricklet)
RegisterStateChangedCallback
(func(buttonL uint8, buttonR uint8, ledL uint8, ledR uint8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called whenever a button is pressed.
Possible states for buttons are:
Possible states for LEDs are:
The following constants are available for this function:
For buttonL:
For buttonR:
For ledL:
For ledR:
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.
(*DualButtonBricklet)
GetAPIVersion
() (apiVersion [3]uint8, err error)¶Returns: |
|
---|
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.
(*DualButtonBricklet)
GetResponseExpected
(functionId uint8) (responseExpected bool, err error)¶Parameters: |
|
---|---|
Returns: |
|
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:
(*DualButtonBricklet)
SetResponseExpected
(functionId uint8, responseExpected bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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:
(*DualButtonBricklet)
SetResponseExpectedAll
(responseExpected bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
This constant is used to identify a Dual Button Bricklet.
The GetIdentity()
function and
the (*IPConnection) RegisterEnumerateCallback
callback of the IPConnection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
This constant represents the human readable name of a Dual Button Bricklet.