This is the description of the Java API bindings for the DC Bricklet 2.0. General information and technical specifications for the DC Bricklet 2.0 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).
Download (ExampleConfiguration.java)
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 30 31 32 33 34 35 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletDCV2;
public class ExampleConfiguration {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your DC Bricklet 2.0
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
BrickletDCV2 dc = new BrickletDCV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
dc.setDriveMode(BrickletDCV2.DRIVE_MODE_DRIVE_COAST);
dc.setPWMFrequency(10000); // Use PWM frequency of 10 kHz
dc.setMotion(4096,
16384); // Slow acceleration (12.5 %/s), fast decceleration (50 %/s) for stopping
dc.setVelocity(32767); // Full speed forward (100 %)
dc.setEnabled(true); // Enable motor power
System.out.println("Press key to exit"); System.in.read();
dc.setVelocity(0); // Stop motor before disabling motor power
Thread.sleep(2000); // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
dc.setEnabled(false); // Disable motor power
ipcon.disconnect();
}
}
|
Download (ExampleCallback.java)
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 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletDCV2;
import com.tinkerforge.TinkerforgeException;
public class ExampleCallback {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your DC Bricklet 2.0
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
// Note: Declare dc as final, so the listener can access it
final BrickletDCV2 dc = new BrickletDCV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// The acceleration has to be smaller or equal to the maximum
// acceleration of the DC motor, otherwise the velocity reached
// callback will be called too early
dc.setMotion(4096,
16384); // Slow acceleration (12.5 %/s), fast decceleration (50 %/s) for stopping
dc.setVelocity(32767); // Full speed forward (100 %)
// Use velocity reached callback to swing back and forth
// between full speed forward and full speed backward
dc.addVelocityReachedListener(new BrickletDCV2.VelocityReachedListener() {
public void velocityReached(int velocity) {
if(velocity == 32767) {
System.out.println("Velocity: Full speed forward, now turning backward");
try {
dc.setVelocity(-32767);
} catch(TinkerforgeException e) {
}
} else if(velocity == -32767) {
System.out.println("Velocity: Full speed backward, now turning forward");
try {
dc.setVelocity(32767);
} catch(TinkerforgeException e) {
}
} else {
System.out.println("Error"); // Can only happen if another program sets velocity
}
}
});
// Enable motor power
dc.setEnabled(true);
System.out.println("Press key to exit"); System.in.read();
dc.setVelocity(0); // Stop motor before disabling motor power
Thread.sleep(2000); // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
dc.setEnabled(false); // Disable motor power
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.
BrickletDCV2
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickletDCV2 dcV2 = new BrickletDCV2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletDCV2.
setEnabled
(boolean enabled)¶Parameters: |
|
---|
Enables/Disables the driver chip. The driver parameters can be configured (velocity, acceleration, etc) before it is enabled.
BrickletDCV2.
getEnabled
()¶Returns: |
|
---|
Returns true if the driver chip is enabled, false otherwise.
BrickletDCV2.
setVelocity
(int velocity)¶Parameters: |
|
---|
Sets the velocity of the motor. Whereas -32767 is full speed backward,
0 is stop and 32767 is full speed forward. Depending on the
acceleration (see setMotion()
), the motor is not immediately
brought to the velocity but smoothly accelerated.
The velocity describes the duty cycle of the PWM with which the motor is
controlled, e.g. a velocity of 3277 sets a PWM with a 10% duty cycle.
You can not only control the duty cycle of the PWM but also the frequency,
see setPWMFrequency()
.
BrickletDCV2.
getVelocity
()¶Returns: |
|
---|
Returns the velocity as set by setVelocity()
.
BrickletDCV2.
getCurrentVelocity
()¶Returns: |
|
---|
Returns the current velocity of the motor. This value is different
from getVelocity()
whenever the motor is currently accelerating
to a goal set by setVelocity()
.
BrickletDCV2.
setMotion
(int acceleration, int deceleration)¶Parameters: |
|
---|
Sets the acceleration and deceleration of the motor. It is given in velocity/s. An acceleration of 10000 means, that every second the velocity is increased by 10000 (or about 30% duty cycle).
For example: If the current velocity is 0 and you want to accelerate to a velocity of 16000 (about 50% duty cycle) in 10 seconds, you should set an acceleration of 1600.
If acceleration and deceleration is set to 0, there is no speed ramping, i.e. a new velocity is immediately given to the motor.
BrickletDCV2.
getMotion
()¶Return Object: |
|
---|
Returns the acceleration/deceleration as set by setMotion()
.
BrickletDCV2.
fullBrake
()¶Executes an active full brake.
Warning
This function is for emergency purposes, where an immediate brake is necessary. Depending on the current velocity and the strength of the motor, a full brake can be quite violent.
Call setVelocity()
with 0 if you just want to stop the motor.
BrickletDCV2.
getPWMFrequency
()¶Returns: |
|
---|
Returns the PWM frequency as set by setPWMFrequency()
.
BrickletDCV2.
getPowerStatistics
()¶Return Object: |
|
---|
Returns input voltage and current usage of the driver.
BrickletDCV2.
setDriveMode
(int mode)¶Parameters: |
|
---|
Sets the drive mode. Possible modes are:
These modes are different kinds of motor controls.
In Drive/Brake mode, the motor is always either driving or braking. There is no freewheeling. Advantages are: A more linear correlation between PWM and velocity, more exact accelerations and the possibility to drive with slower velocities.
In Drive/Coast mode, the motor is always either driving or freewheeling. Advantages are: Less current consumption and less demands on the motor and driver chip.
The following constants are available for this function:
For mode:
BrickletDCV2.
getDriveMode
()¶Returns: |
|
---|
Returns the drive mode, as set by setDriveMode()
.
The following constants are available for this function:
For mode:
BrickletDCV2.
setPWMFrequency
(int frequency)¶Parameters: |
|
---|
Sets the frequency of the PWM with which the motor is driven. Often a high frequency is less noisy and the motor runs smoother. However, with a low frequency there are less switches and therefore fewer switching losses. Also with most motors lower frequencies enable higher torque.
If you have no idea what all this means, just ignore this function and use the default frequency, it will very likely work fine.
BrickletDCV2.
setErrorLEDConfig
(int config)¶Parameters: |
|
---|
Configures the error LED to be either turned off, turned on, blink in heartbeat mode or show an error.
If the LED is configured to show errors it has three different states:
The following constants are available for this function:
For config:
BrickletDCV2.
getErrorLEDConfig
()¶Returns: |
|
---|
Returns the LED configuration as set by setErrorLEDConfig()
The following constants are available for this function:
For config:
BrickletDCV2.
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.
BrickletDCV2.
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:
BrickletDCV2.
getStatusLEDConfig
()¶Returns: |
|
---|
Returns the configuration as set by setStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletDCV2.
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.
BrickletDCV2.
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!
BrickletDCV2.
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.
BrickletDCV2.
setEmergencyShutdownCallbackConfiguration
(boolean enabled)¶Parameters: |
|
---|
Enable/Disable EmergencyShutdownListener
listener.
BrickletDCV2.
getEmergencyShutdownCallbackConfiguration
()¶Returns: |
|
---|
Returns the listener configuration as set by
setEmergencyShutdownCallbackConfiguration()
.
BrickletDCV2.
setVelocityReachedCallbackConfiguration
(boolean enabled)¶Parameters: |
|
---|
Enable/Disable VelocityReachedListener
listener.
BrickletDCV2.
getVelocityReachedCallbackConfiguration
()¶Returns: |
|
---|
Returns the listener configuration as set by
setVelocityReachedCallbackConfiguration()
.
BrickletDCV2.
setCurrentVelocityCallbackConfiguration
(long period, boolean valueHasToChange)¶Parameters: |
|
---|
The period is the period with which the CurrentVelocityListener
listener is triggered periodically. A value of 0 turns the listener off.
If the value has to change-parameter is set to true, the listener is only triggered after the value has changed. If the value didn't change within the period, the listener is triggered immediately on change.
If it is set to false, the listener is continuously triggered with the period, independent of the value.
BrickletDCV2.
getCurrentVelocityCallbackConfiguration
()¶Return Object: |
|
---|
Returns the listener configuration as set by
setCurrentVelocityCallbackConfiguration()
.
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 BrickletDCV2.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.
BrickletDCV2.
EmergencyShutdownListener
()¶This listener can be added with the addEmergencyShutdownListener()
function.
An added listener can be removed with the removeEmergencyShutdownListener()
function.
emergencyShutdown
()This listener is triggered if either the current consumption is too high (above 5A) or the temperature of the driver chip is too high (above 175°C). These two possibilities are essentially the same, since the temperature will reach this threshold immediately if the motor consumes too much current. In case of a voltage below 3.3V (external or stack) this listener is triggered as well.
If this listener is triggered, the driver chip gets disabled at the same time.
That means, setEnabled()
has to be called to drive the motor again.
Note
This listener only works in Drive/Brake mode (see setDriveMode()
). In
Drive/Coast mode it is unfortunately impossible to reliably read the
overcurrent/overtemperature signal from the driver chip.
BrickletDCV2.
VelocityReachedListener
()¶This listener can be added with the addVelocityReachedListener()
function.
An added listener can be removed with the removeVelocityReachedListener()
function.
velocityReached
(int velocity)Parameters: |
|
---|
This listener is triggered whenever a set velocity is reached. For example:
If a velocity of 0 is present, acceleration is set to 5000 and velocity
to 10000, the VelocityReachedListener
listener will be triggered after about
2 seconds, when the set velocity is actually reached.
Note
Since we can't get any feedback from the DC motor, this only works if the
acceleration (see setMotion()
) is set smaller or equal to the
maximum acceleration of the motor. Otherwise the motor will lag behind the
control value and the listener will be triggered too early.
BrickletDCV2.
CurrentVelocityListener
()¶This listener can be added with the addCurrentVelocityListener()
function.
An added listener can be removed with the removeCurrentVelocityListener()
function.
currentVelocity
(int velocity)Parameters: |
|
---|
This listener is triggered with the period that is set by
setCurrentVelocityCallbackConfiguration()
. The parameter is the current
velocity used by the motor.
The CurrentVelocityListener
listener is only triggered after the set period
if there is a change in the velocity.
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.
BrickletDCV2.
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.
BrickletDCV2.
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:
BrickletDCV2.
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:
BrickletDCV2.
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.
BrickletDCV2.
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:
BrickletDCV2.
getBootloaderMode
()¶Returns: |
|
---|
Returns the current bootloader mode, see setBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletDCV2.
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.
BrickletDCV2.
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.
BrickletDCV2.
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.
BrickletDCV2.
readUID
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletDCV2.
DEVICE_IDENTIFIER
¶This constant is used to identify a DC Bricklet 2.0.
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.
BrickletDCV2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a DC Bricklet 2.0.