This is the description of the Go 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 Go API bindings is part of their general description. Additional documentation can be found on godoc.org.
The example code below is Public Domain (CC0 1.0).
Download (example_loopback.go)
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 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"github.com/Tinkerforge/go-api-bindings/rs232_bricklet"
)
// For this example connect the RX1 and TX pin to receive the send message
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your RS232 Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
rs232, _ := rs232_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
rs232.RegisterReadCallback(func(message [60]rune, length uint8) {
fmt.Println("Message (Length %d) %s", length, string(message[:length]))
})
// Enable read callback
rs232.EnableReadCallback()
var chars [60]rune
testChars := []rune{'t', 'e', 's', 't'}
copy(chars[:], testChars)
rs232.Write(chars, 4)
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
The RS232 Bricklet's API is defined in the package github.com/Tinkerforge/go-api-bindings/rs232_bricklet
Nearly every function of the Go bindings can return an BrickletError, implementing the error interface. The error can have one of the following values:
which correspond to the values returned from Bricks and Bricklets.
All functions listed below are thread-safe.
Creates a new RS232Bricklet object with the unique device ID uid and adds it to the IPConnection ipcon:
This device object can be used after the IP connection has been connected (see examples above).
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 (*RS232Bricklet) SetConfiguration for configuration possibilities regarding baudrate, parity and so on.
Returns the currently buffered message. The maximum length of message is 60. If the length is given as 0, there was no new data available.
Instead of polling with this function, you can also use callbacks. See (*RS232Bricklet) EnableReadCallback and (*RS232Bricklet) RegisterReadCallback callback.
Sets the configuration for the RS232 communication. Available options:
The default is: 115200 baud, parity none, 1 stop bit, word length 8, hard-/software flow control off.
The following constants are available for this function:
Returns the configuration as set by (*RS232Bricklet) SetConfiguration.
The following constants are available for this function:
Sets a break condition (the TX output is forced to a logic 0 state). The parameter sets the hold-time of the break condition (in ms).
New in version 2.0.2 (Plugin).
Returns the version of the API definition (major, minor, revision) 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.
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 (*RS232Bricklet) 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 send and errors are silently ignored, because they cannot be detected.
See (*RS232Bricklet) SetResponseExpected for the list of function ID constants available for this function.
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 send and errors are silently ignored, because they cannot be detected.
The following function ID constants are available for this function:
Changes the response expected flag for all setter and callback configuration functions of this device at once.
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' or 'd'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
Enables the (*RS232Bricklet) RegisterReadCallback callback.
By default the callback is disabled.
Disables the (*RS232Bricklet) RegisterReadCallback callback.
By default the callback is disabled.
Returns true if the (*RS232Bricklet) RegisterReadCallback callback is enabled, false otherwise.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding Register*Callback function, which returns a unique callback ID. This ID can be used to deregister the callback later.
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.
A callback can be registered for this event with the RegisterReadCallback() function. This function returns the ID of the registered callback. An added callback can be removed with the DeregisterReadCallback(callbackID uint64) function.
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 (*RS232Bricklet) EnableReadCallback.
A callback can be registered for this event with the RegisterErrorCallback() function. This function returns the ID of the registered callback. An added callback can be removed with the DeregisterErrorCallback(callbackID uint64) function.
This callback is called if an error occurs. Possible errors are overrun, parity or framing error.
The following constants are available for this function:
New in version 2.0.1 (Plugin).
This constant is used to identify a RS232 Bricklet.
The (*RS232Bricklet) GetIdentity function and the (*IPConnection) RegisterEnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.
This constant represents the human readable name of a RS232 Bricklet.