Struct MasterBrick 

pub struct MasterBrick { /* private fields */ }

Basis to build stacks and has 4 Bricklet ports

Implementations

impl MasterBrick

pub const DEVICE_IDENTIFIER: u16 = 13u16

pub const DEVICE_DISPLAY_NAME: &'static str = "Master Brick"

pub fn new<T: GetRequestSender>(uid: &str, req_sender: T) -> MasterBrick

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: MasterBrickFunction, ) -> 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 sent 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: MasterBrickFunction, 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 sent 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_api_version(&self) -> [u8; 3]

Returns the version of the API definition (major, minor, revision) 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.

pub fn get_stack_current_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered periodically with the period that is set by set_stack_current_callback_period. The parameter is the current of the sensor.

The get_stack_current_callback_receiver receiver is only triggered if the current has changed since the last triggering.

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_stack_voltage_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered periodically with the period that is set by [set_stack_voltage_callback_period]. The parameter is the voltage of the sensor.

The [get_stack_voltage_callback_receiver] receiver is only triggered if the voltage has changed since the last triggering.

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_usb_voltage_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered periodically with the period that is set by [set_usb_voltage_callback_period]. The parameter is the USB voltage.

The [get_usb_voltage_callback_receiver] receiver is only triggered if the USB voltage has changed since the last triggering.

Does not work with hardware version 2.1 or newer.

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_stack_current_reached_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered when the threshold as set by [set_stack_current_callback_threshold] is reached. The parameter is the stack current.

If the threshold keeps being reached, the receiver is triggered periodically with the period as set by [set_debounce_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_stack_voltage_reached_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered when the threshold as set by [set_stack_voltage_callback_threshold] is reached. The parameter is the stack voltage.

If the threshold keeps being reached, the receiver is triggered periodically with the period as set by [set_debounce_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_usb_voltage_reached_callback_receiver( &self, ) -> ConvertingCallbackReceiver<u16>

This receiver is triggered when the threshold as set by [set_usb_voltage_callback_threshold] is reached. The parameter is the voltage of the sensor.

If the threshold keeps being reached, the receiver is triggered periodically with the period as set by [set_debounce_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_stack_voltage(&self) -> ConvertingReceiver<u16>

Returns the stack voltage. The stack voltage is the voltage that is supplied via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.

Note

It is not possible to measure voltages supplied per PoE or USB with this function.

pub fn get_stack_current(&self) -> ConvertingReceiver<u16>

Returns the stack current. The stack current is the current that is drawn via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.

Note

It is not possible to measure the current drawn via PoE or USB with this function.

pub fn set_extension_type( &self, extension: u8, exttype: u32, ) -> ConvertingReceiver<()>

Writes the extension type to the EEPROM of a specified extension. The extension is either 0 or 1 (0 is the lower one, 1 is the upper one, if only one extension is present use 0).

Possible extension types:

Type	Description
1	Chibi
2	RS485
3	WIFI
4	Ethernet
5	WIFI 2.0

The extension type is already set when bought and it can be set with the Brick Viewer, it is unlikely that you need this function.

Associated constants:

• MASTER_BRICK_EXTENSION_TYPE_CHIBI
• MASTER_BRICK_EXTENSION_TYPE_RS485
• MASTER_BRICK_EXTENSION_TYPE_WIFI
• MASTER_BRICK_EXTENSION_TYPE_ETHERNET
• MASTER_BRICK_EXTENSION_TYPE_WIFI2

pub fn get_extension_type(&self, extension: u8) -> ConvertingReceiver<u32>

Returns the type for a given extension as set by [set_extension_type].

Associated constants:

• MASTER_BRICK_EXTENSION_TYPE_CHIBI
• MASTER_BRICK_EXTENSION_TYPE_RS485
• MASTER_BRICK_EXTENSION_TYPE_WIFI
• MASTER_BRICK_EXTENSION_TYPE_ETHERNET
• MASTER_BRICK_EXTENSION_TYPE_WIFI2

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

Returns true if the Master Brick is at position 0 in the stack and a Chibi Extension is available.

pub fn set_chibi_address(&self, address: u8) -> ConvertingReceiver<()>

Sets the address belonging to the Chibi Extension.

It is possible to set the address with the Brick Viewer and it will be saved in the EEPROM of the Chibi Extension, it does not have to be set on every startup.

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

Returns the address as set by [set_chibi_address].

pub fn set_chibi_master_address(&self, address: u8) -> ConvertingReceiver<()>

Sets the address of the Chibi Master. This address is used if the Chibi Extension is used as slave (i.e. it does not have a USB connection).

It is possible to set the address with the Brick Viewer and it will be saved in the EEPROM of the Chibi Extension, it does not have to be set on every startup.

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

Returns the address as set by [set_chibi_master_address].

pub fn set_chibi_slave_address( &self, num: u8, address: u8, ) -> ConvertingReceiver<()>

Sets up to 254 slave addresses. 0 has a special meaning, it is used as list terminator and not allowed as normal slave address. The address numeration (via \c num parameter) has to be used ascending from 0. For example: If you use the Chibi Extension in Master mode (i.e. the stack has an USB connection) and you want to talk to three other Chibi stacks with the slave addresses 17, 23, and 42, you should call with (0, 17), (1, 23), (2, 42) and (3, 0). The last call with (3, 0) is a list terminator and indicates that the Chibi slave address list contains 3 addresses in this case.

It is possible to set the addresses with the Brick Viewer, that will take care of correct address numeration and list termination.

The slave addresses will be saved in the EEPROM of the Chibi Extension, they don’t have to be set on every startup.

pub fn get_chibi_slave_address(&self, num: u8) -> ConvertingReceiver<u8>

Returns the slave address for a given \c num as set by [set_chibi_slave_address].

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

Returns the signal strength in dBm. The signal strength updates every time a packet is received.

pub fn get_chibi_error_log(&self) -> ConvertingReceiver<ChibiErrorLog>

Returns underrun, CRC error, no ACK and overflow error counts of the Chibi communication. If these errors start rising, it is likely that either the distance between two Chibi stacks is becoming too big or there are interferences.

pub fn set_chibi_frequency(&self, frequency: u8) -> ConvertingReceiver<()>

Sets the Chibi frequency range for the Chibi Extension. Possible values are:

Type	Description
0	OQPSK 868MHz (Europe)
1	OQPSK 915MHz (US)
2	OQPSK 780MHz (China)
3	BPSK40 915MHz

It is possible to set the frequency with the Brick Viewer and it will be saved in the EEPROM of the Chibi Extension, it does not have to be set on every startup.

Associated constants:

• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_868_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_915_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_780_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_BPSK40_915_MHZ

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

Returns the frequency value as set by [set_chibi_frequency].

Associated constants:

• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_868_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_915_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_OQPSK_780_MHZ
• MASTER_BRICK_CHIBI_FREQUENCY_BPSK40_915_MHZ

pub fn set_chibi_channel(&self, channel: u8) -> ConvertingReceiver<()>

Sets the channel used by the Chibi Extension. Possible channels are different for different frequencies:

Frequency	Possible Channels
OQPSK 868MHz (Europe)	0
OQPSK 915MHz (US)	1
OQPSK 780MHz (China)	0
BPSK40 915MHz	1

It is possible to set the channel with the Brick Viewer and it will be saved in the EEPROM of the Chibi Extension, it does not have to be set on every startup.

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

Returns the channel as set by [set_chibi_channel].

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

Returns true if the Master Brick is at position 0 in the stack and a RS485 Extension is available.

pub fn set_rs485_address(&self, address: u8) -> ConvertingReceiver<()>

Sets the address (0-255) belonging to the RS485 Extension.

Set to 0 if the RS485 Extension should be the RS485 Master (i.e. connected to a PC via USB).

It is possible to set the address with the Brick Viewer and it will be saved in the EEPROM of the RS485 Extension, it does not have to be set on every startup.

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

Returns the address as set by [set_rs485_address].

pub fn set_rs485_slave_address( &self, num: u8, address: u8, ) -> ConvertingReceiver<()>

Sets up to 255 slave addresses. Valid addresses are in range 1-255. 0 has a special meaning, it is used as list terminator and not allowed as normal slave address. The address numeration (via num parameter) has to be used ascending from 0. For example: If you use the RS485 Extension in Master mode (i.e. the stack has an USB connection) and you want to talk to three other RS485 stacks with the addresses 17, 23, and 42, you should call with (0, 17), (1, 23), (2, 42) and (3, 0). The last call with (3, 0) is a list terminator and indicates that the RS485 slave address list contains 3 addresses in this case.

It is possible to set the addresses with the Brick Viewer, that will take care of correct address numeration and list termination.

The slave addresses will be saved in the EEPROM of the Chibi Extension, they don’t have to be set on every startup.

pub fn get_rs485_slave_address(&self, num: u8) -> ConvertingReceiver<u8>

Returns the slave address for a given num as set by [set_rs485_slave_address].

pub fn get_rs485_error_log(&self) -> ConvertingReceiver<u16>

Returns CRC error counts of the RS485 communication. If this counter starts rising, it is likely that the distance between the RS485 nodes is too big or there is some kind of interference.

pub fn set_rs485_configuration( &self, speed: u32, parity: char, stopbits: u8, ) -> ConvertingReceiver<()>

Sets the configuration of the RS485 Extension. The Master Brick will try to match the given baud rate as exactly as possible. The maximum recommended baud rate is 2000000 (2MBd). Possible values for parity are ‘n’ (none), ‘e’ (even) and ‘o’ (odd).

If your RS485 is unstable (lost messages etc.), the first thing you should try is to decrease the speed. On very large bus (e.g. 1km), you probably should use a value in the range of 100000 (100kBd).

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

Associated constants:

• MASTER_BRICK_RS485_PARITY_NONE
• MASTER_BRICK_RS485_PARITY_EVEN
• MASTER_BRICK_RS485_PARITY_ODD

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

Returns the configuration as set by [set_rs485_configuration].

Associated constants:

• MASTER_BRICK_RS485_PARITY_NONE
• MASTER_BRICK_RS485_PARITY_EVEN
• MASTER_BRICK_RS485_PARITY_ODD

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

Returns true if the Master Brick is at position 0 in the stack and a WIFI Extension is available.

pub fn set_wifi_configuration( &self, ssid: String, connection: u8, ip: [u8; 4], subnet_mask: [u8; 4], gateway: [u8; 4], port: u16, ) -> ConvertingReceiver<()>

Sets the configuration of the WIFI Extension. The ssid can have a max length of 32 characters. Possible values for connection are:

Value	Description
0	DHCP
1	Static IP
2	Access Point: DHCP
3	Access Point: Static IP
4	Ad Hoc: DHCP
5	Ad Hoc: Static IP

If you set connection to one of the static IP options then you have to supply ip, subnet_mask and gateway as an array of size 4 (first element of the array is the least significant byte of the address). If connection is set to one of the DHCP options then ip, subnet_mask and gateway are ignored, you can set them to 0.

The last parameter is the port that your program will connect to.

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the WIFI configuration.

Associated constants:

• MASTER_BRICK_WIFI_CONNECTION_DHCP
• MASTER_BRICK_WIFI_CONNECTION_STATIC_IP
• MASTER_BRICK_WIFI_CONNECTION_ACCESS_POINT_DHCP
• MASTER_BRICK_WIFI_CONNECTION_ACCESS_POINT_STATIC_IP
• MASTER_BRICK_WIFI_CONNECTION_AD_HOC_DHCP
• MASTER_BRICK_WIFI_CONNECTION_AD_HOC_STATIC_IP

pub fn get_wifi_configuration(&self) -> ConvertingReceiver<WifiConfiguration>

Returns the configuration as set by [set_wifi_configuration].

Associated constants:

• MASTER_BRICK_WIFI_CONNECTION_DHCP
• MASTER_BRICK_WIFI_CONNECTION_STATIC_IP
• MASTER_BRICK_WIFI_CONNECTION_ACCESS_POINT_DHCP
• MASTER_BRICK_WIFI_CONNECTION_ACCESS_POINT_STATIC_IP
• MASTER_BRICK_WIFI_CONNECTION_AD_HOC_DHCP
• MASTER_BRICK_WIFI_CONNECTION_AD_HOC_STATIC_IP

pub fn set_wifi_encryption( &self, encryption: u8, key: String, key_index: u8, eap_options: u8, ca_certificate_length: u16, client_certificate_length: u16, private_key_length: u16, ) -> ConvertingReceiver<()>

Sets the encryption of the WIFI Extension. The first parameter is the type of the encryption. Possible values are:

Value	Description
0	WPA/WPA2
1	WPA Enterprise (EAP-FAST
2	WEP
3	No Encryption

The key has a max length of 50 characters and is used if encryption is set to 0 or 2 (WPA/WPA2 or WEP). Otherwise the value is ignored.

For WPA/WPA2 the key has to be at least 8 characters long. If you want to set a key with more than 50 characters, see [set_long_wifi_key].

For WEP the key has to be either 10 or 26 hexadecimal digits long. It is possible to set the WEP key_index (1-4). If you don’t know your key_index, it is likely 1.

If you choose WPA Enterprise as encryption, you have to set eap_options and the length of the certificates (for other encryption types these parameters are ignored). The certificates themselves can be set with [set_wifi_certificate]. eap_options consist of the outer authentication (bits 1-2), inner authentication (bit 3) and certificate type (bits 4-5):

Option	Bits	Description
outer authentication	1-2	0=EAP-FAST
inner authentication	3	0=EAP-MSCHAP
certificate type	4-5	0=CA Certificate

Example for EAP-TTLS + EAP-GTC + Private Key: option = 2 | (1 << 2) | (2 << 3).

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the Wi-Fi encryption.

Associated constants:

• MASTER_BRICK_WIFI_ENCRYPTION_WPA_WPA2
• MASTER_BRICK_WIFI_ENCRYPTION_WPA_ENTERPRISE
• MASTER_BRICK_WIFI_ENCRYPTION_WEP
• MASTER_BRICK_WIFI_ENCRYPTION_NO_ENCRYPTION
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_FAST
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TLS
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TTLS
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_PEAP
• MASTER_BRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_MSCHAP
• MASTER_BRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_GTC
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_CA_CERT
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_CLIENT_CERT
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_PRIVATE_KEY

pub fn get_wifi_encryption(&self) -> ConvertingReceiver<WifiEncryption>

Returns the encryption as set by [set_wifi_encryption].

Note

Since Master Brick Firmware version 2.4.4 the key is not returned anymore.

Associated constants:

• MASTER_BRICK_WIFI_ENCRYPTION_WPA_WPA2
• MASTER_BRICK_WIFI_ENCRYPTION_WPA_ENTERPRISE
• MASTER_BRICK_WIFI_ENCRYPTION_WEP
• MASTER_BRICK_WIFI_ENCRYPTION_NO_ENCRYPTION
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_FAST
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TLS
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TTLS
• MASTER_BRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_PEAP
• MASTER_BRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_MSCHAP
• MASTER_BRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_GTC
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_CA_CERT
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_CLIENT_CERT
• MASTER_BRICK_WIFI_EAP_OPTION_CERT_TYPE_PRIVATE_KEY

pub fn get_wifi_status(&self) -> ConvertingReceiver<WifiStatus>

Returns the status of the WIFI Extension. The state is updated automatically, all of the other parameters are updated on startup and every time [refresh_wifi_status] is called.

Possible states are:

State	Description
0	Disassociated
1	Associated
2	Associating
3	Error
255	Not initialized yet

Associated constants:

• MASTER_BRICK_WIFI_STATE_DISASSOCIATED
• MASTER_BRICK_WIFI_STATE_ASSOCIATED
• MASTER_BRICK_WIFI_STATE_ASSOCIATING
• MASTER_BRICK_WIFI_STATE_ERROR
• MASTER_BRICK_WIFI_STATE_NOT_INITIALIZED_YET

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

Refreshes the Wi-Fi status (see [get_wifi_status]). To read the status of the Wi-Fi module, the Master Brick has to change from data mode to command mode and back. This transaction and the readout itself is unfortunately time consuming. This means, that it might take some ms until the stack with attached WIFI Extension reacts again after this function is called.

pub fn set_wifi_certificate( &self, index: u16, data: [u8; 32], data_length: u8, ) -> ConvertingReceiver<()>

This function is used to set the certificate as well as password and username for WPA Enterprise. To set the username use index 0xFFFF, to set the password use index 0xFFFE. The max length of username and password is 32.

The certificate is written in chunks of size 32 and the index is used as the index of the chunk. data_length should nearly always be 32. Only the last chunk can have a length that is not equal to 32.

The starting index of the CA Certificate is 0, of the Client Certificate 10000 and for the Private Key 20000. Maximum sizes are 1312, 1312 and 4320 byte respectively.

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after uploading the certificate.

It is recommended to use the Brick Viewer to set the certificate, username and password.

pub fn get_wifi_certificate( &self, index: u16, ) -> ConvertingReceiver<WifiCertificate>

Returns the certificate for a given index as set by [set_wifi_certificate].

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

Sets the power mode of the WIFI Extension. Possible modes are:

Mode	Description
0	Full Speed (high power consumption
1	Low Power (low power consumption

Associated constants:

• MASTER_BRICK_WIFI_POWER_MODE_FULL_SPEED
• MASTER_BRICK_WIFI_POWER_MODE_LOW_POWER

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

Returns the power mode as set by [set_wifi_power_mode].

Associated constants:

• MASTER_BRICK_WIFI_POWER_MODE_FULL_SPEED
• MASTER_BRICK_WIFI_POWER_MODE_LOW_POWER

pub fn get_wifi_buffer_info(&self) -> ConvertingReceiver<WifiBufferInfo>

Returns informations about the Wi-Fi receive buffer. The Wi-Fi receive buffer has a max size of 1500 byte and if data is transfered too fast, it might overflow.

The return values are the number of overflows, the low watermark (i.e. the smallest number of bytes that were free in the buffer) and the bytes that are currently used.

You should always try to keep the buffer empty, otherwise you will have a permanent latency. A good rule of thumb is, that you can transfer 1000 messages per second without problems.

Try to not send more then 50 messages at a time without any kind of break between them.

pub fn set_wifi_regulatory_domain(&self, domain: u8) -> ConvertingReceiver<()>

Sets the regulatory domain of the WIFI Extension. Possible domains are:

Domain	Description
0	FCC: Channel 1-11 (N/S America
1	ETSI: Channel 1-13 (Europe
2	TELEC: Channel 1-14 (Japan)

Associated constants:

• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO11
• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO13
• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO14

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

Returns the regulatory domain as set by [set_wifi_regulatory_domain].

Associated constants:

• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO11
• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO13
• MASTER_BRICK_WIFI_DOMAIN_CHANNEL_1TO14

pub fn get_usb_voltage(&self) -> ConvertingReceiver<u16>

Returns the USB voltage. Does not work with hardware version 2.1 or newer.

pub fn set_long_wifi_key(&self, key: String) -> ConvertingReceiver<()>

Sets a long Wi-Fi key (up to 63 chars, at least 8 chars) for WPA encryption. This key will be used if the key in [set_wifi_encryption] is set to -. In the old protocol, a payload of size 63 was not possible, so the maximum key length was 50 chars.

With the new protocol this is possible, since we didn’t want to break API, this function was added additionally.

.. versionadded:: 2.0.2$nbsp;(Firmware)

pub fn get_long_wifi_key(&self) -> ConvertingReceiver<String>

Returns the encryption key as set by [set_long_wifi_key].

Note

Since Master Brick firmware version 2.4.4 the key is not returned anymore.

.. versionadded:: 2.0.2$nbsp;(Firmware)

pub fn set_wifi_hostname(&self, hostname: String) -> ConvertingReceiver<()>

Sets the hostname of the WIFI Extension. The hostname will be displayed by access points as the hostname in the DHCP clients table.

Setting an empty String will restore the default hostname.

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn get_wifi_hostname(&self) -> ConvertingReceiver<String>

Returns the hostname as set by [set_wifi_hostname].

An empty String means, that the default hostname is used.

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn set_stack_current_callback_period( &self, period: u32, ) -> ConvertingReceiver<()>

Sets the period with which the [get_stack_current_callback_receiver] receiver is triggered periodically. A value of 0 turns the receiver off.

The [get_stack_current_callback_receiver] receiver is only triggered if the current has changed since the last triggering.

.. versionadded:: 2.0.5$nbsp;(Firmware)

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

Returns the period as set by [set_stack_current_callback_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn set_stack_voltage_callback_period( &self, period: u32, ) -> ConvertingReceiver<()>

Sets the period with which the [get_stack_voltage_callback_receiver] receiver is triggered periodically. A value of 0 turns the receiver off.

The [get_stack_voltage_callback_receiver] receiver is only triggered if the voltage has changed since the last triggering.

.. versionadded:: 2.0.5$nbsp;(Firmware)

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

Returns the period as set by [set_stack_voltage_callback_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn set_usb_voltage_callback_period( &self, period: u32, ) -> ConvertingReceiver<()>

Sets the period with which the [get_usb_voltage_callback_receiver] receiver is triggered periodically. A value of 0 turns the receiver off.

The [get_usb_voltage_callback_receiver] receiver is only triggered if the voltage has changed since the last triggering.

.. versionadded:: 2.0.5$nbsp;(Firmware)

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

Returns the period as set by [set_usb_voltage_callback_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

pub fn set_stack_current_callback_threshold( &self, option: char, min: u16, max: u16, ) -> ConvertingReceiver<()>

Sets the thresholds for the [get_stack_current_reached_callback_receiver] receiver.

The following options are possible:

Option	Description
‘x’	Receiver is turned off
‘o’	Receiver is triggered when the current is outside the min and max values
‘i’	Receiver is triggered when the current is inside the min and max values
‘<’	Receiver is triggered when the current is smaller than the min value (max is ignored)
‘>’	Receiver is triggered when the current is greater than the min value (max is ignored)

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn get_stack_current_callback_threshold( &self, ) -> ConvertingReceiver<StackCurrentCallbackThreshold>

Returns the threshold as set by [set_stack_current_callback_threshold].

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn set_stack_voltage_callback_threshold( &self, option: char, min: u16, max: u16, ) -> ConvertingReceiver<()>

Sets the thresholds for the [get_stack_voltage_reached_callback_receiver] receiver.

The following options are possible:

Option	Description
‘x’	Receiver is turned off
‘o’	Receiver is triggered when the voltage is outside the min and max values
‘i’	Receiver is triggered when the voltage is inside the min and max values
‘<’	Receiver is triggered when the voltage is smaller than the min value (max is ignored)
‘>’	Receiver is triggered when the voltage is greater than the min value (max is ignored)

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn get_stack_voltage_callback_threshold( &self, ) -> ConvertingReceiver<StackVoltageCallbackThreshold>

Returns the threshold as set by [set_stack_voltage_callback_threshold].

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn set_usb_voltage_callback_threshold( &self, option: char, min: u16, max: u16, ) -> ConvertingReceiver<()>

Sets the thresholds for the [get_usb_voltage_reached_callback_receiver] receiver.

The following options are possible:

Option	Description
‘x’	Receiver is turned off
‘o’	Receiver is triggered when the voltage is outside the min and max values
‘i’	Receiver is triggered when the voltage is inside the min and max values
‘<’	Receiver is triggered when the voltage is smaller than the min value (max is ignored)
‘>’	Receiver is triggered when the voltage is greater than the min value (max is ignored)

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn get_usb_voltage_callback_threshold( &self, ) -> ConvertingReceiver<UsbVoltageCallbackThreshold>

Returns the threshold as set by [set_usb_voltage_callback_threshold].

.. versionadded:: 2.0.5$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_THRESHOLD_OPTION_OFF
• MASTER_BRICK_THRESHOLD_OPTION_OUTSIDE
• MASTER_BRICK_THRESHOLD_OPTION_INSIDE
• MASTER_BRICK_THRESHOLD_OPTION_SMALLER
• MASTER_BRICK_THRESHOLD_OPTION_GREATER

pub fn set_debounce_period(&self, debounce: u32) -> ConvertingReceiver<()>

Sets the period with which the threshold receivers

• [get_stack_current_reached_callback_receiver],
• [get_stack_voltage_reached_callback_receiver],
• [get_usb_voltage_reached_callback_receiver]

are triggered, if the thresholds

• [set_stack_current_callback_threshold],
• [set_stack_voltage_callback_threshold],
• [set_usb_voltage_callback_threshold]

keep being reached.

.. versionadded:: 2.0.5$nbsp;(Firmware)

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

Returns the debounce period as set by [set_debounce_period].

.. versionadded:: 2.0.5$nbsp;(Firmware)

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

Returns true if the Master Brick is at position 0 in the stack and an Ethernet Extension is available.

.. versionadded:: 2.1.0$nbsp;(Firmware)

pub fn set_ethernet_configuration( &self, connection: u8, ip: [u8; 4], subnet_mask: [u8; 4], gateway: [u8; 4], port: u16, ) -> ConvertingReceiver<()>

Sets the configuration of the Ethernet Extension. Possible values for connection are:

Value	Description
0	DHCP
1	Static IP

If you set connection to static IP options then you have to supply ip, subnet_mask and gateway as an array of size 4 (first element of the array is the least significant byte of the address). If connection is set to the DHCP options then ip, subnet_mask and gateway are ignored, you can set them to 0.

The last parameter is the port that your program will connect to.

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the Ethernet configuration.

.. versionadded:: 2.1.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_ETHERNET_CONNECTION_DHCP
• MASTER_BRICK_ETHERNET_CONNECTION_STATIC_IP

pub fn get_ethernet_configuration( &self, ) -> ConvertingReceiver<EthernetConfiguration>

Returns the configuration as set by [set_ethernet_configuration].

.. versionadded:: 2.1.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_ETHERNET_CONNECTION_DHCP
• MASTER_BRICK_ETHERNET_CONNECTION_STATIC_IP

pub fn get_ethernet_status(&self) -> ConvertingReceiver<EthernetStatus>

Returns the status of the Ethernet Extension.

mac_address, ip, subnet_mask and gateway are given as an array. The first element of the array is the least significant byte of the address.

rx_count and tx_count are the number of bytes that have been received/send since last restart.

hostname is the currently used hostname.

.. versionadded:: 2.1.0$nbsp;(Firmware)

pub fn set_ethernet_hostname(&self, hostname: String) -> ConvertingReceiver<()>

Sets the hostname of the Ethernet Extension. The hostname will be displayed by access points as the hostname in the DHCP clients table.

Setting an empty String will restore the default hostname.

The current hostname can be discovered with [get_ethernet_status].

.. versionadded:: 2.1.0$nbsp;(Firmware)

pub fn set_ethernet_mac_address( &self, mac_address: [u8; 6], ) -> ConvertingReceiver<()>

Sets the MAC address of the Ethernet Extension. The Ethernet Extension should come configured with a valid MAC address, that is also written on a sticker of the extension itself.

The MAC address can be read out again with [get_ethernet_status].

.. versionadded:: 2.1.0$nbsp;(Firmware)

pub fn set_ethernet_websocket_configuration( &self, sockets: u8, port: u16, ) -> ConvertingReceiver<()>

Sets the Ethernet WebSocket configuration. The first parameter sets the number of socket connections that are reserved for WebSockets. The range is 0-7. The connections are shared with the plain sockets. Example: If you set the connections to 3, there will be 3 WebSocket and 4 plain socket connections available.

The second parameter is the port for the WebSocket connections. The port can not be the same as the port for the plain socket connections.

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the Ethernet configuration.

.. versionadded:: 2.2.0$nbsp;(Firmware)

pub fn get_ethernet_websocket_configuration( &self, ) -> ConvertingReceiver<EthernetWebsocketConfiguration>

Returns the configuration as set by [set_ethernet_configuration].

.. versionadded:: 2.2.0$nbsp;(Firmware)

pub fn set_ethernet_authentication_secret( &self, secret: String, ) -> ConvertingReceiver<()>

Sets the Ethernet authentication secret. The secret can be a string of up to 64 characters. An empty string disables the authentication.

See the authentication tutorial for more information.

The secret is stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the Ethernet authentication secret.

The default value is an empty string (authentication disabled).

.. versionadded:: 2.2.0$nbsp;(Firmware)

pub fn get_ethernet_authentication_secret(&self) -> ConvertingReceiver<String>

Returns the authentication secret as set by [set_ethernet_authentication_secret].

.. versionadded:: 2.2.0$nbsp;(Firmware)

pub fn set_wifi_authentication_secret( &self, secret: String, ) -> ConvertingReceiver<()>

Sets the WIFI authentication secret. The secret can be a string of up to 64 characters. An empty string disables the authentication.

See the authentication tutorial for more information.

The secret is stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

It is recommended to use the Brick Viewer to set the WIFI authentication secret.

The default value is an empty string (authentication disabled).

.. versionadded:: 2.2.0$nbsp;(Firmware)

pub fn get_wifi_authentication_secret(&self) -> ConvertingReceiver<String>

Returns the authentication secret as set by [set_wifi_authentication_secret].

.. versionadded:: 2.2.0$nbsp;(Firmware)

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

Returns the type of the connection over which this function was called.

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_CONNECTION_TYPE_NONE
• MASTER_BRICK_CONNECTION_TYPE_USB
• MASTER_BRICK_CONNECTION_TYPE_SPI_STACK
• MASTER_BRICK_CONNECTION_TYPE_CHIBI
• MASTER_BRICK_CONNECTION_TYPE_RS485
• MASTER_BRICK_CONNECTION_TYPE_WIFI
• MASTER_BRICK_CONNECTION_TYPE_ETHERNET
• MASTER_BRICK_CONNECTION_TYPE_WIFI2

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

Returns true if the Master Brick is at position 0 in the stack and a WIFI Extension 2.0 is available.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn start_wifi2_bootloader(&self) -> ConvertingReceiver<i8>

Starts the bootloader of the WIFI Extension 2.0. Returns 0 on success. Afterwards the [write_wifi2_serial_port] and [read_wifi2_serial_port] functions can be used to communicate with the bootloader to flash a new firmware.

The bootloader should only be started over a USB connection. It cannot be started over a WIFI2 connection, see the [get_connection_type] function.

It is recommended to use the Brick Viewer to update the firmware of the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn write_wifi2_serial_port( &self, data: [u8; 60], length: u8, ) -> ConvertingReceiver<i8>

Writes up to 60 bytes (number of bytes to be written specified by length) to the serial port of the bootloader of the WIFI Extension 2.0. Returns 0 on success.

Before this function can be used the bootloader has to be started using the [start_wifi2_bootloader] function.

It is recommended to use the Brick Viewer to update the firmware of the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn read_wifi2_serial_port( &self, length: u8, ) -> ConvertingReceiver<ReadWifi2SerialPort>

Reads up to 60 bytes (number of bytes to be read specified by length) from the serial port of the bootloader of the WIFI Extension 2.0. Returns the number of actually read bytes.

Before this function can be used the bootloader has to be started using the [start_wifi2_bootloader] function.

It is recommended to use the Brick Viewer to update the firmware of the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_authentication_secret( &self, secret: String, ) -> ConvertingReceiver<()>

Sets the WIFI authentication secret. The secret can be a string of up to 64 characters. An empty string disables the authentication. The default value is an empty string (authentication disabled).

See the authentication tutorial for more information.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_authentication_secret(&self) -> ConvertingReceiver<String>

Returns the WIFI authentication secret as set by [set_wifi2_authentication_secret].

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_configuration( &self, port: u16, websocket_port: u16, website_port: u16, phy_mode: u8, sleep_mode: u8, website: u8, ) -> ConvertingReceiver<()>

Sets the general configuration of the WIFI Extension 2.0.

The port parameter sets the port number that your programm will connect to.

The websocket_port parameter sets the WebSocket port number that your JavaScript programm will connect to.

The website_port parameter sets the port number for the website of the WIFI Extension 2.0.

The phy_mode parameter sets the specific wireless network mode to be used. Possible values are B, G and N.

The sleep_mode parameter is currently unused.

The website parameter is used to enable or disable the web interface of the WIFI Extension 2.0, which is available from firmware version 2.0.1. Note that, for firmware version 2.0.3 and older, to disable the the web interface the website_port parameter must be set to 1 and greater than 1 to enable the web interface. For firmware version 2.0.4 and later, setting this parameter to 1 will enable the web interface and setting it to 0 will disable the web interface.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_PHY_MODE_B
• MASTER_BRICK_WIFI2_PHY_MODE_G
• MASTER_BRICK_WIFI2_PHY_MODE_N

pub fn get_wifi2_configuration(&self) -> ConvertingReceiver<Wifi2Configuration>

Returns the general configuration as set by [set_wifi2_configuration].

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_PHY_MODE_B
• MASTER_BRICK_WIFI2_PHY_MODE_G
• MASTER_BRICK_WIFI2_PHY_MODE_N

pub fn get_wifi2_status(&self) -> ConvertingReceiver<Wifi2Status>

Returns the client and access point status of the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_CLIENT_STATUS_IDLE
• MASTER_BRICK_WIFI2_CLIENT_STATUS_CONNECTING
• MASTER_BRICK_WIFI2_CLIENT_STATUS_WRONG_PASSWORD
• MASTER_BRICK_WIFI2_CLIENT_STATUS_NO_AP_FOUND
• MASTER_BRICK_WIFI2_CLIENT_STATUS_CONNECT_FAILED
• MASTER_BRICK_WIFI2_CLIENT_STATUS_GOT_IP
• MASTER_BRICK_WIFI2_CLIENT_STATUS_UNKNOWN

pub fn set_wifi2_client_configuration( &self, enable: bool, ssid: String, ip: [u8; 4], subnet_mask: [u8; 4], gateway: [u8; 4], mac_address: [u8; 6], bssid: [u8; 6], ) -> ConvertingReceiver<()>

Sets the client specific configuration of the WIFI Extension 2.0.

The enable parameter enables or disables the client part of the WIFI Extension 2.0.

The ssid parameter sets the SSID (up to 32 characters) of the access point to connect to.

If the ip parameter is set to all zero then subnet_mask and gateway parameters are also set to all zero and DHCP is used for IP address configuration. Otherwise those three parameters can be used to configure a static IP address. The default configuration is DHCP.

If the mac_address parameter is set to all zero then the factory MAC address is used. Otherwise this parameter can be used to set a custom MAC address.

If the bssid parameter is set to all zero then WIFI Extension 2.0 will connect to any access point that matches the configured SSID. Otherwise this parameter can be used to make the WIFI Extension 2.0 only connect to an access point if SSID and BSSID match.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_client_configuration( &self, ) -> ConvertingReceiver<Wifi2ClientConfiguration>

Returns the client configuration as set by [set_wifi2_client_configuration].

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_client_hostname( &self, hostname: String, ) -> ConvertingReceiver<()>

Sets the client hostname (up to 32 characters) of the WIFI Extension 2.0. The hostname will be displayed by access points as the hostname in the DHCP clients table.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_client_hostname(&self) -> ConvertingReceiver<String>

Returns the client hostname as set by [set_wifi2_client_hostname].

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_client_password( &self, password: String, ) -> ConvertingReceiver<()>

Sets the client password (up to 63 chars) for WPA/WPA2 encryption.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_client_password(&self) -> ConvertingReceiver<String>

Returns the client password as set by [set_wifi2_client_password].

Note

Since WIFI Extension 2.0 firmware version 2.1.3 the password is not returned anymore.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_ap_configuration( &self, enable: bool, ssid: String, ip: [u8; 4], subnet_mask: [u8; 4], gateway: [u8; 4], encryption: u8, hidden: bool, channel: u8, mac_address: [u8; 6], ) -> ConvertingReceiver<()>

Sets the access point specific configuration of the WIFI Extension 2.0.

The enable parameter enables or disables the access point part of the WIFI Extension 2.0.

The ssid parameter sets the SSID (up to 32 characters) of the access point.

If the ip parameter is set to all zero then subnet_mask and gateway parameters are also set to all zero and DHCP is used for IP address configuration. Otherwise those three parameters can be used to configure a static IP address. The default configuration is DHCP.

The encryption parameter sets the encryption mode to be used. Possible values are Open (no encryption), WEP or WPA/WPA2 PSK. Use the [set_wifi2_ap_password] function to set the encryption password.

The hidden parameter makes the access point hide or show its SSID.

The channel parameter sets the channel (1 to 13) of the access point.

If the mac_address parameter is set to all zero then the factory MAC address is used. Otherwise this parameter can be used to set a custom MAC address.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_AP_ENCRYPTION_OPEN
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WEP
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA_PSK
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA2_PSK
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA_WPA2_PSK

pub fn get_wifi2_ap_configuration( &self, ) -> ConvertingReceiver<Wifi2ApConfiguration>

Returns the access point configuration as set by [set_wifi2_ap_configuration].

.. versionadded:: 2.4.0$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_AP_ENCRYPTION_OPEN
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WEP
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA_PSK
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA2_PSK
• MASTER_BRICK_WIFI2_AP_ENCRYPTION_WPA_WPA2_PSK

pub fn set_wifi2_ap_password(&self, password: String) -> ConvertingReceiver<()>

Sets the access point password (at least 8 and up to 63 chars) for the configured encryption mode, see [set_wifi2_ap_configuration].

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_ap_password(&self) -> ConvertingReceiver<String>

Returns the access point password as set by [set_wifi2_ap_password].

Note

Since WIFI Extension 2.0 firmware version 2.1.3 the password is not returned anymore.

.. versionadded:: 2.4.0$nbsp;(Firmware)

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

All configuration functions for the WIFI Extension 2.0 do not change the values permanently. After configuration this function has to be called to permanently store the values.

The values are stored in the EEPROM and only applied on startup. That means you have to restart the Master Brick after configuration.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn get_wifi2_firmware_version(&self) -> ConvertingReceiver<[u8; 3]>

Returns the current version of the WIFI Extension 2.0 firmware.

.. versionadded:: 2.4.0$nbsp;(Firmware)

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

Turns the green status LED of the WIFI Extension 2.0 on.

.. versionadded:: 2.4.0$nbsp;(Firmware)

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

Turns the green status LED of the WIFI Extension 2.0 off.

.. versionadded:: 2.4.0$nbsp;(Firmware)

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

Returns true if the green status LED of the WIFI Extension 2.0 is turned on.

.. versionadded:: 2.4.0$nbsp;(Firmware)

pub fn set_wifi2_mesh_configuration( &self, enable: bool, root_ip: [u8; 4], root_subnet_mask: [u8; 4], root_gateway: [u8; 4], router_bssid: [u8; 6], group_id: [u8; 6], group_ssid_prefix: String, gateway_ip: [u8; 4], gateway_port: u16, ) -> ConvertingReceiver<()>

Requires WIFI Extension 2.0 firmware 2.1.0.

Sets the mesh specific configuration of the WIFI Extension 2.0.

The enable parameter enables or disables the mesh part of the WIFI Extension 2.0. The mesh part cannot be enabled together with the client and access-point part.

If the root_ip parameter is set to all zero then root_subnet_mask and root_gateway parameters are also set to all zero and DHCP is used for IP address configuration. Otherwise those three parameters can be used to configure a static IP address. The default configuration is DHCP.

If the router_bssid parameter is set to all zero then the information is taken from Wi-Fi scan when connecting the SSID as set by [set_wifi2_mesh_router_ssid]. This only works if the the SSID is not hidden. In case the router has hidden SSID this parameter must be specified, otherwise the node will not be able to reach the mesh router.

The group_id and the group_ssid_prefix parameters identifies a particular mesh network and nodes configured with same group_id and the group_ssid_prefix are considered to be in the same mesh network.

The gateway_ip and the gateway_port parameters specifies the location of the brickd that supports mesh feature.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn get_wifi2_mesh_configuration( &self, ) -> ConvertingReceiver<Wifi2MeshConfiguration>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh configuration as set by [set_wifi2_mesh_configuration].

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn set_wifi2_mesh_router_ssid(&self, ssid: String) -> ConvertingReceiver<()>

Requires WIFI Extension 2.0 firmware 2.1.0.

Sets the mesh router SSID of the WIFI Extension 2.0. It is used to specify the mesh router to connect to.

Note that even though in the argument of this function a 32 characters long SSID is allowed, in practice valid SSID should have a maximum of 31 characters. This is due to a bug in the mesh library that we use in the firmware of the extension.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn get_wifi2_mesh_router_ssid(&self) -> ConvertingReceiver<String>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh router SSID as set by [set_wifi2_mesh_router_ssid].

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn set_wifi2_mesh_router_password( &self, password: String, ) -> ConvertingReceiver<()>

Requires WIFI Extension 2.0 firmware 2.1.0.

Sets the mesh router password (up to 64 characters) for WPA/WPA2 encryption. The password will be used to connect to the mesh router.

To apply configuration changes to the WIFI Extension 2.0 the [save_wifi2_configuration] function has to be called and the Master Brick has to be restarted afterwards.

It is recommended to use the Brick Viewer to configure the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn get_wifi2_mesh_router_password(&self) -> ConvertingReceiver<String>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh router password as set by [set_wifi2_mesh_router_password].

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn get_wifi2_mesh_common_status( &self, ) -> ConvertingReceiver<Wifi2MeshCommonStatus>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the common mesh status of the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_WIFI2_MESH_STATUS_DISABLED
• MASTER_BRICK_WIFI2_MESH_STATUS_WIFI_CONNECTING
• MASTER_BRICK_WIFI2_MESH_STATUS_GOT_IP
• MASTER_BRICK_WIFI2_MESH_STATUS_MESH_LOCAL
• MASTER_BRICK_WIFI2_MESH_STATUS_MESH_ONLINE
• MASTER_BRICK_WIFI2_MESH_STATUS_AP_AVAILABLE
• MASTER_BRICK_WIFI2_MESH_STATUS_AP_SETUP
• MASTER_BRICK_WIFI2_MESH_STATUS_LEAF_AVAILABLE

pub fn get_wifi2_mesh_client_status( &self, ) -> ConvertingReceiver<Wifi2MeshClientStatus>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh client status of the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn get_wifi2_mesh_ap_status(&self) -> ConvertingReceiver<Wifi2MeshApStatus>

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh AP status of the WIFI Extension 2.0.

.. versionadded:: 2.4.2$nbsp;(Firmware)

pub fn set_bricklet_xmc_flash_config( &self, config: u32, parameter1: u32, parameter2: u32, data: [u8; 52], ) -> ConvertingReceiver<SetBrickletXmcFlashConfig>

This function is for internal use to flash the initial bootstrapper and bootloader to the Bricklets.

If you need to flash a boostrapper/bootloader (for exmaple because you made your own Bricklet from scratch) please take a look at our open source flash and test tool at https://github.com/Tinkerforge/flash-test__

Don’t use this function directly.

.. versionadded:: 2.5.0$nbsp;(Firmware)

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

This function is for internal use to flash the initial bootstrapper and bootloader to the Bricklets.

If you need to flash a boostrapper/bootloader (for exmaple because you made your own Bricklet from scratch) please take a look at our open source flash and test tool at https://github.com/Tinkerforge/flash-test__

Don’t use this function directly.

.. versionadded:: 2.5.0$nbsp;(Firmware)

pub fn set_bricklets_enabled( &self, bricklets_enabled: bool, ) -> ConvertingReceiver<()>

This function is only available in Master Brick hardware version >= 3.0.

Enables/disables all four Bricklets if set to true/false.

If you disable the Bricklets the power supply to the Bricklets will be disconnected. The Bricklets will lose all configurations if disabled.

.. versionadded:: 2.5.0$nbsp;(Firmware)

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

Returns true if the Bricklets are enabled, false otherwise.

.. versionadded:: 2.5.0$nbsp;(Firmware)

pub fn set_spitfp_baudrate_config( &self, enable_dynamic_baudrate: bool, minimum_dynamic_baudrate: u32, ) -> ConvertingReceiver<()>

The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Brick will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.

The baudrate will be increased exponentially if lots of data is sent/received and decreased linearly if little data is sent/received.

This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.

In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.

The maximum value of the baudrate can be set per port with the function [set_spitfp_baudrate]. If the dynamic baudrate is disabled, the baudrate as set by [set_spitfp_baudrate] will be used statically.

.. versionadded:: 2.4.6$nbsp;(Firmware)

pub fn get_spitfp_baudrate_config( &self, ) -> ConvertingReceiver<SpitfpBaudrateConfig>

Returns the baudrate config, see [set_spitfp_baudrate_config].

.. versionadded:: 2.4.6$nbsp;(Firmware)

pub fn get_send_timeout_count( &self, communication_method: u8, ) -> ConvertingReceiver<u32>

Returns the timeout count for the different communication methods.

The methods 0-2 are available for all Bricks, 3-7 only for Master Bricks.

This function is mostly used for debugging during development, in normal operation the counters should nearly always stay at 0.

.. versionadded:: 2.4.3$nbsp;(Firmware)

Associated constants:

• MASTER_BRICK_COMMUNICATION_METHOD_NONE
• MASTER_BRICK_COMMUNICATION_METHOD_USB
• MASTER_BRICK_COMMUNICATION_METHOD_SPI_STACK
• MASTER_BRICK_COMMUNICATION_METHOD_CHIBI
• MASTER_BRICK_COMMUNICATION_METHOD_RS485
• MASTER_BRICK_COMMUNICATION_METHOD_WIFI
• MASTER_BRICK_COMMUNICATION_METHOD_ETHERNET
• MASTER_BRICK_COMMUNICATION_METHOD_WIFI_V2

pub fn set_spitfp_baudrate( &self, bricklet_port: char, baudrate: u32, ) -> ConvertingReceiver<()>

Sets the baudrate for a specific Bricklet port.

If you want to increase the throughput of Bricklets you can increase the baudrate. If you get a high error count because of high interference (see [get_spitfp_error_count]) you can decrease the baudrate.

If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see [set_spitfp_baudrate_config]).

Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.

.. versionadded:: 2.4.3$nbsp;(Firmware)

pub fn get_spitfp_baudrate( &self, bricklet_port: char, ) -> ConvertingReceiver<u32>

Returns the baudrate for a given Bricklet port, see [set_spitfp_baudrate].

.. versionadded:: 2.4.3$nbsp;(Firmware)

pub fn get_spitfp_error_count( &self, bricklet_port: char, ) -> 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 Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.

.. versionadded:: 2.4.3$nbsp;(Firmware)

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

Enables the status LED.

The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.

The default state is enabled.

.. versionadded:: 2.3.2$nbsp;(Firmware)

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

Disables the status LED.

The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.

The default state is enabled.

.. versionadded:: 2.3.2$nbsp;(Firmware)

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

Returns true if the status LED is enabled, false otherwise.

.. versionadded:: 2.3.2$nbsp;(Firmware)

pub fn get_protocol1_bricklet_name( &self, port: char, ) -> ConvertingReceiver<Protocol1BrickletName>

Returns the firmware and protocol version and the name of the Bricklet for a given port.

This functions sole purpose is to allow automatic flashing of v1.x.y Bricklet plugins.

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

Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has an accuracy of ±15%. Practically it is only useful as an indicator for temperature changes.

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

Calling this function will reset the Brick. Calling this function on a Brick inside of a stack will reset the whole stack.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

pub fn write_bricklet_plugin( &self, port: char, offset: u8, chunk: [u8; 32], ) -> ConvertingReceiver<()>

Writes 32 bytes of firmware to the bricklet attached at the given port. The bytes are written to the position offset * 32.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

pub fn read_bricklet_plugin( &self, port: char, offset: u8, ) -> ConvertingReceiver<[u8; 32]>

Reads 32 bytes of firmware from the bricklet attached at the given port. The bytes are read starting at the position offset * 32.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

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

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

The position is the position in the stack from ‘0’ (bottom) to ‘8’ (top).

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

Trait Implementations

impl Clone for MasterBrick

fn clone(&self) -> MasterBrick

Returns a duplicate of the value.

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

Performs copy-assignment from source.