MQTT - XMC1400 Breakout Bricklet

This is the description of the MQTT API bindings for the XMC1400 Breakout Bricklet. General information and technical specifications for the XMC1400 Breakout Bricklet 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).

Gpio

Download (example-gpio.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
# Change XYZ to the UID of your XMC1400 Breakout Bricklet

setup:
    # Set Port 1, Pin 0 alternating high/low for 5 times with 1s delay
    for i in 0 1 2 3 4; do
    
        wait for 1s 
    
        publish '{"port": 1, "pin": 0, "mode": "output_push_pull", "input_hysteresis": "standard", "output_level": false}' to tinkerforge/request/xmc1400_breakout_bricklet/XYZ/set_gpio_config 
    
        wait for 1s 
    
        publish '{"port": 1, "pin": 0, "mode": "output_push_pull", "input_hysteresis": "standard", "output_level": true}' to tinkerforge/request/xmc1400_breakout_bricklet/XYZ/set_gpio_config 
    
    done

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 member _ERROR. It is published on the corresponding response topic: .../response/... for .../request/... and .../callback/... for .../register/....

Basic Functions

request/xmc1400_breakout_bricklet/<UID>/set_gpio_config
Request:
  • port – Type: int, Range: [0 to 255]
  • pin – Type: int, Range: [0 to 255]
  • mode – Type: int, Range: See symbols
  • input_hysteresis – Type: int, Range: See symbols
  • output_level – Type: bool
Response:
  • no response

Example for a setter function. The values are the values that can be given to the XMC_GPIO_Init function. See communication.c in the firmware.

The following symbols are available for this function:

For mode:

  • "InputTristate" = 0
  • "InputPullDown" = 1
  • "InputPullUp" = 2
  • "InputSampling" = 3
  • "InputInvertedTristate" = 4
  • "InputInvertedPullDown" = 5
  • "InputInvertedPullUp" = 6
  • "InputInvertedSampling" = 7
  • "OutputPushPull" = 8
  • "OutputOpenDrain" = 9

For input_hysteresis:

  • "Standard" = 0
  • "Large" = 4
request/xmc1400_breakout_bricklet/<UID>/get_gpio_input
Request:
  • port – Type: int, Range: [0 to 255]
  • pin – Type: int, Range: [0 to 255]
Response:
  • value – Type: bool

Example for a getter function. Returns the result of a XMC_GPIO_GetInput call for the given port/pin.

request/xmc1400_breakout_bricklet/<UID>/set_adc_channel_config
Request:
  • channel – Type: int, Range: [0 to 255]
  • enable – Type: bool
Response:
  • no response

Enables a ADC channel for the ADC driver example (adc.c/adc.h).

There are 8 ADC channels and they correspond to the following pins:

  • Channel 0: P2_6
  • Channel 1: P2_8
  • Channel 2: P2_9
  • Channel 3: P2_10
  • Channel 4: P2_11
  • Channel 5: P2_0
  • Channel 6: P2_1
  • Channel 7: P2_2
request/xmc1400_breakout_bricklet/<UID>/get_adc_channel_config
Request:
  • channel – Type: int, Range: [0 to 255]
Response:
  • enable – Type: bool

Returns the config for the given channel as set by request/xmc1400_breakout_bricklet/<UID>/set_adc_channel_config.

request/xmc1400_breakout_bricklet/<UID>/get_adc_channel_value
Request:
  • channel – Type: int, Range: [0 to 255]
Response:
  • value – Type: int, Range: [0 to 216 - 1]

Returns the 12-bit value of the given ADC channel of the ADC driver example.

request/xmc1400_breakout_bricklet/<UID>/get_adc_values
Request:
  • empty payload
Response:
  • values – Type: [int, ...], Length: 8, Range: [0 to 216 - 1]

Returns the values for all 8 ADC channels of the adc driver example.

This example function also has a corresponding callback.

See request/xmc1400_breakout_bricklet/<UID>/set_adc_values_callback_configuration and register/xmc1400_breakout_bricklet/<UID>/adc_values callback.

request/xmc1400_breakout_bricklet/<UID>/get_count
Request:
  • empty payload
Response:
  • count – Type: int, Range: [0 to 232 - 1]

Returns the value of the example count (see example.c).

This example function uses the "add_callback_value_function"-helper in the generator. The getter as well as the callback and callback configuration functions are auto-generated for the API as well as the firmware.

If you want to get the value periodically, it is recommended to use the register/xmc1400_breakout_bricklet/<UID>/count callback. You can set the callback configuration with request/xmc1400_breakout_bricklet/<UID>/set_count_callback_configuration.

Advanced Functions

request/xmc1400_breakout_bricklet/<UID>/get_spitfp_error_count
Request:
  • empty payload
Response:
  • error_count_ack_checksum – Type: int, Range: [0 to 232 - 1]
  • error_count_message_checksum – Type: int, Range: [0 to 232 - 1]
  • error_count_frame – Type: int, Range: [0 to 232 - 1]
  • error_count_overflow – Type: int, Range: [0 to 232 - 1]

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

The errors are divided into

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

The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

request/xmc1400_breakout_bricklet/<UID>/set_bootloader_mode
Request:
  • mode – Type: int, Range: See symbols
Response:
  • status – Type: int, Range: See symbols

Sets the bootloader mode and returns the status after the requested mode change was instigated.

You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.

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

The following symbols are available for this function:

For mode:

  • "Bootloader" = 0
  • "Firmware" = 1
  • "BootloaderWaitForReboot" = 2
  • "FirmwareWaitForReboot" = 3
  • "FirmwareWaitForEraseAndReboot" = 4

For status:

  • "OK" = 0
  • "InvalidMode" = 1
  • "NoChange" = 2
  • "EntryFunctionNotPresent" = 3
  • "DeviceIdentifierIncorrect" = 4
  • "CRCMismatch" = 5
request/xmc1400_breakout_bricklet/<UID>/get_bootloader_mode
Request:
  • empty payload
Response:
  • mode – Type: int, Range: See symbols

Returns the current bootloader mode, see request/xmc1400_breakout_bricklet/<UID>/set_bootloader_mode.

The following symbols are available for this function:

For mode:

  • "Bootloader" = 0
  • "Firmware" = 1
  • "BootloaderWaitForReboot" = 2
  • "FirmwareWaitForReboot" = 3
  • "FirmwareWaitForEraseAndReboot" = 4
request/xmc1400_breakout_bricklet/<UID>/set_write_firmware_pointer
Request:
  • pointer – Type: int, Range: [0 to 232 - 1]
Response:
  • no response

Sets the firmware pointer for request/xmc1400_breakout_bricklet/<UID>/write_firmware. The pointer has to be increased by chunks of size 64. The data is written to flash every 4 chunks (which equals to one page of size 256).

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

request/xmc1400_breakout_bricklet/<UID>/write_firmware
Request:
  • data – Type: [int, ...], Length: 64, Range: [0 to 255]
Response:
  • status – Type: int, Range: [0 to 255]

Writes 64 Bytes of firmware at the position as written by request/xmc1400_breakout_bricklet/<UID>/set_write_firmware_pointer before. The firmware is written to flash every 4 chunks.

You can only write firmware in bootloader mode.

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

request/xmc1400_breakout_bricklet/<UID>/set_status_led_config
Request:
  • config – Type: int, Range: See symbols
Response:
  • no response

Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.

The following symbols are available for this function:

For config:

  • "Off" = 0
  • "On" = 1
  • "ShowHeartbeat" = 2
  • "ShowStatus" = 3
request/xmc1400_breakout_bricklet/<UID>/get_status_led_config
Request:
  • empty payload
Response:
  • config – Type: int, Range: See symbols

Returns the configuration as set by request/xmc1400_breakout_bricklet/<UID>/set_status_led_config

The following symbols are available for this function:

For config:

  • "Off" = 0
  • "On" = 1
  • "ShowHeartbeat" = 2
  • "ShowStatus" = 3
request/xmc1400_breakout_bricklet/<UID>/get_chip_temperature
Request:
  • empty payload
Response:
  • temperature – Type: int, Range: [-215 to 215 - 1]

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

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

request/xmc1400_breakout_bricklet/<UID>/reset
Request:
  • empty payload
Response:
  • no response

Calling this function will reset the Bricklet. All configurations will be lost.

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

request/xmc1400_breakout_bricklet/<UID>/write_uid
Request:
  • uid – Type: int, Range: [0 to 232 - 1]
Response:
  • no response

Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.

We recommend that you use Brick Viewer to change the UID.

request/xmc1400_breakout_bricklet/<UID>/read_uid
Request:
  • empty payload
Response:
  • uid – Type: int, Range: [0 to 232 - 1]

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

request/xmc1400_breakout_bricklet/<UID>/get_identity
Request:
  • empty payload
Response:
  • uid – Type: string, Length: up to 8
  • connected_uid – Type: string, Length: up to 8
  • position – Type: char
  • hardware_version – Type: [int, ...], Length: 3, Range: [0 to 255]
  • firmware_version – Type: [int, ...], Length: 3, Range: [0 to 255]
  • device_identifier – Type: int, Range: [0 to 216 - 1]
  • _display_name – Type: string

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

The position can be 'a', 'b', 'c' or 'd'.

The device identifier numbers can be found here. 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 XMC1400 Breakout's name in a human readable form.

Callback Configuration Functions

request/xmc1400_breakout_bricklet/<UID>/set_adc_values_callback_configuration
Request:
  • period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false
Response:
  • no response

The period is the period with which the register/xmc1400_breakout_bricklet/<UID>/adc_values callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

request/xmc1400_breakout_bricklet/<UID>/get_adc_values_callback_configuration
Request:
  • empty payload
Response:
  • period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false

Returns the callback configuration as set by request/xmc1400_breakout_bricklet/<UID>/set_adc_values_callback_configuration.

request/xmc1400_breakout_bricklet/<UID>/set_count_callback_configuration
Request:
  • period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false
  • option – Type: char, Range: See symbols, Default: "x"
  • min – Type: int, Range: [0 to 232 - 1]
  • max – Type: int, Range: [0 to 232 - 1]
Response:
  • no response

The period is the period with which the register/xmc1400_breakout_bricklet/<UID>/count callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

It is furthermore possible to constrain the callback with thresholds.

The option-parameter together with min/max sets a threshold for the register/xmc1400_breakout_bricklet/<UID>/count callback.

The following options are possible:

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

If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.

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

The following symbols are available for this function:

For option:

  • "Off" = "x"
  • "Outside" = "o"
  • "Inside" = "i"
  • "Smaller" = "<"
  • "Greater" = ">"
request/xmc1400_breakout_bricklet/<UID>/get_count_callback_configuration
Request:
  • empty payload
Response:
  • period – Type: int, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • value_has_to_change – Type: bool, Default: false
  • option – Type: char, Range: See symbols, Default: "x"
  • min – Type: int, Range: [0 to 232 - 1]
  • max – Type: int, Range: [0 to 232 - 1]

Returns the callback configuration as set by request/xmc1400_breakout_bricklet/<UID>/set_count_callback_configuration.

The following symbols are available for this function:

For option:

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

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/xmc1400_breakout_bricklet/<UID>/adc_values
Register Request:
  • register – Type: bool
Callback Response:
  • values – Type: [int, ...], Length: 8, Range: [0 to 216 - 1]

A callback can be registered for this event by publishing to the .../register/xmc1400_breakout_bricklet/<UID>/adc_values[/<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/xmc1400_breakout_bricklet/<UID>/adc_values[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically according to the configuration set by request/xmc1400_breakout_bricklet/<UID>/set_adc_values_callback_configuration.

The callback payload members are the same as request/xmc1400_breakout_bricklet/<UID>/get_adc_values.

register/xmc1400_breakout_bricklet/<UID>/count
Register Request:
  • register – Type: bool
Callback Response:
  • count – Type: int, Range: [0 to 232 - 1]

A callback can be registered for this event by publishing to the .../register/xmc1400_breakout_bricklet/<UID>/count[/<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/xmc1400_breakout_bricklet/<UID>/count[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically according to the configuration set by request/xmc1400_breakout_bricklet/<UID>/set_count_callback_configuration.

The callback payload is the same as request/xmc1400_breakout_bricklet/<UID>/get_count.