Software / API Bindings / MQTT / API Reference and Examples / Bricklets / Industrial Counter Bricklet

MQTT - Industrial Counter Bricklet¶

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

Callback¶

Download (example-callback.txt)

# Change XYZ to the UID of your Industrial Counter Bricklet

setup:
    # Handle incoming all counter callbacks
    subscribe to tinkerforge/callback/industrial_counter_bricklet/XYZ/all_counter
    publish '{"register": true}' to tinkerforge/register/industrial_counter_bricklet/XYZ/all_counter # Register all_counter callback

    # Set period for all counter callback to 1s (1000ms)
    publish '{"period": 1000, "value_has_to_change": true}' to tinkerforge/request/industrial_counter_bricklet/XYZ/set_all_counter_callback_configuration

Simple¶

Download (example-simple.txt)

# Change XYZ to the UID of your Industrial Counter Bricklet

setup:
    # Get current counter from channel 0
    subscribe to tinkerforge/response/industrial_counter_bricklet/XYZ/get_counter
    publish '{"channel": "0"}' to tinkerforge/request/industrial_counter_bricklet/XYZ/get_counter

    # Get current signal data from channel 0
    subscribe to tinkerforge/response/industrial_counter_bricklet/XYZ/get_signal_data
    publish '{"channel": "0"}' to tinkerforge/request/industrial_counter_bricklet/XYZ/get_signal_data

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/industrial_counter_bricklet/<UID>/get_counter¶

Request:	channel – Type: int, Range: See symbols
Response:	counter – Type: int, Range: [-2⁴⁷ to 2⁴⁷ - 1]

Returns the current counter value for the given channel.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

request/industrial_counter_bricklet/<UID>/get_all_counter¶

Request:	empty payload
Response:	counter – Type: [int, ...], Length: 4, Range: [-2⁴⁷ to 2⁴⁷ - 1]

Returns the current counter values for all four channels.

request/industrial_counter_bricklet/<UID>/set_counter¶

Request:	channel – Type: int, Range: See symbols counter – Type: int, Range: [-2⁴⁷ to 2⁴⁷ - 1]
Response:	no response

Sets the counter value for the given channel.

The default value for the counters on startup is 0.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

request/industrial_counter_bricklet/<UID>/set_all_counter¶

Request:	counter – Type: [int, ...], Length: 4, Range: [-2⁴⁷ to 2⁴⁷ - 1]
Response:	no response

Sets the counter values for all four channels.

The default value for the counters on startup is 0.

request/industrial_counter_bricklet/<UID>/get_signal_data¶

Request:	channel – Type: int, Range: See symbols
Response:	duty_cycle – Type: int, Unit: 1/100 %, Range: [0 to 10000] period – Type: int, Unit: 1 ns, Range: [0 to 2⁶⁴ - 1] frequency – Type: int, Unit: 1/1000 Hz, Range: [0 to 2³² - 1] value – Type: bool

Returns the signal data (duty cycle, period, frequency and value) for the given channel.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

request/industrial_counter_bricklet/<UID>/get_all_signal_data¶

Request:	empty payload
Response:	duty_cycle – Type: [int, ...], Length: 4, Unit: 1/100 %, Range: [0 to 10000] period – Type: [int, ...], Length: 4, Unit: 1 ns, Range: [0 to 2⁶⁴ - 1] frequency – Type: [int, ...], Length: 4, Unit: 1/1000 Hz, Range: [0 to 2³² - 1] value – Type: [bool, ...], Length: 4

Returns the signal data (duty cycle, period, frequency and value) for all four channels.

request/industrial_counter_bricklet/<UID>/set_counter_active¶

Request:	channel – Type: int, Range: See symbols active – Type: bool, Default: true
Response:	no response

Activates/deactivates the counter of the given channel.

true = activate, false = deactivate.

By default all channels are activated.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

request/industrial_counter_bricklet/<UID>/set_all_counter_active¶

Request:	active – Type: [bool, ...], Length: 4, Default: [true,true,true,true]
Response:	no response

Activates/deactivates the counter of all four channels.

true = activate, false = deactivate.

By default all channels are activated.

request/industrial_counter_bricklet/<UID>/get_counter_active¶

Request:	channel – Type: int, Range: See symbols
Response:	active – Type: bool, Default: true

Returns the activation state of the given channel.

true = activated, false = deactivated.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

request/industrial_counter_bricklet/<UID>/get_all_counter_active¶

Request:	empty payload
Response:	active – Type: [bool, ...], Length: 4, Default: [true,true,true,true]

Returns the activation state of all four channels.

true = activated, false = deactivated.

request/industrial_counter_bricklet/<UID>/set_counter_configuration¶

Request:	channel – Type: int, Range: See symbols count_edge – Type: int, Range: See symbols, Default: 0 count_direction – Type: int, Range: See symbols, Default: 0 duty_cycle_prescaler – Type: int, Range: See symbols, Default: 0 frequency_integration_time – Type: int, Range: See symbols, Default: 3
Response:	no response

Sets the counter configuration for the given channel.

Count Edge: Counter can count on rising, falling or both edges.
Count Direction: Counter can count up or down. You can also use another channel as direction input, see here for details.
Duty Cycle Prescaler: Sets a divider for the internal clock. See here for details.
Frequency Integration Time: Sets the integration time for the frequency measurement. See here for details.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

For count_edge:

"rising" = 0
"falling" = 1
"both" = 2

For count_direction:

"up" = 0
"down" = 1
"external_up" = 2
"external_down" = 3

For duty_cycle_prescaler:

"1" = 0
"2" = 1
"4" = 2
"8" = 3
"16" = 4
"32" = 5
"64" = 6
"128" = 7
"256" = 8
"512" = 9
"1024" = 10
"2048" = 11
"4096" = 12
"8192" = 13
"16384" = 14
"32768" = 15

For frequency_integration_time:

"128_ms" = 0
"256_ms" = 1
"512_ms" = 2
"1024_ms" = 3
"2048_ms" = 4
"4096_ms" = 5
"8192_ms" = 6
"16384_ms" = 7
"32768_ms" = 8

request/industrial_counter_bricklet/<UID>/get_counter_configuration¶

Request:	channel – Type: int, Range: See symbols
Response:	count_edge – Type: int, Range: See symbols, Default: 0 count_direction – Type: int, Range: See symbols, Default: 0 duty_cycle_prescaler – Type: int, Range: See symbols, Default: 0 frequency_integration_time – Type: int, Range: See symbols, Default: 3

Returns the counter configuration as set by request/industrial_counter_bricklet/<UID>/set_counter_configuration.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

For count_edge:

"rising" = 0
"falling" = 1
"both" = 2

For count_direction:

"up" = 0
"down" = 1
"external_up" = 2
"external_down" = 3

For duty_cycle_prescaler:

"1" = 0
"2" = 1
"4" = 2
"8" = 3
"16" = 4
"32" = 5
"64" = 6
"128" = 7
"256" = 8
"512" = 9
"1024" = 10
"2048" = 11
"4096" = 12
"8192" = 13
"16384" = 14
"32768" = 15

For frequency_integration_time:

"128_ms" = 0
"256_ms" = 1
"512_ms" = 2
"1024_ms" = 3
"2048_ms" = 4
"4096_ms" = 5
"8192_ms" = 6
"16384_ms" = 7
"32768_ms" = 8

request/industrial_counter_bricklet/<UID>/set_channel_led_config¶

Request:	channel – Type: int, Range: See symbols config – Type: int, Range: See symbols, Default: 3
Response:	no response

Each channel has a corresponding LED. You can turn the LED off, on or show a heartbeat. You can also set the LED to "Channel Status". In this mode the LED is on if the channel is high and off otherwise.

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

For config:

"off" = 0
"on" = 1
"show_heartbeat" = 2
"show_channel_status" = 3

request/industrial_counter_bricklet/<UID>/get_channel_led_config¶

Request:	channel – Type: int, Range: See symbols
Response:	config – Type: int, Range: See symbols, Default: 3

Returns the channel LED configuration as set by request/industrial_counter_bricklet/<UID>/set_channel_led_config

The following symbols are available for this function:

For channel:

"0" = 0
"1" = 1
"2" = 2
"3" = 3

For config:

"off" = 0
"on" = 1
"show_heartbeat" = 2
"show_channel_status" = 3

Advanced Functions¶

request/industrial_counter_bricklet/<UID>/get_spitfp_error_count¶

Request:	empty payload
Response:	error_count_ack_checksum – Type: int, Range: [0 to 2³² - 1] error_count_message_checksum – Type: int, Range: [0 to 2³² - 1] error_count_frame – Type: int, Range: [0 to 2³² - 1] error_count_overflow – Type: int, Range: [0 to 2³² - 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/industrial_counter_bricklet/<UID>/set_status_led_config¶

Request:	config – Type: int, Range: See symbols, Default: 3
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
"show_heartbeat" = 2
"show_status" = 3

request/industrial_counter_bricklet/<UID>/get_status_led_config¶

Request:	empty payload
Response:	config – Type: int, Range: See symbols, Default: 3

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

The following symbols are available for this function:

For config:

"off" = 0
"on" = 1
"show_heartbeat" = 2
"show_status" = 3

request/industrial_counter_bricklet/<UID>/get_chip_temperature¶

Request:	empty payload
Response:	temperature – Type: int, Unit: 1 °C, Range: [-2¹⁵ to 2¹⁵ - 1]

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

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

request/industrial_counter_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/industrial_counter_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, Range: ["a" to "h", "z"]
hardware_version – Type: [int, ...], Length: 3

0: major – Type: int, Range: [0 to 255]
1: minor – Type: int, Range: [0 to 255]
2: revision – Type: int, Range: [0 to 255]

firmware_version – Type: [int, ...], Length: 3

0: major – Type: int, Range: [0 to 255]
1: minor – Type: int, Range: [0 to 255]
2: revision – Type: int, Range: [0 to 255]

device_identifier – Type: int, Range: [0 to 2¹⁶ - 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', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.

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 Industrial Counter's name in a human readable form.

Callback Configuration Functions¶

request/industrial_counter_bricklet/<UID>/set_all_counter_callback_configuration¶

Request:	period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 value_has_to_change – Type: bool, Default: false
Response:	no response

The period is the period with which the register/industrial_counter_bricklet/<UID>/all_counter 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/industrial_counter_bricklet/<UID>/get_all_counter_callback_configuration¶

Request:	empty payload
Response:	period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 value_has_to_change – Type: bool, Default: false

Returns the callback configuration as set by request/industrial_counter_bricklet/<UID>/set_all_counter_callback_configuration.

request/industrial_counter_bricklet/<UID>/set_all_signal_data_callback_configuration¶

Request:	period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 value_has_to_change – Type: bool, Default: false
Response:	no response

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

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

request/industrial_counter_bricklet/<UID>/get_all_signal_data_callback_configuration¶

Request:	empty payload
Response:	period – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 0 value_has_to_change – Type: bool, Default: false

Returns the callback configuration as set by request/industrial_counter_bricklet/<UID>/set_all_signal_data_callback_configuration.

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/industrial_counter_bricklet/<UID>/all_counter¶

Register Request:	register – Type: bool
Callback Response:	counter – Type: [int, ...], Length: 4, Range: [-2⁴⁷ to 2⁴⁷ - 1]

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

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

The callback payload members are the same as request/industrial_counter_bricklet/<UID>/get_all_counter.

register/industrial_counter_bricklet/<UID>/all_signal_data¶

Register Request:	register – Type: bool
Callback Response:	duty_cycle – Type: [int, ...], Length: 4, Unit: 1/100 %, Range: [0 to 10000] period – Type: [int, ...], Length: 4, Unit: 1 ns, Range: [0 to 2⁶⁴ - 1] frequency – Type: [int, ...], Length: 4, Unit: 1/1000 Hz, Range: [0 to 2³² - 1] value – Type: [bool, ...], Length: 4

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

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

The callback payload members are the same as request/industrial_counter_bricklet/<UID>/get_all_signal_data.

Internal Functions¶

Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.

request/industrial_counter_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
"bootloader_wait_for_reboot" = 2
"firmware_wait_for_reboot" = 3
"firmware_wait_for_erase_and_reboot" = 4

For status:

"ok" = 0
"invalid_mode" = 1
"no_change" = 2
"entry_function_not_present" = 3
"device_identifier_incorrect" = 4
"crc_mismatch" = 5

request/industrial_counter_bricklet/<UID>/get_bootloader_mode¶

Request:	empty payload
Response:	mode – Type: int, Range: See symbols

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

The following symbols are available for this function:

For mode:

"bootloader" = 0
"firmware" = 1
"bootloader_wait_for_reboot" = 2
"firmware_wait_for_reboot" = 3
"firmware_wait_for_erase_and_reboot" = 4

request/industrial_counter_bricklet/<UID>/set_write_firmware_pointer¶

Request:	pointer – Type: int, Unit: 1 B, Range: [0 to 2³² - 1]
Response:	no response

Sets the firmware pointer for request/industrial_counter_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/industrial_counter_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/industrial_counter_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/industrial_counter_bricklet/<UID>/write_uid¶

Request:	uid – Type: int, Range: [0 to 2³² - 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/industrial_counter_bricklet/<UID>/read_uid¶

Request:	empty payload
Response:	uid – Type: int, Range: [0 to 2³² - 1]

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