This is the description of the LabVIEW 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 LabVIEW API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Generally, every function of the LabVIEW bindings that outputs a value can
report a Tinkerforge.TimeoutException
. This error gets reported if the
device did not respond. If a cable based connection is used, it is
unlikely that this exception gets thrown (assuming nobody plugs the
device out). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
The namespace for all Brick/Bricklet bindings and the IPConnection is
Tinkerforge.*
.
BrickletIndustrialDigitalIn4
(uid, ipcon) → industrialDigitalIn4¶Input: |
|
---|---|
Output: |
|
Creates an object with the unique device ID uid
.
This object can then be used after the IP Connection is connected.
BrickletIndustrialDigitalIn4.
GetValue
() → valueMask¶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 SetGroup()
), the pins correspond to the
markings on the IndustrialDigital 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.
BrickletIndustrialDigitalIn4.
GetEdgeCount
(pin, resetCounter) → count¶Input: |
|
---|---|
Output: |
|
Returns the current value of the edge counter for the selected pin. You can
configure the edges that are counted with SetEdgeCountConfig()
.
If you set the reset counter to true, the count is set back to 0 directly after it is read.
The edge counters use the grouping as set by SetGroup()
.
New in version 2.0.1 (Plugin).
BrickletIndustrialDigitalIn4.
SetGroup
(group)¶Input: |
|
---|
Sets a group of Digital In 4 Bricklets that should work together. You can
find Bricklets that can be grouped together with GetAvailableForGroup()
.
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 GetValue()
and read out two Bricklets at the same time.
Changing the group configuration resets all edge counter configurations and values.
BrickletIndustrialDigitalIn4.
GetGroup
() → group¶Output: |
|
---|
Returns the group as set by SetGroup()
BrickletIndustrialDigitalIn4.
GetAvailableForGroup
() → available¶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.
BrickletIndustrialDigitalIn4.
SetEdgeCountConfig
(selectionMask, edgeType, debounce)¶Input: |
|
---|
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:
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 edge counters use the grouping as set by SetGroup()
.
The following constants are available for this function:
For edgeType:
New in version 2.0.1 (Plugin).
BrickletIndustrialDigitalIn4.
GetEdgeCountConfig
(pin) → edgeType, debounce¶Input: |
|
---|---|
Output: |
|
Returns the edge type and debounce time for the selected pin as set by
SetEdgeCountConfig()
.
The following constants are available for this function:
For edgeType:
New in version 2.0.1 (Plugin).
BrickletIndustrialDigitalIn4.
GetIdentity
() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier¶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', '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.
BrickletIndustrialDigitalIn4.
SetDebouncePeriod
(debounce)¶Input: |
|
---|
Sets the debounce period of the InterruptCallback
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 Digital In 4 Bricklet, such as a button.
BrickletIndustrialDigitalIn4.
GetDebouncePeriod
() → debounce¶Output: |
|
---|
Returns the debounce period as set by SetDebouncePeriod()
.
BrickletIndustrialDigitalIn4.
SetInterrupt
(interruptMask)¶Input: |
|
---|
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 SetGroup()
.
The interrupt is delivered with the InterruptCallback
callback.
BrickletIndustrialDigitalIn4.
GetInterrupt
() → interruptMask¶Output: |
|
---|
Returns the interrupt bitmask as set by SetInterrupt()
.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a function to a callback property of the device object. The available callback property and their 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.
BrickletIndustrialDigitalIn4.
InterruptCallback
→ sender, interruptMask, valueMask¶Callback Output: |
|
---|
This callback is triggered whenever a change of the voltage level is detected
on pins where the interrupt was activated with SetInterrupt()
.
The values are a bitmask that specifies which interrupts occurred and the current value bitmask.
For example:
The interrupts use the grouping as set by SetGroup()
.
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.
BrickletIndustrialDigitalIn4.
GetAPIVersion
() → apiVersion¶Output: |
|
---|
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.
BrickletIndustrialDigitalIn4.
GetResponseExpected
(functionId) → responseExpected¶Input: |
|
---|---|
Output: |
|
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
SetResponseExpected()
. 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 functionId:
BrickletIndustrialDigitalIn4.
SetResponseExpected
(functionId, responseExpected)¶Input: |
|
---|
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 functionId:
BrickletIndustrialDigitalIn4.
SetResponseExpectedAll
(responseExpected)¶Input: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletIndustrialDigitalIn4.
DEVICE_IDENTIFIER
¶This constant is used to identify a Industrial Digital In 4 Bricklet.
The GetIdentity()
function and the
IPConnection.EnumerateCallback
callback of the IP Connection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
BrickletIndustrialDigitalIn4.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Industrial Digital In 4 Bricklet.