This is the description of the Go API bindings for the Isolator Bricklet. General information and technical specifications for the Isolator 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).
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 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"github.com/Tinkerforge/go-api-bindings/isolator_bricklet"
)
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your Isolator Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
i, _ := isolator_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
// Get current statistics.
messagesFromBrick, messagesFromBricklet, connectedBrickletDeviceIdentifier, connectedBrickletUID, _ := i.GetStatistics()
fmt.Printf("Messages From Brick: %d\n", messagesFromBrick)
fmt.Printf("Messages From Bricklet: %d\n", messagesFromBricklet)
fmt.Printf("Connected Bricklet Device Identifier: %d\n", connectedBrickletDeviceIdentifier)
fmt.Printf("Connected Bricklet UID: %s\n", connectedBrickletUID)
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
The Isolator Bricklet API is defined in the package github.com/Tinkerforge/go-api-bindings/isolator_bricklet
Nearly every function of the Go bindings can return an
ipconnection.DeviceError
, 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.
isolator_bricklet.
New
(uid string, ipcon *IPConnection) (device IsolatorBricklet, err error)¶Parameters: |
|
---|---|
Returns: |
|
Creates a new IsolatorBricklet
object with the unique device ID uid
and adds
it to the IPConnection ipcon
:
device, err := isolator_bricklet.New("YOUR_DEVICE_UID", &ipcon)
This device object can be used after the IPConnection has been connected.
(*IsolatorBricklet)
GetStatistics
() (messagesFromBrick uint32, messagesFromBricklet uint32, connectedBrickletDeviceIdentifier uint16, connectedBrickletUID string, err error)¶Returns: |
|
---|
Returns statistics for the Isolator Bricklet.
(*IsolatorBricklet)
SetSPITFPBaudrateConfig
(enableDynamicBaudrate bool, minimumDynamicBaudrate uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Isolator Bricklet will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.
The baudrate for communication config between Brick and Isolator Bricklet can be set through the API of the Brick.
The baudrate will be increased exponentially if lots of data is sent/received and decreased linearly if little data is sent/received.
This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.
In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.
The maximum value of the baudrate can be set per port with the function
SetSPITFPBaudrate()
. If the dynamic baudrate is disabled, the baudrate
as set by SetSPITFPBaudrate()
will be used statically.
(*IsolatorBricklet)
GetSPITFPBaudrateConfig
() (enableDynamicBaudrate bool, minimumDynamicBaudrate uint32, err error)¶Returns: |
|
---|
Returns the baudrate config, see SetSPITFPBaudrateConfig()
.
(*IsolatorBricklet)
SetSPITFPBaudrate
(baudrate uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the baudrate for a the communication between Isolator Bricklet and the connected Bricklet. The baudrate for communication between Brick and Isolator Bricklet can be set through the API of the Brick.
If you want to increase the throughput of Bricklets you can increase
the baudrate. If you get a high error count because of high
interference (see GetSPITFPErrorCount()
) you can decrease the
baudrate.
If the dynamic baudrate feature is enabled, the baudrate set by this
function corresponds to the maximum baudrate (see SetSPITFPBaudrateConfig()
).
Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.
(*IsolatorBricklet)
GetSPITFPBaudrate
() (baudrate uint32, err error)¶Returns: |
|
---|
Returns the baudrate, see SetSPITFPBaudrate()
.
(*IsolatorBricklet)
GetIsolatorSPITFPErrorCount
() (errorCountACKChecksum uint32, errorCountMessageChecksum uint32, errorCountFrame uint32, errorCountOverflow uint32, err error)¶Returns: |
|
---|
Returns the error count for the communication between Isolator Bricklet and
the connected Bricklet. Call GetSPITFPErrorCount()
to get the
error count between Isolator Bricklet and Brick.
The errors are divided into
(*IsolatorBricklet)
GetSPITFPErrorCount
() (errorCountAckChecksum uint32, errorCountMessageChecksum uint32, errorCountFrame uint32, errorCountOverflow uint32, err error)¶Returns: |
|
---|
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.
(*IsolatorBricklet)
SetStatusLEDConfig
(config uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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:
(*IsolatorBricklet)
GetStatusLEDConfig
() (config uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig()
The following constants are available for this function:
For config:
(*IsolatorBricklet)
GetChipTemperature
() (temperature int16, err error)¶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.
(*IsolatorBricklet)
Reset
() (err error)¶Returns: |
|
---|
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!
(*IsolatorBricklet)
GetIdentity
() (uid string, connectedUid string, position rune, hardwareVersion [3]uint8, firmwareVersion [3]uint8, deviceIdentifier uint16, err error)¶Returns: |
|
---|
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.
(*IsolatorBricklet)
SetStatisticsCallbackConfiguration
(period uint32, valueHasToChange bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the StatisticsCallback
callback is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
New in version 2.0.2 (Plugin).
(*IsolatorBricklet)
GetStatisticsCallbackConfiguration
() (period uint32, valueHasToChange bool, err error)¶Returns: |
|
---|
Returns the callback configuration as set by
SetStatisticsCallbackConfiguration()
.
New in version 2.0.2 (Plugin).
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 with the corresponding Deregister*Callback
function.
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.
(*IsolatorBricklet)
RegisterStatisticsCallback
(func(messagesFromBrick uint32, messagesFromBricklet uint32, connectedBrickletDeviceIdentifier uint16, connectedBrickletUID string)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is triggered periodically according to the configuration set by
SetStatisticsCallbackConfiguration()
.
The callback parameters are the same as GetStatistics()
.
New in version 2.0.2 (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.
(*IsolatorBricklet)
GetAPIVersion
() (apiVersion [3]uint8, err error)¶Returns: |
|
---|
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.
(*IsolatorBricklet)
GetResponseExpected
(functionId uint8) (responseExpected bool, err error)¶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:
(*IsolatorBricklet)
SetResponseExpected
(functionId uint8, responseExpected bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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:
(*IsolatorBricklet)
SetResponseExpectedAll
(responseExpected bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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.
(*IsolatorBricklet)
SetBootloaderMode
(mode uint8) (status uint8, err error)¶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:
(*IsolatorBricklet)
GetBootloaderMode
() (mode uint8, err error)¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode()
.
The following constants are available for this function:
For mode:
(*IsolatorBricklet)
SetWriteFirmwarePointer
(pointer uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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.
(*IsolatorBricklet)
WriteFirmware
(data [64]uint8) (status uint8, err error)¶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.
(*IsolatorBricklet)
WriteUID
(uid uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
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.
(*IsolatorBricklet)
ReadUID
() (uid uint32, err error)¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
isolator_bricklet.
DeviceIdentifier
¶This constant is used to identify a Isolator Bricklet.
The GetIdentity()
function and
the (*IPConnection) RegisterEnumerateCallback
callback of the IPConnection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
isolator_bricklet.
DeviceDisplayName
¶This constant represents the human readable name of a Isolator Bricklet.