This is the description of the C/C++ 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 C/C++ API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_motion_detector.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change to your UID
// Callback function for end of detection cycle
void cb_detection_cycle_ended(void *user_data) {
(void)user_data; // avoid unused parameter warning
printf("Detection Cycle Ended (next detection possible in ~3 seconds)\n");
}
// Callback function for detected motion
void cb_motion_detected(void *user_data) {
(void)user_data; // avoid unused parameter warning
printf("Motion Detected\n");
}
int main() {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
MotionDetector md;
motion_detector_create(&md, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
exit(1);
}
// Don't use device before ipcon is connected
// Register detected callback to function cb_motion_detected
motion_detector_register_callback(&md,
MOTION_DETECTOR_CALLBACK_MOTION_DETECTED,
(void *)cb_motion_detected,
NULL);
// Register detection cycle ended callback to function cb_detection_cycle_ended
motion_detector_register_callback(&md,
MOTION_DETECTOR_CALLBACK_DETECTION_CYCLE_ENDED,
(void *)cb_detection_cycle_ended,
NULL);
printf("Press key to exit\n");
getchar();
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
}
|
Every function of the C/C++ bindings returns an integer which describes an error code. Data returned from the device, when a getter is called, is handled via call by reference. These parameters are labeled with the ret_ prefix.
Possible error codes are:
as defined in ip_connection.h.
All functions listed below are thread-safe.
Creates the device object motion_detector with the unique device ID uid and adds it to the IPConnection ipcon:
MotionDetector motion_detector;
motion_detector_create(&motion_detector, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected (see examples above).
Removes the device object motion_detector from its IPConnection and destroys it. The device object cannot be used anymore afterwards.
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 defines are available for this function:
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.
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 motion_detector_set_response_expected(). 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 motion_detector_set_response_expected() for the list of function ID defines 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 and callbacks it is always disabled.
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 defines are available for this function:
Changes the response expected flag for all setter and callback configuration functions of this device at once.
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.
Registers a callback with ID id to the function callback. The user_data will be given as a parameter of the callback.
The available IDs with corresponding function signatures are listed below.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the motion_detector_register_callback() function. The parameters consist of the device object, the callback ID, the callback function and optional user data:
void my_callback(int p, void *user_data) { printf("parameter: %d\n", p); } motion_detector_register_callback(&motion_detector, MOTION_DETECTOR_CALLBACK_EXAMPLE, (void *)my_callback, NULL);
The available constants with corresponding callback function signatures 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.
void callback(void *user_data)
This callback is called after a motion was detected.
void callback(void *user_data)
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.
This constant is used to identify a Motion Detector Bricklet.
The motion_detector_get_identity() function and the IPCON_CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.