Mathematica - DMX Bricklet

This is the description of the Mathematica 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 Mathematica API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (ExampleSimple.nb)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your DMX Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
dmx=NETNew["Tinkerforge.BrickletDMX",uid,ipcon]
ipcon@Connect[host,port]

(*Configure Bricklet as DMX master*)
dmx@SetDMXMode[Tinkerforge`BrickletDMX`DMXUMODEUMASTER]

(*Write DMX frame with 3 channels*)
dmx@WriteFrame[{255,128,0}]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[dmx]
ReleaseNETObject[ipcon]

API

Generally, every method of the Mathematica bindings that returns a value can throw a Tinkerforge.TimeoutException. This exception gets thrown 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.

Since .NET/Link does not support multiple return values directly, we use the out keyword to return multiple values from a method. For further information about the out keyword in .NET/Link see the corresponding Mathematica .NET/Link documentation.

The namespace for all Brick/Bricklet bindings and the IPConnection is Tinkerforge.*.

Basic Functions

BrickletDMX[uid, ipcon] → dmx
Parameters:
  • uid -- String
  • ipcon -- NETObject[IPConnection]
Returns:
  • dmx -- NETObject[BrickletDMX]

Creates an object with the unique device ID uid:

dmx=NETNew["Tinkerforge.BrickletDMX","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected (see examples above).

The .NET runtime has built-in garbage collection that frees objects that are no longer in use by a program. But because Mathematica can not automatically tell when a Mathematica "program" doesn't use a .NET object anymore, this has to be done by the program. For this the ReleaseNETObject[] function is used in the examples.

For further information about object management in .NET/Link see the corresponding Mathematica .NET/Link documentation.

BrickletDMX@SetDMXMode[dmxMode] → Null
Parameters:
  • dmxMode -- Integer

Sets the DMX mode to either master or slave.

Calling this function sets frame number to 0.

The default value is 0 (master).

The following constants are available for this function:

  • BrickletDMX`DMXUMODEUMASTER = 0
  • BrickletDMX`DMXUMODEUSLAVE = 1
BrickletDMX@GetDMXMode[] → dmxMode
Returns:
  • dmxMode -- Integer

Returns the DMX mode, as set by SetDMXMode[].

The following constants are available for this function:

  • BrickletDMX`DMXUMODEUMASTER = 0
  • BrickletDMX`DMXUMODEUSLAVE = 1
BrickletDMX@WriteFrame[{frame1, frame2, ...}] → Null
Parameters:
  • framei -- Integer

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:

  • Set the frame duration to a value that represents the number of frames per second you want to achieve.
  • Set channels for first frame.
  • Wait for the FrameStartedCallback callback.
  • Set channels for next frame.
  • Wait for the FrameStartedCallback callback.
  • and so on.

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[out {frame1, frame2, ...}, out frameNumber] → Null
Parameters:
  • framei -- Integer
  • frameNumber -- Integer

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:

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] → Null
Parameters:
  • frameDuration -- Integer

Sets the duration of a frame in ms.

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.

Default value: 100ms (10 frames per second).

BrickletDMX@GetFrameDuration[] → frameDuration
Returns:
  • frameDuration -- Integer

Returns the frame duration as set by SetFrameDuration[].

Advanced Functions

BrickletDMX@GetFrameErrorCount[out overrunErrorCount, out framingErrorCount] → Null
Parameters:
  • overrunErrorCount -- Integer
  • framingErrorCount -- Integer

Returns the current number of overrun and framing errors.

BrickletDMX@SetCommunicationLEDConfig[config] → Null
Parameters:
  • config -- Integer

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:

  • BrickletDMX`COMMUNICATIONULEDUCONFIGUOFF = 0
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUON = 1
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUSHOWUCOMMUNICATION = 3
BrickletDMX@GetCommunicationLEDConfig[] → config
Returns:
  • config -- Integer

Returns the configuration as set by SetCommunicationLEDConfig[]

The following constants are available for this function:

  • BrickletDMX`COMMUNICATIONULEDUCONFIGUOFF = 0
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUON = 1
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`COMMUNICATIONULEDUCONFIGUSHOWUCOMMUNICATION = 3
BrickletDMX@SetErrorLEDConfig[config] → Null
Parameters:
  • config -- Integer

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:

  • BrickletDMX`ERRORULEDUCONFIGUOFF = 0
  • BrickletDMX`ERRORULEDUCONFIGUON = 1
  • BrickletDMX`ERRORULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`ERRORULEDUCONFIGUSHOWUERROR = 3
BrickletDMX@GetErrorLEDConfig[] → config
Returns:
  • config -- Integer

Returns the configuration as set by SetErrorLEDConfig[].

The following constants are available for this function:

  • BrickletDMX`ERRORULEDUCONFIGUOFF = 0
  • BrickletDMX`ERRORULEDUCONFIGUON = 1
  • BrickletDMX`ERRORULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`ERRORULEDUCONFIGUSHOWUERROR = 3
BrickletDMX@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Returns:
  • apiVersioni -- Integer

Returns the version of the API definition (major, minor, revision) 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
Parameters:
  • functionId -- Integer
Returns:
  • responseExpected -- True/False

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 send and errors are silently ignored, because they cannot be detected.

See SetResponseExpected[] for the list of function ID constants available for this function.

BrickletDMX@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId -- Integer
  • responseExpected -- True/False

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 send and errors are silently ignored, because they cannot be detected.

The following function ID constants are available for this function:

  • BrickletDMX`FUNCTIONUSETUDMXUMODE = 1
  • BrickletDMX`FUNCTIONUWRITEUFRAME = 3
  • BrickletDMX`FUNCTIONUSETUFRAMEUDURATION = 5
  • BrickletDMX`FUNCTIONUSETUCOMMUNICATIONULEDUCONFIG = 8
  • BrickletDMX`FUNCTIONUSETUERRORULEDUCONFIG = 10
  • BrickletDMX`FUNCTIONUSETUFRAMEUCALLBACKUCONFIG = 12
  • BrickletDMX`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletDMX`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletDMX`FUNCTIONURESET = 243
  • BrickletDMX`FUNCTIONUWRITEUUID = 248
BrickletDMX@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected -- True/False

Changes the response expected flag for all setter and callback configuration functions of this device at once.

BrickletDMX@GetSPITFPErrorCount[out errorCountAckChecksum, out errorCountMessageChecksum, out errorCountFrame, out errorCountOverflow] → Null
Parameters:
  • errorCountAckChecksum -- Integer
  • errorCountMessageChecksum -- Integer
  • errorCountFrame -- Integer
  • errorCountOverflow -- Integer

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

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@SetBootloaderMode[mode] → status
Parameters:
  • mode -- Integer
Returns:
  • status -- Integer

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:

  • BrickletDMX`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletDMX`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletDMX`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletDMX`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletDMX`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
  • BrickletDMX`BOOTLOADERUSTATUSUOK = 0
  • BrickletDMX`BOOTLOADERUSTATUSUINVALIDUMODE = 1
  • BrickletDMX`BOOTLOADERUSTATUSUNOUCHANGE = 2
  • BrickletDMX`BOOTLOADERUSTATUSUENTRYUFUNCTIONUNOTUPRESENT = 3
  • BrickletDMX`BOOTLOADERUSTATUSUDEVICEUIDENTIFIERUINCORRECT = 4
  • BrickletDMX`BOOTLOADERUSTATUSUCRCUMISMATCH = 5
BrickletDMX@GetBootloaderMode[] → mode
Returns:
  • mode -- Integer

Returns the current bootloader mode, see SetBootloaderMode[].

The following constants are available for this function:

  • BrickletDMX`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletDMX`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletDMX`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletDMX`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletDMX`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
BrickletDMX@SetWriteFirmwarePointer[pointer] → Null
Parameters:
  • pointer -- Integer

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[{data1, data2, ..., data64}] → status
Parameters:
  • datai -- Integer
Returns:
  • status -- Integer

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@SetStatusLEDConfig[config] → Null
Parameters:
  • config -- Integer

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:

  • BrickletDMX`STATUSULEDUCONFIGUOFF = 0
  • BrickletDMX`STATUSULEDUCONFIGUON = 1
  • BrickletDMX`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletDMX@GetStatusLEDConfig[] → config
Returns:
  • config -- Integer

Returns the configuration as set by SetStatusLEDConfig[]

The following constants are available for this function:

  • BrickletDMX`STATUSULEDUCONFIGUOFF = 0
  • BrickletDMX`STATUSULEDUCONFIGUON = 1
  • BrickletDMX`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletDMX`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletDMX@GetChipTemperature[] → temperature
Returns:
  • temperature -- Integer

Returns the temperature in °C 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[] → Null

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@WriteUID[uid] → Null
Parameters:
  • uid -- Integer

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
Returns:
  • uid -- Integer

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

BrickletDMX@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Parameters:
  • uid -- String
  • connectedUid -- String
  • position -- Integer
  • hardwareVersioni -- Integer
  • firmwareVersioni -- Integer
  • deviceIdentifier -- Integer

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. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions

BrickletDMX@SetFrameCallbackConfig[frameStartedCallbackEnabled, frameAvailableCallbackEnabled, frameCallbackEnabled, frameErrorCountCallbackEnabled] → Null
Parameters:
  • frameStartedCallbackEnabled -- True/False
  • frameAvailableCallbackEnabled -- True/False
  • frameCallbackEnabled -- True/False
  • frameErrorCountCallbackEnabled -- True/False

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 cb:Frame Available callback at the same time. It becomes redundant in this case.

BrickletDMX@GetFrameCallbackConfig[out frameStartedCallbackEnabled, out frameAvailableCallbackEnabled, out frameCallbackEnabled, out frameErrorCountCallbackEnabled] → Null
Parameters:
  • frameStartedCallbackEnabled -- True/False
  • frameAvailableCallbackEnabled -- True/False
  • frameCallbackEnabled -- True/False
  • frameErrorCountCallbackEnabled -- True/False

Returns the frame callback config as set by SetFrameCallbackConfig[].

Callbacks

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:

MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]]

AddEventHandler[dmx@ExampleCallback,MyCallback]

For further information about event handling using .NET/Link see the corresponding Mathematica .NET/Link documentation.

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.

event BrickletDMX@FrameStartedCallback[sender]
Parameters:
  • sender -- NETObject[BrickletDMX]

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.

event BrickletDMX@FrameAvailableCallback[sender, frameNumber]
Parameters:
  • sender -- NETObject[BrickletDMX]
  • frameNumber -- Integer

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.

event BrickletDMX@FrameCallback[sender, {frame1, frame2, ...}, frameNumber]
Parameters:
  • sender -- NETObject[BrickletDMX]
  • framei -- Integer
  • frameNumber -- Integer

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.

event BrickletDMX@FrameErrorCountCallback[sender, overrunErrorCount, framingErrorCount]
Parameters:
  • sender -- NETObject[BrickletDMX]
  • overrunErrorCount -- Integer
  • framingErrorCount -- Integer

This callback is called if a new error occurs. It returns the current overrun and framing error count.

Constants

BrickletDMX`DEVICEUIDENTIFIER

This constant is used to identify a DMX Bricklet.

The GetIdentity[] function and the EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickletDMX`DEVICEDISPLAYNAME

This constant represents the human readable name of a DMX Bricklet.