This is the description of the Java 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 Java 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 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletDMX;
public class ExampleSimple {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your DMX Bricklet
private static final String UID = "XYZ";
// Note: To make the example code cleaner we do not handle exceptions. Exceptions
// you might normally want to catch are described in the documentation
public static void main(String args[]) throws Exception {
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickletDMX dmx = new BrickletDMX(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Configure Bricklet as DMX master
dmx.setDMXMode(BrickletDMX.DMX_MODE_MASTER);
// Write DMX frame with 3 channels
dmx.writeFrame(new int[]{255, 128, 0});
System.out.println("Press key to exit"); System.in.read();
ipcon.disconnect();
}
}
|
Generally, every method of the Java bindings that returns a value can
throw a 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 unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException
there is also a NotConnectedException
that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since Java does not support multiple return values and return by reference is not possible for primitive types, we use small classes that only consist of member variables. The member variables of the returned objects are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
BrickletDMX
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickletDMX dmx = new BrickletDMX("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletDMX.
setDMXMode
(int dmxMode)¶Parameters: |
|
---|
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
()¶Returns: |
|
---|
Returns the DMX mode, as set by setDMXMode()
.
The following constants are available for this function:
For dmxMode:
BrickletDMX.
writeFrame
(int[] frame)¶Parameters: |
|
---|
Writes a DMX frame. The maximum frame size is 512 byte. Each byte represents one channel.
The next frame can be written after the FrameStartedListener
listener 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:
FrameStartedListener
listener.FrameStartedListener
listener.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
()¶Return Object: |
|
---|
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 FrameAvailableListener
listener was called.
Generic approach:
readFrame()
to get first frame.FrameAvailableListener
listener.readFrame()
to get second frame.FrameAvailableListener
listener.Instead of polling this function you can also use the FrameListener
listener.
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
(int frameDuration)¶Parameters: |
|
---|
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
()¶Returns: |
|
---|
Returns the frame duration as set by setFrameDuration()
.
BrickletDMX.
getFrameErrorCount
()¶Return Object: |
|
---|
Returns the current number of overrun and framing errors.
BrickletDMX.
setCommunicationLEDConfig
(int config)¶Parameters: |
|
---|
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
()¶Returns: |
|
---|
Returns the configuration as set by setCommunicationLEDConfig()
The following constants are available for this function:
For config:
BrickletDMX.
setErrorLEDConfig
(int config)¶Parameters: |
|
---|
Sets the error LED configuration.
By default the error LED turns on if there is any error (see FrameErrorCountListener
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
()¶Returns: |
|
---|
Returns the configuration as set by setErrorLEDConfig()
.
The following constants are available for this function:
For config:
BrickletDMX.
getSPITFPErrorCount
()¶Return Object: |
|
---|
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
(int config)¶Parameters: |
|
---|
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
()¶Returns: |
|
---|
Returns the configuration as set by setStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletDMX.
getChipTemperature
()¶Returns: |
|
---|
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
()¶Return Object: |
|
---|
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
(boolean frameStartedCallbackEnabled, boolean frameAvailableCallbackEnabled, boolean frameCallbackEnabled, boolean frameErrorCountCallbackEnabled)¶Parameters: |
|
---|
Enables/Disables the different listeners. By default the
FrameStartedListener
listener and FrameAvailableListener
listener are enabled while
the FrameListener
listener and FrameErrorCountListener
listener are disabled.
If you want to use the FrameListener
listener you can enable it and disable
the FrameAvailableListener
listener at the same time. It becomes redundant in
this case.
BrickletDMX.
getFrameCallbackConfig
()¶Return Object: |
|
---|
Returns the frame listener config as set by setFrameCallbackConfig()
.
Listeners can be registered to receive
time critical or recurring data from the device. The registration is done
with add*Listener()
functions of the device object.
The parameter is a listener class object, for example:
device.addExampleListener(new BrickletDMX.ExampleListener() {
public void property(int value) {
System.out.println("Value: " + value);
}
});
The available listener classes with inherent methods to be overwritten
are described below. It is possible to add several listeners and
to remove them with the corresponding remove*Listener()
function.
Note
Using listeners 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.
FrameStartedListener
()¶This listener can be added with the addFrameStartedListener()
function.
An added listener can be removed with the removeFrameStartedListener()
function.
frameStarted
()This listener is triggered as soon as a new frame write is started. You should send the data for the next frame directly after this listener was triggered.
For an explanation of the general approach see writeFrame()
.
This listener can be enabled via setFrameCallbackConfig()
.
This listener can only be triggered in master mode.
BrickletDMX.
FrameAvailableListener
()¶This listener can be added with the addFrameAvailableListener()
function.
An added listener can be removed with the removeFrameAvailableListener()
function.
frameAvailable
(long frameNumber)Parameters: |
|
---|
This listener 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 listener can be enabled via setFrameCallbackConfig()
.
This listener can only be triggered in slave mode.
BrickletDMX.
FrameListener
()¶This listener can be added with the addFrameListener()
function.
An added listener can be removed with the removeFrameListener()
function.
frame
(int[] frame, long frameNumber)Parameters: |
|
---|
This listener 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 listener can be enabled via setFrameCallbackConfig()
.
This listener can only be triggered in slave mode.
Note
If reconstructing the value fails, the listener is triggered with null for frame.
BrickletDMX.
FrameErrorCountListener
()¶This listener can be added with the addFrameErrorCountListener()
function.
An added listener can be removed with the removeFrameErrorCountListener()
function.
frameErrorCount
(long overrunErrorCount, long framingErrorCount)Parameters: |
|
---|
This listener 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
()¶Return Object: |
|
---|
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
(byte functionId)¶Parameters: |
|
---|---|
Returns: |
|
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 listener 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
(byte functionId, boolean responseExpected)¶Parameters: |
|
---|
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 listener 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
(boolean responseExpected)¶Parameters: |
|
---|
Changes the response expected flag for all setter and listener 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
(int mode)¶Parameters: |
|
---|---|
Returns: |
|
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
()¶Returns: |
|
---|
Returns the current bootloader mode, see setBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletDMX.
setWriteFirmwarePointer
(long pointer)¶Parameters: |
|
---|
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
(int[] data)¶Parameters: |
|
---|---|
Returns: |
|
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
(long uid)¶Parameters: |
|
---|
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
()¶Returns: |
|
---|
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.EnumerateListener
listener 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.