This is the description of the Delphi/Lazarus API bindings for the RS232 Bricklet. General information and technical specifications for the RS232 Bricklet 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 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 | 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, BrickletRS232;
type
TExample = class
private
ipcon: TIPConnection;
rs232: TBrickletRS232;
public
function StringToCharArray(const message_: string): TArray0To59OfChar;
function CharArrayToString(const message_: TArray0To59OfChar; const length_: byte): string;
procedure ReadCB(sender: TBrickletRS232; const message_: TArray0To59OfChar;
const length_: byte);
procedure Execute;
end;
const
HOST = 'localhost';
PORT = 4223;
UID = 'XYZ'; { Change XYZ to the UID of your RS232 Bricklet }
var
e: TExample;
{ Convert string to char array with length 60, as needed by write }
function TExample.StringToCharArray(const message_: string): TArray0To59OfChar;
var i: longint;
begin
FillChar(result, 60, 0);
for i := 1 to Length(message_) do begin
result[i - 1] := message_[i];
end;
end;
{ Assume that the message consists of ASCII characters and convert it from
an array of chars to a string }
function TExample.CharArrayToString(const message_: TArray0To59OfChar; const length_: byte): string;
begin
SetString(result, PChar(@message_[0]), length_);
end;
{ Callback procedure for read callback }
procedure TExample.ReadCB(sender: TBrickletRS232; const message_: TArray0To59OfChar;
const length_: byte);
begin
WriteLn(Format('Message (Length: %d): "%s"', [length_, CharArrayToString(message_, length_)]));
end;
procedure TExample.Execute;
begin
{ Create IP connection }
ipcon := TIPConnection.Create;
{ Create device object }
rs232 := TBrickletRS232.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(StringToCharArray('test'), 4);
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.
TBrickletRS232.
Create
(const uid: string; ipcon: TIPConnection)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
rs232 := TBrickletRS232.Create('YOUR_DEVICE_UID', ipcon);
This object can then be used after the IP Connection is connected.
TBrickletRS232.
Write
(const message: array [0..59] of char; const length: byte): byte¶Parameters: |
|
---|---|
Returns: |
|
Writes a string of up to 60 characters to the RS232 interface. The string can be binary data, ASCII or similar is not necessary.
The length of the string has to be given as an additional parameter.
The return value is the number of bytes that could be written.
See SetConfiguration
for configuration possibilities
regarding baudrate, parity and so on.
TBrickletRS232.
Read
(out message: array [0..59] of char; out length: byte)¶Output Parameters: |
|
---|
Returns the currently buffered message. The maximum length of message is 60. If the returned length is 0, no new data was available.
Instead of polling with this function, you can also use
callbacks. See EnableReadCallback
and OnRead
callback.
TBrickletRS232.
SetConfiguration
(const baudrate: byte; const parity: byte; const stopbits: byte; const wordlength: byte; const hardwareFlowcontrol: byte; const softwareFlowcontrol: byte)¶Parameters: |
|
---|
Sets the configuration for the RS232 communication.
Hard-/Software flow control can either be on or off but not both simultaneously on.
The following constants are available for this function:
For baudrate:
For parity:
For stopbits:
For wordlength:
For hardwareFlowcontrol:
For softwareFlowcontrol:
TBrickletRS232.
GetConfiguration
(out baudrate: byte; out parity: byte; out stopbits: byte; out wordlength: byte; out hardwareFlowcontrol: byte; out softwareFlowcontrol: byte)¶Output Parameters: |
|
---|
Returns the configuration as set by SetConfiguration
.
The following constants are available for this function:
For baudrate:
For parity:
For stopbits:
For wordlength:
For hardwareFlowcontrol:
For softwareFlowcontrol:
TBrickletRS232.
SetBreakCondition
(const breakTime: word)¶Parameters: |
|
---|
Sets a break condition (the TX output is forced to a logic 0 state). The parameter sets the hold-time of the break condition.
New in version 2.0.2 (Plugin).
TBrickletRS232.
ReadFrame
(out message: array [0..59] of char; out length: byte)¶Output Parameters: |
|
---|
Returns up to one frame of bytes from the read buffer.
The frame size is configured with SetFrameReadableCallbackConfiguration
.
If the returned length is 0, no new data was available.
New in version 2.0.4 (Plugin).
TBrickletRS232.
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.
TBrickletRS232.
EnableReadCallback
¶Enables the OnRead
callback. This will disable the OnFrameReadable
callback.
By default the callback is disabled.
TBrickletRS232.
DisableReadCallback
¶Disables the OnRead
callback.
By default the callback is disabled.
TBrickletRS232.
IsReadCallbackEnabled
: boolean¶Returns: |
|
---|
Returns true if the OnRead
callback is enabled,
false otherwise.
TBrickletRS232.
SetFrameReadableCallbackConfiguration
(const frameSize: byte)¶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.4 (Plugin).
TBrickletRS232.
GetFrameReadableCallbackConfiguration
: byte¶Returns: |
|
---|
Returns the callback configuration as set by SetFrameReadableCallbackConfiguration
.
New in version 2.0.4 (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: TBrickletRS232; const value: longint); begin WriteLn(Format('Value: %d', [value])); end; rs232.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.
TBrickletRS232.
OnRead
¶procedure(sender: TBrickletRS232; const message: array [0..59] of char; const length: byte) of object;
Callback Parameters: |
|
---|
This callback is called if new data is available. The message has a maximum size of 60 characters. The actual length of the message is given in addition.
To enable this callback, use EnableReadCallback
.
TBrickletRS232.
OnError
¶procedure(sender: TBrickletRS232; const error: byte) of object;
Callback Parameters: |
|
---|
This callback is called if an error occurs. Possible errors are overrun, parity or framing error.
The following constants are available for this function:
For error:
New in version 2.0.1 (Plugin).
TBrickletRS232.
OnFrameReadable
¶procedure(sender: TBrickletRS232; const frameCount: byte) 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
or ReadFrame
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the ReadFrame
function, every time the callback triggers without checking the frame count parameter.
New in version 2.0.4 (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.
TBrickletRS232.
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.
TBrickletRS232.
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:
TBrickletRS232.
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:
TBrickletRS232.
SetResponseExpectedAll
(const responseExpected: boolean)¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BRICKLET_RS232_DEVICE_IDENTIFIER
¶This constant is used to identify a RS232 Bricklet.
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_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a RS232 Bricklet.