1importcom.tinkerforge.IPConnection; 2importcom.tinkerforge.BrickletDualButton; 3 4publicclassExampleCallback{ 5privatestaticfinalStringHOST="localhost"; 6privatestaticfinalintPORT=4223; 7 8// Change XYZ to the UID of your Dual Button Bricklet 9privatestaticfinalStringUID="XYZ";1011// Note: To make the example code cleaner we do not handle exceptions. Exceptions12// you might normally want to catch are described in the documentation13publicstaticvoidmain(Stringargs[])throwsException{14IPConnectionipcon=newIPConnection();// Create IP connection15BrickletDualButtondb=newBrickletDualButton(UID,ipcon);// Create device object1617ipcon.connect(HOST,PORT);// Connect to brickd18// Don't use device before ipcon is connected1920// Add state changed listener21db.addStateChangedListener(newBrickletDualButton.StateChangedListener(){22publicvoidstateChanged(shortbuttonL,shortbuttonR,shortledL,23shortledR){24if(buttonL==BrickletDualButton.BUTTON_STATE_PRESSED){25System.out.println("Left Button: Pressed");26}elseif(buttonL==BrickletDualButton.BUTTON_STATE_RELEASED){27System.out.println("Left Button: Released");28}2930if(buttonR==BrickletDualButton.BUTTON_STATE_PRESSED){31System.out.println("Right Button: Pressed");32}elseif(buttonR==BrickletDualButton.BUTTON_STATE_RELEASED){33System.out.println("Right Button: Released");34}3536System.out.println("");37}38});3940System.out.println("Press key to exit");System.in.read();41ipcon.disconnect();42}43}
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.*
ledL – Type: short, Range: See constants, Default: 1
ledR – Type: short, 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:
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:
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.
This listener can be added with the addStateChangedListener() function.
An added listener can be removed with the removeStateChangedListener() function.
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.
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.
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:
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:
This constant is used to identify a Dual Button Bricklet.
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.