This is the description of the LabVIEW API bindings for the Ambient Light Bricklet 2.0. General information and technical specifications for the Ambient Light Bricklet 2.0 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.*
.
BrickletAmbientLightV2
(uid, ipcon) → ambientLightV2¶Input: |
|
---|---|
Output: |
|
Creates an object with the unique device ID uid
.
This object can then be used after the IP Connection is connected.
BrickletAmbientLightV2.
GetIlluminance
() → illuminance¶Output: |
|
---|
Returns the illuminance of the ambient light sensor. The measurement range goes up to about 100000lux, but above 64000lux the precision starts to drop.
Changed in version 2.0.2 (Plugin): An illuminance of 0lux indicates an error condition where the sensor cannot
perform a reasonable measurement. This can happen with very dim or very bright
light conditions. In bright light conditions this might indicate that the sensor
is saturated and the configuration should be modified (SetConfiguration()
)
to better match the light conditions.
If you want to get the illuminance periodically, it is recommended to use the
IlluminanceCallback
callback and set the period with
SetIlluminanceCallbackPeriod()
.
BrickletAmbientLightV2.
SetConfiguration
(illuminanceRange, integrationTime)¶Input: |
|
---|
Sets the configuration. It is possible to configure an illuminance range between 0-600lux and 0-64000lux and an integration time between 50ms and 400ms.
New in version 2.0.2 (Plugin): The unlimited illuminance range allows to measure up to about 100000lux, but above 64000lux the precision starts to drop.
A smaller illuminance range increases the resolution of the data. A longer integration time will result in less noise on the data.
Changed in version 2.0.2 (Plugin): If the actual measure illuminance is out-of-range then the current illuminance
range maximum +0.01lux is reported by GetIlluminance()
and the
IlluminanceCallback
callback. For example, 800001 for the 0-8000lux range.
Changed in version 2.0.2 (Plugin): With a long integration time the sensor might be saturated before the measured
value reaches the maximum of the selected illuminance range. In this case 0lux
is reported by GetIlluminance()
and the IlluminanceCallback
callback.
If the measurement is out-of-range or the sensor is saturated then you should configure the next higher illuminance range. If the highest range is already in use, then start to reduce the integration time.
The following constants are available for this function:
For illuminanceRange:
For integrationTime:
BrickletAmbientLightV2.
GetConfiguration
() → illuminanceRange, integrationTime¶Output: |
|
---|
Returns the configuration as set by SetConfiguration()
.
The following constants are available for this function:
For illuminanceRange:
For integrationTime:
BrickletAmbientLightV2.
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.
BrickletAmbientLightV2.
SetIlluminanceCallbackPeriod
(period)¶Input: |
|
---|
Sets the period with which the IlluminanceCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The IlluminanceCallback
callback is only triggered if the illuminance has changed
since the last triggering.
BrickletAmbientLightV2.
GetIlluminanceCallbackPeriod
() → period¶Output: |
|
---|
Returns the period as set by SetIlluminanceCallbackPeriod()
.
BrickletAmbientLightV2.
SetIlluminanceCallbackThreshold
(option, min, max)¶Input: |
|
---|
Sets the thresholds for the IlluminanceReachedCallback
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the illuminance is outside the min and max values |
'i' | Callback is triggered when the illuminance is inside the min and max values |
'<' | Callback is triggered when the illuminance is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the illuminance is greater than the min value (max is ignored) |
The following constants are available for this function:
For option:
BrickletAmbientLightV2.
GetIlluminanceCallbackThreshold
() → option, min, max¶Output: |
|
---|
Returns the threshold as set by SetIlluminanceCallbackThreshold()
.
The following constants are available for this function:
For option:
BrickletAmbientLightV2.
SetDebouncePeriod
(debounce)¶Input: |
|
---|
Sets the period with which the threshold callbacks
are triggered, if the thresholds
keep being reached.
BrickletAmbientLightV2.
GetDebouncePeriod
() → debounce¶Output: |
|
---|
Returns the debounce period as set by SetDebouncePeriod()
.
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.
BrickletAmbientLightV2.
IlluminanceCallback
→ sender, illuminance¶Callback Output: |
|
---|
This callback is triggered periodically with the period that is set by
SetIlluminanceCallbackPeriod()
. The parameter is the illuminance of the
ambient light sensor.
The IlluminanceCallback
callback is only triggered if the illuminance has changed since the
last triggering.
BrickletAmbientLightV2.
IlluminanceReachedCallback
→ sender, illuminance¶Callback Output: |
|
---|
This callback is triggered when the threshold as set by
SetIlluminanceCallbackThreshold()
is reached.
The parameter is the illuminance of the ambient light sensor.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by SetDebouncePeriod()
.
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.
BrickletAmbientLightV2.
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.
BrickletAmbientLightV2.
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:
BrickletAmbientLightV2.
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:
BrickletAmbientLightV2.
SetResponseExpectedAll
(responseExpected)¶Input: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletAmbientLightV2.
DEVICE_IDENTIFIER
¶This constant is used to identify a Ambient Light Bricklet 2.0.
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.
BrickletAmbientLightV2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Ambient Light Bricklet 2.0.