This is the description of the Java API bindings for the RS232 Bricklet 2.0. General information and technical specifications for the RS232 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 (ExampleLoopback.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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletRS232V2;
// For this example connect the RX1 and TX pin to receive the send message
public class ExampleLoopback {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XYZ to the UID of your RS232 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
BrickletRS232V2 rs232 = new BrickletRS232V2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Add read listener
rs232.addReadListener(new BrickletRS232V2.ReadListener() {
public void read(char[] message) {
// Assume that the message consists of ASCII characters and
// convert it from an array of chars to a string
System.out.println("Message: \"" + new String(message) + "\"");
}
});
// Enable read callback
rs232.enableReadCallback();
// Write "test" string
rs232.write("test".toCharArray());
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.
BrickletRS232V2
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickletRS232V2 rs232V2 = new BrickletRS232V2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletRS232V2.
write
(char[] message)¶Parameters: |
|
---|---|
Returns: |
|
Writes characters to the RS232 interface. The characters can be binary data, ASCII or similar is not necessary.
The return value is the number of characters that were written.
See setConfiguration()
for configuration possibilities
regarding baud rate, parity and so on.
BrickletRS232V2.
read
(int length)¶Parameters: |
|
---|---|
Returns: |
|
Returns up to length characters from receive buffer.
Instead of polling with this function, you can also use
callbacks. But note that this function will return available
data only when the read listener is disabled.
See enableReadCallback()
and ReadListener
listener.
BrickletRS232V2.
setConfiguration
(long baudrate, int parity, int stopbits, int wordlength, int flowcontrol)¶Parameters: |
|
---|
Sets the configuration for the RS232 communication.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
BrickletRS232V2.
getConfiguration
()¶Return Object: |
|
---|
Returns the configuration as set by setConfiguration()
.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
BrickletRS232V2.
setBufferConfig
(int sendBufferSize, int receiveBufferSize)¶Parameters: |
|
---|
Sets the send and receive buffer size in byte. In total the buffers have to be 10240 byte (10KiB) in size, the minimum buffer size is 1024 byte (1KiB) for each.
The current buffer content is lost if this function is called.
The send buffer holds data that is given by write()
and
can not be written yet. The receive buffer holds data that is
received through RS232 but could not yet be send to the
user, either by read()
or through ReadListener
listener.
BrickletRS232V2.
getBufferConfig
()¶Return Object: |
|
---|
Returns the buffer configuration as set by setBufferConfig()
.
BrickletRS232V2.
getBufferStatus
()¶Return Object: |
|
---|
Returns the currently used bytes for the send and received buffer.
See setBufferConfig()
for buffer size configuration.
BrickletRS232V2.
getErrorCount
()¶Return Object: |
|
---|
Returns the current number of overrun and parity errors.
BrickletRS232V2.
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.
BrickletRS232V2.
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:
BrickletRS232V2.
getStatusLEDConfig
()¶Returns: |
|
---|
Returns the configuration as set by setStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletRS232V2.
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.
BrickletRS232V2.
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!
BrickletRS232V2.
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.
BrickletRS232V2.
enableReadCallback
()¶Enables the ReadListener
listener. This will disable the FrameReadableListener
listener.
By default the listener is disabled.
BrickletRS232V2.
disableReadCallback
()¶Disables the ReadListener
listener.
By default the listener is disabled.
BrickletRS232V2.
isReadCallbackEnabled
()¶Returns: |
|
---|
Returns true if the ReadListener
listener is enabled,
false otherwise.
BrickletRS232V2.
setFrameReadableCallbackConfiguration
(int frameSize)¶Parameters: |
|
---|
Configures the FrameReadableListener
listener. The frame size is the number of bytes, that have to be readable to trigger the listener.
A frame size of 0 disables the listener. A frame size greater than 0 enables the listener and disables the ReadListener
listener.
By default the listener is disabled.
New in version 2.0.3 (Plugin).
BrickletRS232V2.
getFrameReadableCallbackConfiguration
()¶Returns: |
|
---|
Returns the listener configuration as set by setFrameReadableCallbackConfiguration()
.
New in version 2.0.3 (Plugin).
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 BrickletRS232V2.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.
BrickletRS232V2.
ReadListener
()¶This listener can be added with the addReadListener()
function.
An added listener can be removed with the removeReadListener()
function.
read
(char[] message)Parameters: |
|
---|
This listener is called if new data is available.
To enable this listener, use enableReadCallback()
.
Note
If reconstructing the value fails, the listener is triggered with null for message.
BrickletRS232V2.
ErrorCountListener
()¶This listener can be added with the addErrorCountListener()
function.
An added listener can be removed with the removeErrorCountListener()
function.
errorCount
(long errorCountOverrun, long errorCountParity)Parameters: |
|
---|
This listener is called if a new error occurs. It returns the current overrun and parity error count.
BrickletRS232V2.
FrameReadableListener
()¶This listener can be added with the addFrameReadableListener()
function.
An added listener can be removed with the removeFrameReadableListener()
function.
frameReadable
(int frameCount)Parameters: |
|
---|
This listener is called if at least one frame of data is readable. The frame size is configured with setFrameReadableCallbackConfiguration()
.
The frame count parameter is the number of frames that can be read.
This listener is triggered only once until read()
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the read()
function, every time the listener triggers without checking the frame count parameter.
New in version 2.0.3 (Plugin).
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.
BrickletRS232V2.
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.
BrickletRS232V2.
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:
BrickletRS232V2.
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:
BrickletRS232V2.
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.
BrickletRS232V2.
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:
BrickletRS232V2.
getBootloaderMode
()¶Returns: |
|
---|
Returns the current bootloader mode, see setBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletRS232V2.
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.
BrickletRS232V2.
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.
BrickletRS232V2.
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.
BrickletRS232V2.
readUID
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletRS232V2.
DEVICE_IDENTIFIER
¶This constant is used to identify a RS232 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.
BrickletRS232V2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a RS232 Bricklet 2.0.