1Needs["NETLink`"] 2LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."] 3 4host="localhost" 5port=4223 6uid="XYZ"(*Change XYZ to the UID of your Dual Button Bricklet*) 7 8(*Create IPConnection and device object*) 9ipcon=NETNew["Tinkerforge.IPConnection"]10db=NETNew["Tinkerforge.BrickletDualButton",uid,ipcon]11ipcon@Connect[host,port]1213(*Callback function for state changed callback*)14StateChangedCB[sender_,buttonL_,buttonR_,ledL_,ledR_]:=15Module[{},16If[buttonL==Tinkerforge`BrickletDualButton`BUTTONUSTATEUPRESSED,Print["Left Button: Pressed"]];17If[buttonL==Tinkerforge`BrickletDualButton`BUTTONUSTATEURELEASED,Print["Left Button: Released"]];18If[buttonR==Tinkerforge`BrickletDualButton`BUTTONUSTATEUPRESSED,Print["Right Button: Pressed"]];19If[buttonR==Tinkerforge`BrickletDualButton`BUTTONUSTATEURELEASED,Print["Right Button: Released"]]20]2122AddEventHandler[db@StateChangedCallback,StateChangedCB]2324Input["Click OK to exit"]2526(*Clean up*)27ipcon@Disconnect[]28ReleaseNETObject[db]29ReleaseNETObject[ipcon]
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.*.
This object can then be used after the IP Connection is connected.
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.
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:
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:
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.
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 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:
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:
This constant is used to identify a Dual Button Bricklet.
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.