MQTT - Master Brick

This is the description of the MQTT API bindings for the Master Brick. General information and technical specifications for the Master Brick are summarized in its hardware description.

An installation guide for the MQTT API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Stack Status

Download (example-stack-status.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
# Change XXYYZZ to the UID of your Master Brick

setup:
    # Get current stack voltage
    subscribe to tinkerforge/response/master_brick/XXYYZZ/get_stack_voltage
    publish '' to tinkerforge/request/master_brick/XXYYZZ/get_stack_voltage
    
    # Get current stack current
    subscribe to tinkerforge/response/master_brick/XXYYZZ/get_stack_current
    publish '' to tinkerforge/request/master_brick/XXYYZZ/get_stack_current

API

All published payloads to and from the MQTT bindings are in JSON format.

If an error occures, the bindings publish a JSON object containing the error message as attribute "_ERROR". It is published on the corresponding response topic: .../response/... for .../request/... and .../callback/... for .../register/....

Basic Functions

request/master_brick/<UID>/get_stack_voltage
Response payload:
 
  • voltage -- int

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.

request/master_brick/<UID>/get_stack_current
Response payload:
 
  • current -- int

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.

Advanced Functions

request/master_brick/<UID>/set_extension_type
Request payload:
 
  • extension -- int
  • exttype -- int (has symbols)

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:

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.

The following symbols are available for this function:

for exttype:

  • "Chibi" = 1
  • "RS485" = 2
  • "Wifi" = 3
  • "Ethernet" = 4
  • "Wifi2" = 5
request/master_brick/<UID>/get_extension_type
Request payload:
 
  • extension -- int
Response payload:
 
  • exttype -- int (has symbols)

Returns the type for a given extension as set by request/master_brick/<UID>/set_extension_type.

The following symbols are available for this function:

for exttype:

  • "Chibi" = 1
  • "RS485" = 2
  • "Wifi" = 3
  • "Ethernet" = 4
  • "Wifi2" = 5
request/master_brick/<UID>/is_chibi_present
Response payload:
 
  • present -- bool

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

request/master_brick/<UID>/set_chibi_address
Request payload:
 
  • address -- int

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.

request/master_brick/<UID>/get_chibi_address
Response payload:
 
  • address -- int

Returns the address as set by request/master_brick/<UID>/set_chibi_address.

request/master_brick/<UID>/set_chibi_master_address
Request payload:
 
  • address -- int

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.

request/master_brick/<UID>/get_chibi_master_address
Response payload:
 
  • address -- int

Returns the address as set by request/master_brick/<UID>/set_chibi_master_address.

request/master_brick/<UID>/set_chibi_slave_address
Request payload:
 
  • num -- int
  • address -- int

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

request/master_brick/<UID>/get_chibi_slave_address
Request payload:
 
  • num -- int
Response payload:
 
  • address -- int

Returns the slave address for a given num as set by request/master_brick/<UID>/set_chibi_slave_address.

request/master_brick/<UID>/get_chibi_signal_strength
Response payload:
 
  • signal_strength -- int

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

request/master_brick/<UID>/get_chibi_error_log
Response payload:
 
  • underrun -- int
  • crc_error -- int
  • no_ack -- int
  • overflow -- int

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.

request/master_brick/<UID>/set_chibi_frequency
Request payload:
 
  • frequency -- int (has symbols)

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.

The following symbols are available for this function:

for frequency:

  • "OQPSK868MHz" = 0
  • "OQPSK915MHz" = 1
  • "OQPSK780MHz" = 2
  • "BPSK40915MHz" = 3
request/master_brick/<UID>/get_chibi_frequency
Response payload:
 
  • frequency -- int (has symbols)

Returns the frequency value as set by request/master_brick/<UID>/set_chibi_frequency.

The following symbols are available for this function:

for frequency:

  • "OQPSK868MHz" = 0
  • "OQPSK915MHz" = 1
  • "OQPSK780MHz" = 2
  • "BPSK40915MHz" = 3
request/master_brick/<UID>/set_chibi_channel
Request payload:
 
  • channel -- int

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, 2, 3, 4, 5, 6, 7, 8, 9, 10
OQPSK 780MHz (China) 0, 1, 2, 3
BPSK40 915MHz 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

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.

request/master_brick/<UID>/get_chibi_channel
Response payload:
 
  • channel -- int

Returns the channel as set by request/master_brick/<UID>/set_chibi_channel.

request/master_brick/<UID>/is_rs485_present
Response payload:
 
  • present -- bool

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

request/master_brick/<UID>/set_rs485_address
Request payload:
 
  • address -- int

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.

request/master_brick/<UID>/get_rs485_address
Response payload:
 
  • address -- int

Returns the address as set by request/master_brick/<UID>/set_rs485_address.

request/master_brick/<UID>/set_rs485_slave_address
Request payload:
 
  • num -- int
  • address -- int

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.

request/master_brick/<UID>/get_rs485_slave_address
Request payload:
 
  • num -- int
Response payload:
 
  • address -- int

Returns the slave address for a given num as set by request/master_brick/<UID>/set_rs485_slave_address.

request/master_brick/<UID>/get_rs485_error_log
Response payload:
 
  • crc_error -- int

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.

request/master_brick/<UID>/set_rs485_configuration
Request payload:
 
  • speed -- int
  • parity -- string (has symbols)
  • stopbits -- int

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.

The following symbols are available for this function:

for parity:

  • "None" = 'n'
  • "Even" = 'e'
  • "Odd" = 'o'
request/master_brick/<UID>/get_rs485_configuration
Response payload:
 
  • speed -- int
  • parity -- string (has symbols)
  • stopbits -- int

Returns the configuration as set by request/master_brick/<UID>/set_rs485_configuration.

The following symbols are available for this function:

for parity:

  • "None" = 'n'
  • "Even" = 'e'
  • "Odd" = 'o'
request/master_brick/<UID>/is_wifi_present
Response payload:
 
  • present -- bool

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

request/master_brick/<UID>/set_wifi_configuration
Request payload:
 
  • ssid -- string
  • connection -- int (has symbols)
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • port -- int

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

The following symbols are available for this function:

for connection:

  • "DHCP" = 0
  • "StaticIP" = 1
  • "AccessPointDHCP" = 2
  • "AccessPointStaticIP" = 3
  • "AdHocDHCP" = 4
  • "AdHocStaticIP" = 5
request/master_brick/<UID>/get_wifi_configuration
Response payload:
 
  • ssid -- string
  • connection -- int (has symbols)
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • port -- int

Returns the configuration as set by request/master_brick/<UID>/set_wifi_configuration.

The following symbols are available for this function:

for connection:

  • "DHCP" = 0
  • "StaticIP" = 1
  • "AccessPointDHCP" = 2
  • "AccessPointStaticIP" = 3
  • "AdHocDHCP" = 4
  • "AdHocStaticIP" = 5
request/master_brick/<UID>/set_wifi_encryption
Request payload:
 
  • encryption -- int (has symbols)
  • key -- string
  • key_index -- int
  • eap_options -- int (has symbols)
  • ca_certificate_length -- int
  • client_certificate_length -- int
  • private_key_length -- int

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, EAP-TLS, EAP-TTLS, PEAP)
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 request/master_brick/<UID>/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 request/master_brick/<UID>/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, 1=EAP-TLS, 2=EAP-TTLS, 3=EAP-PEAP
inner authentication 3 0=EAP-MSCHAP, 1=EAP-GTC
certificate type 4-5 0=CA Certificate, 1=Client Certificate, 2=Private Key

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.

The following symbols are available for this function:

for encryption:

  • "WPAWPA2" = 0
  • "WPAEnterprise" = 1
  • "WEP" = 2
  • "NoEncryption" = 3

for eap_options:

  • "OuterAuthEAPFAST" = 0
  • "OuterAuthEAPTLS" = 1
  • "OuterAuthEAPTTLS" = 2
  • "OuterAuthEAPPEAP" = 3
  • "InnerAuthEAPMSCHAP" = 0
  • "InnerAuthEAPGTC" = 4
  • "CertTypeCACert" = 0
  • "CertTypeClientCert" = 8
  • "CertTypePrivateKey" = 16
request/master_brick/<UID>/get_wifi_encryption
Response payload:
 
  • encryption -- int (has symbols)
  • key -- string
  • key_index -- int
  • eap_options -- int (has symbols)
  • ca_certificate_length -- int
  • client_certificate_length -- int
  • private_key_length -- int

Returns the encryption as set by request/master_brick/<UID>/set_wifi_encryption.

Note

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

The following symbols are available for this function:

for encryption:

  • "WPAWPA2" = 0
  • "WPAEnterprise" = 1
  • "WEP" = 2
  • "NoEncryption" = 3

for eap_options:

  • "OuterAuthEAPFAST" = 0
  • "OuterAuthEAPTLS" = 1
  • "OuterAuthEAPTTLS" = 2
  • "OuterAuthEAPPEAP" = 3
  • "InnerAuthEAPMSCHAP" = 0
  • "InnerAuthEAPGTC" = 4
  • "CertTypeCACert" = 0
  • "CertTypeClientCert" = 8
  • "CertTypePrivateKey" = 16
request/master_brick/<UID>/get_wifi_status
Response payload:
 
  • mac_address -- [int,... (x6)]
  • bssid -- [int,... (x6)]
  • channel -- int
  • rssi -- int
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • rx_count -- int
  • tx_count -- int
  • state -- int (has symbols)

Returns the status of the WIFI Extension. The state is updated automatically, all of the other parameters are updated on startup and every time request/master_brick/<UID>/refresh_wifi_status is called.

Possible states are:

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

The following symbols are available for this function:

for state:

  • "Disassociated" = 0
  • "Associated" = 1
  • "Associating" = 2
  • "Error" = 3
  • "NotInitializedYet" = 255
request/master_brick/<UID>/refresh_wifi_status

Refreshes the Wi-Fi status (see request/master_brick/<UID>/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.

request/master_brick/<UID>/set_wifi_certificate
Request payload:
 
  • index -- int
  • data -- [int,... (x32)]
  • data_length -- int

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.

request/master_brick/<UID>/get_wifi_certificate
Request payload:
 
  • index -- int
Response payload:
 
  • data -- [int,... (x32)]
  • data_length -- int

Returns the certificate for a given index as set by request/master_brick/<UID>/set_wifi_certificate.

request/master_brick/<UID>/set_wifi_power_mode
Request payload:
 
  • mode -- int (has symbols)

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

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

The default value is 0 (Full Speed).

The following symbols are available for this function:

for mode:

  • "FullSpeed" = 0
  • "LowPower" = 1
request/master_brick/<UID>/get_wifi_power_mode
Response payload:
 
  • mode -- int (has symbols)

Returns the power mode as set by request/master_brick/<UID>/set_wifi_power_mode.

The following symbols are available for this function:

for mode:

  • "FullSpeed" = 0
  • "LowPower" = 1
request/master_brick/<UID>/get_wifi_buffer_info
Response payload:
 
  • overflow -- int
  • low_watermark -- int
  • used -- int

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.

request/master_brick/<UID>/set_wifi_regulatory_domain
Request payload:
 
  • domain -- int (has symbols)

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

Domain Description
0 FCC: Channel 1-11 (N/S America, Australia, New Zealand)
1 ETSI: Channel 1-13 (Europe, Middle East, Africa)
2 TELEC: Channel 1-14 (Japan)

The default value is 1 (ETSI).

The following symbols are available for this function:

for domain:

  • "Channel1To11" = 0
  • "Channel1To13" = 1
  • "Channel1To14" = 2
request/master_brick/<UID>/get_wifi_regulatory_domain
Response payload:
 
  • domain -- int (has symbols)

Returns the regulatory domain as set by request/master_brick/<UID>/set_wifi_regulatory_domain.

The following symbols are available for this function:

for domain:

  • "Channel1To11" = 0
  • "Channel1To13" = 1
  • "Channel1To14" = 2
request/master_brick/<UID>/get_usb_voltage
Response payload:
 
  • voltage -- int

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

request/master_brick/<UID>/set_long_wifi_key
Request payload:
 
  • key -- string

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 request/master_brick/<UID>/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.

New in version 2.0.2 (Firmware).

request/master_brick/<UID>/get_long_wifi_key
Response payload:
 
  • key -- string

Returns the encryption key as set by request/master_brick/<UID>/set_long_wifi_key.

Note

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

New in version 2.0.2 (Firmware).

request/master_brick/<UID>/set_wifi_hostname
Request payload:
 
  • hostname -- string

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.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_wifi_hostname
Response payload:
 
  • hostname -- string

Returns the hostname as set by request/master_brick/<UID>/set_wifi_hostname.

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

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/is_ethernet_present
Response payload:
 
  • present -- bool

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

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/set_ethernet_configuration
Request payload:
 
  • connection -- int (has symbols)
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • port -- int

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

The following symbols are available for this function:

for connection:

  • "DHCP" = 0
  • "StaticIP" = 1

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/get_ethernet_configuration
Response payload:
 
  • connection -- int (has symbols)
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • port -- int

Returns the configuration as set by request/master_brick/<UID>/set_ethernet_configuration.

The following symbols are available for this function:

for connection:

  • "DHCP" = 0
  • "StaticIP" = 1

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/get_ethernet_status
Response payload:
 
  • mac_address -- [int,... (x6)]
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • rx_count -- int
  • tx_count -- int
  • hostname -- string

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.

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/set_ethernet_hostname
Request payload:
 
  • hostname -- string

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 request/master_brick/<UID>/get_ethernet_status.

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/set_ethernet_mac_address
Request payload:
 
  • mac_address -- [int,... (x6)]

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 request/master_brick/<UID>/get_ethernet_status.

New in version 2.1.0 (Firmware).

request/master_brick/<UID>/set_ethernet_websocket_configuration
Request payload:
 
  • sockets -- int
  • port -- int

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.

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/get_ethernet_websocket_configuration
Response payload:
 
  • sockets -- int
  • port -- int

Returns the configuration as set by request/master_brick/<UID>/set_ethernet_configuration.

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/set_ethernet_authentication_secret
Request payload:
 
  • secret -- string

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

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/get_ethernet_authentication_secret
Response payload:
 
  • secret -- string

Returns the authentication secret as set by request/master_brick/<UID>/set_ethernet_authentication_secret.

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/set_wifi_authentication_secret
Request payload:
 
  • secret -- string

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

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/get_wifi_authentication_secret
Response payload:
 
  • secret -- string

Returns the authentication secret as set by request/master_brick/<UID>/set_wifi_authentication_secret.

New in version 2.2.0 (Firmware).

request/master_brick/<UID>/get_connection_type
Response payload:
 
  • connection_type -- int (has symbols)

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

The following symbols are available for this function:

for connection_type:

  • "None" = 0
  • "USB" = 1
  • "SPIStack" = 2
  • "Chibi" = 3
  • "RS485" = 4
  • "Wifi" = 5
  • "Ethernet" = 6
  • "Wifi2" = 7

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/is_wifi2_present
Response payload:
 
  • present -- bool

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/start_wifi2_bootloader
Response payload:
 
  • result -- int

Starts the bootloader of the WIFI Extension 2.0. Returns 0 on success. Afterwards the request/master_brick/<UID>/write_wifi2_serial_port and request/master_brick/<UID>/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 request/master_brick/<UID>/get_connection_type function.

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/write_wifi2_serial_port
Request payload:
 
  • data -- [int,... (x60)]
  • length -- int
Response payload:
 
  • result -- int

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 request/master_brick/<UID>/start_wifi2_bootloader function.

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/read_wifi2_serial_port
Request payload:
 
  • length -- int
Response payload:
 
  • data -- [int,... (x60)]
  • result -- int

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 request/master_brick/<UID>/start_wifi2_bootloader function.

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_authentication_secret
Request payload:
 
  • secret -- string

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 request/master_brick/<UID>/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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_authentication_secret
Response payload:
 
  • secret -- string

Returns the WIFI authentication secret as set by request/master_brick/<UID>/set_wifi2_authentication_secret.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_configuration
Request payload:
 
  • port -- int
  • websocket_port -- int
  • website_port -- int
  • phy_mode -- int (has symbols)
  • sleep_mode -- int
  • website -- int

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 request/master_brick/<UID>/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.

The following symbols are available for this function:

for phy_mode:

  • "B" = 0
  • "G" = 1
  • "N" = 2

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_configuration
Response payload:
 
  • port -- int
  • websocket_port -- int
  • website_port -- int
  • phy_mode -- int (has symbols)
  • sleep_mode -- int
  • website -- int

Returns the general configuration as set by request/master_brick/<UID>/set_wifi2_configuration.

The following symbols are available for this function:

for phy_mode:

  • "B" = 0
  • "G" = 1
  • "N" = 2

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_status
Response payload:
 
  • client_enabled -- bool
  • client_status -- int (has symbols)
  • client_ip -- [int,int,int,int]
  • client_subnet_mask -- [int,int,int,int]
  • client_gateway -- [int,int,int,int]
  • client_mac_address -- [int,... (x6)]
  • client_rx_count -- int
  • client_tx_count -- int
  • client_rssi -- int
  • ap_enabled -- bool
  • ap_ip -- [int,int,int,int]
  • ap_subnet_mask -- [int,int,int,int]
  • ap_gateway -- [int,int,int,int]
  • ap_mac_address -- [int,... (x6)]
  • ap_rx_count -- int
  • ap_tx_count -- int
  • ap_connected_count -- int

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

The following symbols are available for this function:

for client_status:

  • "Idle" = 0
  • "Connecting" = 1
  • "WrongPassword" = 2
  • "NoAPFound" = 3
  • "ConnectFailed" = 4
  • "GotIP" = 5
  • "Unknown" = 255

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_client_configuration
Request payload:
 
  • enable -- bool
  • ssid -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • mac_address -- [int,... (x6)]
  • bssid -- [int,... (x6)]

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 request/master_brick/<UID>/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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_client_configuration
Response payload:
 
  • enable -- bool
  • ssid -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • mac_address -- [int,... (x6)]
  • bssid -- [int,... (x6)]

Returns the client configuration as set by request/master_brick/<UID>/set_wifi2_client_configuration.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_client_hostname
Request payload:
 
  • hostname -- string

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 request/master_brick/<UID>/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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_client_hostname
Response payload:
 
  • hostname -- string

Returns the client hostname as set by request/master_brick/<UID>/set_wifi2_client_hostname.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_client_password
Request payload:
 
  • password -- string

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

To apply configuration changes to the WIFI Extension 2.0 the request/master_brick/<UID>/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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_client_password
Response payload:
 
  • password -- string

Returns the client password as set by request/master_brick/<UID>/set_wifi2_client_password.

Note

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_ap_configuration
Request payload:
 
  • enable -- bool
  • ssid -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • encryption -- int (has symbols)
  • hidden -- bool
  • channel -- int
  • mac_address -- [int,... (x6)]

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 request/master_brick/<UID>/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 request/master_brick/<UID>/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.

The following symbols are available for this function:

for encryption:

  • "Open" = 0
  • "WEP" = 1
  • "WPAPSK" = 2
  • "WPA2PSK" = 3
  • "WPAWPA2PSK" = 4

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_ap_configuration
Response payload:
 
  • enable -- bool
  • ssid -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • encryption -- int (has symbols)
  • hidden -- bool
  • channel -- int
  • mac_address -- [int,... (x6)]

Returns the access point configuration as set by request/master_brick/<UID>/set_wifi2_ap_configuration.

The following symbols are available for this function:

for encryption:

  • "Open" = 0
  • "WEP" = 1
  • "WPAPSK" = 2
  • "WPA2PSK" = 3
  • "WPAWPA2PSK" = 4

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_ap_password
Request payload:
 
  • password -- string

Sets the access point password (at least 8 and up to 63 chars) for the configured encryption mode, see request/master_brick/<UID>/set_wifi2_ap_configuration.

To apply configuration changes to the WIFI Extension 2.0 the request/master_brick/<UID>/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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_ap_password
Response payload:
 
  • password -- string

Returns the access point password as set by request/master_brick/<UID>/set_wifi2_ap_password.

Note

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/save_wifi2_configuration
Response payload:
 
  • result -- int

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.

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/get_wifi2_firmware_version
Response payload:
 
  • firmware_version -- [int,int,int]

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/enable_wifi2_status_led

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/disable_wifi2_status_led

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/is_wifi2_status_led_enabled
Response payload:
 
  • enabled -- bool

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

New in version 2.4.0 (Firmware).

request/master_brick/<UID>/set_wifi2_mesh_configuration
Request payload:
 
  • enable -- bool
  • root_ip -- [int,int,int,int]
  • root_subnet_mask -- [int,int,int,int]
  • root_gateway -- [int,int,int,int]
  • router_bssid -- [int,... (x6)]
  • group_id -- [int,... (x6)]
  • group_ssid_prefix -- string
  • gateway_ip -- [int,int,int,int]
  • gateway_port -- int

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 request/master_brick/<UID>/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 request/master_brick/<UID>/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.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_configuration
Response payload:
 
  • enable -- bool
  • root_ip -- [int,int,int,int]
  • root_subnet_mask -- [int,int,int,int]
  • root_gateway -- [int,int,int,int]
  • router_bssid -- [int,... (x6)]
  • group_id -- [int,... (x6)]
  • group_ssid_prefix -- string
  • gateway_ip -- [int,int,int,int]
  • gateway_port -- int

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh configuration as set by request/master_brick/<UID>/set_wifi2_mesh_configuration.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/set_wifi2_mesh_router_ssid
Request payload:
 
  • ssid -- string

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 request/master_brick/<UID>/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.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_router_ssid
Response payload:
 
  • ssid -- string

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh router SSID as set by request/master_brick/<UID>/set_wifi2_mesh_router_ssid.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/set_wifi2_mesh_router_password
Request payload:
 
  • password -- string

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 request/master_brick/<UID>/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.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_router_password
Response payload:
 
  • password -- string

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh router password as set by request/master_brick/<UID>/set_wifi2_mesh_router_password.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_common_status
Response payload:
 
  • status -- int (has symbols)
  • root_node -- bool
  • root_candidate -- bool
  • connected_nodes -- int
  • rx_count -- int
  • tx_count -- int

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the common mesh status of the WIFI Extension 2.0.

The following symbols are available for this function:

for status:

  • "Disabled" = 0
  • "WIFIConnecting" = 1
  • "GotIP" = 2
  • "MeshLocal" = 3
  • "MeshOnline" = 4
  • "APAvailable" = 5
  • "APSetup" = 6
  • "LeafAvailable" = 7

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_client_status
Response payload:
 
  • hostname -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • mac_address -- [int,... (x6)]

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh client status of the WIFI Extension 2.0.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/get_wifi2_mesh_ap_status
Response payload:
 
  • ssid -- string
  • ip -- [int,int,int,int]
  • subnet_mask -- [int,int,int,int]
  • gateway -- [int,int,int,int]
  • mac_address -- [int,... (x6)]

Requires WIFI Extension 2.0 firmware 2.1.0.

Returns the mesh AP status of the WIFI Extension 2.0.

New in version 2.4.2 (Firmware).

request/master_brick/<UID>/set_spitfp_baudrate_config
Request payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

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 request/master_brick/<UID>/set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate as set by request/master_brick/<UID>/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.

New in version 2.4.6 (Firmware).

request/master_brick/<UID>/get_spitfp_baudrate_config
Response payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

Returns the baudrate config, see request/master_brick/<UID>/set_spitfp_baudrate_config.

New in version 2.4.6 (Firmware).

request/master_brick/<UID>/get_send_timeout_count
Request payload:
 
  • communication_method -- int (has symbols)
Response payload:
 
  • timeout_count -- int

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.

The following symbols are available for this function:

for communication_method:

  • "None" = 0
  • "USB" = 1
  • "SPIStack" = 2
  • "Chibi" = 3
  • "RS485" = 4
  • "WIFI" = 5
  • "Ethernet" = 6
  • "WIFIV2" = 7

New in version 2.4.3 (Firmware).

request/master_brick/<UID>/set_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
  • baudrate -- int

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 request/master_brick/<UID>/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 request/master_brick/<UID>/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.

New in version 2.4.3 (Firmware).

request/master_brick/<UID>/get_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • baudrate -- int

Returns the baudrate for a given Bricklet port, see request/master_brick/<UID>/set_spitfp_baudrate.

New in version 2.4.3 (Firmware).

request/master_brick/<UID>/get_spitfp_error_count
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • error_count_ack_checksum -- int
  • error_count_message_checksum -- int
  • error_count_frame -- int
  • error_count_overflow -- int

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.

New in version 2.4.3 (Firmware).

request/master_brick/<UID>/enable_status_led

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.

New in version 2.3.2 (Firmware).

request/master_brick/<UID>/disable_status_led

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.

New in version 2.3.2 (Firmware).

request/master_brick/<UID>/is_status_led_enabled
Response payload:
 
  • enabled -- bool

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

New in version 2.3.2 (Firmware).

request/master_brick/<UID>/get_protocol1_bricklet_name
Request payload:
 
  • port -- string
Response payload:
 
  • protocol_version -- int
  • firmware_version -- [int,int,int]
  • name -- string

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.

request/master_brick/<UID>/get_chip_temperature
Response payload:
 
  • temperature -- int

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.

request/master_brick/<UID>/reset

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!

request/master_brick/<UID>/get_identity
Response payload:
 
  • uid -- string
  • connected_uid -- string
  • position -- string
  • hardware_version -- [int,int,int]
  • firmware_version -- [int,int,int]
  • device_identifier -- int (has symbols)
  • _display_name -- string

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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.

The display name contains the Master's name in a human readable form.

Callback Configuration Functions

request/master_brick/<UID>/set_stack_current_callback_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/master_brick/<UID>/stack_current callback is triggered periodically. A value of 0 turns the callback off.

The register/master_brick/<UID>/stack_current callback is only triggered if the current has changed since the last triggering.

The default value is 0.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_stack_current_callback_period
Response payload:
 
  • period -- int

Returns the period as set by request/master_brick/<UID>/set_stack_current_callback_period.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_stack_voltage_callback_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/master_brick/<UID>/stack_voltage callback is triggered periodically. A value of 0 turns the callback off.

The register/master_brick/<UID>/stack_voltage callback is only triggered if the voltage has changed since the last triggering.

The default value is 0.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_stack_voltage_callback_period
Response payload:
 
  • period -- int

Returns the period as set by request/master_brick/<UID>/set_stack_voltage_callback_period.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_usb_voltage_callback_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/master_brick/<UID>/usb_voltage callback is triggered periodically. A value of 0 turns the callback off.

The register/master_brick/<UID>/usb_voltage callback is only triggered if the voltage has changed since the last triggering.

The default value is 0.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_usb_voltage_callback_period
Response payload:
 
  • period -- int

Returns the period as set by request/master_brick/<UID>/set_usb_voltage_callback_period.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_stack_current_callback_threshold
Request payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Sets the thresholds for the register/master_brick/<UID>/stack_current_reached callback.

The following options are possible:

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

The default value is ('x', 0, 0).

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_stack_current_callback_threshold
Response payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Returns the threshold as set by request/master_brick/<UID>/set_stack_current_callback_threshold.

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_stack_voltage_callback_threshold
Request payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Sets the thresholds for the register/master_brick/<UID>/stack_voltage_reached callback.

The following options are possible:

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

The default value is ('x', 0, 0).

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_stack_voltage_callback_threshold
Response payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Returns the threshold as set by request/master_brick/<UID>/set_stack_voltage_callback_threshold.

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_usb_voltage_callback_threshold
Request payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Sets the thresholds for the register/master_brick/<UID>/usb_voltage_reached callback.

The following options are possible:

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

The default value is ('x', 0, 0).

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_usb_voltage_callback_threshold
Response payload:
 
  • option -- string (has symbols)
  • min -- int
  • max -- int

Returns the threshold as set by request/master_brick/<UID>/set_usb_voltage_callback_threshold.

The following symbols are available for this function:

for option:

  • "Off" = 'x'
  • "Outside" = 'o'
  • "Inside" = 'i'
  • "Smaller" = '<'
  • "Greater" = '>'

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/set_debounce_period
Request payload:
 
  • debounce -- int

Sets the period in ms with which the threshold callbacks

are triggered, if the thresholds

keep being reached.

The default value is 100.

New in version 2.0.5 (Firmware).

request/master_brick/<UID>/get_debounce_period
Response payload:
 
  • debounce -- int

Returns the debounce period as set by request/master_brick/<UID>/set_debounce_period.

New in version 2.0.5 (Firmware).

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding .../register/... topic and an optional suffix. This suffix can be used to deregister the callback later.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

register/master_brick/<UID>/stack_current
Request payload:
 
  • register -- bool
Response payload:
 
  • current -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/stack_current[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/stack_current[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/master_brick/<UID>/set_stack_current_callback_period. The callback payload is the current of the sensor.

The register/master_brick/<UID>/stack_current callback is only triggered if the current has changed since the last triggering.

New in version 2.0.5 (Firmware).

register/master_brick/<UID>/stack_voltage
Request payload:
 
  • register -- bool
Response payload:
 
  • voltage -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/stack_voltage[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/stack_voltage[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/master_brick/<UID>/set_stack_voltage_callback_period. The callback payload is the voltage of the sensor.

The register/master_brick/<UID>/stack_voltage callback is only triggered if the voltage has changed since the last triggering.

New in version 2.0.5 (Firmware).

register/master_brick/<UID>/usb_voltage
Request payload:
 
  • register -- bool
Response payload:
 
  • voltage -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/usb_voltage[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/usb_voltage[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/master_brick/<UID>/set_usb_voltage_callback_period. The callback payload is the USB voltage in mV.

The register/master_brick/<UID>/usb_voltage callback is only triggered if the USB voltage has changed since the last triggering.

Does not work with hardware version 2.1.

New in version 2.0.5 (Firmware).

register/master_brick/<UID>/stack_current_reached
Request payload:
 
  • register -- bool
Response payload:
 
  • current -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/stack_current_reached[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/stack_current_reached[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when the threshold as set by request/master_brick/<UID>/set_stack_current_callback_threshold is reached. The callback payload is the stack current in mA.

If the threshold keeps being reached, the callback is triggered periodically with the period as set by request/master_brick/<UID>/set_debounce_period.

New in version 2.0.5 (Firmware).

register/master_brick/<UID>/stack_voltage_reached
Request payload:
 
  • register -- bool
Response payload:
 
  • voltage -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/stack_voltage_reached[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/stack_voltage_reached[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when the threshold as set by request/master_brick/<UID>/set_stack_voltage_callback_threshold is reached. The callback payload is the stack voltage in mV.

If the threshold keeps being reached, the callback is triggered periodically with the period as set by request/master_brick/<UID>/set_debounce_period.

New in version 2.0.5 (Firmware).

register/master_brick/<UID>/usb_voltage_reached
Request payload:
 
  • register -- bool
Response payload:
 
  • voltage -- int

A callback can be registered for this event by publishing to the .../register/master_brick/<UID>/usb_voltage_reached[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/master_brick/<UID>/usb_voltage_reached[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when the threshold as set by request/master_brick/<UID>/set_usb_voltage_callback_threshold is reached. The callback payload is the voltage of the sensor.

If the threshold keeps being reached, the callback is triggered periodically with the period as set by request/master_brick/<UID>/set_debounce_period.

New in version 2.0.5 (Firmware).