This is the description of the Delphi/Lazarus 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 Delphi/Lazarus API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (ExampleLoopback.pas)
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 63 64 65 66 67 68 69 | program ExampleLoopback;
{ For this example connect the RX1 and TX pin to receive the send message }
{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}
uses
SysUtils, IPConnection, BrickletRS232V2;
type
TExample = class
private
ipcon: TIPConnection;
rs232: TBrickletRS232V2;
public
procedure ReadCB(sender: TBrickletRS232V2; const message_: TArrayOfChar);
procedure Execute;
end;
const
HOST = 'localhost';
PORT = 4223;
UID = 'XYZ'; { Change XYZ to the UID of your RS232 Bricklet 2.0 }
var
e: TExample;
{ Callback procedure for read callback }
procedure TExample.ReadCB(sender: TBrickletRS232V2; const message_: TArrayOfChar);
var str: string;
begin
{ Assume that the message consists of ASCII characters and
convert it from an array of chars to a string }
SetString(str, PChar(@message_[0]), Length(message_));
WriteLn(Format('Message: "%s"', [str]));
end;
procedure TExample.Execute;
begin
{ Create IP connection }
ipcon := TIPConnection.Create;
{ Create device object }
rs232 := TBrickletRS232V2.Create(UID, ipcon);
{ Connect to brickd }
ipcon.Connect(HOST, PORT);
{ Don't use device before ipcon is connected }
{ Register read callback to procedure ReadCB }
rs232.OnRead := {$ifdef FPC}@{$endif}ReadCB;
{ Enable read callback }
rs232.EnableReadCallback;
{ Write "test" string }
rs232.Write(['t', 'e', 's', 't']);
WriteLn('Press key to exit');
ReadLn;
ipcon.Destroy; { Calls ipcon.Disconnect internally }
end;
begin
e := TExample.Create;
e.Execute;
e.Destroy;
end.
|
Since Delphi does not support multiple return values directly, we use the
out
keyword to return multiple values from a function.
All functions and procedures listed below are thread-safe.
TBrickletRS232V2.
Create
(const uid: string; ipcon: TIPConnection)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
rs232V2 := TBrickletRS232V2.Create('YOUR_DEVICE_UID', ipcon);
This object can then be used after the IP Connection is connected.
TBrickletRS232V2.
Write
(const message: array of char): word¶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.
TBrickletRS232V2.
Read
(const length: word): array of char¶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 callback is disabled.
See EnableReadCallback
and OnRead
callback.
TBrickletRS232V2.
SetConfiguration
(const baudrate: longword; const parity: byte; const stopbits: byte; const wordlength: byte; const flowcontrol: byte)¶Parameters: |
|
---|
Sets the configuration for the RS232 communication.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
TBrickletRS232V2.
GetConfiguration
(out baudrate: longword; out parity: byte; out stopbits: byte; out wordlength: byte; out flowcontrol: byte)¶Output Parameters: |
|
---|
Returns the configuration as set by SetConfiguration
.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For flowcontrol:
TBrickletRS232V2.
SetBufferConfig
(const sendBufferSize: word; const receiveBufferSize: word)¶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 OnRead
callback.
TBrickletRS232V2.
GetBufferConfig
(out sendBufferSize: word; out receiveBufferSize: word)¶Output Parameters: |
|
---|
Returns the buffer configuration as set by SetBufferConfig
.
TBrickletRS232V2.
GetBufferStatus
(out sendBufferUsed: word; out receiveBufferUsed: word)¶Output Parameters: |
|
---|
Returns the currently used bytes for the send and received buffer.
See SetBufferConfig
for buffer size configuration.
TBrickletRS232V2.
GetErrorCount
(out errorCountOverrun: longword; out errorCountParity: longword)¶Output Parameters: |
|
---|
Returns the current number of overrun and parity errors.
TBrickletRS232V2.
GetSPITFPErrorCount
(out errorCountAckChecksum: longword; out errorCountMessageChecksum: longword; out errorCountFrame: longword; out errorCountOverflow: longword)¶Output Parameters: |
|
---|
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.
TBrickletRS232V2.
SetStatusLEDConfig
(const config: byte)¶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:
TBrickletRS232V2.
GetStatusLEDConfig
: byte¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig
The following constants are available for this function:
For config:
TBrickletRS232V2.
GetChipTemperature
: smallint¶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.
TBrickletRS232V2.
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!
TBrickletRS232V2.
GetIdentity
(out uid: string; out connectedUid: string; out position: char; out hardwareVersion: array [0..2] of byte; out firmwareVersion: array [0..2] of byte; out deviceIdentifier: word)¶Output Parameters: |
|
---|
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.
TBrickletRS232V2.
EnableReadCallback
¶Enables the OnRead
callback. This will disable the OnFrameReadable
callback.
By default the callback is disabled.
TBrickletRS232V2.
DisableReadCallback
¶Disables the OnRead
callback.
By default the callback is disabled.
TBrickletRS232V2.
IsReadCallbackEnabled
: boolean¶Returns: |
|
---|
Returns true if the OnRead
callback is enabled,
false otherwise.
TBrickletRS232V2.
SetFrameReadableCallbackConfiguration
(const frameSize: word)¶Parameters: |
|
---|
Configures the OnFrameReadable
callback. The frame size is the number of bytes, that have to be readable to trigger the callback.
A frame size of 0 disables the callback. A frame size greater than 0 enables the callback and disables the OnRead
callback.
By default the callback is disabled.
New in version 2.0.3 (Plugin).
TBrickletRS232V2.
GetFrameReadableCallbackConfiguration
: word¶Returns: |
|
---|
Returns the callback configuration as set by SetFrameReadableCallbackConfiguration
.
New in version 2.0.3 (Plugin).
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a procedure to an callback property of the device object:
procedure TExample.MyCallback(sender: TBrickletRS232V2; const value: longint); begin WriteLn(Format('Value: %d', [value])); end; rs232V2.OnExample := {$ifdef FPC}@{$endif}example.MyCallback;
The available callback properties and their parameter types 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.
TBrickletRS232V2.
OnRead
¶procedure(sender: TBrickletRS232V2; const message: array of char) of object;
Callback Parameters: |
|
---|
This callback is called if new data is available.
To enable this callback, use EnableReadCallback
.
Note
If reconstructing the value fails, the callback is triggered with nil for message.
TBrickletRS232V2.
OnErrorCount
¶procedure(sender: TBrickletRS232V2; const errorCountOverrun: longword; const errorCountParity: longword) of object;
Callback Parameters: |
|
---|
This callback is called if a new error occurs. It returns the current overrun and parity error count.
TBrickletRS232V2.
OnFrameReadable
¶procedure(sender: TBrickletRS232V2; const frameCount: word) of object;
Callback Parameters: |
|
---|
This callback 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 callback 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 callback 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.
TBrickletRS232V2.
GetAPIVersion
: array [0..2] of byte¶Output Parameters: |
|
---|
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.
TBrickletRS232V2.
GetResponseExpected
(const functionId: byte): boolean¶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 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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For functionId:
TBrickletRS232V2.
SetResponseExpected
(const functionId: byte; const responseExpected: boolean)¶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 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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For functionId:
TBrickletRS232V2.
SetResponseExpectedAll
(const responseExpected: boolean)¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback 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.
TBrickletRS232V2.
SetBootloaderMode
(const mode: byte): byte¶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:
TBrickletRS232V2.
GetBootloaderMode
: byte¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode
.
The following constants are available for this function:
For mode:
TBrickletRS232V2.
SetWriteFirmwarePointer
(const pointer: longword)¶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.
TBrickletRS232V2.
WriteFirmware
(const data: array [0..63] of byte): byte¶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.
TBrickletRS232V2.
WriteUID
(const uid: longword)¶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.
TBrickletRS232V2.
ReadUID
: longword¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BRICKLET_RS232_V2_DEVICE_IDENTIFIER
¶This constant is used to identify a RS232 Bricklet 2.0.
The GetIdentity
function and the
TIPConnection.OnEnumerate
callback of the IP Connection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
BRICKLET_RS232_V2_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a RS232 Bricklet 2.0.