This is the description of the Go API bindings for the RS485 Bricklet. General information and technical specifications for the RS485 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 39 40 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"github.com/Tinkerforge/go-api-bindings/rs485_bricklet"
)
// For this example connect the RX+/- pins to TX+/- pins on the same Bricklet
// and configure the DIP switch on the Bricklet to full-duplex mode
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your RS485 Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
rs485, _ := rs485_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
// Enable full-duplex mode
rs485.SetRS485Configuration(115200, rs485_bricklet.ParityNone,
rs485_bricklet.Stopbits1, rs485_bricklet.Wordlength8,
rs485_bricklet.DuplexFull)
rs485.RegisterReadCallback(func(message []rune) {
fmt.Println(string(message))
})
// Enable read callback
rs485.EnableReadCallback()
rs485.Write([]rune{'t', 'e', 's', 't'})
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
Download (example_modbus_slave.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 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"github.com/Tinkerforge/go-api-bindings/rs485_bricklet"
)
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your RS485 Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
rs485, _ := rs485_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
// Set operating mode to Modbus RTU slave
rs485.SetMode(rs485_bricklet.ModeModbusSlaveRTU)
// Modbus specific configuration:
// - slave address = 17
// - master request timeout = 0ms (unused in slave mode)
rs485.SetModbusConfiguration(17, 0)
rs485.RegisterModbusSlaveWriteSingleRegisterRequestCallback(func(requestID uint8, registerAddress uint32, registerValue uint16) {
fmt.Println("Request ID: ", requestID)
fmt.Println("Register Address: ", registerAddress)
fmt.Println("Register Value: ", registerValue)
if registerAddress != 42 {
fmt.Println("Error: Invalid register address")
rs485.ModbusSlaveReportException(requestID, rs485_bricklet.ExceptionCodeIllegalDataAddress)
} else {
rs485.ModbusSlaveAnswerWriteSingleRegisterRequest(requestID)
}
})
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
Download (example_modbus_master.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 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 | package main
import (
"fmt"
"github.com/Tinkerforge/go-api-bindings/ipconnection"
"github.com/Tinkerforge/go-api-bindings/rs485_bricklet"
)
const ADDR string = "localhost:4223"
const UID string = "XYZ" // Change XYZ to the UID of your RS485 Bricklet.
func main() {
ipcon := ipconnection.New()
defer ipcon.Close()
rs485, _ := rs485_bricklet.New(UID, &ipcon) // Create device object.
ipcon.Connect(ADDR) // Connect to brickd.
defer ipcon.Disconnect()
// Don't use device before ipcon is connected.
// Set operating mode to Modbus RTU master
rs485.SetMode(rs485_bricklet.ModeModbusMasterRTU)
// Modbus specific configuration:
// - slave address = 1 (unused in master mode)
// - master request timeout = 1000ms
rs485.SetModbusConfiguration(1, 1000)
expectedRequestID := uint8(0)
rs485.RegisterModbusMasterWriteSingleRegisterResponseCallback(func(requestID uint8, exceptionCode rs485_bricklet.ExceptionCode) {
fmt.Printf("Request ID: %d\n", requestID)
if exceptionCode == rs485_bricklet.ExceptionCodeTimeout {
fmt.Println("Exception Code: Timeout")
} else if exceptionCode == rs485_bricklet.ExceptionCodeSuccess {
fmt.Println("Exception Code: Success")
} else if exceptionCode == rs485_bricklet.ExceptionCodeIllegalFunction {
fmt.Println("Exception Code: Illegal Function")
} else if exceptionCode == rs485_bricklet.ExceptionCodeIllegalDataAddress {
fmt.Println("Exception Code: Illegal Data Address")
} else if exceptionCode == rs485_bricklet.ExceptionCodeIllegalDataValue {
fmt.Println("Exception Code: Illegal Data Value")
} else if exceptionCode == rs485_bricklet.ExceptionCodeSlaveDeviceFailure {
fmt.Println("Exception Code: Slave Device Failure")
} else if exceptionCode == rs485_bricklet.ExceptionCodeAcknowledge {
fmt.Println("Exception Code: Acknowledge")
} else if exceptionCode == rs485_bricklet.ExceptionCodeSlaveDeviceBusy {
fmt.Println("Exception Code: Slave Device Busy")
} else if exceptionCode == rs485_bricklet.ExceptionCodeMemoryParityError {
fmt.Println("Exception Code: Memory Parity Error")
} else if exceptionCode == rs485_bricklet.ExceptionCodeGatewayPathUnavailable {
fmt.Println("Exception Code: Gateway Path Unavailable")
} else if exceptionCode == rs485_bricklet.ExceptionCodeGatewayTargetDeviceFailedToRespond {
fmt.Println("Exception Code: Gateway Target Device Failed To Respond")
}
if requestID != expectedRequestID {
fmt.Println("Error: Unexpected request ID")
}
})
// Write 65535 to register 42 of slave 17
expectedRequestID, _ = rs485.ModbusMasterWriteSingleRegister(17, 42, 65535)
fmt.Print("Press enter to exit.")
fmt.Scanln()
}
|
The RS485 Bricklet API is defined in the package github.com/Tinkerforge/go-api-bindings/rs485_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.
rs485_bricklet.
New
(uid string, ipcon *IPConnection) (device RS485Bricklet, err error)¶Parameters: |
|
---|---|
Returns: |
|
Creates a new RS485Bricklet
object with the unique device ID uid
and adds
it to the IPConnection ipcon
:
device, err := rs485_bricklet.New("YOUR_DEVICE_UID", &ipcon)
This device object can be used after the IPConnection has been connected.
(*RS485Bricklet)
Write
(message []rune) (messageChunkWritten uint64, err error)¶Parameters: |
|
---|---|
Returns: |
|
Writes characters to the RS485 interface. The characters can be binary data, ASCII or similar is not necessary.
The return value is the number of characters that were written.
See SetRS485Configuration()
for configuration possibilities
regarding baudrate, parity and so on.
(*RS485Bricklet)
Read
(length uint16) (message []rune, err error)¶Parameters: |
|
---|---|
Returns: |
|
Returns up to length characters from receive buffer.
Instead of polling with this function, you can also use
callbacks. But note that this function will return available
data only when the read callback is disabled.
See EnableReadCallback()
and ReadCallback
callback.
(*RS485Bricklet)
SetRS485Configuration
(baudrate uint32, parity uint8, stopbits uint8, wordlength uint8, duplex uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the configuration for the RS485 communication.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For duplex:
(*RS485Bricklet)
GetRS485Configuration
() (baudrate uint32, parity uint8, stopbits uint8, wordlength uint8, duplex uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetRS485Configuration()
.
The following constants are available for this function:
For parity:
For stopbits:
For wordlength:
For duplex:
(*RS485Bricklet)
SetModbusConfiguration
(slaveAddress uint8, masterRequestTimeout uint32) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the configuration for the RS485 Modbus communication. Available options:
(*RS485Bricklet)
GetModbusConfiguration
() (slaveAddress uint8, masterRequestTimeout uint32, err error)¶Returns: |
|
---|
Returns the configuration as set by SetModbusConfiguration()
.
(*RS485Bricklet)
SetMode
(mode uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the mode of the Bricklet in which it operates. Available options are
The following constants are available for this function:
For mode:
(*RS485Bricklet)
GetMode
() (mode uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetMode()
.
The following constants are available for this function:
For mode:
(*RS485Bricklet)
SetCommunicationLEDConfig
(config uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the communication LED configuration. By default the LED shows RS485 communication traffic by flickering.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
(*RS485Bricklet)
GetCommunicationLEDConfig
() (config uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetCommunicationLEDConfig()
The following constants are available for this function:
For config:
(*RS485Bricklet)
SetErrorLEDConfig
(config uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the error LED configuration.
By default the error LED turns on if there is any error (see ErrorCountCallback
callback). If you call this function with the SHOW ERROR option again, the LED
will turn off until the next error occurs.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
(*RS485Bricklet)
GetErrorLEDConfig
() (config uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetErrorLEDConfig()
.
The following constants are available for this function:
For config:
(*RS485Bricklet)
SetBufferConfig
(sendBufferSize uint16, receiveBufferSize uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Sets the send and receive buffer size in byte. In sum there is 10240 byte (10KiB) buffer available and the minimum buffer size is 1024 byte (1KiB) for both.
The current buffer content is lost if this function is called.
The send buffer holds data that was given by Write()
and
could not be written yet. The receive buffer holds data that is
received through RS485 but could not yet be send to the
user, either by Read()
or through ReadCallback
callback.
(*RS485Bricklet)
GetBufferConfig
() (sendBufferSize uint16, receiveBufferSize uint16, err error)¶Returns: |
|
---|
Returns the buffer configuration as set by SetBufferConfig()
.
(*RS485Bricklet)
GetBufferStatus
() (sendBufferUsed uint16, receiveBufferUsed uint16, err error)¶Returns: |
|
---|
Returns the currently used bytes for the send and received buffer.
See SetBufferConfig()
for buffer size configuration.
(*RS485Bricklet)
GetErrorCount
() (overrunErrorCount uint32, parityErrorCount uint32, err error)¶Returns: |
|
---|
Returns the current number of overrun and parity errors.
(*RS485Bricklet)
GetModbusCommonErrorCount
() (timeoutErrorCount uint32, checksumErrorCount uint32, frameTooBigErrorCount uint32, illegalFunctionErrorCount uint32, illegalDataAddressErrorCount uint32, illegalDataValueErrorCount uint32, slaveDeviceFailureErrorCount uint32, err error)¶Returns: |
|
---|
Returns the current number of errors occurred in Modbus mode.
(*RS485Bricklet)
ModbusSlaveReportException
(requestID uint8, exceptionCode int8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to report a Modbus exception for a Modbus master request.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
ModbusSlaveAnswerReadCoilsRequest
(requestID uint8, coils []bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to read coils.
This function must be called from the ModbusSlaveReadCoilsRequestCallback
callback
with the Request ID as provided by the argument of the callback.
(*RS485Bricklet)
ModbusMasterReadCoils
(slaveAddress uint8, startingAddress uint32, count uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to read coils from a slave. This function creates a Modbus function code 1 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterReadCoilsResponseCallback
callback. In this callback the Request ID provided by the callback argument must be
matched with the Request ID returned from this function to verify that the callback
is indeed for a particular request.
(*RS485Bricklet)
ModbusSlaveAnswerReadHoldingRegistersRequest
(requestID uint8, holdingRegisters []uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to read holding registers.
This function must be called from the ModbusSlaveReadHoldingRegistersRequestCallback
callback with the Request ID as provided by the argument of the callback.
(*RS485Bricklet)
ModbusMasterReadHoldingRegisters
(slaveAddress uint8, startingAddress uint32, count uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to read holding registers from a slave. This function creates a Modbus function code 3 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterReadHoldingRegistersResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerWriteSingleCoilRequest
(requestID uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to write a single coil.
This function must be called from the ModbusSlaveWriteSingleCoilRequestCallback
callback with the Request ID as provided by the arguments of the callback.
(*RS485Bricklet)
ModbusMasterWriteSingleCoil
(slaveAddress uint8, coilAddress uint32, coilValue bool) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to write a single coil of a slave. This function creates a Modbus function code 5 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterWriteSingleCoilResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerWriteSingleRegisterRequest
(requestID uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to write a single register.
This function must be called from the ModbusSlaveWriteSingleRegisterRequestCallback
callback with the Request ID, Register Address and Register Value as provided by
the arguments of the callback.
(*RS485Bricklet)
ModbusMasterWriteSingleRegister
(slaveAddress uint8, registerAddress uint32, registerValue uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to write a single holding register of a slave. This function creates a Modbus function code 6 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterWriteSingleRegisterResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerWriteMultipleCoilsRequest
(requestID uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to write multiple coils.
This function must be called from the ModbusSlaveWriteMultipleCoilsRequestCallback
callback with the Request ID of the callback.
(*RS485Bricklet)
ModbusMasterWriteMultipleCoils
(slaveAddress uint8, startingAddress uint32, coils []bool) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to write multiple coils of a slave. This function creates a Modbus function code 15 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterWriteMultipleCoilsResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerWriteMultipleRegistersRequest
(requestID uint8) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to write multiple registers.
This function must be called from the ModbusSlaveWriteMultipleRegistersRequestCallback
callback with the Request ID of the callback.
(*RS485Bricklet)
ModbusMasterWriteMultipleRegisters
(slaveAddress uint8, startingAddress uint32, registers []uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to write multiple registers of a slave. This function creates a Modbus function code 16 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterWriteMultipleRegistersResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerReadDiscreteInputsRequest
(requestID uint8, discreteInputs []bool) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to read discrete inputs.
This function must be called from the ModbusSlaveReadDiscreteInputsRequestCallback
callback with the Request ID as provided by the argument of the callback.
(*RS485Bricklet)
ModbusMasterReadDiscreteInputs
(slaveAddress uint8, startingAddress uint32, count uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to read discrete inputs from a slave. This function creates a Modbus function code 2 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterReadDiscreteInputsResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
ModbusSlaveAnswerReadInputRegistersRequest
(requestID uint8, inputRegisters []uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus slave mode this function can be used to answer a master request to read input registers.
This function must be called from the ModbusSlaveReadInputRegistersRequestCallback
callback
with the Request ID as provided by the argument of the callback.
(*RS485Bricklet)
ModbusMasterReadInputRegisters
(slaveAddress uint8, startingAddress uint32, count uint16) (requestID uint8, err error)¶Parameters: |
|
---|---|
Returns: |
|
In Modbus master mode this function can be used to read input registers from a slave. This function creates a Modbus function code 4 request.
Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.
When successful this function will also invoke the ModbusMasterReadInputRegistersResponseCallback
callback. In this callback the Request ID provided by the callback argument must be matched
with the Request ID returned from this function to verify that the callback is indeed for a
particular request.
(*RS485Bricklet)
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.
(*RS485Bricklet)
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:
(*RS485Bricklet)
GetStatusLEDConfig
() (config uint8, err error)¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig()
The following constants are available for this function:
For config:
(*RS485Bricklet)
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.
(*RS485Bricklet)
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!
(*RS485Bricklet)
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.
(*RS485Bricklet)
EnableReadCallback
() (err error)¶Returns: |
|
---|
Enables the ReadCallback
callback. This will disable the FrameReadableCallback
callback.
By default the callback is disabled.
(*RS485Bricklet)
DisableReadCallback
() (err error)¶Returns: |
|
---|
Disables the ReadCallback
callback.
By default the callback is disabled.
(*RS485Bricklet)
IsReadCallbackEnabled
() (enabled bool, err error)¶Returns: |
|
---|
Returns true if the ReadCallback
callback is enabled,
false otherwise.
(*RS485Bricklet)
EnableErrorCountCallback
() (err error)¶Returns: |
|
---|
Enables the ErrorCountCallback
callback.
By default the callback is disabled.
(*RS485Bricklet)
DisableErrorCountCallback
() (err error)¶Returns: |
|
---|
Disables the ErrorCountCallback
callback.
By default the callback is disabled.
(*RS485Bricklet)
IsErrorCountCallbackEnabled
() (enabled bool, err error)¶Returns: |
|
---|
Returns true if the ErrorCountCallback
callback is enabled,
false otherwise.
(*RS485Bricklet)
SetFrameReadableCallbackConfiguration
(frameSize uint16) (err error)¶Parameters: |
|
---|---|
Returns: |
|
Configures the FrameReadableCallback
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 ReadCallback
callback.
By default the callback is disabled.
New in version 2.0.5 (Plugin).
(*RS485Bricklet)
GetFrameReadableCallbackConfiguration
() (frameSize uint16, err error)¶Returns: |
|
---|
Returns the callback configuration as set by SetFrameReadableCallbackConfiguration()
.
New in version 2.0.5 (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.
(*RS485Bricklet)
RegisterReadCallback
(func(message []rune)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called if new data is available.
To enable this callback, use EnableReadCallback()
.
Note
If reconstructing the value fails, the callback is triggered with nil for message.
(*RS485Bricklet)
RegisterErrorCountCallback
(func(overrunErrorCount uint32, parityErrorCount uint32)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called if a new error occurs. It returns the current overrun and parity error count.
(*RS485Bricklet)
RegisterModbusSlaveReadCoilsRequestCallback
(func(requestID uint8, startingAddress uint32, count uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read coils. The callback parameters are request ID of the request, the number of the first coil to be read and the number of coils to be read as received by the request. The number of the first coil is called starting address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.
To send a response of this request use ModbusSlaveAnswerReadCoilsRequest()
.
(*RS485Bricklet)
RegisterModbusMasterReadCoilsResponseCallback
(func(coils []bool, requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.
The callback parameters are request ID of the request, exception code of the response and the data as received by the response.
Any non-zero exception code indicates a problem. If the exception code
is greater than 0 then the number represents a Modbus exception code. If it is
less than 0 then it represents other errors. For example, -1 indicates that
the request timed out or that the master did not receive any valid response of the
request within the master request timeout period as set by
SetModbusConfiguration()
.
Note
If reconstructing the value fails, the callback is triggered with nil for coils.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveReadHoldingRegistersRequestCallback
(func(requestID uint8, startingAddress uint32, count uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read holding registers. The callback parameters are request ID of the request, the number of the first holding register to be read and the number of holding registers to be read as received by the request. The number of the first holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.
To send a response of this request use ModbusSlaveAnswerReadHoldingRegistersRequest()
.
(*RS485Bricklet)
RegisterModbusMasterReadHoldingRegistersResponseCallback
(func(holdingRegisters []uint16, requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to read holding registers.
The callback parameters are request ID of the request, exception code of the response and the data as received by the response.
Any non-zero exception code indicates a problem. If the exception
code is greater than 0 then the number represents a Modbus exception code. If
it is less than 0 then it represents other errors. For example, -1 indicates that
the request timed out or that the master did not receive any valid response of the
request within the master request timeout period as set by
SetModbusConfiguration()
.
Note
If reconstructing the value fails, the callback is triggered with nil for holdingRegisters.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveWriteSingleCoilRequestCallback
(func(requestID uint8, coilAddress uint32, coilValue bool)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write a single coil. The callback parameters are request ID of the request, the number of the coil and the value of coil to be written as received by the request. The number of the coil is called coil address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.
To send a response of this request use ModbusSlaveAnswerWriteSingleCoilRequest()
.
(*RS485Bricklet)
RegisterModbusMasterWriteSingleCoilResponseCallback
(func(requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to write a single coil.
The callback parameters are request ID of the request and exception code of the response.
Any non-zero exception code indicates a problem.
If the exception code is greater than 0 then the number represents a Modbus
exception code. If it is less than 0 then it represents other errors. For
example, -1 indicates that the request timed out or that the master did not receive
any valid response of the request within the master request timeout period as set
by SetModbusConfiguration()
.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveWriteSingleRegisterRequestCallback
(func(requestID uint8, registerAddress uint32, registerValue uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write a single holding register. The callback parameters are request ID of the request, the number of the holding register and the register value to be written as received by the request. The number of the holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.
To send a response of this request use ModbusSlaveAnswerWriteSingleRegisterRequest()
.
(*RS485Bricklet)
RegisterModbusMasterWriteSingleRegisterResponseCallback
(func(requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to write a single register.
The callback parameters are request ID of the request and exception code of the response.
Any non-zero exception code
indicates a problem. If the exception code is greater than 0 then the number
represents a Modbus exception code. If it is less than 0 then it represents
other errors. For example, -1 indicates that the request timed out or that the
master did not receive any valid response of the request within the master request
timeout period as set by SetModbusConfiguration()
.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveWriteMultipleCoilsRequestCallback
(func(coils []bool, requestID uint8, startingAddress uint32)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple coils. The callback parameters are request ID of the request, the number of the first coil and the data to be written as received by the request. The number of the first coil is called starting address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.
To send a response of this request use ModbusSlaveAnswerWriteMultipleCoilsRequest()
.
Note
If reconstructing the value fails, the callback is triggered with nil for coils.
(*RS485Bricklet)
RegisterModbusMasterWriteMultipleCoilsResponseCallback
(func(requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.
The callback parameters are request ID of the request and exception code of the response.
Any non-zero exception code
indicates a problem. If the exception code is greater than 0 then the number
represents a Modbus exception code. If it is less than 0 then it represents
other errors. For example, -1 indicates that the request timedout or that the
master did not receive any valid response of the request within the master request
timeout period as set by SetModbusConfiguration()
.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveWriteMultipleRegistersRequestCallback
(func(registers []uint16, requestID uint8, startingAddress uint32)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple holding registers. The callback parameters are request ID of the request, the number of the first holding register and the data to be written as received by the request. The number of the first holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.
To send a response of this request use ModbusSlaveAnswerWriteMultipleRegistersRequest()
.
Note
If reconstructing the value fails, the callback is triggered with nil for registers.
(*RS485Bricklet)
RegisterModbusMasterWriteMultipleRegistersResponseCallback
(func(requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to write multiple registers.
The callback parameters are request ID of the request and exception code of the response.
Any non-zero
exception code indicates a problem. If the exception code is greater than 0 then
the number represents a Modbus exception code. If it is less than 0 then it
represents other errors. For example, -1 indicates that the request timedout or
that the master did not receive any valid response of the request within the master
request timeout period as set by SetModbusConfiguration()
.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveReadDiscreteInputsRequestCallback
(func(requestID uint8, startingAddress uint32, count uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read discrete inputs. The callback parameters are request ID of the request, the number of the first discrete input and the number of discrete inputs to be read as received by the request. The number of the first discrete input is called starting address for backwards compatibility reasons. It is not an address, but instead a discrete input number in the range of 1 to 65536. The prefix digit 1 (for discrete input) is omitted.
To send a response of this request use ModbusSlaveAnswerReadDiscreteInputsRequest()
.
(*RS485Bricklet)
RegisterModbusMasterReadDiscreteInputsResponseCallback
(func(discreteInputs []bool, requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to read discrete inputs.
The callback parameters are request ID of the request, exception code of the response and the data as received by the response.
Any non-zero exception code indicates a problem. If the exception
code is greater than 0 then the number represents a Modbus exception code. If
it is less than 0 then it represents other errors. For example, -1 indicates that
the request timedout or that the master did not receive any valid response of the
request within the master request timeout period as set by
SetModbusConfiguration()
.
Note
If reconstructing the value fails, the callback is triggered with nil for discreteInputs.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterModbusSlaveReadInputRegistersRequestCallback
(func(requestID uint8, startingAddress uint32, count uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read input registers. The callback parameters are request ID of the request, the number of the first input register and the number of input registers to be read as received by the request. The number of the first input register is called starting address for backwards compatibility reasons. It is not an address, but instead a input register number in the range of 1 to 65536. The prefix digit 3 (for input register) is omitted.
To send a response of this request use ModbusSlaveAnswerReadInputRegistersRequest()
.
(*RS485Bricklet)
RegisterModbusMasterReadInputRegistersResponseCallback
(func(inputRegisters []uint16, requestID uint8, exceptionCode int8)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
This callback is called only in Modbus master mode when the master receives a valid response of a request to read input registers.
The callback parameters are request ID of the request, exception code of the response and the data as received by the response.
Any non-zero exception code indicates a problem. If the exception
code is greater than 0 then the number represents a Modbus exception code. If
it is less than 0 then it represents other errors. For example, -1 indicates that
the request timedout or that the master did not receive any valid response of the
request within the master request timeout period as set by
SetModbusConfiguration()
.
Note
If reconstructing the value fails, the callback is triggered with nil for inputRegisters.
The following constants are available for this function:
For exceptionCode:
(*RS485Bricklet)
RegisterFrameReadableCallback
(func(frameCount uint16)) (registrationId uint64)¶Callback Parameters: |
|
---|---|
Returns: |
|
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()
is called. This means, that if you have configured a frame size of X bytes,
you can read exactly X bytes using the Read()
function, every time the callback triggers without checking the frame count callback parameter.
New in version 2.0.5 (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.
(*RS485Bricklet)
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.
(*RS485Bricklet)
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:
(*RS485Bricklet)
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:
(*RS485Bricklet)
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.
(*RS485Bricklet)
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:
(*RS485Bricklet)
GetBootloaderMode
() (mode uint8, err error)¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode()
.
The following constants are available for this function:
For mode:
(*RS485Bricklet)
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.
(*RS485Bricklet)
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.
(*RS485Bricklet)
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.
(*RS485Bricklet)
ReadUID
() (uid uint32, err error)¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
rs485_bricklet.
DeviceIdentifier
¶This constant is used to identify a RS485 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.
rs485_bricklet.
DeviceDisplayName
¶This constant represents the human readable name of a RS485 Bricklet.