Mathematica - Motion Detector Bricklet

This is the description of the Mathematica API bindings for the Motion Detector Bricklet. General information and technical specifications for the Motion Detector Bricklet are summarized in its hardware description.

An installation guide for the Mathematica API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Callback

Download (ExampleCallback.nb)

 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
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Motion Detector Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
md=NETNew["Tinkerforge.BrickletMotionDetector",uid,ipcon]
ipcon@Connect[host,port]

(*Callback function for motion detected callback*)
MotionDetectedCB[sender_]:=
 Print["Motion Detected"]
AddEventHandler[md@MotionDetectedCallback,MotionDetectedCB]

(*Callback function for detection cycle ended callback*)
DetectionCycleEndedCB[sender_]:=
 Print["Detection Cycle Ended (next detection possible in ~3 seconds)"]
AddEventHandler[md@DetectionCycleEndedCallback,DetectionCycleEndedCB]

Input["Click OK to exit"]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[md]
ReleaseNETObject[ipcon]

API

Generally, every method 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 method. 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.*.

Basic Functions

BrickletMotionDetector[uid, ipcon] → motionDetector
Parameters:
  • uid -- String
  • ipcon -- NETObject[IPConnection]
Returns:
  • motionDetector -- NETObject[BrickletMotionDetector]

Creates an object with the unique device ID uid:

motionDetector=NETNew["Tinkerforge.BrickletMotionDetector","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected (see examples above).

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.

BrickletMotionDetector@GetMotionDetected[] → motion
Returns:
  • motion -- Integer

Returns 1 if a motion was detected. How long this returns 1 after a motion was detected can be adjusted with one of the small potentiometers on the Motion Detector Bricklet, see here.

There is also a blue LED on the Bricklet that is on as long as the Bricklet is in the "motion detected" state.

The following constants are available for this function:

  • BrickletMotionDetector`MOTIONUNOTUDETECTED = 0
  • BrickletMotionDetector`MOTIONUDETECTED = 1

Advanced Functions

BrickletMotionDetector@SetStatusLEDConfig[config] → Null
Parameters:
  • config -- Integer

Sets the status led configuration.

By default the status LED turns on if a motion is detected and off is no motion is detected.

You can also turn the LED permanently on/off.

The following constants are available for this function:

  • BrickletMotionDetector`STATUSULEDUCONFIGUOFF = 0
  • BrickletMotionDetector`STATUSULEDUCONFIGUON = 1
  • BrickletMotionDetector`STATUSULEDUCONFIGUSHOWUSTATUS = 2

New in version 2.0.1 (Plugin).

BrickletMotionDetector@GetStatusLEDConfig[] → config
Returns:
  • config -- Integer

Returns the configuration as set by SetStatusLEDConfig[].

The following constants are available for this function:

  • BrickletMotionDetector`STATUSULEDUCONFIGUOFF = 0
  • BrickletMotionDetector`STATUSULEDUCONFIGUON = 1
  • BrickletMotionDetector`STATUSULEDUCONFIGUSHOWUSTATUS = 2

New in version 2.0.1 (Plugin).

BrickletMotionDetector@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Returns:
  • apiVersioni -- Integer

Returns the version of the API definition (major, minor, revision) 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.

BrickletMotionDetector@GetResponseExpected[functionId] → responseExpected
Parameters:
  • functionId -- Integer
Returns:
  • responseExpected -- True/False

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 send and errors are silently ignored, because they cannot be detected.

See SetResponseExpected[] for the list of function ID constants available for this function.

BrickletMotionDetector@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId -- Integer
  • responseExpected -- True/False

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 send and errors are silently ignored, because they cannot be detected.

The following function ID constants are available for this function:

  • BrickletMotionDetector`FUNCTIONUSETUSTATUSULEDUCONFIG = 4
BrickletMotionDetector@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected -- True/False

Changes the response expected flag for all setter and callback configuration functions of this device at once.

BrickletMotionDetector@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Parameters:
  • uid -- String
  • connectedUid -- String
  • position -- Integer
  • hardwareVersioni -- Integer
  • firmwareVersioni -- Integer
  • deviceIdentifier -- Integer

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' or 'd'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

Callbacks

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:

MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]]

AddEventHandler[motionDetector@ExampleCallback,MyCallback]

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.

event BrickletMotionDetector@MotionDetectedCallback[sender]
Parameters:
  • sender -- NETObject[BrickletMotionDetector]

This callback is called after a motion was detected.

event BrickletMotionDetector@DetectionCycleEndedCallback[sender]
Parameters:
  • sender -- NETObject[BrickletMotionDetector]

This callback is called when the detection cycle ended. When this callback is called, a new motion can be detected again after approximately 2 seconds.

Constants

BrickletMotionDetector`DEVICEUIDENTIFIER

This constant is used to identify a Motion Detector Bricklet.

The GetIdentity[] function and the EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickletMotionDetector`DEVICEDISPLAYNAME

This constant represents the human readable name of a Motion Detector Bricklet.