This is the description of the Python API bindings for the IO-4 Bricklet. General information and technical specifications for the IO-4 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 23 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your IO-4 Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_io4 import BrickletIO4
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
io = BrickletIO4(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Get current value as bitmask
value_mask = io.get_value()
print("Value Mask: " + format(value_mask, "04b"))
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
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 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your IO-4 Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_io4 import BrickletIO4
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
io = BrickletIO4(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Set pin 1 to output low
io.set_configuration(1 << 1, "o", False)
# Set pin 2 and 3 to output high
io.set_configuration((1 << 2) | (1 << 3), "o", True)
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
Download (example_interrupt.py)
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 | #!/usr/bin/env python
# -*- coding: utf-8 -*-
HOST = "localhost"
PORT = 4223
UID = "XYZ" # Change XYZ to the UID of your IO-4 Bricklet
from tinkerforge.ip_connection import IPConnection
from tinkerforge.bricklet_io4 import BrickletIO4
# Callback function for interrupt callback
def cb_interrupt(interrupt_mask, value_mask):
print("Interrupt Mask: " + format(interrupt_mask, "04b"))
print("Value Mask: " + format(value_mask, "04b"))
print("")
if __name__ == "__main__":
ipcon = IPConnection() # Create IP connection
io = BrickletIO4(UID, ipcon) # Create device object
ipcon.connect(HOST, PORT) # Connect to brickd
# Don't use device before ipcon is connected
# Register interrupt callback to function cb_interrupt
io.register_callback(io.CALLBACK_INTERRUPT, cb_interrupt)
# Enable interrupt on pin 0
io.set_interrupt(1 << 0)
input("Press key to exit\n") # Use raw_input() in Python 2
ipcon.disconnect()
|
Generally, every function 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 functions listed below are thread-safe.
BrickletIO4
(uid, ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
io4 = BrickletIO4("YOUR_DEVICE_UID", ipcon)
This object can then be used after the IP Connection is connected.
BrickletIO4.
set_value
(value_mask)¶Parameters: |
|
---|---|
Returns: |
|
Sets the output value (high or low) with a bitmask (4bit). A 1 in the bitmask means high and a 0 in the bitmask means low.
For example: The value 3 or 0b0011 will turn the pins 0-1 high and the pins 2-3 low.
All running monoflop timers will be aborted if this function is called.
Note
This function does nothing for pins that are configured as input.
Pull-up resistors can be switched on with set_configuration()
.
BrickletIO4.
get_value
()¶Returns: |
|
---|
Returns a bitmask of the values that are currently measured. This function works if the pin is configured to input as well as if it is configured to output.
BrickletIO4.
set_configuration
(selection_mask, direction, value)¶Parameters: |
|
---|---|
Returns: |
|
Configures the value and direction of the specified pins. Possible directions are 'i' and 'o' for input and output.
If the direction is configured as output, the value is either high or low (set as true or false).
If the direction is configured as input, the value is either pull-up or default (set as true or false).
For example:
Running monoflop timers for the specified pins will be aborted if this function is called.
The following constants are available for this function:
For direction:
BrickletIO4.
get_configuration
()¶Return Object: |
|
---|
Returns a value bitmask and a direction bitmask. A 1 in the direction bitmask means input and a 0 in the bitmask means output.
For example: A return value of (3, 5) or (0b0011, 0b0101) for direction and value means that:
BrickletIO4.
get_edge_count
(pin, reset_counter)¶Parameters: |
|
---|---|
Returns: |
|
Returns the current value of the edge counter for the selected pin. You can
configure the edges that are counted with set_edge_count_config()
.
If you set the reset counter to true, the count is set back to 0 directly after it is read.
New in version 2.0.1 (Plugin).
BrickletIO4.
set_monoflop
(selection_mask, value_mask, time)¶Parameters: |
|
---|---|
Returns: |
|
Configures a monoflop of the pins specified by the first parameter as 4 bit long bitmask. The specified pins must be configured for output. Non-output pins will be ignored.
The second parameter is a bitmask with the desired value of the specified output pins. A 1 in the bitmask means high and a 0 in the bitmask means low.
The third parameter indicates the time that the pins should hold the value.
If this function is called with the parameters (9, 1, 1500) or (0b1001, 0b0001, 1500): Pin 0 will get high and pin 3 will get low. In 1.5s pin 0 will get low and pin 3 will get high again.
A monoflop can be used as a fail-safe mechanism. For example: Lets assume you have a RS485 bus and an IO-4 Bricklet connected to one of the slave stacks. You can now call this function every second, with a time parameter of two seconds and pin 0 set to high. Pin 0 will be high all the time. If now the RS485 connection is lost, then pin 0 will get low in at most two seconds.
BrickletIO4.
get_monoflop
(pin)¶Parameters: |
|
---|---|
Return Object: |
|
Returns (for the given pin) the current value and the time as set by
set_monoflop()
as well as the remaining time until the value flips.
If the timer is not running currently, the remaining time will be returned as 0.
BrickletIO4.
set_selected_values
(selection_mask, value_mask)¶Parameters: |
|
---|---|
Returns: |
|
Sets the output value (high or low) with a bitmask, according to the selection mask. The bitmask is 4 bit long, true refers to high and false refers to low.
For example: The parameters (9, 4) or (0b0110, 0b0100) will turn pin 1 low and pin 2 high, pin 0 and 3 will remain untouched.
Running monoflop timers for the selected pins will be aborted if this function is called.
Note
This function does nothing for pins that are configured as input.
Pull-up resistors can be switched on with set_configuration()
.
BrickletIO4.
set_edge_count_config
(selection_mask, edge_type, debounce)¶Parameters: |
|
---|---|
Returns: |
|
Configures the edge counter for the selected pins.
The edge type parameter configures if rising edges, falling edges or both are counted if the pin is configured for input. Possible edge types are:
Configuring an edge counter resets its value to 0.
If you don't know what any of this means, just leave it at default. The default configuration is very likely OK for you.
The following constants are available for this function:
For edge_type:
New in version 2.0.1 (Plugin).
BrickletIO4.
get_edge_count_config
(pin)¶Parameters: |
|
---|---|
Return Object: |
|
Returns the edge type and debounce time for the selected pin as set by
set_edge_count_config()
.
The following constants are available for this function:
For edge_type:
New in version 2.0.1 (Plugin).
BrickletIO4.
get_identity
()¶Return Object: |
|
---|
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', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
BrickletIO4.
register_callback
(callback_id, function)¶Parameters: |
|
---|---|
Returns: |
|
Registers the given function
with the given callback_id
.
The available callback IDs with corresponding function signatures are listed below.
BrickletIO4.
set_debounce_period
(debounce)¶Parameters: |
|
---|---|
Returns: |
|
Sets the debounce period of the CALLBACK_INTERRUPT
callback.
For example: If you set this value to 100, you will get the interrupt maximal every 100ms. This is necessary if something that bounces is connected to the IO-4 Bricklet, such as a button.
BrickletIO4.
get_debounce_period
()¶Returns: |
|
---|
Returns the debounce period as set by set_debounce_period()
.
BrickletIO4.
set_interrupt
(interrupt_mask)¶Parameters: |
|
---|---|
Returns: |
|
Sets the pins on which an interrupt is activated with a bitmask. Interrupts are triggered on changes of the voltage level of the pin, i.e. changes from high to low and low to high.
For example: An interrupt bitmask of 10 or 0b1010 will enable the interrupt for pins 1 and 3.
The interrupt is delivered with the CALLBACK_INTERRUPT
callback.
BrickletIO4.
get_interrupt
()¶Returns: |
|
---|
Returns the interrupt bitmask as set by set_interrupt()
.
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)
io4.register_callback(BrickletIO4.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.
BrickletIO4.
CALLBACK_INTERRUPT
¶Callback Parameters: |
|
---|
This callback is triggered whenever a change of the voltage level is detected
on pins where the interrupt was activated with set_interrupt()
.
The values are a bitmask that specifies which interrupts occurred and the current value bitmask.
For example:
BrickletIO4.
CALLBACK_MONOFLOP_DONE
¶Callback Parameters: |
|
---|
This callback is triggered whenever a monoflop timer reaches 0. The parameters contain the involved pins and the current value of the pins (the value after the monoflop).
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.
BrickletIO4.
get_api_version
()¶Return Object: |
|
---|
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.
BrickletIO4.
get_response_expected
(function_id)¶Parameters: |
|
---|---|
Returns: |
|
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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletIO4.
set_response_expected
(function_id, response_expected)¶Parameters: |
|
---|---|
Returns: |
|
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:
For function_id:
BrickletIO4.
set_response_expected_all
(response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletIO4.
DEVICE_IDENTIFIER
¶This constant is used to identify a IO-4 Bricklet.
The get_identity()
function and the
IPConnection.CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletIO4.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a IO-4 Bricklet.