This is the description of the Python 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 Python 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 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change to your UID
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_piezo_buzzer import PiezoBuzzer
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
pb = PiezoBuzzer(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Make 2 second beep
pb.beep(2000)
raw_input('Press key to exit\n') # Use input() in Python 3
ipcon.disconnect()
|
Download (example_morse_code.py)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change to your UID
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_piezo_buzzer import PiezoBuzzer
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
pb = PiezoBuzzer(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Morse SOS
pb.morse_code('... --- ...')
raw_input('Press key to exit\n') # Use input() in Python 3
ipcon.disconnect()
|
Generally, every method of the Python bindings can throw an tinkerforge.ip_connection.Error exception that has a value and a description property. value can have different values:
All methods listed below are thread-safe.
Parameters: |
|
---|
Creates an object with the unique device ID uid:
piezo_buzzer = PiezoBuzzer("YOUR_DEVICE_UID", ipcon)
This object can then be used after the IP Connection is connected (see examples above).
Parameters: | duration -- int |
---|---|
Return type: | None |
Beeps with the duration in ms. For example: If you set a value of 1000, the piezo buzzer will beep for one second.
Parameters: | morse -- str |
---|---|
Return type: | None |
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.
Return type: | [int, int, int] |
---|
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.
Parameters: | function_id -- int |
---|---|
Return type: | bool |
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 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 set_response_expected() for the list of function ID constants available for this function.
Parameters: |
|
---|---|
Return type: | None |
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 constants are available for this function:
Parameters: | response_expected -- bool |
---|---|
Return type: | None |
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Return type: | (str, str, chr, [int, int, int], [int, int, int], int) |
---|
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.
The returned namedtuple has the variables uid, connected_uid, position, hardware_version, firmware_version and device_identifier.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the register_callback() function of the device object. The first parameter is the callback ID and the second parameter the callback function:
def my_callback(param):
print(param)
piezo_buzzer.register_callback(PiezoBuzzer.CALLBACK_EXAMPLE, my_callback)
The available constants with inherent number and 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.
This callback is triggered if the playback of the morse code set by morse_code() is finished.
This constant is used to identify a Piezo Buzzer Bricklet.
The get_identity() function and the CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.