This is the description of the Shell API bindings for the Industrial Digital In 4 Bricklet. General information and technical specifications for the Industrial Digital In 4 Bricklet are summarized in its hardware description.
An installation guide for the Shell 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 | #!/bin/sh
# connects to localhost:4223 by default, use --host and --port to change it
# change to your UID
uid=XYZ
# get current input status
tinkerforge call industrial-digital-in-4-bricklet $uid get-value
|
Download (example-interrupt.sh)
1 2 3 4 5 6 7 8 9 10 11 | #!/bin/sh
# connects to localhost:4223 by default, use --host and --port to change it
# change to your UID
uid=XYZ
# enable interrupt on pin 0
tinkerforge call industrial-digital-in-4-bricklet $uid set-interrupt 1
# handle incoming interrupt callbacks
tinkerforge dispatch industrial-digital-in-4-bricklet $uid interrupt
|
Possible exit codes for all tinkerforge commands are:
The common options of the call and dispatch commands are documented here. The specific command structure is shown below.
Parameters: |
|
---|
The call command is used to call a function of the Industrial Digital In 4 Bricklet. It can take several options:
Parameters: |
|
---|
The dispatch command is used to dispatch a callback of the Industrial Digital In 4 Bricklet. It can take several options:
Parameters: |
|
---|
The <function> to be called can take different options depending of its kind. All functions can take the following options:
Getter functions can take the following options:
Setter functions can take the following options:
The --expect-response option for setter functions allows to detect timeouts and other error conditions calls of setters as well. The device will then send a response for this purpose. If this option is not given for a setter function then no response is send and errors are silently ignored, because they cannot be detected.
Parameters: |
|
---|
The <callback> to be dispatched can take several options:
Output: |
|
---|
Returns the input value with a bitmask. The bitmask is 16bit long, true refers to high and false refers to low.
For example: The value 3 or 0b0011 means that pins 0-1 are high and the other pins are low.
If no groups are used (see set-group), the pins correspond to the markings on the Digital In 4 Bricklet.
If groups are used, the pins correspond to the element in the group. Element 1 in the group will get pins 0-3, element 2 pins 4-7, element 3 pins 8-11 and element 4 pins 12-15.
Parameters: |
|
---|---|
Output: |
|
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).
Parameters: |
|
---|---|
Output: | no output |
Sets a group of Digital In 4 Bricklets that should work together. You can find Bricklets that can be grouped together with get-available-for-group.
The group consists of 4 elements. Element 1 in the group will get pins 0-3, element 2 pins 4-7, element 3 pins 8-11 and element 4 pins 12-15.
Each element can either be one of the ports ('a' to 'd') or 'n' if it should not be used.
For example: If you have two Digital In 4 Bricklets connected to port A and port B respectively, you could call with ['a', 'b', 'n', 'n'].
Now the pins on the Digital In 4 on port A are assigned to 0-3 and the pins on the Digital In 4 on port B are assigned to 4-7. It is now possible to call get-value and read out two Bricklets at the same time.
Changing the group configuration resets all edge counter configurations and values.
Output: |
|
---|
Returns the group as set by set-group
Output: |
|
---|
Returns a bitmask of ports that are available for grouping. For example the value 5 or 0b0101 means: Port A and port C are connected to Bricklets that can be grouped together.
Parameters: |
|
---|---|
Output: | no output |
Configures the edge counter for the selected pins. A bitmask of 9 or 0b1001 will enable the edge counter for pins 0 and 3.
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:
The debounce time is given in ms.
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.
Default values: 0 (edge type) and 100ms (debounce time)
The following symbols are available for this function:
New in version 2.0.1 (Plugin).
Parameters: |
|
---|---|
Output: |
|
Returns the edge type and debounce time for the selected pin as set by set-edge-count-config.
The following symbols are available for this function:
New in version 2.0.1 (Plugin).
Output: |
|
---|
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.
Parameters: |
|
---|---|
Output: | no output |
Sets the debounce period of the interrupt callback in ms.
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 Digital In 4 Bricklet, such as a button.
The default value is 100.
Output: |
|
---|
Returns the debounce period as set by set-debounce-period.
Parameters: |
|
---|---|
Output: | no output |
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 9 or 0b1001 will enable the interrupt for pins 0 and 3.
The interrupts use the grouping as set by set-group.
The interrupt is delivered with the callback interrupt.
Output: |
|
---|
Returns the interrupt bitmask as set by set-interrupt.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch industrial-digital-in-4-bricklet <uid> example
The available callbacks 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.
Output: |
|
---|
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: