pub struct MasterBrick { /* private fields */ }
Expand description

Basis to build stacks and has 4 Bricklet ports

Implementations

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

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.

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.

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

This receiver is triggered periodically with the period that is set by Set Stack Current Receiver 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)

This receiver is triggered periodically with the period that is set by Set Stack Voltage Receiver 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)

This receiver is triggered periodically with the period that is set by Set USB Voltage Receiver Period. The parameter is the USB voltage in mV.

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.

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

This receiver is triggered when the threshold as set by Set Stack Current Receiver Threshold is reached. The parameter is the stack current in mA.

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)

This receiver is triggered when the threshold as set by Set Stack Voltage Receiver Threshold is reached. The parameter is the stack voltage in mV.

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)

This receiver is triggered when the threshold as set by Set USB Voltage Receiver 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)

Returns the stack voltage in mV. 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.

Returns the stack current in mA. 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.

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

Possible extension types:

TypeDescription
1Chibi
2RS485
3WIFI
4Ethernet
5WIFI 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:

  • MASTERBRICK_EXTENSION_TYPE_CHIBI
  • MASTERBRICK_EXTENSION_TYPE_RS485
  • MASTERBRICK_EXTENSION_TYPE_WIFI
  • MASTERBRICK_EXTENSION_TYPE_ETHERNET
  • MASTERBRICK_EXTENSION_TYPE_WIFI2

Returns the type for a given extension as set by Set Extension Type.

Associated constants:

  • MASTERBRICK_EXTENSION_TYPE_CHIBI
  • MASTERBRICK_EXTENSION_TYPE_RS485
  • MASTERBRICK_EXTENSION_TYPE_WIFI
  • MASTERBRICK_EXTENSION_TYPE_ETHERNET
  • MASTERBRICK_EXTENSION_TYPE_WIFI2

Returns true if a Chibi Extension is available to be used by the Master Brick.

Sets the address (1-255) 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.

Returns the address as set by Set Chibi Address.

Sets the address (1-255) 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.

Returns the address as set by Set Chibi Master Address.

Sets up to 254 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 \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.

Returns the slave address for a given \c num as set by Set Chibi Slave Address.

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

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.

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

TypeDescription
0OQPSK 868MHz (Europe)
1OQPSK 915MHz (US)
2OQPSK 780MHz (China)
3BPSK40 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:

  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_868_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_915_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_780_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_BPSK40_915_MHZ

Returns the frequency value as set by Set Chibi Frequency.

Associated constants:

  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_868_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_915_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_OQPSK_780_MHZ
  • MASTERBRICK_CHIBI_FREQUENCY_BPSK40_915_MHZ

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

FrequencyPossible Channels
OQPSK 868MHz (Europe)0
OQPSK 915MHz (US)1
OQPSK 780MHz (China)0
BPSK40 915MHz1

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.

Returns the channel as set by Set Chibi Channel.

Returns true if a RS485 Extension is available to be used by the Master Brick.

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.

Returns the address as set by Set RS485 Address.

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.

Returns the slave address for a given num as set by Set RS485 Slave Address.

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.

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

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 (100kbit/s).

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:

  • MASTERBRICK_RS485_PARITY_NONE
  • MASTERBRICK_RS485_PARITY_EVEN
  • MASTERBRICK_RS485_PARITY_ODD

Returns the configuration as set by Set RS485 Configuration.

Associated constants:

  • MASTERBRICK_RS485_PARITY_NONE
  • MASTERBRICK_RS485_PARITY_EVEN
  • MASTERBRICK_RS485_PARITY_ODD

Returns true if a WIFI Extension is available to be used by the Master Brick.

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

ValueDescription
0DHCP
1Static IP
2Access Point: DHCP
3Access Point: Static IP
4Ad Hoc: DHCP
5Ad 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 default port, that is used by brickd, is 4223.

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:

  • MASTERBRICK_WIFI_CONNECTION_DHCP
  • MASTERBRICK_WIFI_CONNECTION_STATIC_IP
  • MASTERBRICK_WIFI_CONNECTION_ACCESS_POINT_DHCP
  • MASTERBRICK_WIFI_CONNECTION_ACCESS_POINT_STATIC_IP
  • MASTERBRICK_WIFI_CONNECTION_AD_HOC_DHCP
  • MASTERBRICK_WIFI_CONNECTION_AD_HOC_STATIC_IP

Returns the configuration as set by Set Wifi Configuration.

Associated constants:

  • MASTERBRICK_WIFI_CONNECTION_DHCP
  • MASTERBRICK_WIFI_CONNECTION_STATIC_IP
  • MASTERBRICK_WIFI_CONNECTION_ACCESS_POINT_DHCP
  • MASTERBRICK_WIFI_CONNECTION_ACCESS_POINT_STATIC_IP
  • MASTERBRICK_WIFI_CONNECTION_AD_HOC_DHCP
  • MASTERBRICK_WIFI_CONNECTION_AD_HOC_STATIC_IP

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

ValueDescription
0WPA/WPA2
1WPA Enterprise (EAP-FAST
2WEP
3No 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 certificate length are given in byte and 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):

OptionBitsDescription
outer authentication1-20=EAP-FAST
inner authentication30=EAP-MSCHAP
certificate type4-50=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:

  • MASTERBRICK_WIFI_ENCRYPTION_WPA_WPA2
  • MASTERBRICK_WIFI_ENCRYPTION_WPA_ENTERPRISE
  • MASTERBRICK_WIFI_ENCRYPTION_WEP
  • MASTERBRICK_WIFI_ENCRYPTION_NO_ENCRYPTION
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_FAST
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TLS
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TTLS
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_PEAP
  • MASTERBRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_MSCHAP
  • MASTERBRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_GTC
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_CA_CERT
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_CLIENT_CERT
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_PRIVATE_KEY

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:

  • MASTERBRICK_WIFI_ENCRYPTION_WPA_WPA2
  • MASTERBRICK_WIFI_ENCRYPTION_WPA_ENTERPRISE
  • MASTERBRICK_WIFI_ENCRYPTION_WEP
  • MASTERBRICK_WIFI_ENCRYPTION_NO_ENCRYPTION
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_FAST
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TLS
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_TTLS
  • MASTERBRICK_WIFI_EAP_OPTION_OUTER_AUTH_EAP_PEAP
  • MASTERBRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_MSCHAP
  • MASTERBRICK_WIFI_EAP_OPTION_INNER_AUTH_EAP_GTC
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_CA_CERT
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_CLIENT_CERT
  • MASTERBRICK_WIFI_EAP_OPTION_CERT_TYPE_PRIVATE_KEY

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:

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

Associated constants:

  • MASTERBRICK_WIFI_STATE_DISASSOCIATED
  • MASTERBRICK_WIFI_STATE_ASSOCIATED
  • MASTERBRICK_WIFI_STATE_ASSOCIATING
  • MASTERBRICK_WIFI_STATE_ERROR
  • MASTERBRICK_WIFI_STATE_NOT_INITIALIZED_YET

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.

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.

Returns the certificate for a given index as set by Set Wifi Certificate.

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

ModeDescription
0Full Speed (high power consumption
1Low Power (low power consumption

The default value is 0 (Full Speed).

Associated constants:

  • MASTERBRICK_WIFI_POWER_MODE_FULL_SPEED
  • MASTERBRICK_WIFI_POWER_MODE_LOW_POWER

Returns the power mode as set by Set Wifi Power Mode.

Associated constants:

  • MASTERBRICK_WIFI_POWER_MODE_FULL_SPEED
  • MASTERBRICK_WIFI_POWER_MODE_LOW_POWER

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.

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

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

The default value is 1 (ETSI).

Associated constants:

  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO11
  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO13
  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO14

Returns the regulatory domain as set by Set Wifi Regulatory Domain.

Associated constants:

  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO11
  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO13
  • MASTERBRICK_WIFI_DOMAIN_CHANNEL_1TO14

Returns the USB voltage in mV. Does not work with hardware version 2.1.

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)

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)

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)

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)

Sets the period in ms 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.

The default value is 0.

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

Returns the period as set by Set Stack Current Receiver Period.

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

Sets the period in ms 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.

The default value is 0.

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

Returns the period as set by Set Stack Voltage Receiver Period.

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

Sets the period in ms 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.

The default value is 0.

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

Returns the period as set by Set USB Voltage Receiver Period.

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

Sets the thresholds for the get_stack_current_reached_callback_receiver receiver.

The following options are possible:

OptionDescription
‘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)

The default value is (‘x’, 0, 0).

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Returns the threshold as set by Set Stack Current Receiver Threshold.

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Sets the thresholds for the get_stack_voltage_reached_callback_receiver receiver.

The following options are possible:

OptionDescription
‘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)

The default value is (‘x’, 0, 0).

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Returns the threshold as set by Set Stack Voltage Receiver Threshold.

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Sets the thresholds for the get_usb_voltage_reached_callback_receiver receiver.

The following options are possible:

OptionDescription
‘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)

The default value is (‘x’, 0, 0).

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Returns the threshold as set by Set USB Voltage Receiver Threshold.

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

Associated constants:

  • MASTERBRICK_THRESHOLD_OPTION_OFF
  • MASTERBRICK_THRESHOLD_OPTION_OUTSIDE
  • MASTERBRICK_THRESHOLD_OPTION_INSIDE
  • MASTERBRICK_THRESHOLD_OPTION_SMALLER
  • MASTERBRICK_THRESHOLD_OPTION_GREATER

Sets the period in ms with which the threshold receivers

are triggered, if the thresholds

  • Set Stack Current Receiver Threshold,
  • Set Stack Voltage Receiver Threshold,
  • Set USB Voltage Receiver Threshold

keep being reached.

The default value is 100.

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

Returns the debounce period as set by Set Debounce Period.

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

Returns true if a Ethernet Extension is available to be used by the Master Brick.

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

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

ValueDescription
0DHCP
1Static 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 default port, that is used by brickd, is 4223.

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:

  • MASTERBRICK_ETHERNET_CONNECTION_DHCP
  • MASTERBRICK_ETHERNET_CONNECTION_STATIC_IP

Returns the configuration as set by Set Ethernet Configuration.

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

Associated constants:

  • MASTERBRICK_ETHERNET_CONNECTION_DHCP
  • MASTERBRICK_ETHERNET_CONNECTION_STATIC_IP

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)

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)

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)

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.

The default values are 3 for the socket connections and 4280 for the port.

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

Returns the configuration as set by Set Ethernet Configuration.

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

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)

Returns the authentication secret as set by Set Ethernet Authentication Secret.

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

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)

Returns the authentication secret as set by Set Wifi Authentication Secret.

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

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

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

Associated constants:

  • MASTERBRICK_CONNECTION_TYPE_NONE
  • MASTERBRICK_CONNECTION_TYPE_USB
  • MASTERBRICK_CONNECTION_TYPE_SPI_STACK
  • MASTERBRICK_CONNECTION_TYPE_CHIBI
  • MASTERBRICK_CONNECTION_TYPE_RS485
  • MASTERBRICK_CONNECTION_TYPE_WIFI
  • MASTERBRICK_CONNECTION_TYPE_ETHERNET
  • MASTERBRICK_CONNECTION_TYPE_WIFI2

Returns true if a WIFI Extension 2.0 is available to be used by the Master Brick.

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

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)

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)

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)

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)

Returns the WIFI authentication secret as set by Set Wifi2 Authentication Secret.

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

Sets the general configuration of the WIFI Extension 2.0.

The port parameter sets the port number that your programm will connect to. The default value is 4223.

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

The website_port parameter sets the port number for the website of the WIFI Extension 2.0. The default value is 80.

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

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:

  • MASTERBRICK_WIFI2_PHY_MODE_B
  • MASTERBRICK_WIFI2_PHY_MODE_G
  • MASTERBRICK_WIFI2_PHY_MODE_N

Returns the general configuration as set by Set Wifi2 Configuration.

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

Associated constants:

  • MASTERBRICK_WIFI2_PHY_MODE_B
  • MASTERBRICK_WIFI2_PHY_MODE_G
  • MASTERBRICK_WIFI2_PHY_MODE_N

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

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

Associated constants:

  • MASTERBRICK_WIFI2_CLIENT_STATUS_IDLE
  • MASTERBRICK_WIFI2_CLIENT_STATUS_CONNECTING
  • MASTERBRICK_WIFI2_CLIENT_STATUS_WRONG_PASSWORD
  • MASTERBRICK_WIFI2_CLIENT_STATUS_NO_AP_FOUND
  • MASTERBRICK_WIFI2_CLIENT_STATUS_CONNECT_FAILED
  • MASTERBRICK_WIFI2_CLIENT_STATUS_GOT_IP
  • MASTERBRICK_WIFI2_CLIENT_STATUS_UNKNOWN

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 default value is true.

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)

Returns the client configuration as set by Set Wifi2 Client Configuration.

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

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)

Returns the client hostname as set by Set Wifi2 Client Hostname.

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

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)

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)

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 default value is true.

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. The default value is 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 default value is false.

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

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:

  • MASTERBRICK_WIFI2_AP_ENCRYPTION_OPEN
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WEP
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA_PSK
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA2_PSK
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA_WPA2_PSK

Returns the access point configuration as set by Set Wifi2 AP Configuration.

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

Associated constants:

  • MASTERBRICK_WIFI2_AP_ENCRYPTION_OPEN
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WEP
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA_PSK
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA2_PSK
  • MASTERBRICK_WIFI2_AP_ENCRYPTION_WPA_WPA2_PSK

Sets the access point password (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)

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)

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)

Returns the current version of the WIFI Extension 2.0 firmware (major, minor, revision).

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

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

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

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

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

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

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

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 default value is false. 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)

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)

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)

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)

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)

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)

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:

  • MASTERBRICK_WIFI2_MESH_STATUS_DISABLED
  • MASTERBRICK_WIFI2_MESH_STATUS_WIFI_CONNECTING
  • MASTERBRICK_WIFI2_MESH_STATUS_GOT_IP
  • MASTERBRICK_WIFI2_MESH_STATUS_MESH_LOCAL
  • MASTERBRICK_WIFI2_MESH_STATUS_MESH_ONLINE
  • MASTERBRICK_WIFI2_MESH_STATUS_AP_AVAILABLE
  • MASTERBRICK_WIFI2_MESH_STATUS_AP_SETUP
  • MASTERBRICK_WIFI2_MESH_STATUS_LEAF_AVAILABLE

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)

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)

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 send/received and decreased linearly if little data is send/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.

The minimum dynamic baudrate has a value range of 400000 to 2000000 baud.

By default dynamic baudrate is enabled and the minimum dynamic baudrate is 400000.

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

Returns the baudrate config, see Set SPITFP Baudrate Config.

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

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:

  • MASTERBRICK_COMMUNICATION_METHOD_NONE
  • MASTERBRICK_COMMUNICATION_METHOD_USB
  • MASTERBRICK_COMMUNICATION_METHOD_SPI_STACK
  • MASTERBRICK_COMMUNICATION_METHOD_CHIBI
  • MASTERBRICK_COMMUNICATION_METHOD_RS485
  • MASTERBRICK_COMMUNICATION_METHOD_WIFI
  • MASTERBRICK_COMMUNICATION_METHOD_ETHERNET
  • MASTERBRICK_COMMUNICATION_METHOD_WIFI_V2

Sets the baudrate for a specific Bricklet port (‘a’ - ‘d’). The baudrate can be in the range 400000 to 2000000.

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 you applications we recommend to not change the baudrate.

The default baudrate for all ports is 1400000.

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

Returns the baudrate for a given Bricklet port, see Set SPITFP Baudrate.

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

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)

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)

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)

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

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

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.

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

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!

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 can be ‘0’-‘8’ (stack position).

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

Trait Implementations

Returns a copy of the value. Read more
Performs copy-assignment from source. Read more

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

Should always be Self
The resulting type after obtaining ownership.
Creates owned data from borrowed data, usually by cloning. Read more
Uses borrowed data to replace owned data, usually by cloning. Read more
The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.