This is the description of the C/C++ API bindings for the Performance DC Bricklet. General information and technical specifications for the Performance DC Bricklet are summarized in its hardware description.
An installation guide for the C/C++ API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example_configuration.c)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 | #define IPCON_EXPOSE_MILLISLEEP
#include <stdio.h>
#include "ip_connection.h"
#include "bricklet_performance_dc.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Performance DC Bricklet
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
PerformanceDC pdc;
performance_dc_create(&pdc, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
return 1;
}
// Don't use device before ipcon is connected
performance_dc_set_drive_mode(&pdc, PERFORMANCE_DC_DRIVE_MODE_DRIVE_COAST);
performance_dc_set_pwm_frequency(&pdc, 10000); // Use PWM frequency of 10 kHz
performance_dc_set_motion(&pdc, 4096, 4096); // Slow ac-/deceleration (12.5 %/s)
performance_dc_set_velocity(&pdc, 32767); // Full speed forward (100 %)
performance_dc_set_enabled(&pdc, true); // Enable motor power
printf("Press key to exit\n");
getchar();
// Stop motor before disabling motor power
performance_dc_set_motion(&pdc, 4096,
16384); // Fast decceleration (50 %/s) for stopping
performance_dc_set_velocity(&pdc, 0); // Request motor stop
millisleep(2000); // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
performance_dc_set_enabled(&pdc, false); // Disable motor power
performance_dc_destroy(&pdc);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | #define IPCON_EXPOSE_MILLISLEEP
#include <stdio.h>
#include "ip_connection.h"
#include "bricklet_performance_dc.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Performance DC Bricklet
// Use velocity reached callback to swing back and forth
// between full speed forward and full speed backward
void cb_velocity_reached(int16_t velocity, void *user_data) {
PerformanceDC *pdc = (PerformanceDC *)user_data;
if(velocity == 32767) {
printf("Velocity: Full speed forward, now turning backward\n");
performance_dc_set_velocity(pdc, -32767);
} else if(velocity == -32767) {
printf("Velocity: Full speed backward, now turning forward\n");
performance_dc_set_velocity(pdc, 32767);
} else {
printf("Error\n"); // Can only happen if another program sets velocity
}
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
PerformanceDC pdc;
performance_dc_create(&pdc, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
return 1;
}
// Don't use device before ipcon is connected
// Register velocity reached callback to function cb_velocity_reached
performance_dc_register_callback(&pdc,
PERFORMANCE_DC_CALLBACK_VELOCITY_REACHED,
(void (*)(void))cb_velocity_reached,
&pdc);
// Enable velocity reached callback
performance_dc_set_velocity_reached_callback_configuration(&pdc, true);
// The acceleration has to be smaller or equal to the maximum
// acceleration of the DC motor, otherwise the velocity reached
// callback will be called too early
performance_dc_set_motion(&pdc, 4096, 4096); // Slow acceleration (12.5 %/s)
performance_dc_set_velocity(&pdc, 32767); // Full speed forward (100 %)
// Enable motor power
performance_dc_set_enabled(&pdc, true);
printf("Press key to exit\n");
getchar();
// Stop motor before disabling motor power
performance_dc_set_motion(&pdc, 4096,
16384); // Fast decceleration (50 %/s) for stopping
performance_dc_set_velocity(&pdc, 0); // Request motor stop
millisleep(2000); // Wait for motor to actually stop: velocity (100 %) / decceleration (50 %/s) = 2 s
performance_dc_set_enabled(&pdc, false); // Disable motor power
performance_dc_destroy(&pdc);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
Most functions of the C/C++ bindings return an error code (e_code
).
Data returned from the device, when a getter is called,
is handled via output parameters. These parameters are labeled with the
ret_
prefix.
Possible error codes are:
as defined in ip_connection.h
.
All functions listed below are thread-safe.
performance_dc_create
(PerformanceDC *performance_dc, const char *uid, IPConnection *ipcon)¶Parameters: |
|
---|
Creates the device object performance_dc
with the unique device ID uid
and adds
it to the IPConnection ipcon
:
PerformanceDC performance_dc;
performance_dc_create(&performance_dc, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected.
performance_dc_destroy
(PerformanceDC *performance_dc)¶Parameters: |
|
---|
Removes the device object performance_dc
from its IPConnection and destroys it.
The device object cannot be used anymore afterwards.
performance_dc_set_enabled
(PerformanceDC *performance_dc, bool enabled)¶Parameters: |
|
---|---|
Returns: |
|
Enables/Disables the driver chip. The driver parameters can be configured (velocity, acceleration, etc) before it is enabled.
performance_dc_get_enabled
(PerformanceDC *performance_dc, bool *ret_enabled)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns true if the driver chip is enabled, false otherwise.
performance_dc_set_velocity
(PerformanceDC *performance_dc, int16_t velocity)¶Parameters: |
|
---|---|
Returns: |
|
Sets the velocity of the motor. Whereas -32767 is full speed backward,
0 is stop and 32767 is full speed forward. Depending on the
acceleration (see performance_dc_set_motion()
), the motor is not immediately
brought to the velocity but smoothly accelerated.
The velocity describes the duty cycle of the PWM with which the motor is
controlled, e.g. a velocity of 3277 sets a PWM with a 10% duty cycle.
You can not only control the duty cycle of the PWM but also the frequency,
see performance_dc_set_pwm_frequency()
.
performance_dc_get_velocity
(PerformanceDC *performance_dc, int16_t *ret_velocity)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the velocity as set by performance_dc_set_velocity()
.
performance_dc_get_current_velocity
(PerformanceDC *performance_dc, int16_t *ret_velocity)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current velocity of the motor. This value is different
from performance_dc_get_velocity()
whenever the motor is currently accelerating
to a goal set by performance_dc_set_velocity()
.
performance_dc_set_motion
(PerformanceDC *performance_dc, uint16_t acceleration, uint16_t deceleration)¶Parameters: |
|
---|---|
Returns: |
|
Sets the acceleration and deceleration of the motor. It is given in velocity/s. An acceleration of 10000 means, that every second the velocity is increased by 10000 (or about 30% duty cycle).
For example: If the current velocity is 0 and you want to accelerate to a velocity of 16000 (about 50% duty cycle) in 10 seconds, you should set an acceleration of 1600.
If acceleration and deceleration is set to 0, there is no speed ramping, i.e. a new velocity is immediately given to the motor.
performance_dc_get_motion
(PerformanceDC *performance_dc, uint16_t *ret_acceleration, uint16_t *ret_deceleration)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the acceleration/deceleration as set by performance_dc_set_motion()
.
performance_dc_full_brake
(PerformanceDC *performance_dc)¶Parameters: |
|
---|---|
Returns: |
|
Executes an active full brake.
Warning
This function is for emergency purposes, where an immediate brake is necessary. Depending on the current velocity and the strength of the motor, a full brake can be quite violent.
Call performance_dc_set_velocity()
with 0 if you just want to stop the motor.
performance_dc_get_pwm_frequency
(PerformanceDC *performance_dc, uint16_t *ret_frequency)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the PWM frequency as set by performance_dc_set_pwm_frequency()
.
performance_dc_get_power_statistics
(PerformanceDC *performance_dc, uint16_t *ret_voltage, uint16_t *ret_current, int16_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns input voltage, current usage and temperature of the driver.
performance_dc_set_thermal_shutdown
(PerformanceDC *performance_dc, uint8_t temperature)¶Parameters: |
|
---|---|
Returns: |
|
Sets a temperature threshold that is used for thermal shutdown.
Additionally to this user defined threshold the driver chip will shut down at a temperature of 150°C.
If a thermal shutdown is triggered the driver is disabled and has to be
explicitly re-enabled with performance_dc_set_enabled()
.
performance_dc_get_thermal_shutdown
(PerformanceDC *performance_dc, uint8_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the thermal shutdown temperature as set by performance_dc_set_thermal_shutdown()
.
performance_dc_set_gpio_configuration
(PerformanceDC *performance_dc, uint8_t channel, uint16_t debounce, uint16_t stop_deceleration)¶Parameters: |
|
---|---|
Returns: |
|
Sets the GPIO configuration for the given channel.
You can configure a debounce and the deceleration that is used if the action is
configured as normal stop
. See performance_dc_set_gpio_action()
.
performance_dc_get_gpio_configuration
(PerformanceDC *performance_dc, uint8_t channel, uint16_t *ret_debounce, uint16_t *ret_stop_deceleration)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the GPIO configuration for a channel as set by performance_dc_set_gpio_configuration()
.
performance_dc_set_gpio_action
(PerformanceDC *performance_dc, uint8_t channel, uint32_t action)¶Parameters: |
|
---|---|
Returns: |
|
Sets the GPIO action for the given channel.
The action can be a normal stop, a full brake or a callback. Each for a rising edge or falling edge. The actions are a bitmask they can be used at the same time. You can for example trigger a full brake and a callback at the same time or for rising and falling edge.
The deceleration speed for the normal stop can be configured with
performance_dc_set_gpio_configuration()
.
The following constants are available for this function:
For action:
performance_dc_get_gpio_action
(PerformanceDC *performance_dc, uint8_t channel, uint32_t *ret_action)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the GPIO action for a channel as set by performance_dc_set_gpio_action()
.
The following constants are available for this function:
For ret_action:
performance_dc_get_gpio_state
(PerformanceDC *performance_dc, bool ret_gpio_state[2])¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the GPIO state for both channels. True if the state is high
and
false if the state is low
.
performance_dc_set_drive_mode
(PerformanceDC *performance_dc, uint8_t mode)¶Parameters: |
|
---|---|
Returns: |
|
Sets the drive mode. Possible modes are:
These modes are different kinds of motor controls.
In Drive/Brake mode, the motor is always either driving or braking. There is no freewheeling. Advantages are: A more linear correlation between PWM and velocity, more exact accelerations and the possibility to drive with slower velocities.
In Drive/Coast mode, the motor is always either driving or freewheeling. Advantages are: Less current consumption and less demands on the motor and driver chip.
The following constants are available for this function:
For mode:
performance_dc_get_drive_mode
(PerformanceDC *performance_dc, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the drive mode, as set by performance_dc_set_drive_mode()
.
The following constants are available for this function:
For ret_mode:
performance_dc_set_pwm_frequency
(PerformanceDC *performance_dc, uint16_t frequency)¶Parameters: |
|
---|---|
Returns: |
|
Sets the frequency of the PWM with which the motor is driven. Often a high frequency is less noisy and the motor runs smoother. However, with a low frequency there are less switches and therefore fewer switching losses. Also with most motors lower frequencies enable higher torque.
If you have no idea what all this means, just ignore this function and use the default frequency, it will very likely work fine.
performance_dc_set_error_led_config
(PerformanceDC *performance_dc, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Configures the error LED to be either turned off, turned on, blink in heartbeat mode or show an error.
If the LED is configured to show errors it has three different states:
The following constants are available for this function:
For config:
performance_dc_get_error_led_config
(PerformanceDC *performance_dc, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the LED configuration as set by performance_dc_set_error_led_config()
The following constants are available for this function:
For ret_config:
performance_dc_set_cw_led_config
(PerformanceDC *performance_dc, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Configures the CW LED to be either turned off, turned on, blink in heartbeat mode or if the motor turn clockwise.
The following constants are available for this function:
For config:
performance_dc_get_cw_led_config
(PerformanceDC *performance_dc, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the LED configuration as set by performance_dc_set_cw_led_config()
The following constants are available for this function:
For ret_config:
performance_dc_set_ccw_led_config
(PerformanceDC *performance_dc, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Configures the CCW LED to be either turned off, turned on, blink in heartbeat mode or if the motor turn counter-clockwise.
The following constants are available for this function:
For config:
performance_dc_get_ccw_led_config
(PerformanceDC *performance_dc, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the LED configuration as set by performance_dc_set_ccw_led_config()
The following constants are available for this function:
For ret_config:
performance_dc_set_gpio_led_config
(PerformanceDC *performance_dc, uint8_t channel, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Configures the GPIO LED to be either turned off, turned on, blink in heartbeat mode or the GPIO state.
The GPIO LED can be configured for both channels.
The following constants are available for this function:
For config:
performance_dc_get_gpio_led_config
(PerformanceDC *performance_dc, uint8_t channel, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the LED configuration as set by performance_dc_set_gpio_led_config()
The following constants are available for this function:
For ret_config:
performance_dc_get_spitfp_error_count
(PerformanceDC *performance_dc, uint32_t *ret_error_count_ack_checksum, uint32_t *ret_error_count_message_checksum, uint32_t *ret_error_count_frame, uint32_t *ret_error_count_overflow)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
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.
performance_dc_set_status_led_config
(PerformanceDC *performance_dc, uint8_t config)¶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:
performance_dc_get_status_led_config
(PerformanceDC *performance_dc, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by performance_dc_set_status_led_config()
The following constants are available for this function:
For ret_config:
performance_dc_get_chip_temperature
(PerformanceDC *performance_dc, int16_t *ret_temperature)¶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.
performance_dc_reset
(PerformanceDC *performance_dc)¶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!
performance_dc_get_identity
(PerformanceDC *performance_dc, char ret_uid[8], char ret_connected_uid[8], char *ret_position, uint8_t ret_hardware_version[3], uint8_t ret_firmware_version[3], uint16_t *ret_device_identifier)¶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.
performance_dc_register_callback
(PerformanceDC *performance_dc, int16_t callback_id, void (*function)(void), void *user_data)¶Parameters: |
|
---|
Registers the given function
with the given callback_id
. The
user_data
will be passed as the last parameter to the function
.
The available callback IDs with corresponding function signatures are listed below.
performance_dc_set_emergency_shutdown_callback_configuration
(PerformanceDC *performance_dc, bool enabled)¶Parameters: |
|
---|---|
Returns: |
|
Enable/Disable PERFORMANCE_DC_CALLBACK_EMERGENCY_SHUTDOWN
callback.
performance_dc_get_emergency_shutdown_callback_configuration
(PerformanceDC *performance_dc, bool *ret_enabled)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by
performance_dc_set_emergency_shutdown_callback_configuration()
.
performance_dc_set_velocity_reached_callback_configuration
(PerformanceDC *performance_dc, bool enabled)¶Parameters: |
|
---|---|
Returns: |
|
Enable/Disable PERFORMANCE_DC_CALLBACK_VELOCITY_REACHED
callback.
performance_dc_get_velocity_reached_callback_configuration
(PerformanceDC *performance_dc, bool *ret_enabled)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by
performance_dc_set_velocity_reached_callback_configuration()
.
performance_dc_set_current_velocity_callback_configuration
(PerformanceDC *performance_dc, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the PERFORMANCE_DC_CALLBACK_CURRENT_VELOCITY
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.
performance_dc_get_current_velocity_callback_configuration
(PerformanceDC *performance_dc, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by
performance_dc_set_current_velocity_callback_configuration()
.
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the performance_dc_register_callback()
function:
void my_callback(int value, void *user_data) { printf("Value: %d\n", value); } performance_dc_register_callback(&performance_dc, PERFORMANCE_DC_CALLBACK_EXAMPLE, (void (*)(void))my_callback, NULL);
The available constants with corresponding function signatures are described below.
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.
PERFORMANCE_DC_CALLBACK_EMERGENCY_SHUTDOWN
¶void callback(void *user_data)
Callback Parameters: |
|
---|
This callback is triggered if either the current consumption
is too high or the temperature of the driver chip is too high
(above 150°C) or the user defined thermal shutdown is triggered (see performance_dc_set_thermal_shutdown()
).
n case of a voltage below 6V (input voltage) this
callback is triggered as well.
If this callback is triggered, the driver chip gets disabled at the same time.
That means, performance_dc_set_enabled()
has to be called to drive the motor again.
PERFORMANCE_DC_CALLBACK_VELOCITY_REACHED
¶void callback(int16_t velocity, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered whenever a set velocity is reached. For example:
If a velocity of 0 is present, acceleration is set to 5000 and velocity
to 10000, the PERFORMANCE_DC_CALLBACK_VELOCITY_REACHED
callback will be triggered after about
2 seconds, when the set velocity is actually reached.
Note
Since we can't get any feedback from the DC motor, this only works if the
acceleration (see performance_dc_set_motion()
) is set smaller or equal to the
maximum acceleration of the motor. Otherwise the motor will lag behind the
control value and the callback will be triggered too early.
PERFORMANCE_DC_CALLBACK_CURRENT_VELOCITY
¶void callback(int16_t velocity, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered with the period that is set by
performance_dc_set_current_velocity_callback_configuration()
. The parameter is the current
velocity used by the motor.
The PERFORMANCE_DC_CALLBACK_CURRENT_VELOCITY
callback is only triggered after the set period
if there is a change in the velocity.
PERFORMANCE_DC_CALLBACK_GPIO_STATE
¶void callback(bool gpio_state[2], void *user_data)
Callback Parameters: |
|
---|
This callback is triggered by GPIO changes if it is activated through performance_dc_set_gpio_action()
.
New in version 2.0.1 (Plugin).
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
performance_dc_get_api_version
(PerformanceDC *performance_dc, uint8_t ret_api_version[3])¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
performance_dc_get_response_expected
(PerformanceDC *performance_dc, uint8_t function_id, bool *ret_response_expected)¶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
performance_dc_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:
performance_dc_set_response_expected
(PerformanceDC *performance_dc, uint8_t function_id, bool response_expected)¶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:
performance_dc_set_response_expected_all
(PerformanceDC *performance_dc, bool response_expected)¶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.
performance_dc_set_bootloader_mode
(PerformanceDC *performance_dc, uint8_t mode, uint8_t *ret_status)¶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:
For ret_status:
performance_dc_get_bootloader_mode
(PerformanceDC *performance_dc, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see performance_dc_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
performance_dc_set_write_firmware_pointer
(PerformanceDC *performance_dc, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for performance_dc_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.
performance_dc_write_firmware
(PerformanceDC *performance_dc, uint8_t data[64], uint8_t *ret_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
performance_dc_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.
performance_dc_write_uid
(PerformanceDC *performance_dc, uint32_t uid)¶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.
performance_dc_read_uid
(PerformanceDC *performance_dc, uint32_t *ret_uid)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
PERFORMANCE_DC_DEVICE_IDENTIFIER
¶This constant is used to identify a Performance DC Bricklet.
The performance_dc_get_identity()
function and the IPCON_CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
PERFORMANCE_DC_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Performance DC Bricklet.