This is the description of the C/C++ for Microcontrollers API bindings for the Servo Bricklet 2.0. General information and technical specifications for the Servo Bricklet 2.0 are summarized in its hardware description.
An installation guide for the C/C++ for Microcontrollers API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example_configuration.c)
1// This example is not self-contained.
2// It requires usage of the example driver specific to your platform.
3// See the HAL documentation.
4
5#include "src/bindings/hal_common.h"
6#include "src/bindings/bricklet_servo_v2.h"
7
8void check(int rc, const char *msg);
9void example_setup(TF_HAL *hal);
10void example_loop(TF_HAL *hal);
11
12static TF_ServoV2 s;
13
14void example_setup(TF_HAL *hal) {
15 // Create device object
16 check(tf_servo_v2_create(&s, NULL, hal), "create device object");
17
18 // Servo 1: Connected to port 0, period of 19.5ms, pulse width of 1 to 2ms
19 // and operating angle -100 to 100°
20 check(tf_servo_v2_set_degree(&s, 0, -10000, 10000), "call set_degree");
21 check(tf_servo_v2_set_pulse_width(&s, 0, 1000, 2000), "call set_pulse_width");
22 check(tf_servo_v2_set_period(&s, 0, 19500), "call set_period");
23 check(tf_servo_v2_set_motion_configuration(&s, 0, 500000, 1000,
24 1000), "call set_motion_configuration"); // Full velocity with slow ac-/deceleration
25
26
27 // Servo 2: Connected to port 5, period of 20ms, pulse width of 0.95 to 1.95ms
28 // and operating angle -90 to 90°
29 check(tf_servo_v2_set_degree(&s, 5, -9000, 9000), "call set_degree");
30 check(tf_servo_v2_set_pulse_width(&s, 5, 950, 1950), "call set_pulse_width");
31 check(tf_servo_v2_set_period(&s, 5, 20000), "call set_period");
32 check(tf_servo_v2_set_motion_configuration(&s, 5, 500000, 500000,
33 500000), "call set_motion_configuration"); // Full velocity with full ac-/deceleration
34
35 check(tf_servo_v2_set_position(&s, 0,
36 10000), "call set_position"); // Set to most right position
37 check(tf_servo_v2_set_enable(&s, 0, true), "call set_enable");
38
39 check(tf_servo_v2_set_position(&s, 5,
40 -9000), "call set_position"); // Set to most left position
41 check(tf_servo_v2_set_enable(&s, 5, true), "call set_enable");
42}
43
44void example_loop(TF_HAL *hal) {
45 // Poll for callbacks
46 tf_hal_callback_tick(hal, 0);
47}
1// This example is not self-contained.
2// It requires usage of the example driver specific to your platform.
3// See the HAL documentation.
4
5#include "src/bindings/hal_common.h"
6#include "src/bindings/bricklet_servo_v2.h"
7
8void check(int rc, const char *msg);
9void example_setup(TF_HAL *hal);
10void example_loop(TF_HAL *hal);
11
12// Use position reached callback to swing back and forth
13static void position_reached_handler(TF_ServoV2 *device, uint16_t servo_channel,
14 int16_t position, void *user_data) {
15 (void)device; (void)user_data; // avoid unused parameter warning
16
17 if (position == 9000) {
18 tf_hal_printf("Position: 90°, going to -90°\n");
19 tf_servo_v2_set_position(device, servo_channel, -9000);
20 } else if (position == -9000) {
21 tf_hal_printf("Position: -90°, going to 90°\n");
22 tf_servo_v2_set_position(device, servo_channel, 9000);
23 } else {
24 tf_hal_printf("Error\n"); // Can only happen if another program sets position
25 }
26}
27
28static TF_ServoV2 s;
29
30void example_setup(TF_HAL *hal) {
31 // Create device object
32 check(tf_servo_v2_create(&s, NULL, hal), "create device object");
33
34 // Register position reached callback to function position_reached_handler
35 tf_servo_v2_register_position_reached_callback(&s,
36 position_reached_handler,
37 NULL);
38
39 // Enable position reached callback
40 check(tf_servo_v2_set_position_reached_callback_configuration(&s, 0,
41 true), "call set_position_reached_callback_configuration");
42
43 // Set velocity to 100°/s. This has to be smaller or equal to the
44 // maximum velocity of the servo you are using, otherwise the position
45 // reached callback will be called too early
46 check(tf_servo_v2_set_motion_configuration(&s, 0, 10000, 500000,
47 500000), "call set_motion_configuration");
48 check(tf_servo_v2_set_position(&s, 0, 9000), "call set_position");
49 check(tf_servo_v2_set_enable(&s, 0, true), "call set_enable");
50}
51
52void example_loop(TF_HAL *hal) {
53 // Poll for callbacks
54 tf_hal_callback_tick(hal, 0);
55}
Most functions of the C/C++ bindings for microcontrollers return an error code
(e_code).
Possible error codes are:
TF_E\ _OK = 0
TF_E\ _TIMEOUT = -1
TF_E\ _INVALID_PARAMETER = -2
TF_E\ _NOT_SUPPORTED = -3
TF_E\ _UNKNOWN_ERROR_CODE = -4
TF_E\ _STREAM_OUT_OF_SYNC = -5
TF_E\ _INVALID_CHAR_IN_UID = -6
TF_E\ _UID_TOO_LONG = -7
TF_E\ _UID_OVERFLOW = -8
TF_E\ _TOO_MANY_DEVICES = -9
TF_E\ _DEVICE_NOT_FOUND = -10
TF_E\ _WRONG_DEVICE_TYPE = -11
TF_E\ _LOCKED = -12
TF_E\ _PORT_NOT_FOUND = -13
(as defined in errors.h) as well as the errors returned from
the hardware abstraction layer (HAL) that is used.
Use :cpp:func`tf_hal_strerror` (defined in the HAL's header file) to get an error string for an error code.
Data returned from the device, when a getter is called,
is handled via output parameters. These parameters are labeled with the
ret_ prefix. The bindings will not write to an output parameter if NULL or nullptr
is passed. This can be used to ignore outputs that you are not interested in.
None of the functions listed below are thread-safe. See the API bindings description for details.
Every function of the Servo Brick API that has a servo_channel parameter can
address a servo with the servo channel (0 to 9). If it is a setter function then
multiple servos can be addressed at once with a bitmask for the
servos, if the highest bit is set. For example: 1 will address servo 1,
(1 << 1) | (1 << 5) | (1 << 15) will address servos 1 and 5.
This allows to set configurations to several
servos with one function call. It is guaranteed that the changes will take
effect in the same PWM period for all servos you specified in the bitmask.
| Parameters: |
|
|---|---|
| Returns: |
|
Creates the device object servo_v2 with the optional unique device ID or port name
uid_or_port_name and adds it to the HAL hal:
TF_ServoV2 servo_v2;
tf_servo_v2_create(&servo_v2, NULL, &hal);
Normally uid_or_port_name can stay NULL. For more details about this
see section UID or Port Name.
| Parameters: |
|
|---|---|
| Returns: |
|
Removes the device object servo_v2 from its HAL and destroys it.
The device object cannot be used anymore afterwards.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the status information of the Servo Bricklet 2.0.
The status includes
for each channel if it is enabled or disabled,
for each channel the current position,
for each channel the current velocity,
for each channel the current usage and
the input voltage.
Please note that the position and the velocity is a snapshot of the current position and velocity of the servo in motion.
| Parameters: |
|
|---|---|
| Returns: |
|
Enables a servo channel (0 to 9). If a servo is enabled, the configured position, velocity, acceleration, etc. are applied immediately.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns true if the specified servo channel is enabled, false otherwise.
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the position in °/100 for the specified servo channel.
The default range of the position is -9000 to 9000, but it can be specified
according to your servo with tf_servo_v2_set_degree().
If you want to control a linear servo or RC brushless motor controller or
similar with the Servo Brick, you can also define lengths or speeds with
tf_servo_v2_set_degree().
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the position of the specified servo channel as set by tf_servo_v2_set_position().
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current position of the specified servo channel. This may not be the
value of tf_servo_v2_set_position() if the servo is currently approaching a
position goal.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current velocity of the specified servo channel. This may not be the
velocity specified by tf_servo_v2_set_motion_configuration(). if the servo is
currently approaching a velocity goal.
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the maximum velocity of the specified servo channel in °/100s as well as the acceleration and deceleration in °/100s²
With a velocity of 0 °/100s the position will be set immediately (no velocity).
With an acc-/deceleration of 0 °/100s² the velocity will be set immediately (no acc-/deceleration).
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the motion configuration as set by tf_servo_v2_set_motion_configuration().
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the minimum and maximum pulse width of the specified servo channel in µs.
Usually, servos are controlled with a PWM, whereby the length of the pulse controls the position of the servo. Every servo has different minimum and maximum pulse widths, these can be specified with this function.
If you have a datasheet for your servo that specifies the minimum and maximum pulse width, you should set the values accordingly. If your servo comes without any datasheet you have to find the values via trial and error.
Both values have a range from 1 to 65535 (unsigned 16-bit integer). The minimum must be smaller than the maximum.
The default values are 1000µs (1ms) and 2000µs (2ms) for minimum and maximum pulse width.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the minimum and maximum pulse width for the specified servo channel as set by
tf_servo_v2_set_pulse_width().
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the minimum and maximum degree for the specified servo channel (by default given as °/100).
This only specifies the abstract values between which the minimum and maximum
pulse width is scaled. For example: If you specify a pulse width of 1000µs
to 2000µs and a degree range of -90° to 90°, a call of tf_servo_v2_set_position()
with 0 will result in a pulse width of 1500µs
(-90° = 1000µs, 90° = 2000µs, etc.).
Possible usage:
The datasheet of your servo specifies a range of 200° with the middle position at 110°. In this case you can set the minimum to -9000 and the maximum to 11000.
You measure a range of 220° on your servo and you don't have or need a middle position. In this case you can set the minimum to 0 and the maximum to 22000.
You have a linear servo with a drive length of 20cm, In this case you could
set the minimum to 0 and the maximum to 20000. Now you can set the Position
with tf_servo_v2_set_position() with a resolution of cm/100. Also the velocity will
have a resolution of cm/100s and the acceleration will have a resolution of
cm/100s².
You don't care about units and just want the highest possible resolution. In this case you should set the minimum to -32767 and the maximum to 32767.
You have a brushless motor with a maximum speed of 10000 rpm and want to
control it with a RC brushless motor controller. In this case you can set the
minimum to 0 and the maximum to 10000. tf_servo_v2_set_position() now controls the rpm.
Both values have a possible range from -32767 to 32767 (signed 16-bit integer). The minimum must be smaller than the maximum.
The default values are -9000 and 9000 for the minimum and maximum degree.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the minimum and maximum degree for the specified servo channel as set by
tf_servo_v2_set_degree().
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the period of the specified servo channel in µs.
Usually, servos are controlled with a PWM. Different servos expect PWMs with different periods. Most servos run well with a period of about 20ms.
If your servo comes with a datasheet that specifies a period, you should set it accordingly. If you don't have a datasheet and you have no idea what the correct period is, the default value (19.5ms) will most likely work fine.
The minimum possible period is 1µs and the maximum is 1000000µs.
The default value is 19.5ms (19500µs).
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the period for the specified servo channel as set by tf_servo_v2_set_period().
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current consumption of the specified servo channel in mA.
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the averaging duration of the current measurement for the specified servo channel in ms.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the servo current configuration for the specified servo channel as set
by tf_servo_v2_set_servo_current_configuration().
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the averaging duration of the input voltage measurement for the specified servo channel in ms.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the input voltage configuration as set by tf_servo_v2_set_input_voltage_configuration().
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current consumption of all servos together in mA.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the input voltage in mV. The input voltage is given via the black power input connector on the Servo Brick.
| Parameters: |
|
|---|---|
| Returns: |
|
Sets an offset value (in mA) for each channel.
Note: On delivery the Servo Bricklet 2.0 is already calibrated.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current calibration as set by tf_servo_v2_set_current_calibration().
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
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.
| Parameters: |
|
|---|---|
| Returns: |
|
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 constants are available for this function:
For config:
TF_SERVO_V2_STATUS_LED_CONFIG_OFF = 0
TF_SERVO_V2_STATUS_LED_CONFIG_ON = 1
TF_SERVO_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
TF_SERVO_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the configuration as set by tf_servo_v2_set_status_led_config()
The following constants are available for this function:
For ret_config:
TF_SERVO_V2_STATUS_LED_CONFIG_OFF = 0
TF_SERVO_V2_STATUS_LED_CONFIG_ON = 1
TF_SERVO_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
TF_SERVO_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
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.
| Parameters: |
|
|---|---|
| Returns: |
|
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!
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
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. There is also a constant for the device identifier of this Bricklet.
| Parameters: |
|
|---|---|
| Returns: |
|
Enable/Disable Position Reached callback.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the callback configuration as set by
tf_servo_v2_set_position_reached_callback_configuration().
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the corresponding tf_servo_v2_register_*_callback function.
The user_data passed to the registration function as well as the device that triggered the callback are
passed to the registered callback handler.
Only one handler can be registered to a callback at the same time.
To deregister a callback, call the tf_servo_v2_register_*_callback function
with NULL as handler.
Note
Using callbacks for recurring events is preferred compared to using getters. Polling for a callback requires writing one byte only. See here Optimizing Performance.
Warning
Calling bindings function from inside a callback handler is not allowed. See here Thread safety.
void handler(TF_ServoV2 *servo_v2, uint16_t servo_channel, int16_t position, void *user_data)
| Callback Parameters: |
|
|---|
This callback is triggered when a position set by tf_servo_v2_set_position()
is reached. If the new position matches the current position then the
callback is not triggered, because the servo didn't move.
The parameters are the servo and the position that is reached.
You can enable this callback with tf_servo_v2_set_position_reached_callback_configuration().
Note
Since we can't get any feedback from the servo, this only works if the
velocity (see tf_servo_v2_set_motion_configuration()) is set smaller or equal to the
maximum velocity of the servo. Otherwise the servo will lag behind the
control value and the callback will be triggered too early.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled,
because those functions will always send a response. For callback configuration
functions it is enabled by default too, but can be disabled by
tf_servo_v2_set_response_expected(). For setter functions it is disabled by default
and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
TF_SERVO_V2_FUNCTION_SET_ENABLE = 2
TF_SERVO_V2_FUNCTION_SET_POSITION = 4
TF_SERVO_V2_FUNCTION_SET_MOTION_CONFIGURATION = 8
TF_SERVO_V2_FUNCTION_SET_PULSE_WIDTH = 10
TF_SERVO_V2_FUNCTION_SET_DEGREE = 12
TF_SERVO_V2_FUNCTION_SET_PERIOD = 14
TF_SERVO_V2_FUNCTION_SET_SERVO_CURRENT_CONFIGURATION = 17
TF_SERVO_V2_FUNCTION_SET_INPUT_VOLTAGE_CONFIGURATION = 19
TF_SERVO_V2_FUNCTION_SET_CURRENT_CALIBRATION = 23
TF_SERVO_V2_FUNCTION_SET_POSITION_REACHED_CALLBACK_CONFIGURATION = 25
TF_SERVO_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
TF_SERVO_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
TF_SERVO_V2_FUNCTION_RESET = 243
TF_SERVO_V2_FUNCTION_WRITE_UID = 248
| Parameters: |
|
|---|---|
| Returns: |
|
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
TF_SERVO_V2_FUNCTION_SET_ENABLE = 2
TF_SERVO_V2_FUNCTION_SET_POSITION = 4
TF_SERVO_V2_FUNCTION_SET_MOTION_CONFIGURATION = 8
TF_SERVO_V2_FUNCTION_SET_PULSE_WIDTH = 10
TF_SERVO_V2_FUNCTION_SET_DEGREE = 12
TF_SERVO_V2_FUNCTION_SET_PERIOD = 14
TF_SERVO_V2_FUNCTION_SET_SERVO_CURRENT_CONFIGURATION = 17
TF_SERVO_V2_FUNCTION_SET_INPUT_VOLTAGE_CONFIGURATION = 19
TF_SERVO_V2_FUNCTION_SET_CURRENT_CALIBRATION = 23
TF_SERVO_V2_FUNCTION_SET_POSITION_REACHED_CALLBACK_CONFIGURATION = 25
TF_SERVO_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
TF_SERVO_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
TF_SERVO_V2_FUNCTION_RESET = 243
TF_SERVO_V2_FUNCTION_WRITE_UID = 248
| Parameters: |
|
|---|---|
| Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
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.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
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 constants are available for this function:
For mode:
TF_SERVO_V2_BOOTLOADER_MODE_BOOTLOADER = 0
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE = 1
TF_SERVO_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
For ret_status:
TF_SERVO_V2_BOOTLOADER_STATUS_OK = 0
TF_SERVO_V2_BOOTLOADER_STATUS_INVALID_MODE = 1
TF_SERVO_V2_BOOTLOADER_STATUS_NO_CHANGE = 2
TF_SERVO_V2_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
TF_SERVO_V2_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
TF_SERVO_V2_BOOTLOADER_STATUS_CRC_MISMATCH = 5
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current bootloader mode, see tf_servo_v2_set_bootloader_mode().
The following constants are available for this function:
For ret_mode:
TF_SERVO_V2_BOOTLOADER_MODE_BOOTLOADER = 0
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE = 1
TF_SERVO_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
TF_SERVO_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
| Parameters: |
|
|---|---|
| Returns: |
|
Sets the firmware pointer for tf_servo_v2_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.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Writes 64 Bytes of firmware at the position as written by
tf_servo_v2_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.
| Parameters: |
|
|---|---|
| Returns: |
|
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.
| Parameters: |
|
|---|---|
| Output Parameters: |
|
| Returns: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
This constant is used to identify a Servo Bricklet 2.0.
The functions tf_servo_v2_get_identity() and tf_hal_get_device_info()
have a device_identifier output parameter to specify
the Brick's or Bricklet's type.
This constant represents the human readable name of a Servo Bricklet 2.0.