This is the description of the Go API bindings for the DC Brick. General information and technical specifications for the DC Brick 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_configuration.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 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/dc_brick"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"time"
)
const ADDR string = "localhost:4223"
const UID string = "XXYYZZ" // Change XXYYZZ to the UID of your DC Brick.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
dc, _ := dc_brick.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
dc.SetDriveMode(dc_brick.DriveModeDriveCoast)
dc.SetPWMFrequency(10000) // Use PWM frequency of 10 kHz
dc.SetAcceleration(4096) // Slow acceleration (12.5 %/s)
dc.SetVelocity(32767) // Full speed forward (100 %)
dc.Enable() // Enable motor power
fmt.Print("Press enter to exit.")
fmt.Scanln()
// Stop motor before disabling motor power
dc.SetAcceleration(16384) // Fast decceleration (50 %/s) for stopping
dc.SetVelocity(0) // Request motor stop
time.Sleep(2000 * time.Millisecond) // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
dc.Disable() // Disable motor power
}
|
Download (example_callback.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 39 40 41 42 43 44 45 46 47 48 49 50 51 52 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/dc_brick"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"time"
)
const ADDR string = "localhost:4223"
const UID string = "XXYYZZ" // Change XXYYZZ to the UID of your DC Brick.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
dc, _ := dc_brick.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
// The acceleration has to be smaller or equal to the maximum
// acceleration of the DC motor, otherwise the velocity reached
// callback will be called too early
dc.SetAcceleration(4096) // Slow acceleration (12.5 %/s)
dc.SetVelocity(32767) // Full speed forward (100 %)
dc.RegisterVelocityReachedCallback(func(velocity int16) {
if velocity == 32767 {
fmt.Println("Velocity: Full speed forward, now turning backward")
dc.SetVelocity(-32767)
} else if velocity == -32767 {
fmt.Println("Velocity: Full speed backward, now turning forward")
dc.SetVelocity(32767)
} else {
//can only happen if another program sets velocity
fmt.Println("Error")
}
})
// Enable motor power
dc.Enable()
fmt.Print("Press enter to exit.")
fmt.Scanln()
// Stop motor before disabling motor power
dc.SetAcceleration(16384) // Fast decceleration (50 %/s) for stopping
dc.SetVelocity(0) // Request motor stop
time.Sleep(2000 * time.Millisecond) // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
dc.Disable() // Disable motor power
}
|
The DC Brick API is defined in the package github.com/Tinkerforge/go-api-bindings/dc_brick
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.
dc_brick.
New
(uid string, ipcon *IPConnection) (device DCBrick, err error)¶Parameters: |
|
---|---|
Returns: |
|
Creates a new DCBrick
object with the unique device ID uid
and adds
it to the IPConnection ipcon
:
device, err := dc_brick.New("YOUR_DEVICE_UID", &ipcon)
This device object can be used after the IPConnection has been connected.
(*DCBrick)
SetVelocity
(velocity int16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the velocity of the motor. Whereas -32767 is full speed backward,
0 is stop and 32767 is full speed forward. Depending on the
acceleration (see SetAcceleration()
), the motor is not immediately
brought to the velocity but smoothly accelerated.
The velocity describes the duty cycle of the PWM with which the motor is
controlled, e.g. a velocity of 3277 sets a PWM with a 10% duty cycle.
You can not only control the duty cycle of the PWM but also the frequency,
see SetPWMFrequency()
.
(*DCBrick)
GetVelocity
() (velocity int16, err error)¶Returns: |
|
---|
Returns the velocity as set by SetVelocity()
.
(*DCBrick)
GetCurrentVelocity
() (velocity int16, err error)¶Returns: |
|
---|
Returns the current velocity of the motor. This value is different
from GetVelocity()
whenever the motor is currently accelerating
to a goal set by SetVelocity()
.
(*DCBrick)
SetAcceleration
(acceleration uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the acceleration of the motor. It is given in velocity/s. An acceleration of 10000 means, that every second the velocity is increased by 10000 (or about 30% duty cycle).
For example: If the current velocity is 0 and you want to accelerate to a velocity of 16000 (about 50% duty cycle) in 10 seconds, you should set an acceleration of 1600.
If acceleration is set to 0, there is no speed ramping, i.e. a new velocity is immediately given to the motor.
(*DCBrick)
GetAcceleration
() (acceleration uint16, err error)¶Returns: |
|
---|
Returns the acceleration as set by SetAcceleration()
.
(*DCBrick)
FullBrake
() (err error)¶Returns: |
|
---|
Executes an active full brake.
Warning
This function is for emergency purposes, where an immediate brake is necessary. Depending on the current velocity and the strength of the motor, a full brake can be quite violent.
Call SetVelocity()
with 0 if you just want to stop the motor.
(*DCBrick)
Enable
() (err error)¶Returns: |
|
---|
Enables the driver chip. The driver parameters can be configured (velocity, acceleration, etc) before it is enabled.
(*DCBrick)
Disable
() (err error)¶Returns: |
|
---|
Disables the driver chip. The configurations are kept (velocity, acceleration, etc) but the motor is not driven until it is enabled again.
Warning
Disabling the driver chip while the motor is still turning can damage the
driver chip. The motor should be stopped calling SetVelocity()
with 0
before disabling the motor power. The SetVelocity()
function will not
wait until the motor is actually stopped. You have to explicitly wait for the
appropriate time after calling the SetVelocity()
function before calling
the Disable()
function.
(*DCBrick)
IsEnabled
() (enabled bool, err error)¶Returns: |
|
---|
Returns true if the driver chip is enabled, false otherwise.
(*DCBrick)
SetPWMFrequency
(frequency uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the frequency of the PWM with which the motor is driven. Often a high frequency is less noisy and the motor runs smoother. However, with a low frequency there are less switches and therefore fewer switching losses. Also with most motors lower frequencies enable higher torque.
If you have no idea what all this means, just ignore this function and use the default frequency, it will very likely work fine.
(*DCBrick)
GetPWMFrequency
() (frequency uint16, err error)¶Returns: |
|
---|
Returns the PWM frequency as set by SetPWMFrequency()
.
(*DCBrick)
GetStackInputVoltage
() (voltage uint16, err error)¶Returns: |
|
---|
Returns the stack input voltage. The stack input voltage is the voltage that is supplied via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.
(*DCBrick)
GetExternalInputVoltage
() (voltage uint16, err error)¶Returns: |
|
---|
Returns the external input voltage. The external input voltage is given via the black power input connector on the DC Brick.
If there is an external input voltage and a stack input voltage, the motor will be driven by the external input voltage. If there is only a stack voltage present, the motor will be driven by this voltage.
Warning
This means, if you have a high stack voltage and a low external voltage, the motor will be driven with the low external voltage. If you then remove the external connection, it will immediately be driven by the high stack voltage.
(*DCBrick)
GetCurrentConsumption
() (voltage uint16, err error)¶Returns: |
|
---|
Returns the current consumption of the motor.
(*DCBrick)
SetDriveMode
(mode uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the drive mode. Possible modes are:
These modes are different kinds of motor controls.
In Drive/Brake mode, the motor is always either driving or braking. There is no freewheeling. Advantages are: A more linear correlation between PWM and velocity, more exact accelerations and the possibility to drive with slower velocities.
In Drive/Coast mode, the motor is always either driving or freewheeling. Advantages are: Less current consumption and less demands on the motor and driver chip.
The following constants are available for this function:
For mode:
(*DCBrick)
GetDriveMode
() (mode uint8, err error)¶Returns: |
|
---|
Returns the drive mode, as set by SetDriveMode()
.
The following constants are available for this function:
For mode:
(*DCBrick)
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 Brick will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.
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.
New in version 2.3.5 (Firmware).
(*DCBrick)
GetSPITFPBaudrateConfig
() (enableDynamicBaudrate bool, minimumDynamicBaudrate uint32, err error)¶Returns: |
|
---|
Returns the baudrate config, see SetSPITFPBaudrateConfig()
.
New in version 2.3.5 (Firmware).
(*DCBrick)
GetSendTimeoutCount
(communicationMethod uint8) (timeoutCount uint32, err error)¶Parameters: |
|
---|---|
Returns: |
|
Returns the timeout count for the different communication methods.
The methods 0-2 are available for all Bricks, 3-7 only for Master Bricks.
This function is mostly used for debugging during development, in normal operation the counters should nearly always stay at 0.
The following constants are available for this function:
For communicationMethod:
New in version 2.3.3 (Firmware).
(*DCBrick)
SetSPITFPBaudrate
(brickletPort rune, baudrate uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the baudrate for a specific Bricklet port.
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.
New in version 2.3.3 (Firmware).
(*DCBrick)
GetSPITFPBaudrate
(brickletPort rune) (baudrate uint32, err error)¶Parameters: |
|
---|---|
Returns: |
|
Returns the baudrate for a given Bricklet port, see SetSPITFPBaudrate()
.
New in version 2.3.3 (Firmware).
(*DCBrick)
GetSPITFPErrorCount
(brickletPort rune) (errorCountACKChecksum uint32, errorCountMessageChecksum uint32, errorCountFrame uint32, errorCountOverflow uint32, err error)¶Parameters: |
|
---|---|
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 Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.
New in version 2.3.3 (Firmware).
(*DCBrick)
EnableStatusLED
() (err error)¶Returns: |
|
---|
Enables the status LED.
The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.
The default state is enabled.
New in version 2.3.1 (Firmware).
(*DCBrick)
DisableStatusLED
() (err error)¶Returns: |
|
---|
Disables the status LED.
The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.
The default state is enabled.
New in version 2.3.1 (Firmware).
(*DCBrick)
IsStatusLEDEnabled
() (enabled bool, err error)¶Returns: |
|
---|
Returns true if the status LED is enabled, false otherwise.
New in version 2.3.1 (Firmware).
(*DCBrick)
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 an accuracy of ±15%. Practically it is only useful as an indicator for temperature changes.
(*DCBrick)
Reset
() (err error)¶Returns: |
|
---|
Calling this function will reset the Brick. Calling this function on a Brick inside of a stack will reset the whole stack.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
(*DCBrick)
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 Brick is connected to, the position, the hardware and firmware version as well as the device identifier.
The position is the position in the stack from '0' (bottom) to '8' (top).
The device identifier numbers can be found here. There is also a constant for the device identifier of this Brick.
(*DCBrick)
SetMinimumVoltage
(voltage uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the minimum voltage, below which the UnderVoltageCallback
callback
is triggered. The minimum possible value that works with the DC Brick is 6V.
You can use this function to detect the discharge of a battery that is used
to drive the motor. If you have a fixed power supply, you likely do not need
this functionality.
(*DCBrick)
GetMinimumVoltage
() (voltage uint16, err error)¶Returns: |
|
---|
Returns the minimum voltage as set by SetMinimumVoltage()
(*DCBrick)
SetCurrentVelocityPeriod
(period uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets a period with which the CurrentVelocityCallback
callback is triggered.
A period of 0 turns the callback off.
(*DCBrick)
GetCurrentVelocityPeriod
() (period uint16, err error)¶Returns: |
|
---|
Returns the period as set by SetCurrentVelocityPeriod()
.
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.
(*DCBrick)
RegisterUnderVoltageCallback
(func(voltage uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is triggered when the input voltage drops below the value set by
SetMinimumVoltage()
. The callback parameter is the current voltage.
(*DCBrick)
RegisterEmergencyShutdownCallback
(func()) (registrationId uint64)¶Returns: |
|
---|
This callback is triggered if either the current consumption is too high (above 5A) or the temperature of the driver chip is too high (above 175°C). These two possibilities are essentially the same, since the temperature will reach this threshold immediately if the motor consumes too much current. In case of a voltage below 3.3V (external or stack) this callback is triggered as well.
If this callback is triggered, the driver chip gets disabled at the same time.
That means, Enable()
has to be called to drive the motor again.
Note
This callback only works in Drive/Brake mode (see SetDriveMode()
). In
Drive/Coast mode it is unfortunately impossible to reliably read the
overcurrent/overtemperature signal from the driver chip.
(*DCBrick)
RegisterVelocityReachedCallback
(func(velocity int16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is triggered whenever a set velocity is reached. For example:
If a velocity of 0 is present, acceleration is set to 5000 and velocity
to 10000, the VelocityReachedCallback
callback will be triggered after about
2 seconds, when the set velocity is actually reached.
Note
Since we can't get any feedback from the DC motor, this only works if the
acceleration (see SetAcceleration()
) is set smaller or equal to the
maximum acceleration of the motor. Otherwise the motor will lag behind the
control value and the callback will be triggered too early.
(*DCBrick)
RegisterCurrentVelocityCallback
(func(velocity int16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is triggered with the period that is set by
SetCurrentVelocityPeriod()
. The callback parameter is the current
velocity used by the motor.
The CurrentVelocityCallback
callback is only triggered after the set period
if there is a change in the velocity.
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.
(*DCBrick)
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.
(*DCBrick)
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:
(*DCBrick)
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:
(*DCBrick)
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.
(*DCBrick)
GetProtocol1BrickletName
(port rune) (protocolVersion uint8, firmwareVersion [3]uint8, name string, err error)¶Parameters: |
|
---|---|
Returns: |
|
Returns the firmware and protocol version and the name of the Bricklet for a given port.
This functions sole purpose is to allow automatic flashing of v1.x.y Bricklet plugins.
(*DCBrick)
WriteBrickletPlugin
(port rune, offset uint8, chunk [32]uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Writes 32 bytes of firmware to the bricklet attached at the given port. The bytes are written to the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
(*DCBrick)
ReadBrickletPlugin
(port rune, offset uint8) (chunk [32]uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
Reads 32 bytes of firmware from the bricklet attached at the given port. The bytes are read starting at the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
dc_brick.
DeviceIdentifier
¶This constant is used to identify a DC Brick.
The GetIdentity()
function and
the (*IPConnection) RegisterEnumerateCallback
callback of the IPConnection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
dc_brick.
DeviceDisplayName
¶This constant represents the human readable name of a DC Brick.