LabVIEW - RS485 Bricklet¶

Loopback¶

Download (Example Loopback.vi), Download (Example Loopback - ReadCallback Callback.vi)

Modbus Master¶

Download (Example Modbus Master.vi), Download (Example Modbus Master - ModbusMasterWriteSingleRegisterResponseCallback Callback.vi)

Modbus Slave¶

Download (Example Modbus Slave.vi), Download (Example Modbus Slave - ModbusSlaveWriteSingleRegisterRequestCallback Callback.vi)

Basic Functions¶

BrickletRS485(uid, ipcon) → rs485¶

Input:	uid – Type: String ipcon – Type: .NET Refnum (IPConnection)
Output:	rs485 – Type: .NET Refnum (BrickletRS485)

Creates an object with the unique device ID uid. This object can then be used after the IP Connection is connected.

BrickletRS485.Write(message) → messageWritten¶

Input:	message – Type: Char[], Length: variable
Output:	messageWritten – Type: Int32, Range: [0 to 216 - 1]

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.

BrickletRS485.Read(length) → message¶

Input:	length – Type: Int32, Range: [0 to 216 - 1]
Output:	message – Type: Char[], Length: variable

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.

BrickletRS485.SetRS485Configuration(baudrate, parity, stopbits, wordlength, duplex)¶

Input:	baudrate – Type: Int64, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200 parity – Type: Byte, Range: See constants, Default: 0 stopbits – Type: Byte, Range: See constants, Default: 1 wordlength – Type: Byte, Range: See constants, Default: 8 duplex – Type: Byte, Range: See constants, Default: 0

Sets the configuration for the RS485 communication.

The following constants are available for this function:

For parity:

• BrickletRS485.PARITY_NONE = 0
• BrickletRS485.PARITY_ODD = 1
• BrickletRS485.PARITY_EVEN = 2

For stopbits:

• BrickletRS485.STOPBITS_1 = 1
• BrickletRS485.STOPBITS_2 = 2

For wordlength:

• BrickletRS485.WORDLENGTH_5 = 5
• BrickletRS485.WORDLENGTH_6 = 6
• BrickletRS485.WORDLENGTH_7 = 7
• BrickletRS485.WORDLENGTH_8 = 8

For duplex:

• BrickletRS485.DUPLEX_HALF = 0
• BrickletRS485.DUPLEX_FULL = 1

BrickletRS485.GetRS485Configuration() → baudrate, parity, stopbits, wordlength, duplex¶

Output:	baudrate – Type: Int64, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200 parity – Type: Byte, Range: See constants, Default: 0 stopbits – Type: Byte, Range: See constants, Default: 1 wordlength – Type: Byte, Range: See constants, Default: 8 duplex – Type: Byte, Range: See constants, Default: 0

Returns the configuration as set by SetRS485Configuration().

The following constants are available for this function:

For parity:

• BrickletRS485.PARITY_NONE = 0
• BrickletRS485.PARITY_ODD = 1
• BrickletRS485.PARITY_EVEN = 2

For stopbits:

• BrickletRS485.STOPBITS_1 = 1
• BrickletRS485.STOPBITS_2 = 2

For wordlength:

• BrickletRS485.WORDLENGTH_5 = 5
• BrickletRS485.WORDLENGTH_6 = 6
• BrickletRS485.WORDLENGTH_7 = 7
• BrickletRS485.WORDLENGTH_8 = 8

For duplex:

• BrickletRS485.DUPLEX_HALF = 0
• BrickletRS485.DUPLEX_FULL = 1

BrickletRS485.SetModbusConfiguration(slaveAddress, masterRequestTimeout)¶

Input:	slaveAddress – Type: Byte, Range: [1 to 247], Default: 1 masterRequestTimeout – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 1000

Sets the configuration for the RS485 Modbus communication. Available options:

• Slave Address: Address to be used as the Modbus slave address in Modbus slave mode. Valid Modbus slave address range is 1 to 247.
• Master Request Timeout: Specifies how long the master should wait for a response from a slave when in Modbus master mode.

BrickletRS485.GetModbusConfiguration() → slaveAddress, masterRequestTimeout¶

Output:	slaveAddress – Type: Byte, Range: [1 to 247], Default: 1 masterRequestTimeout – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 1000

Returns the configuration as set by SetModbusConfiguration().

BrickletRS485.SetMode(mode)¶

Input:	mode – Type: Byte, Range: See constants, Default: 0

Sets the mode of the Bricklet in which it operates. Available options are

• RS485,
• Modbus Master RTU and
• Modbus Slave RTU.

The following constants are available for this function:

For mode:

• BrickletRS485.MODE_RS485 = 0
• BrickletRS485.MODE_MODBUS_MASTER_RTU = 1
• BrickletRS485.MODE_MODBUS_SLAVE_RTU = 2

BrickletRS485.GetMode() → mode¶

Output:	mode – Type: Byte, Range: See constants, Default: 0

Returns the configuration as set by SetMode().

The following constants are available for this function:

For mode:

• BrickletRS485.MODE_RS485 = 0
• BrickletRS485.MODE_MODBUS_MASTER_RTU = 1
• BrickletRS485.MODE_MODBUS_SLAVE_RTU = 2

Advanced Functions¶

BrickletRS485.SetCommunicationLEDConfig(config)¶

Input:	config – Type: Byte, Range: See constants, Default: 3

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:

• BrickletRS485.COMMUNICATION_LED_CONFIG_OFF = 0
• BrickletRS485.COMMUNICATION_LED_CONFIG_ON = 1
• BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION = 3

BrickletRS485.GetCommunicationLEDConfig() → config¶

Output:	config – Type: Byte, Range: See constants, Default: 3

Returns the configuration as set by SetCommunicationLEDConfig()

The following constants are available for this function:

For config:

• BrickletRS485.COMMUNICATION_LED_CONFIG_OFF = 0
• BrickletRS485.COMMUNICATION_LED_CONFIG_ON = 1
• BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION = 3

BrickletRS485.SetErrorLEDConfig(config)¶

Input:	config – Type: Byte, Range: See constants, Default: 3

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:

• BrickletRS485.ERROR_LED_CONFIG_OFF = 0
• BrickletRS485.ERROR_LED_CONFIG_ON = 1
• BrickletRS485.ERROR_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.ERROR_LED_CONFIG_SHOW_ERROR = 3

BrickletRS485.GetErrorLEDConfig() → config¶

Output:	config – Type: Byte, Range: See constants, Default: 3

Returns the configuration as set by SetErrorLEDConfig().

The following constants are available for this function:

For config:

• BrickletRS485.ERROR_LED_CONFIG_OFF = 0
• BrickletRS485.ERROR_LED_CONFIG_ON = 1
• BrickletRS485.ERROR_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.ERROR_LED_CONFIG_SHOW_ERROR = 3

BrickletRS485.SetBufferConfig(sendBufferSize, receiveBufferSize)¶

Input:	sendBufferSize – Type: Int32, Unit: 1 B, Range: [210 to 9216], Default: 5120 receiveBufferSize – Type: Int32, Unit: 1 B, Range: [210 to 9216], Default: 5120

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.

BrickletRS485.GetBufferConfig() → sendBufferSize, receiveBufferSize¶

Output:	sendBufferSize – Type: Int32, Unit: 1 B, Range: [210 to 9216], Default: 5120 receiveBufferSize – Type: Int32, Unit: 1 B, Range: [210 to 9216], Default: 5120

Returns the buffer configuration as set by SetBufferConfig().

BrickletRS485.GetBufferStatus() → sendBufferUsed, receiveBufferUsed¶

Output:	sendBufferUsed – Type: Int32, Unit: 1 B, Range: [0 to 9216] receiveBufferUsed – Type: Int32, Unit: 1 B, Range: [0 to 9216]

Returns the currently used bytes for the send and received buffer.

See SetBufferConfig() for buffer size configuration.

BrickletRS485.GetErrorCount() → overrunErrorCount, parityErrorCount¶

Output:	overrunErrorCount – Type: Int64, Range: [0 to 232 - 1] parityErrorCount – Type: Int64, Range: [0 to 232 - 1]

Returns the current number of overrun and parity errors.

BrickletRS485.GetModbusCommonErrorCount() → timeoutErrorCount, checksumErrorCount, frameTooBigErrorCount, illegalFunctionErrorCount, illegalDataAddressErrorCount, illegalDataValueErrorCount, slaveDeviceFailureErrorCount¶

Output:

timeoutErrorCount – Type: Int64, Range: [0 to 232 - 1] checksumErrorCount – Type: Int64, Range: [0 to 232 - 1] frameTooBigErrorCount – Type: Int64, Range: [0 to 232 - 1] illegalFunctionErrorCount – Type: Int64, Range: [0 to 232 - 1] illegalDataAddressErrorCount – Type: Int64, Range: [0 to 232 - 1] illegalDataValueErrorCount – Type: Int64, Range: [0 to 232 - 1] slaveDeviceFailureErrorCount – Type: Int64, Range: [0 to 232 - 1]

Returns the current number of errors occurred in Modbus mode.

• Timeout Error Count: Number of timeouts occurred.
• Checksum Error Count: Number of failures due to Modbus frame CRC16 checksum mismatch.
• Frame Too Big Error Count: Number of times frames were rejected because they exceeded maximum Modbus frame size which is 256 bytes.
• Illegal Function Error Count: Number of errors when an unimplemented or illegal function is requested. This corresponds to Modbus exception code 1.
• Illegal Data Address Error Count: Number of errors due to invalid data address. This corresponds to Modbus exception code 2.
• Illegal Data Value Error Count: Number of errors due to invalid data value. This corresponds to Modbus exception code 3.
• Slave Device Failure Error Count: Number of errors occurred on the slave device which were unrecoverable. This corresponds to Modbus exception code 4.

BrickletRS485.ModbusSlaveReportException(requestID, exceptionCode)¶

Input:	requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants

In Modbus slave mode this function can be used to report a Modbus exception for a Modbus master request.

• Request ID: Request ID of the request received by the slave.
• Exception Code: Modbus exception code to report to the Modbus master.

The following constants are available for this function:

For exceptionCode:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.ModbusSlaveAnswerReadCoilsRequest(requestID, coils)¶

Input:	requestID – Type: Byte, Range: [0 to 255] coils – Type: Boolean[], Length: variable

In Modbus slave mode this function can be used to answer a master request to read coils.

• Request ID: Request ID of the corresponding request that is being answered.
• Coils: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the ModbusSlaveReadCoilsRequestCallback callback with the Request ID as provided by the argument of the callback.

BrickletRS485.ModbusMasterReadCoils(slaveAddress, startingAddress, count) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 2000]
Output:	requestID – Type: Byte, Range: [0 to 255]

In Modbus master mode this function can be used to read coils from a slave. This function creates a Modbus function code 1 request.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first coil to read. For backwards compatibility reasons this parameter is called Starting Address. It is not an address, but instead a coil number in the range of 1 to 65536.
• Count: Number of coils to read.

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.

BrickletRS485.ModbusSlaveAnswerReadHoldingRegistersRequest(requestID, holdingRegisters)¶

Input:	requestID – Type: Byte, Range: [0 to 255] holdingRegisters – Type: Int32[], Length: variable, Range: [0 to 216 - 1]

In Modbus slave mode this function can be used to answer a master request to read holding registers.

• Request ID: Request ID of the corresponding request that is being answered.
• Holding Registers: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the ModbusSlaveReadHoldingRegistersRequestCallback callback with the Request ID as provided by the argument of the callback.

BrickletRS485.ModbusMasterReadHoldingRegisters(slaveAddress, startingAddress, count) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 125]
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first holding register to read. For backwards compatibility reasons this parameter is called Starting Address. 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 implicit and must be omitted.
• Count: Number of holding registers to read.

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.

BrickletRS485.ModbusSlaveAnswerWriteSingleCoilRequest(requestID)¶

Input:	requestID – Type: Byte, Range: [0 to 255]

In Modbus slave mode this function can be used to answer a master request to write a single coil.

• Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the ModbusSlaveWriteSingleCoilRequestCallback callback with the Request ID as provided by the arguments of the callback.

BrickletRS485.ModbusMasterWriteSingleCoil(slaveAddress, coilAddress, coilValue) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] coilAddress – Type: Int64, Range: [1 to 216] coilValue – Type: Boolean
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Coil Address: Number of the coil to be written. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead a coil number in the range of 1 to 65536.
• Coil Value: Value to be written.

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.

BrickletRS485.ModbusSlaveAnswerWriteSingleRegisterRequest(requestID)¶

Input:	requestID – Type: Byte, Range: [0 to 255]

In Modbus slave mode this function can be used to answer a master request to write a single register.

• Request ID: Request ID of the corresponding request that is being answered.

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.

BrickletRS485.ModbusMasterWriteSingleRegister(slaveAddress, registerAddress, registerValue) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] registerAddress – Type: Int64, Range: [1 to 216] registerValue – Type: Int32, Range: [0 to 216 - 1]
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Register Address: Number of the holding register to be written. For backwards compatibility reasons, this parameter is called Starting Address. 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 implicit and must be omitted.
• Register Value: Value to be written.

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.

BrickletRS485.ModbusSlaveAnswerWriteMultipleCoilsRequest(requestID)¶

Input:	requestID – Type: Byte, Range: [0 to 255]

In Modbus slave mode this function can be used to answer a master request to write multiple coils.

• Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the ModbusSlaveWriteMultipleCoilsRequestCallback callback with the Request ID of the callback.

BrickletRS485.ModbusMasterWriteMultipleCoils(slaveAddress, startingAddress, coils) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] coils – Type: Boolean[], Length: variable
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first coil to write. For backwards compatibility reasons, this parameter is called Starting Address.It is not an address, but instead a coil number in the range of 1 to 65536.

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.

BrickletRS485.ModbusSlaveAnswerWriteMultipleRegistersRequest(requestID)¶

Input:	requestID – Type: Byte, Range: [0 to 255]

In Modbus slave mode this function can be used to answer a master request to write multiple registers.

• Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the ModbusSlaveWriteMultipleRegistersRequestCallback callback with the Request ID of the callback.

BrickletRS485.ModbusMasterWriteMultipleRegisters(slaveAddress, startingAddress, registers) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] registers – Type: Int32[], Length: variable, Range: [0 to 216 - 1]
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first holding register to write. For backwards compatibility reasons, this parameter is called Starting Address. 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 implicit and must be omitted.

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.

BrickletRS485.ModbusSlaveAnswerReadDiscreteInputsRequest(requestID, discreteInputs)¶

Input:	requestID – Type: Byte, Range: [0 to 255] discreteInputs – Type: Boolean[], Length: variable

In Modbus slave mode this function can be used to answer a master request to read discrete inputs.

• Request ID: Request ID of the corresponding request that is being answered.
• Discrete Inputs: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the ModbusSlaveReadDiscreteInputsRequestCallback callback with the Request ID as provided by the argument of the callback.

BrickletRS485.ModbusMasterReadDiscreteInputs(slaveAddress, startingAddress, count) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 2000]
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first discrete input to read. For backwards compatibility reasons, this parameter is called Starting Address. 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 implicit and must be omitted.
• Count: Number of discrete inputs to read.

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.

BrickletRS485.ModbusSlaveAnswerReadInputRegistersRequest(requestID, inputRegisters)¶

Input:	requestID – Type: Byte, Range: [0 to 255] inputRegisters – Type: Int32[], Length: variable, Range: [0 to 216 - 1]

In Modbus slave mode this function can be used to answer a master request to read input registers.

• Request ID: Request ID of the corresponding request that is being answered.
• Input Registers: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the ModbusSlaveReadInputRegistersRequestCallback callback with the Request ID as provided by the argument of the callback.

BrickletRS485.ModbusMasterReadInputRegisters(slaveAddress, startingAddress, count) → requestID¶

Input:	slaveAddress – Type: Byte, Range: [0 to 247] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 125]
Output:	requestID – Type: Byte, Range: [0 to 255]

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.

• Slave Address: Address of the target Modbus slave.
• Starting Address: Number of the first input register to read. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead an input register number in the range of 1 to 65536. The prefix digit 3 (for input register) is implicit and must be omitted.
• Count: Number of input registers to read.

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.

BrickletRS485.GetSPITFPErrorCount() → errorCountAckChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow¶

Output:	errorCountAckChecksum – Type: Int64, Range: [0 to 232 - 1] errorCountMessageChecksum – Type: Int64, Range: [0 to 232 - 1] errorCountFrame – Type: Int64, Range: [0 to 232 - 1] errorCountOverflow – Type: Int64, Range: [0 to 232 - 1]

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

• ACK checksum errors,
• message checksum errors,
• framing errors and
• overflow errors.

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.

BrickletRS485.SetStatusLEDConfig(config)¶

Input:	config – Type: Byte, Range: See constants, Default: 3

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:

• BrickletRS485.STATUS_LED_CONFIG_OFF = 0
• BrickletRS485.STATUS_LED_CONFIG_ON = 1
• BrickletRS485.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRS485.GetStatusLEDConfig() → config¶

Output:	config – Type: Byte, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig()

The following constants are available for this function:

For config:

• BrickletRS485.STATUS_LED_CONFIG_OFF = 0
• BrickletRS485.STATUS_LED_CONFIG_ON = 1
• BrickletRS485.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
• BrickletRS485.STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRS485.GetChipTemperature() → temperature¶

Output:	temperature – Type: Int16, Unit: 1 °C, Range: [-215 to 215 - 1]

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.

BrickletRS485.Reset()¶

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!

BrickletRS485.GetIdentity() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier¶

Output:

uid – Type: String, Length: up to 8 connectedUid – Type: String, Length: up to 8 position – Type: Char, Range: ["a" to "h", "z"] hardwareVersion – Type: Byte[3] 0: major – Type: Byte, Range: [0 to 255] 1: minor – Type: Byte, Range: [0 to 255] 2: revision – Type: Byte, Range: [0 to 255] firmwareVersion – Type: Byte[3] 0: major – Type: Byte, Range: [0 to 255] 1: minor – Type: Byte, Range: [0 to 255] 2: revision – Type: Byte, Range: [0 to 255] deviceIdentifier – Type: Int32, Range: [0 to 216 - 1]

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.

Callback Configuration Functions¶

BrickletRS485.EnableReadCallback()¶

Enables the ReadCallback callback. This will disable the FrameReadableCallback callback.

By default the callback is disabled.

BrickletRS485.DisableReadCallback()¶

Disables the ReadCallback callback.

By default the callback is disabled.

BrickletRS485.IsReadCallbackEnabled() → enabled¶

Output:	enabled – Type: Boolean, Default: F

Returns true if the ReadCallback callback is enabled, false otherwise.

BrickletRS485.EnableErrorCountCallback()¶

Enables the ErrorCountCallback callback.

By default the callback is disabled.

BrickletRS485.DisableErrorCountCallback()¶

Disables the ErrorCountCallback callback.

By default the callback is disabled.

BrickletRS485.IsErrorCountCallbackEnabled() → enabled¶

Output:	enabled – Type: Boolean, Default: T

Returns true if the ErrorCountCallback callback is enabled, false otherwise.

BrickletRS485.SetFrameReadableCallbackConfiguration(frameSize)¶

Input:	frameSize – Type: Int32, Unit: 1 B, Range: [0 to 9216], Default: 0

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).

BrickletRS485.GetFrameReadableCallbackConfiguration() → frameSize¶

Output:	frameSize – Type: Int32, Unit: 1 B, Range: [0 to 9216], Default: 0

Returns the callback configuration as set by SetFrameReadableCallbackConfiguration().

New in version 2.0.5 (Plugin).

Callbacks¶

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a function to a callback property of the device object. The available callback property and their type of parameters are described below.

event BrickletRS485.ReadCallback → sender, message¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) message – Type: Char[], Length: variable

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 null for message.

event BrickletRS485.ErrorCountCallback → sender, overrunErrorCount, parityErrorCount¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) overrunErrorCount – Type: Int64, Range: [0 to 232 - 1] parityErrorCount – Type: Int64, Range: [0 to 232 - 1]

This callback is called if a new error occurs. It returns the current overrun and parity error count.

event BrickletRS485.ModbusSlaveReadCoilsRequestCallback → sender, requestID, startingAddress, count¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 2000]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read coils. The 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().

event BrickletRS485.ModbusMasterReadCoilsResponseCallback → sender, requestID, exceptionCode, coils¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants coils – Type: Boolean[], Length: variable

This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.

The 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 null for coils.

The following constants are available for this function:

For exceptionCode:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveReadHoldingRegistersRequestCallback → sender, requestID, startingAddress, count¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 125]

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 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().

event BrickletRS485.ModbusMasterReadHoldingRegistersResponseCallback → sender, requestID, exceptionCode, holdingRegisters¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants holdingRegisters – Type: Int32[], Length: variable, Range: [0 to 216 - 1]

This callback is called only in Modbus master mode when the master receives a valid response of a request to read holding registers.

The 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 null for holdingRegisters.

The following constants are available for this function:

For exceptionCode:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveWriteSingleCoilRequestCallback → sender, requestID, coilAddress, coilValue¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] coilAddress – Type: Int64, Range: [1 to 216] coilValue – Type: Boolean

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 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().

event BrickletRS485.ModbusMasterWriteSingleCoilResponseCallback → sender, requestID, exceptionCode¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants

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 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:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveWriteSingleRegisterRequestCallback → sender, requestID, registerAddress, registerValue¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] registerAddress – Type: Int64, Range: [1 to 216] registerValue – Type: Int32, Range: [0 to 216 - 1]

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 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().

event BrickletRS485.ModbusMasterWriteSingleRegisterResponseCallback → sender, requestID, exceptionCode¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants

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 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:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveWriteMultipleCoilsRequestCallback → sender, requestID, startingAddress, coils¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] coils – Type: Boolean[], Length: variable

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 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 null for coils.

event BrickletRS485.ModbusMasterWriteMultipleCoilsResponseCallback → sender, requestID, exceptionCode¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.

The 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:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveWriteMultipleRegistersRequestCallback → sender, requestID, startingAddress, registers¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] registers – Type: Int32[], Length: variable, Range: [0 to 216 - 1]

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 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 null for registers.

event BrickletRS485.ModbusMasterWriteMultipleRegistersResponseCallback → sender, requestID, exceptionCode¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to write multiple registers.

The 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:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveReadDiscreteInputsRequestCallback → sender, requestID, startingAddress, count¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 2000]

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 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().

event BrickletRS485.ModbusMasterReadDiscreteInputsResponseCallback → sender, requestID, exceptionCode, discreteInputs¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants discreteInputs – Type: Boolean[], Length: variable

This callback is called only in Modbus master mode when the master receives a valid response of a request to read discrete inputs.

The 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 null for discreteInputs.

The following constants are available for this function:

For exceptionCode:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.ModbusSlaveReadInputRegistersRequestCallback → sender, requestID, startingAddress, count¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] startingAddress – Type: Int64, Range: [1 to 216] count – Type: Int32, Range: [1 to 125]

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 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().

event BrickletRS485.ModbusMasterReadInputRegistersResponseCallback → sender, requestID, exceptionCode, inputRegisters¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) requestID – Type: Byte, Range: [0 to 255] exceptionCode – Type: Int16, Range: See constants inputRegisters – Type: Int32[], Length: variable, Range: [0 to 216 - 1]

This callback is called only in Modbus master mode when the master receives a valid response of a request to read input registers.

The 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 null for inputRegisters.

The following constants are available for this function:

For exceptionCode:

• BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
• BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
• BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
• BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
• BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
• BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
• BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
• BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

event BrickletRS485.FrameReadableCallback → sender, frameCount¶

Callback Output:	sender – Type: .NET Refnum (BrickletRS485) frameCount – Type: Int32, Range: [0 to 216 - 1]

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 parameter.

New in version 2.0.5 (Plugin).

Virtual Functions¶

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.

BrickletRS485.GetAPIVersion() → apiVersion¶

Output:	apiVersion – Type: Byte[3] 0: major – Type: Byte, Range: [0 to 255] 1: minor – Type: Byte, Range: [0 to 255] 2: revision – Type: Byte, Range: [0 to 255]

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.

BrickletRS485.GetResponseExpected(functionId) → responseExpected¶

Input:	functionId – Type: Byte, Range: See constants
Output:	responseExpected – Type: Boolean

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:

• BrickletRS485.FUNCTION_ENABLE_READ_CALLBACK = 3
• BrickletRS485.FUNCTION_DISABLE_READ_CALLBACK = 4
• BrickletRS485.FUNCTION_SET_RS485_CONFIGURATION = 6
• BrickletRS485.FUNCTION_SET_MODBUS_CONFIGURATION = 8
• BrickletRS485.FUNCTION_SET_MODE = 10
• BrickletRS485.FUNCTION_SET_COMMUNICATION_LED_CONFIG = 12
• BrickletRS485.FUNCTION_SET_ERROR_LED_CONFIG = 14
• BrickletRS485.FUNCTION_SET_BUFFER_CONFIG = 16
• BrickletRS485.FUNCTION_ENABLE_ERROR_COUNT_CALLBACK = 19
• BrickletRS485.FUNCTION_DISABLE_ERROR_COUNT_CALLBACK = 20
• BrickletRS485.FUNCTION_MODBUS_SLAVE_REPORT_EXCEPTION = 24
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_COILS_REQUEST = 25
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_HOLDING_REGISTERS_REQUEST = 27
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_COIL_REQUEST = 29
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_REGISTER_REQUEST = 31
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_COILS_REQUEST = 33
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_REGISTERS_REQUEST = 35
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_DISCRETE_INPUTS_REQUEST = 37
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_INPUT_REGISTERS_REQUEST = 39
• BrickletRS485.FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 59
• BrickletRS485.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletRS485.FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletRS485.FUNCTION_RESET = 243
• BrickletRS485.FUNCTION_WRITE_UID = 248

BrickletRS485.SetResponseExpected(functionId, responseExpected)¶

Input:	functionId – Type: Byte, Range: See constants responseExpected – Type: Boolean

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:

• BrickletRS485.FUNCTION_ENABLE_READ_CALLBACK = 3
• BrickletRS485.FUNCTION_DISABLE_READ_CALLBACK = 4
• BrickletRS485.FUNCTION_SET_RS485_CONFIGURATION = 6
• BrickletRS485.FUNCTION_SET_MODBUS_CONFIGURATION = 8
• BrickletRS485.FUNCTION_SET_MODE = 10
• BrickletRS485.FUNCTION_SET_COMMUNICATION_LED_CONFIG = 12
• BrickletRS485.FUNCTION_SET_ERROR_LED_CONFIG = 14
• BrickletRS485.FUNCTION_SET_BUFFER_CONFIG = 16
• BrickletRS485.FUNCTION_ENABLE_ERROR_COUNT_CALLBACK = 19
• BrickletRS485.FUNCTION_DISABLE_ERROR_COUNT_CALLBACK = 20
• BrickletRS485.FUNCTION_MODBUS_SLAVE_REPORT_EXCEPTION = 24
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_COILS_REQUEST = 25
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_HOLDING_REGISTERS_REQUEST = 27
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_COIL_REQUEST = 29
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_REGISTER_REQUEST = 31
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_COILS_REQUEST = 33
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_REGISTERS_REQUEST = 35
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_DISCRETE_INPUTS_REQUEST = 37
• BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_INPUT_REGISTERS_REQUEST = 39
• BrickletRS485.FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 59
• BrickletRS485.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
• BrickletRS485.FUNCTION_SET_STATUS_LED_CONFIG = 239
• BrickletRS485.FUNCTION_RESET = 243
• BrickletRS485.FUNCTION_WRITE_UID = 248

BrickletRS485.SetResponseExpectedAll(responseExpected)¶

Input:	responseExpected – Type: Boolean

Changes the response expected flag for all setter and callback configuration functions of this device at once.

Internal Functions¶

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.

BrickletRS485.SetBootloaderMode(mode) → status¶

Input:	mode – Type: Byte, Range: See constants
Output:	status – Type: Byte, Range: See constants

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:

• BrickletRS485.BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE = 1
• BrickletRS485.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

• BrickletRS485.BOOTLOADER_STATUS_OK = 0
• BrickletRS485.BOOTLOADER_STATUS_INVALID_MODE = 1
• BrickletRS485.BOOTLOADER_STATUS_NO_CHANGE = 2
• BrickletRS485.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
• BrickletRS485.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
• BrickletRS485.BOOTLOADER_STATUS_CRC_MISMATCH = 5

BrickletRS485.GetBootloaderMode() → mode¶

Output:	mode – Type: Byte, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode().

The following constants are available for this function:

For mode:

• BrickletRS485.BOOTLOADER_MODE_BOOTLOADER = 0
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE = 1
• BrickletRS485.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
• BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

BrickletRS485.SetWriteFirmwarePointer(pointer)¶

Input:	pointer – Type: Int64, Unit: 1 B, Range: [0 to 232 - 1]

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.

BrickletRS485.WriteFirmware(data) → status¶

Input:	data – Type: Byte[64], Range: [0 to 255]
Output:	status – Type: Byte, Range: [0 to 255]

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.

BrickletRS485.WriteUID(uid)¶

Input:	uid – Type: Int64, Range: [0 to 232 - 1]

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.

BrickletRS485.ReadUID() → uid¶

Output:	uid – Type: Int64, Range: [0 to 232 - 1]

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

Constants¶

BrickletRS485.DEVICE_IDENTIFIER¶

This constant is used to identify a RS485 Bricklet.

The GetIdentity() function and the IPConnection.EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickletRS485.DEVICE_DISPLAY_NAME¶

This constant represents the human readable name of a RS485 Bricklet.