This is the description of the Java API bindings for the Thermocouple Bricklet 2.0. General information and technical specifications for the Thermocouple 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).
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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletThermocoupleV2;
public class ExampleSimple {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your Thermocouple 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
BrickletThermocoupleV2 t = new BrickletThermocoupleV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Get current temperature
int temperature = t.getTemperature(); // Can throw com.tinkerforge.TimeoutException
System.out.println("Temperature: " + temperature/100.0 + " °C");
System.out.println("Press key to exit"); System.in.read();
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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletThermocoupleV2;
public class ExampleCallback {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your Thermocouple 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
BrickletThermocoupleV2 t = new BrickletThermocoupleV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Add temperature listener
t.addTemperatureListener(new BrickletThermocoupleV2.TemperatureListener() {
public void temperature(int temperature) {
System.out.println("Temperature: " + temperature/100.0 + " °C");
}
});
// Set period for temperature callback to 1s (1000ms) without a threshold
t.setTemperatureCallbackConfiguration(1000, false, 'x', 0, 0);
System.out.println("Press key to exit"); System.in.read();
ipcon.disconnect();
}
}
|
Download (ExampleThreshold.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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletThermocoupleV2;
public class ExampleThreshold {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your Thermocouple 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
BrickletThermocoupleV2 t = new BrickletThermocoupleV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Add temperature listener
t.addTemperatureListener(new BrickletThermocoupleV2.TemperatureListener() {
public void temperature(int temperature) {
System.out.println("Temperature: " + temperature/100.0 + " °C");
}
});
// Configure threshold for temperature "greater than 30 °C"
// with a debounce period of 10s (10000ms)
t.setTemperatureCallbackConfiguration(10000, false, '>', 30*100, 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.
BrickletThermocoupleV2
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickletThermocoupleV2 thermocoupleV2 = new BrickletThermocoupleV2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletThermocoupleV2.
getTemperature
()¶Returns: |
|
---|
Returns the temperature of the thermocouple. The value is given in °C/100, e.g. a value of 4223 means that a temperature of 42.23 °C is measured.
If you want to get the temperature periodically, it is recommended
to use the TemperatureListener
listener and set the period with
setTemperatureCallbackConfiguration()
.
If you want to get the value periodically, it is recommended to use the
TemperatureListener
listener. You can set the listener configuration
with setTemperatureCallbackConfiguration()
.
BrickletThermocoupleV2.
setConfiguration
(int averaging, int thermocoupleType, int filter)¶Parameters: |
|
---|
You can configure averaging size, thermocouple type and frequency filtering.
Available averaging sizes are 1, 2, 4, 8 and 16 samples.
As thermocouple type you can use B, E, J, K, N, R, S and T. If you have a different thermocouple or a custom thermocouple you can also use G8 and G32. With these types the returned value will not be in °C/100, it will be calculated by the following formulas:
value = 8 * 1.6 * 2^17 * Vin
value = 32 * 1.6 * 2^17 * Vin
where Vin is the thermocouple input voltage.
The frequency filter can be either configured to 50Hz or to 60Hz. You should configure it according to your utility frequency.
The conversion time depends on the averaging and filter configuration, it can be calculated as follows:
time = 82 + (samples - 1) * 16.67
time = 98 + (samples - 1) * 20
The following constants are available for this function:
For averaging:
For thermocoupleType:
For filter:
BrickletThermocoupleV2.
getConfiguration
()¶Return Object: |
|
---|
Returns the configuration as set by setConfiguration()
.
The following constants are available for this function:
For averaging:
For thermocoupleType:
For filter:
BrickletThermocoupleV2.
getErrorState
()¶Return Object: |
|
---|
Returns the current error state. There are two possible errors:
Over/Under Voltage happens for voltages below 0V or above 3.3V. In this case it is very likely that your thermocouple is defective. An Open Circuit error indicates that there is no thermocouple connected.
You can use the ErrorStateListener
listener to automatically get triggered
when the error state changes.
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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:
BrickletThermocoupleV2.
getStatusLEDConfig
()¶Returns: |
|
---|
Returns the configuration as set by setStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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!
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
setTemperatureCallbackConfiguration
(long period, boolean valueHasToChange, char option, int min, int max)¶Parameters: |
|
---|
The period is the period with which the TemperatureListener
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.
It is furthermore possible to constrain the listener with thresholds.
The option-parameter together with min/max sets a threshold for the TemperatureListener
listener.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the listener is triggered with the fixed period.
The following constants are available for this function:
For option:
BrickletThermocoupleV2.
getTemperatureCallbackConfiguration
()¶Return Object: |
|
---|
Returns the listener configuration as set by setTemperatureCallbackConfiguration()
.
The following constants are available for this function:
For option:
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 BrickletThermocoupleV2.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.
BrickletThermocoupleV2.
TemperatureListener
()¶This listener can be added with the addTemperatureListener()
function.
An added listener can be removed with the removeTemperatureListener()
function.
temperature
(int temperature)Parameters: |
|
---|
This listener is triggered periodically according to the configuration set by
setTemperatureCallbackConfiguration()
.
The parameter is the same as getTemperature()
.
BrickletThermocoupleV2.
ErrorStateListener
()¶This listener can be added with the addErrorStateListener()
function.
An added listener can be removed with the removeErrorStateListener()
function.
errorState
(boolean overUnder, boolean openCircuit)Parameters: |
|
---|
This Listener is triggered every time the error state changes
(see getErrorState()
).
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.
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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:
BrickletThermocoupleV2.
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:
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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:
BrickletThermocoupleV2.
getBootloaderMode
()¶Returns: |
|
---|
Returns the current bootloader mode, see setBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
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.
BrickletThermocoupleV2.
readUID
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletThermocoupleV2.
DEVICE_IDENTIFIER
¶This constant is used to identify a Thermocouple 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.
BrickletThermocoupleV2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Thermocouple Bricklet 2.0.