Struct tinkerforge::rs485_bricklet::Rs485Bricklet

pub struct Rs485Bricklet { /* private fields */ }

Communicates with RS485/Modbus devices with full- or half-duplex

Implementations

impl Rs485Bricklet

pub const DEVICE_IDENTIFIER: u16 = 277u16

pub const DEVICE_DISPLAY_NAME: &'static str = "RS485 Bricklet"

pub fn new(uid: &str, ip_connection: &IpConnection) -> Rs485Bricklet

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

pub fn get_response_expected(
    &mut self,
    fun: Rs485BrickletFunction
) -> Result<bool, GetResponseExpectedError>

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 set_response_expected. For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

See set_response_expected for the list of function ID constants available for this function.

pub fn set_response_expected(
    &mut self,
    fun: Rs485BrickletFunction,
    response_expected: bool
) -> Result<(), SetResponseExpectedError>

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

pub fn set_response_expected_all(&mut self, response_expected: bool)

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

pub fn get_read_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ReadLowLevelEvent>

This receiver is called if new data is available.

To enable this receiver, use Enable Read Receiver.

pub fn get_read_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<char, ReadResult, ReadLowLevelEvent>

This receiver is called if new data is available.

To enable this receiver, use Enable Read Receiver.

pub fn get_error_count_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ErrorCountEvent>

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

pub fn get_modbus_slave_read_coils_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveReadCoilsRequestEvent>

This receiver 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 starting address and the number of coils to be read as received by the request.

To send a response of this request use Modbus Slave Answer Read Coils Request.

pub fn get_modbus_master_read_coils_response_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterReadCoilsResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_master_read_coils_response_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<bool, ModbusMasterReadCoilsResponseResult, ModbusMasterReadCoilsResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_read_holding_registers_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveReadHoldingRegistersRequestEvent>

This receiver 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 starting address and the number of holding registers to be read as received by the request.

To send a response of this request use Modbus Slave Answer Read Holding Registers Request.

pub fn get_modbus_master_read_holding_registers_response_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterReadHoldingRegistersResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_master_read_holding_registers_response_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<u16, ModbusMasterReadHoldingRegistersResponseResult, ModbusMasterReadHoldingRegistersResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_write_single_coil_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveWriteSingleCoilRequestEvent>

This receiver 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 coil address and the value of coil to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Single Coil Request.

pub fn get_modbus_master_write_single_coil_response_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterWriteSingleCoilResponseEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_write_single_register_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveWriteSingleRegisterRequestEvent>

This receiver is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write a single register. The parameters are request ID of the request, the register address and the register value to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Single Register Request.

pub fn get_modbus_master_write_single_register_response_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterWriteSingleRegisterResponseEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_write_multiple_coils_request_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveWriteMultipleCoilsRequestLowLevelEvent>

This receiver 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 starting address and the data to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Multiple Coils Request.

pub fn get_modbus_slave_write_multiple_coils_request_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<bool, ModbusSlaveWriteMultipleCoilsRequestResult, ModbusSlaveWriteMultipleCoilsRequestLowLevelEvent>

This receiver 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 starting address and the data to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Multiple Coils Request.

pub fn get_modbus_master_write_multiple_coils_response_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterWriteMultipleCoilsResponseEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_write_multiple_registers_request_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveWriteMultipleRegistersRequestLowLevelEvent>

This receiver is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple registers. The parameters are request ID of the request, the starting address and the data to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Multiple Registers Request.

pub fn get_modbus_slave_write_multiple_registers_request_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<u16, ModbusSlaveWriteMultipleRegistersRequestResult, ModbusSlaveWriteMultipleRegistersRequestLowLevelEvent>

This receiver is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple registers. The parameters are request ID of the request, the starting address and the data to be written as received by the request.

To send a response of this request use Modbus Slave Answer Write Multiple Registers Request.

pub fn get_modbus_master_write_multiple_registers_response_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterWriteMultipleRegistersResponseEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_read_discrete_inputs_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveReadDiscreteInputsRequestEvent>

This receiver 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 starting address and the number of discrete inputs to be read as received by the request.

To send a response of this request use Modbus Slave Answer Read Discrete Inputs Request.

pub fn get_modbus_master_read_discrete_inputs_response_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterReadDiscreteInputsResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_master_read_discrete_inputs_response_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<bool, ModbusMasterReadDiscreteInputsResponseResult, ModbusMasterReadDiscreteInputsResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_slave_read_input_registers_request_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusSlaveReadInputRegistersRequestEvent>

This receiver 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 starting address and the number of input registers to be read as received by the request.

To send a response of this request use Modbus Slave Answer Read Input Registers Request.

pub fn get_modbus_master_read_input_registers_response_low_level_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<ModbusMasterReadInputRegistersResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn get_modbus_master_read_input_registers_response_callback_receiver(
    &self
) -> ConvertingHighLevelCallbackReceiver<u16, ModbusMasterReadInputRegistersResponseResult, ModbusMasterReadInputRegistersResponseLowLevelEvent>

This receiver 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 zero then the number represents a Modbus exception code. If it is less than zero 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 Set Modbus Configuration.

pub fn write_low_level(
    &self,
    message_length: u16,
    message_chunk_offset: u16,
    message_chunk_data: [char; 60]
) -> ConvertingReceiver<WriteLowLevel>

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 Set RS485 Configuration for configuration possibilities regarding baudrate, parity and so on.

pub fn write(&self, message: &[char]) -> Result<usize, BrickletRecvTimeoutError>

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 Set RS485 Configuration for configuration possibilities regarding baudrate, parity and so on.

pub fn read_low_level(&self, length: u16) -> ConvertingReceiver<ReadLowLevel>

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 receiver is disabled. See Enable Read Receiver and get_read_callback_receiver receiver.

pub fn read(&self, length: u16) -> Result<Vec<char>, BrickletRecvTimeoutError>

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 receiver is disabled. See Enable Read Receiver and get_read_callback_receiver receiver.

pub fn enable_read_callback(&self) -> ConvertingReceiver<()>

Enables the get_read_callback_receiver receiver.

By default the receiver is disabled.

pub fn disable_read_callback(&self) -> ConvertingReceiver<()>

Disables the get_read_callback_receiver receiver.

By default the receiver is disabled.

pub fn is_read_callback_enabled(&self) -> ConvertingReceiver<bool>

Returns true if the get_read_callback_receiver receiver is enabled, false otherwise.

pub fn set_rs485_configuration(
    &self,
    baudrate: u32,
    parity: u8,
    stopbits: u8,
    wordlength: u8,
    duplex: u8
) -> ConvertingReceiver<()>

Sets the configuration for the RS485 communication. Available options:

• Baudrate between 100 and 2000000 baud.
• Parity of none, odd or even.
• Stopbits can be 1 or 2.
• Word length of 5 to 8.
• Half- or Full-Duplex.

The default is: 115200 baud, parity none, 1 stop bit, word length 8, half duplex.

Associated constants:

• RS485BRICKLET_PARITY_NONE
• RS485BRICKLET_PARITY_ODD
• RS485BRICKLET_PARITY_EVEN
• RS485BRICKLET_STOPBITS_1
• RS485BRICKLET_STOPBITS_2
• RS485BRICKLET_WORDLENGTH_5
• RS485BRICKLET_WORDLENGTH_6
• RS485BRICKLET_WORDLENGTH_7
• RS485BRICKLET_WORDLENGTH_8
• RS485BRICKLET_DUPLEX_HALF
• RS485BRICKLET_DUPLEX_FULL

pub fn get_rs485_configuration(&self) -> ConvertingReceiver<Rs485Configuration>

Returns the configuration as set by Set RS485 Configuration.

Associated constants:

• RS485BRICKLET_PARITY_NONE
• RS485BRICKLET_PARITY_ODD
• RS485BRICKLET_PARITY_EVEN
• RS485BRICKLET_STOPBITS_1
• RS485BRICKLET_STOPBITS_2
• RS485BRICKLET_WORDLENGTH_5
• RS485BRICKLET_WORDLENGTH_6
• RS485BRICKLET_WORDLENGTH_7
• RS485BRICKLET_WORDLENGTH_8
• RS485BRICKLET_DUPLEX_HALF
• RS485BRICKLET_DUPLEX_FULL

pub fn set_modbus_configuration(
    &self,
    slave_address: u8,
    master_request_timeout: u32
) -> ConvertingReceiver<()>

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 in milliseconds when in Modbus master mode.

The default is: Slave Address = 1 and Master Request Timeout = 1000 milliseconds (1 second).

pub fn get_modbus_configuration(
    &self
) -> ConvertingReceiver<ModbusConfiguration>

Returns the configuration as set by Set Modbus Configuration.

pub fn set_mode(&self, mode: u8) -> ConvertingReceiver<()>

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

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

The default is: RS485 mode.

Associated constants:

• RS485BRICKLET_MODE_RS485
• RS485BRICKLET_MODE_MODBUS_MASTER_RTU
• RS485BRICKLET_MODE_MODBUS_SLAVE_RTU

pub fn get_mode(&self) -> ConvertingReceiver<u8>

Returns the configuration as set by Set Mode.

Associated constants:

• RS485BRICKLET_MODE_RS485
• RS485BRICKLET_MODE_MODBUS_MASTER_RTU
• RS485BRICKLET_MODE_MODBUS_SLAVE_RTU

pub fn set_communication_led_config(&self, config: u8) -> ConvertingReceiver<()>

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.

Associated constants:

• RS485BRICKLET_COMMUNICATION_LED_CONFIG_OFF
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_ON
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION

pub fn get_communication_led_config(&self) -> ConvertingReceiver<u8>

Returns the configuration as set by Set Communication LED Config

Associated constants:

• RS485BRICKLET_COMMUNICATION_LED_CONFIG_OFF
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_ON
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION

pub fn set_error_led_config(&self, config: u8) -> ConvertingReceiver<()>

Sets the error LED configuration.

By default the error LED turns on if there is any error (see get_error_count_callback_receiver 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.

Associated constants:

• RS485BRICKLET_ERROR_LED_CONFIG_OFF
• RS485BRICKLET_ERROR_LED_CONFIG_ON
• RS485BRICKLET_ERROR_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_ERROR_LED_CONFIG_SHOW_ERROR

pub fn get_error_led_config(&self) -> ConvertingReceiver<u8>

Returns the configuration as set by Set Error LED Config.

Associated constants:

• RS485BRICKLET_ERROR_LED_CONFIG_OFF
• RS485BRICKLET_ERROR_LED_CONFIG_ON
• RS485BRICKLET_ERROR_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_ERROR_LED_CONFIG_SHOW_ERROR

pub fn set_buffer_config(
    &self,
    send_buffer_size: u16,
    receive_buffer_size: u16
) -> ConvertingReceiver<()>

Sets the send and receive buffer size in byte. In sum there is 10240 byte (10kb) buffer available and the minimum buffer size is 1024 byte (1kb) 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 get_read_callback_receiver receiver.

The default configuration is 5120 byte (5kb) per buffer.

pub fn get_buffer_config(&self) -> ConvertingReceiver<BufferConfig>

Returns the buffer configuration as set by Set Buffer Config.

pub fn get_buffer_status(&self) -> ConvertingReceiver<BufferStatus>

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

See Set Buffer Config for buffer size configuration.

pub fn enable_error_count_callback(&self) -> ConvertingReceiver<()>

Enables the get_error_count_callback_receiver receiver.

By default the receiver is disabled.

pub fn disable_error_count_callback(&self) -> ConvertingReceiver<()>

Disables the get_error_count_callback_receiver receiver.

By default the receiver is disabled.

pub fn is_error_count_callback_enabled(&self) -> ConvertingReceiver<bool>

Returns true if the get_error_count_callback_receiver receiver is enabled, false otherwise.

pub fn get_error_count(&self) -> ConvertingReceiver<ErrorCount>

Returns the current number of overrun and parity errors.

pub fn get_modbus_common_error_count(
    &self
) -> ConvertingReceiver<ModbusCommonErrorCount>

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.

pub fn modbus_slave_report_exception(
    &self,
    request_id: u8,
    exception_code: i8
) -> ConvertingReceiver<()>

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.

Associated constants:

• RS485BRICKLET_EXCEPTION_CODE_TIMEOUT
• RS485BRICKLET_EXCEPTION_CODE_SUCCESS
• RS485BRICKLET_EXCEPTION_CODE_ILLEGAL_FUNCTION
• RS485BRICKLET_EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS
• RS485BRICKLET_EXCEPTION_CODE_ILLEGAL_DATA_VALUE
• RS485BRICKLET_EXCEPTION_CODE_SLAVE_DEVICE_FAILURE
• RS485BRICKLET_EXCEPTION_CODE_ACKNOWLEDGE
• RS485BRICKLET_EXCEPTION_CODE_SLAVE_DEVICE_BUSY
• RS485BRICKLET_EXCEPTION_CODE_MEMORY_PARITY_ERROR
• RS485BRICKLET_EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE
• RS485BRICKLET_EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND

pub fn modbus_slave_answer_read_coils_request_low_level(
    &self,
    request_id: u8,
    coils_length: u16,
    coils_chunk_offset: u16,
    coils_chunk_data: [bool; 472]
) -> ConvertingReceiver<ModbusSlaveAnswerReadCoilsRequestLowLevel>

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 get_modbus_slave_read_coils_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_slave_answer_read_coils_request(
    &self,
    request_id: u8,
    coils: &[bool]
) -> Result<(), BrickletRecvTimeoutError>

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 get_modbus_slave_read_coils_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_master_read_coils(
    &self,
    slave_address: u8,
    starting_address: u32,
    count: u16
) -> ConvertingReceiver<u8>

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: Starting address of the read.
• 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 get_modbus_master_read_coils_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_read_holding_registers_request_low_level(
    &self,
    request_id: u8,
    holding_registers_length: u16,
    holding_registers_chunk_offset: u16,
    holding_registers_chunk_data: [u16; 29]
) -> ConvertingReceiver<ModbusSlaveAnswerReadHoldingRegistersRequestLowLevel>

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 get_modbus_slave_read_holding_registers_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_slave_answer_read_holding_registers_request(
    &self,
    request_id: u8,
    holding_registers: &[u16]
) -> Result<(), BrickletRecvTimeoutError>

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 get_modbus_slave_read_holding_registers_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_master_read_holding_registers(
    &self,
    slave_address: u8,
    starting_address: u32,
    count: u16
) -> ConvertingReceiver<u8>

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: Starting address of the read.
• 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 get_modbus_master_read_holding_registers_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_write_single_coil_request(
    &self,
    request_id: u8
) -> ConvertingReceiver<()>

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 get_modbus_slave_write_single_coil_request_callback_receiver receiver with the Request ID as provided by the arguments of the receiver.

pub fn modbus_master_write_single_coil(
    &self,
    slave_address: u8,
    coil_address: u32,
    coil_value: bool
) -> ConvertingReceiver<u8>

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: Address of the coil.
• 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 get_modbus_master_write_single_coil_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_write_single_register_request(
    &self,
    request_id: u8
) -> ConvertingReceiver<()>

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 get_modbus_slave_write_single_register_request_callback_receiver receiver with the Request ID, Register Address and Register Value as provided by the arguments of the receiver.

pub fn modbus_master_write_single_register(
    &self,
    slave_address: u8,
    register_address: u32,
    register_value: u16
) -> ConvertingReceiver<u8>

In Modbus master mode this function can be used to write a single register of a slave. This function creates a Modbus function code 6 request.

• Slave Address: Address of the target Modbus slave.
• Register Address: Address of the register.
• 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 get_modbus_master_write_single_register_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_write_multiple_coils_request(
    &self,
    request_id: u8
) -> ConvertingReceiver<()>

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 get_modbus_slave_write_multiple_coils_request_callback_receiver receiver with the Request ID of the receiver.

pub fn modbus_master_write_multiple_coils_low_level(
    &self,
    slave_address: u8,
    starting_address: u32,
    coils_length: u16,
    coils_chunk_offset: u16,
    coils_chunk_data: [bool; 440]
) -> ConvertingReceiver<ModbusMasterWriteMultipleCoilsLowLevel>

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: Starting address of the write.

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 get_modbus_master_write_multiple_coils_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_master_write_multiple_coils(
    &self,
    slave_address: u8,
    starting_address: u32,
    coils: &[bool]
) -> Result<u8, BrickletRecvTimeoutError>

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: Starting address of the write.

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 get_modbus_master_write_multiple_coils_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_write_multiple_registers_request(
    &self,
    request_id: u8
) -> ConvertingReceiver<()>

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 get_modbus_slave_write_multiple_registers_request_callback_receiver receiver with the Request ID of the receiver.

pub fn modbus_master_write_multiple_registers_low_level(
    &self,
    slave_address: u8,
    starting_address: u32,
    registers_length: u16,
    registers_chunk_offset: u16,
    registers_chunk_data: [u16; 27]
) -> ConvertingReceiver<ModbusMasterWriteMultipleRegistersLowLevel>

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: Starting Address of the write.

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 get_modbus_master_write_multiple_registers_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_master_write_multiple_registers(
    &self,
    slave_address: u8,
    starting_address: u32,
    registers: &[u16]
) -> Result<u8, BrickletRecvTimeoutError>

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: Starting Address of the write.

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 get_modbus_master_write_multiple_registers_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_read_discrete_inputs_request_low_level(
    &self,
    request_id: u8,
    discrete_inputs_length: u16,
    discrete_inputs_chunk_offset: u16,
    discrete_inputs_chunk_data: [bool; 472]
) -> ConvertingReceiver<ModbusSlaveAnswerReadDiscreteInputsRequestLowLevel>

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 get_modbus_slave_read_discrete_inputs_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_slave_answer_read_discrete_inputs_request(
    &self,
    request_id: u8,
    discrete_inputs: &[bool]
) -> Result<(), BrickletRecvTimeoutError>

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 get_modbus_slave_read_discrete_inputs_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_master_read_discrete_inputs(
    &self,
    slave_address: u8,
    starting_address: u32,
    count: u16
) -> ConvertingReceiver<u8>

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: Starting address of the read.
• 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 get_modbus_master_read_discrete_inputs_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn modbus_slave_answer_read_input_registers_request_low_level(
    &self,
    request_id: u8,
    input_registers_length: u16,
    input_registers_chunk_offset: u16,
    input_registers_chunk_data: [u16; 29]
) -> ConvertingReceiver<ModbusSlaveAnswerReadInputRegistersRequestLowLevel>

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 get_modbus_slave_read_input_registers_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_slave_answer_read_input_registers_request(
    &self,
    request_id: u8,
    input_registers: &[u16]
) -> Result<(), BrickletRecvTimeoutError>

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 get_modbus_slave_read_input_registers_request_callback_receiver receiver with the Request ID as provided by the argument of the receiver.

pub fn modbus_master_read_input_registers(
    &self,
    slave_address: u8,
    starting_address: u32,
    count: u16
) -> ConvertingReceiver<u8>

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: Starting address of the read.
• 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 get_modbus_master_read_input_registers_response_callback_receiver callback. In this receiver the Request ID provided by the receiver argument must be matched with the Request ID returned from this function to verify that the receiver is indeed for a particular request.

pub fn get_spitfp_error_count(&self) -> ConvertingReceiver<SpitfpErrorCount>

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.

pub fn set_bootloader_mode(&self, mode: u8) -> ConvertingReceiver<u8>

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.

Associated constants:

• RS485BRICKLET_BOOTLOADER_MODE_BOOTLOADER
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE
• RS485BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT
• RS485BRICKLET_BOOTLOADER_STATUS_OK
• RS485BRICKLET_BOOTLOADER_STATUS_INVALID_MODE
• RS485BRICKLET_BOOTLOADER_STATUS_NO_CHANGE
• RS485BRICKLET_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT
• RS485BRICKLET_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT
• RS485BRICKLET_BOOTLOADER_STATUS_CRC_MISMATCH

pub fn get_bootloader_mode(&self) -> ConvertingReceiver<u8>

Returns the current bootloader mode, see Set Bootloader Mode.

Associated constants:

• RS485BRICKLET_BOOTLOADER_MODE_BOOTLOADER
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE
• RS485BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT
• RS485BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT

pub fn set_write_firmware_pointer(&self, pointer: u32) -> ConvertingReceiver<()>

Sets the firmware pointer for Write Firmware. 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.

pub fn write_firmware(&self, data: [u8; 64]) -> ConvertingReceiver<u8>

Writes 64 Bytes of firmware at the position as written by Set Write Firmware Pointer 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.

pub fn set_status_led_config(&self, config: u8) -> ConvertingReceiver<()>

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.

Associated constants:

• RS485BRICKLET_STATUS_LED_CONFIG_OFF
• RS485BRICKLET_STATUS_LED_CONFIG_ON
• RS485BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS

pub fn get_status_led_config(&self) -> ConvertingReceiver<u8>

Returns the configuration as set by Set Status LED Config

Associated constants:

• RS485BRICKLET_STATUS_LED_CONFIG_OFF
• RS485BRICKLET_STATUS_LED_CONFIG_ON
• RS485BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT
• RS485BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS

pub fn get_chip_temperature(&self) -> ConvertingReceiver<i16>

Returns the temperature in °C 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.

pub fn reset(&self) -> ConvertingReceiver<()>

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!

pub fn write_uid(&self, uid: u32) -> ConvertingReceiver<()>

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.

pub fn read_uid(&self) -> ConvertingReceiver<u32>

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

pub fn get_identity(&self) -> ConvertingReceiver<Identity>

Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.

The position can be ‘a’, ‘b’, ‘c’ or ‘d’.

The device identifier numbers can be found here. |device_identifier_constant|

Trait Implementations

impl Clone for Rs485Bricklet

fn clone(&self) -> Rs485Bricklet

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.