API
Generally, every method of the Java bindings that returns a value can
throw a 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 unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException there is also a NotConnectedException that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since Java does not support multiple return values and return by reference
is not possible for primitive types, we use small classes that
only consist of member variables. The member variables of the returned objects
are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
Basic Functions
-
class BrickletDualButtonV2(String uid, IPConnection ipcon)
| Parameters: | - uid – Type: String
- ipcon – Type: IPConnection
|
| Returns: | - dualButtonV2 – Type: BrickletDualButtonV2
|
Creates an object with the unique device ID uid:
BrickletDualButtonV2 dualButtonV2 = new BrickletDualButtonV2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
-
void BrickletDualButtonV2.setLEDState(int ledL, int ledR)
| Parameters: | - ledL – Type: int, Range: See constants, Default: 1
- ledR – Type: int, 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
-
BrickletDualButtonV2.LEDState BrickletDualButtonV2.getLEDState()
| Return Object: | - ledL – Type: int, Range: See constants, Default: 1
- ledR – Type: int, 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
-
BrickletDualButtonV2.ButtonState BrickletDualButtonV2.getButtonState()
| Return Object: | - buttonL – Type: int, Range: See constants
- buttonR – Type: int, Range: See constants
|
Returns the current state for both buttons. Possible states are:
The following constants are available for this function:
For buttonL:
For buttonR:
Advanced Functions
-
void BrickletDualButtonV2.setSelectedLEDState(int led, int state)
| Parameters: | - led – Type: int, Range: See constants
- state – Type: int, 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:
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
-
BrickletDualButtonV2.SPITFPErrorCount BrickletDualButtonV2.getSPITFPErrorCount()
| Return Object: | - 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.
-
void BrickletDualButtonV2.setStatusLEDConfig(int config)
| Parameters: | - config – Type: int, 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
-
int BrickletDualButtonV2.getStatusLEDConfig()
| Returns: | - config – Type: int, 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
-
int BrickletDualButtonV2.getChipTemperature()
| Returns: | - temperature – Type: int, 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.
-
void 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!
-
BrickletDualButtonV2.Identity BrickletDualButtonV2.getIdentity()
| Return Object: | - uid – Type: String, Length: up to 8
- connectedUid – Type: String, Length: up to 8
- position – Type: char, Range: ['a' to 'h', 'z']
- hardwareVersion – Type: short[], Length: 3
- 0: major – Type: short, Range: [0 to 255]
- 1: minor – Type: short, Range: [0 to 255]
- 2: revision – Type: short, Range: [0 to 255]
- firmwareVersion – Type: short[], Length: 3
- 0: major – Type: short, Range: [0 to 255]
- 1: minor – Type: short, Range: [0 to 255]
- 2: revision – Type: short, Range: [0 to 255]
- deviceIdentifier – Type: int, 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.
Listener Configuration Functions
-
void BrickletDualButtonV2.setStateChangedCallbackConfiguration(boolean enabled)
| Parameters: | - enabled – Type: boolean, Default: false
|
If you enable this listener, the StateChangedListener listener is triggered
every time a button is pressed/released
-
boolean BrickletDualButtonV2.getStateChangedCallbackConfiguration()
| Returns: | - enabled – Type: boolean, Default: false
|
Returns the configuration as set by setStateChangedCallbackConfiguration().
Listeners
Listeners can be registered to receive
time critical or recurring data from the device. The registration is done
with add*Listener() functions of the device object.
The parameter is a listener class object, for example:
device.addExampleListener(new BrickletDualButtonV2.ExampleListener() {
public void property(int value) {
System.out.println("Value: " + value);
}
});
The available listener classes with inherent methods to be overwritten
are described below. It is possible to add several listeners and
to remove them with the corresponding remove*Listener() function.
Note
Using listeners 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.
-
class BrickletDualButtonV2.StateChangedListener()
This listener can be added with the addStateChangedListener() function.
An added listener can be removed with the removeStateChangedListener() function.
-
void stateChanged(int buttonL, int buttonR, int ledL, int ledR)
| Parameters: | - buttonL – Type: int, Range: See constants
- buttonR – Type: int, Range: See constants
- ledL – Type: int, Range: See constants
- ledR – Type: int, Range: See constants
|
This listener is called whenever a button is pressed.
Possible states for buttons are:
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 listener can be enabled with setStateChangedCallbackConfiguration().
The following constants are available for this function:
For buttonL:
For buttonR:
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.
-
short[] BrickletDualButtonV2.getAPIVersion()
| Return Object: | - apiVersion – Type: short[], Length: 3
- 0: major – Type: short, Range: [0 to 255]
- 1: minor – Type: short, Range: [0 to 255]
- 2: revision – Type: short, 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.
-
boolean BrickletDualButtonV2.getResponseExpected(byte functionId)
| 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 listener 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
-
void BrickletDualButtonV2.setResponseExpected(byte functionId, boolean responseExpected)
| 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 listener 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
-
void BrickletDualButtonV2.setResponseExpectedAll(boolean responseExpected)
| Parameters: | - responseExpected – Type: boolean
|
Changes the response expected flag for all setter and listener 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.
-
int BrickletDualButtonV2.setBootloaderMode(int mode)
| Parameters: | - mode – Type: int, Range: See constants
|
| Returns: | - status – Type: int, 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
-
int BrickletDualButtonV2.getBootloaderMode()
| Returns: | - mode – Type: int, 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
-
void BrickletDualButtonV2.setWriteFirmwarePointer(long pointer)
| 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.
-
int BrickletDualButtonV2.writeFirmware(int[] data)
| Parameters: | - data – Type: int[], Length: 64, Range: [0 to 255]
|
| Returns: | - status – Type: int, 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.
-
void BrickletDualButtonV2.writeUID(long uid)
| 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.
-
long BrickletDualButtonV2.readUID()
| 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
-
int BrickletDualButtonV2.DEVICE_IDENTIFIER
This constant is used to identify a Dual Button Bricklet 2.0.
The getIdentity() function and the
IPConnection.EnumerateListener
listener of the IP Connection have a deviceIdentifier parameter to specify
the Brick's or Bricklet's type.
-
String BrickletDualButtonV2.DEVICE_DISPLAY_NAME
This constant represents the human readable name of a Dual Button Bricklet 2.0.