This is the description of the LabVIEW API bindings for the DMX Bricklet. General information and technical specifications for the DMX Bricklet are summarized in its hardware description.
An installation guide for the LabVIEW API bindings is part of their general description.
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.*
.
BrickletDMX
(uid, ipcon) → dmx¶Input: |
|
---|---|
Output: |
|
Creates an object with the unique device ID uid
.
This object can then be used after the IP Connection is connected.
BrickletDMX.
SetDMXMode
(dmxMode)¶Input: |
|
---|
Sets the DMX mode to either master or slave.
Calling this function sets frame number to 0.
The following constants are available for this function:
For dmxMode:
BrickletDMX.
GetDMXMode
() → dmxMode¶Output: |
|
---|
Returns the DMX mode, as set by SetDMXMode()
.
The following constants are available for this function:
For dmxMode:
BrickletDMX.
WriteFrame
(frame)¶Input: |
|
---|
Writes a DMX frame. The maximum frame size is 512 byte. Each byte represents one channel.
The next frame can be written after the FrameStartedCallback
callback was called. The frame
is double buffered, so a new frame can be written as soon as the writing of the prior frame
starts.
The data will be transfered when the next frame duration ends, see SetFrameDuration()
.
Generic approach:
FrameStartedCallback
callback.FrameStartedCallback
callback.This approach ensures that you can set new DMX data with a fixed frame rate.
This function can only be called in master mode.
BrickletDMX.
ReadFrame
() → frame, frameNumber¶Output: |
|
---|
Returns the last frame that was written by the DMX master. The size of the array is equivalent to the number of channels in the frame. Each byte represents one channel.
The next frame is available after the FrameAvailableCallback
callback was called.
Generic approach:
ReadFrame()
to get first frame.FrameAvailableCallback
callback.ReadFrame()
to get second frame.FrameAvailableCallback
callback.Instead of polling this function you can also use the FrameCallback
callback.
You can enable it with SetFrameCallbackConfig()
.
The frame number starts at 0 and it is increased by one with each received frame.
This function can only be called in slave mode.
BrickletDMX.
SetFrameDuration
(frameDuration)¶Input: |
|
---|
Sets the duration of a frame.
Example: If you want to achieve 20 frames per second, you should set the frame duration to 50ms (50ms * 20 = 1 second).
If you always want to send a frame as fast as possible you can set this value to 0.
This setting is only used in master mode.
BrickletDMX.
GetFrameDuration
() → frameDuration¶Output: |
|
---|
Returns the frame duration as set by SetFrameDuration()
.
BrickletDMX.
GetFrameErrorCount
() → overrunErrorCount, framingErrorCount¶Output: |
|
---|
Returns the current number of overrun and framing errors.
BrickletDMX.
SetCommunicationLEDConfig
(config)¶Input: |
|
---|
Sets the communication LED configuration. By default the LED shows communication traffic, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
BrickletDMX.
GetCommunicationLEDConfig
() → config¶Output: |
|
---|
Returns the configuration as set by SetCommunicationLEDConfig()
The following constants are available for this function:
For config:
BrickletDMX.
SetErrorLEDConfig
(config)¶Input: |
|
---|
Sets the error LED configuration.
By default the error LED turns on if there is any error (see FrameErrorCountCallback
callback). If you call this function with the Show-Error option again, the LED
will turn off until the next error occurs.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
BrickletDMX.
GetErrorLEDConfig
() → config¶Output: |
|
---|
Returns the configuration as set by SetErrorLEDConfig()
.
The following constants are available for this function:
For config:
BrickletDMX.
GetSPITFPErrorCount
() → errorCountAckChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow¶Output: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletDMX.
SetStatusLEDConfig
(config)¶Input: |
|
---|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For config:
BrickletDMX.
GetStatusLEDConfig
() → config¶Output: |
|
---|
Returns the configuration as set by SetStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletDMX.
GetChipTemperature
() → temperature¶Output: |
|
---|
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletDMX.
Reset
()¶Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletDMX.
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.
BrickletDMX.
SetFrameCallbackConfig
(frameStartedCallbackEnabled, frameAvailableCallbackEnabled, frameCallbackEnabled, frameErrorCountCallbackEnabled)¶Input: |
|
---|
Enables/Disables the different callbacks. By default the
FrameStartedCallback
callback and FrameAvailableCallback
callback are enabled while
the FrameCallback
callback and FrameErrorCountCallback
callback are disabled.
If you want to use the FrameCallback
callback you can enable it and disable
the FrameAvailableCallback
callback at the same time. It becomes redundant in
this case.
BrickletDMX.
GetFrameCallbackConfig
() → frameStartedCallbackEnabled, frameAvailableCallbackEnabled, frameCallbackEnabled, frameErrorCountCallbackEnabled¶Output: |
|
---|
Returns the frame callback config as set by SetFrameCallbackConfig()
.
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.
BrickletDMX.
FrameStartedCallback
→ sender¶Callback Output: |
|
---|
This callback is triggered as soon as a new frame write is started. You should send the data for the next frame directly after this callback was triggered.
For an explanation of the general approach see WriteFrame()
.
This callback can be enabled via SetFrameCallbackConfig()
.
This callback can only be triggered in master mode.
BrickletDMX.
FrameAvailableCallback
→ sender, frameNumber¶Callback Output: |
|
---|
This callback is triggered in slave mode when a new frame was received from the DMX master
and it can be read out. You have to read the frame before the master has written
the next frame, see ReadFrame()
for more details.
The parameter is the frame number, it is increased by one with each received frame.
This callback can be enabled via SetFrameCallbackConfig()
.
This callback can only be triggered in slave mode.
BrickletDMX.
FrameCallback
→ sender, frame, frameNumber¶Callback Output: |
|
---|
This callback is called as soon as a new frame is available (written by the DMX master).
The size of the array is equivalent to the number of channels in the frame. Each byte represents one channel.
This callback can be enabled via SetFrameCallbackConfig()
.
This callback can only be triggered in slave mode.
Note
If reconstructing the value fails, the callback is triggered with null for frame.
BrickletDMX.
FrameErrorCountCallback
→ sender, overrunErrorCount, framingErrorCount¶Callback Output: |
|
---|
This callback is called if a new error occurs. It returns the current overrun and framing error count.
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.
BrickletDMX.
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.
BrickletDMX.
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:
BrickletDMX.
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:
BrickletDMX.
SetResponseExpectedAll
(responseExpected)¶Input: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletDMX.
SetBootloaderMode
(mode) → status¶Input: |
|
---|---|
Output: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For mode:
For status:
BrickletDMX.
GetBootloaderMode
() → mode¶Output: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletDMX.
SetWriteFirmwarePointer
(pointer)¶Input: |
|
---|
Sets the firmware pointer for WriteFirmware()
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletDMX.
WriteFirmware
(data) → status¶Input: |
|
---|---|
Output: |
|
Writes 64 Bytes of firmware at the position as written by
SetWriteFirmwarePointer()
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletDMX.
WriteUID
(uid)¶Input: |
|
---|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletDMX.
ReadUID
() → uid¶Output: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletDMX.
DEVICE_IDENTIFIER
¶This constant is used to identify a DMX 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.
BrickletDMX.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a DMX Bricklet.