This is the description of the Shell 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 Shell API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example-loopback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
# For this example connect the RX1 and TX pin to receive the send message
uid=XYZ # Change XYZ to the UID of your RS232 Bricklet
# Handle incoming read callbacks
tinkerforge dispatch rs232-bricklet $uid read &
# Enable read callback
tinkerforge call rs232-bricklet $uid enable-read-callback
# Write "test" string
tinkerforge call rs232-bricklet $uid write t,e,s,t,.. 4
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Possible exit codes for all tinkerforge
commands are:
argparse
module is missingThe common options of the call
and dispatch
commands are documented
here. The specific command structure is shown below.
call
rs232-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the RS232 Bricklet. It can take several
options:
--help
shows help for the specific call
command and exits--list-functions
shows a list of known functions of the RS232 Bricklet and exitsdispatch
rs232-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the RS232 Bricklet. It can
take several options:
--help
shows help for the specific dispatch
command and exits--list-callbacks
shows a list of known callbacks of the RS232 Bricklet and exitsrs232-bricklet
<uid> <function>
[<option>..] [<argument>..]¶Parameters: |
|
---|
The <function>
to be called can take different options depending of its
kind. All functions can take the following options:
--help
shows help for the specific function and exitsGetter functions can take the following options:
--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response
requests response and waits for itThe --expect-response
option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
rs232-bricklet
<uid> <callback>
[<option>..]¶Parameters: |
|
---|
The <callback>
to be dispatched can take several options:
--help
shows help for the specific callback and exits--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)rs232-bricklet
<uid> write
<message> <length>¶Parameters: |
|
---|---|
Output: |
|
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 set-configuration
for configuration possibilities
regarding baudrate, parity and so on.
rs232-bricklet
<uid> read
¶Output: |
|
---|
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 enable-read-callback
and read
callback.
rs232-bricklet
<uid> set-configuration
<baudrate> <parity> <stopbits> <wordlength> <hardware-flowcontrol> <software-flowcontrol>¶Parameters: |
|
---|---|
Output: |
|
Sets the configuration for the RS232 communication.
Hard-/Software flow control can either be on or off but not both simultaneously on.
The following symbols are available for this function:
For <baudrate>:
For <parity>:
For <stopbits>:
For <wordlength>:
For <hardware-flowcontrol>:
For <software-flowcontrol>:
rs232-bricklet
<uid> get-configuration
¶Output: |
|
---|
Returns the configuration as set by set-configuration
.
The following symbols are available for this function:
For baudrate:
For parity:
For stopbits:
For wordlength:
For hardware-flowcontrol:
For software-flowcontrol:
rs232-bricklet
<uid> set-break-condition
<break-time>¶Parameters: |
|
---|---|
Output: |
|
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).
rs232-bricklet
<uid> read-frame
¶Output: |
|
---|
Returns up to one frame of bytes from the read buffer.
The frame size is configured with set-frame-readable-callback-configuration
.
If the returned length is 0, no new data was available.
New in version 2.0.4 (Plugin).
rs232-bricklet
<uid> get-identity
¶Output: |
|
---|
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.
rs232-bricklet
<uid> enable-read-callback
¶Output: |
|
---|
Enables the read
callback. This will disable the frame-readable
callback.
By default the callback is disabled.
rs232-bricklet
<uid> disable-read-callback
¶Output: |
|
---|
Disables the read
callback.
By default the callback is disabled.
rs232-bricklet
<uid> is-read-callback-enabled
¶Output: |
|
---|
Returns true if the read
callback is enabled,
false otherwise.
rs232-bricklet
<uid> set-frame-readable-callback-configuration
<frame-size>¶Parameters: |
|
---|---|
Output: |
|
Configures the frame-readable
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 read
callback.
By default the callback is disabled.
New in version 2.0.4 (Plugin).
rs232-bricklet
<uid> get-frame-readable-callback-configuration
¶Output: |
|
---|
Returns the callback configuration as set by set-frame-readable-callback-configuration
.
New in version 2.0.4 (Plugin).
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch rs232-bricklet <uid> example
The available callbacks 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.
rs232-bricklet
<uid> read
Output: |
|
---|
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 enable-read-callback
.
rs232-bricklet
<uid> error
¶Output: |
|
---|
This callback is called if an error occurs. Possible errors are overrun, parity or framing error.
The following symbols are available for this function:
For error:
New in version 2.0.1 (Plugin).
rs232-bricklet
<uid> frame-readable
¶Output: |
|
---|
This callback is called if at least one frame of data is readable. The frame size is configured with set-frame-readable-callback-configuration
.
The frame count parameter is the number of frames that can be read.
This callback is triggered only once until read
or read-frame
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the read-frame
function, every time the callback triggers without checking the frame count parameter.
New in version 2.0.4 (Plugin).