This is the description of the C/C++ API bindings for the Piezo Buzzer Bricklet. General information and technical specifications for the Piezo Buzzer 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 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_piezo_buzzer.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change to your UID
int main() {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
PiezoBuzzer pb;
piezo_buzzer_create(&pb, 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
// Make 2 second beep
piezo_buzzer_beep(&pb, 2000);
printf("Press key to exit\n");
getchar();
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
}
|
Download (example_morse_code.c)
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 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_piezo_buzzer.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change to your UID
int main() {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
PiezoBuzzer pb;
piezo_buzzer_create(&pb, 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
// Morse SOS
piezo_buzzer_morse_code(&pb, "... --- ...");
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 piezo_buzzer with the unique device ID uid and adds it to the IPConnection ipcon:
PiezoBuzzer piezo_buzzer;
piezo_buzzer_create(&piezo_buzzer, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected (see examples above).
Removes the device object piezo_buzzer from its IPConnection and destroys it. The device object cannot be used anymore afterwards.
Beeps with the duration in ms. For example: If you set a value of 1000, the piezo buzzer will beep for one second.
Sets morse code that will be played by the piezo buzzer. The morse code is given as a string consisting of "." (dot), "-" (minus) and " " (space) for dits, dahs and pauses. Every other character is ignored.
For example: If you set the string "...---...", the piezo buzzer will beep nine times with the durations "short short short long long long short short short".
The maximum string size is 60.
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 piezo_buzzer_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 piezo_buzzer_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 piezo_buzzer_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); } piezo_buzzer_register_callback(&piezo_buzzer, PIEZO_BUZZER_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 triggered if a beep set by piezo_buzzer_beep() is finished
void callback(void *user_data)
This callback is triggered if the playback of the morse code set by piezo_buzzer_morse_code() is finished.
This constant is used to identify a Piezo Buzzer Bricklet.
The piezo_buzzer_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.