This is the description of the Modbus protocol for the Silent Stepper Brick. General information and technical specifications for the Silent Stepper Brick are summarized in its hardware description.
A general description of the Modbus protocol structure can be found here.
BrickSilentStepper.
set_max_velocity
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the maximum velocity of the stepper motor.
This function does not start the motor, it merely sets the maximum
velocity the stepper motor is accelerated to. To get the motor running use
either set_target_position
, set_steps
, drive_forward
or
drive_backward
.
BrickSilentStepper.
get_max_velocity
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the velocity as set by set_max_velocity
.
BrickSilentStepper.
get_current_velocity
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current velocity of the stepper motor.
BrickSilentStepper.
set_speed_ramping
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the acceleration and deacceleration of the stepper motor. An acceleration of 1000 means, that every second the velocity is increased by 1000 steps/s.
For example: If the current velocity is 0 and you want to accelerate to a velocity of 8000 steps/s in 10 seconds, you should set an acceleration of 800 steps/s².
An acceleration/deacceleration of 0 means instantaneous acceleration/deacceleration (not recommended)
BrickSilentStepper.
get_speed_ramping
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the acceleration and deacceleration as set by
set_speed_ramping
.
BrickSilentStepper.
full_brake
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 stop
if you just want to stop the motor.
BrickSilentStepper.
set_steps
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the number of steps the stepper motor should run. Positive values
will drive the motor forward and negative values backward.
The velocity, acceleration and deacceleration as set by
set_max_velocity
and set_speed_ramping
will be used.
BrickSilentStepper.
get_steps
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the last steps as set by set_steps
.
BrickSilentStepper.
get_remaining_steps
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the remaining steps of the last call of set_steps
.
For example, if set_steps
is called with 2000 and
get_remaining_steps
is called after the motor has run for 500 steps,
it will return 1500.
BrickSilentStepper.
drive_forward
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Drives the stepper motor forward until drive_backward
or
stop
is called. The velocity, acceleration and deacceleration as
set by set_max_velocity
and set_speed_ramping
will be used.
BrickSilentStepper.
drive_backward
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Drives the stepper motor backward until drive_forward
or
stop
is triggered. The velocity, acceleration and deacceleration as
set by set_max_velocity
and set_speed_ramping
will be used.
BrickSilentStepper.
stop
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Stops the stepper motor with the deacceleration as set by
set_speed_ramping
.
BrickSilentStepper.
set_motor_current
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the current with which the motor will be driven.
Warning
Do not set this value above the specifications of your stepper motor. Otherwise it may damage your motor.
BrickSilentStepper.
get_motor_current
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current as set by set_motor_current
.
BrickSilentStepper.
enable
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Enables the driver chip. The driver parameters can be configured (maximum velocity, acceleration, etc) before it is enabled.
BrickSilentStepper.
disable
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Disables the driver chip. The configurations are kept (maximum velocity, acceleration, etc) but the motor is not driven until it is enabled again.
Warning
Disabling the driver chip while the motor is still turning can damage the
driver chip. The motor should be stopped calling stop
function
before disabling the motor power. The stop
function will not
wait until the motor is actually stopped. You have to explicitly wait for the
appropriate time after calling the stop
function before calling
the disable
function.
BrickSilentStepper.
is_enabled
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns true if the driver chip is enabled, false otherwise.
BrickSilentStepper.
set_basic_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the basic configuration parameters for the different modes (Stealth, Coolstep, Classic).
set_motor_current
).set_motor_current
).If you want to use all three thresholds make sure that Stealth Threshold < Coolstep Threshold < Classic Threshold.
BrickSilentStepper.
get_basic_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_basic_configuration
.
BrickSilentStepper.
set_current_position
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the current steps of the internal step counter. This can be used to set the current position to 0 when some kind of starting position is reached (e.g. when a CNC machine reaches a corner).
BrickSilentStepper.
get_current_position
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current position of the stepper motor in steps. On startup
the position is 0. The steps are counted with all possible driving
functions (set_target_position
, set_steps
, drive_forward
or
drive_backward
). It also is possible to reset the steps to 0 or
set them to any other desired value with set_current_position
.
BrickSilentStepper.
set_target_position
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the target position of the stepper motor in steps. For example,
if the current position of the motor is 500 and set_target_position
is
called with 1000, the stepper motor will drive 500 steps forward. It will
use the velocity, acceleration and deacceleration as set by
set_max_velocity
and set_speed_ramping
.
A call of set_target_position
with the parameter x is equivalent to
a call of set_steps
with the parameter
(x - get_current_position
).
BrickSilentStepper.
get_target_position
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the last target position as set by set_target_position
.
BrickSilentStepper.
set_step_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the step resolution from full-step up to 1/256-step.
If interpolation is turned on, the Silent Stepper Brick will always interpolate your step inputs as 1/256-step. If you use full-step mode with interpolation, each step will generate 256 1/256 steps.
For maximum torque use full-step without interpolation. For maximum resolution use 1/256-step. Turn interpolation on to make the Stepper driving less noisy.
If you often change the speed with high acceleration you should turn the interpolation off.
The following meanings are defined for the elements of this function:
For step_resolution:
BrickSilentStepper.
get_step_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the step mode as set by set_step_configuration
.
The following meanings are defined for the elements of this function:
For step_resolution:
BrickSilentStepper.
get_stack_input_voltage
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the stack input voltage. The stack input voltage is the voltage that is supplied via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.
BrickSilentStepper.
get_external_input_voltage
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the external input voltage. The external input voltage is given via the black power input connector on the Silent Stepper Brick.
If there is an external input voltage and a stack input voltage, the motor will be driven by the external input voltage. If there is only a stack voltage present, the motor will be driven by this voltage.
Warning
This means, if you have a high stack voltage and a low external voltage, the motor will be driven with the low external voltage. If you then remove the external connection, it will immediately be driven by the high stack voltage
BrickSilentStepper.
set_spreadcycle_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Note: If you don't know what any of this means you can very likely keep all of the values as default!
Sets the Spreadcycle configuration parameters. Spreadcycle is a chopper algorithm which actively controls the motor current flow. More information can be found in the TMC2130 datasheet on page 47 (7 spreadCycle and Classic Chopper).
Slow Decay Duration: Controls duration of off time setting of slow decay phase. 0 = driver disabled, all bridges off. Use 1 only with Comparator Blank time >= 2.
Enable Random Slow Decay: Set to false to fix chopper off time as set by Slow Decay Duration. If you set it to true, Decay Duration is randomly modulated.
Fast Decay Duration: Sets the fast decay duration. This parameters is only used if the Chopper Mode is set to Fast Decay.
Hysteresis Start Value: Sets the hysteresis start value. This parameter is only used if the Chopper Mode is set to Spread Cycle.
Hysteresis End Value: Sets the hysteresis end value. This parameter is only used if the Chopper Mode is set to Spread Cycle.
Sine Wave Offset: Sets the sine wave offset. This parameters is only used if the Chopper Mode is set to Fast Decay. 1/512 of the value becomes added to the absolute value of the sine wave.
Chopper Mode: 0 = Spread Cycle, 1 = Fast Decay.
Comparator Blank Time: Sets the blank time of the comparator. Available values are
A value of 1 or 2 is recommended for most applications.
Fast Decay Without Comparator: If set to true the current comparator usage for termination of the fast decay cycle is disabled.
The following meanings are defined for the elements of this function:
For chopper_mode:
BrickSilentStepper.
get_spreadcycle_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_basic_configuration
.
The following meanings are defined for the elements of this function:
For chopper_mode:
BrickSilentStepper.
set_stealth_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Note: If you don't know what any of this means you can very likely keep all of the values as default!
Sets the configuration relevant for Stealth mode.
set_basic_configuration
.set_basic_configuration
) is set to 0.The following meanings are defined for the elements of this function:
For freewheel_mode:
BrickSilentStepper.
get_stealth_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_stealth_configuration
.
The following meanings are defined for the elements of this function:
For freewheel_mode:
BrickSilentStepper.
set_coolstep_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Note: If you don't know what any of this means you can very likely keep all of the values as default!
Sets the configuration relevant for Coolstep.
get_driver_status
).
A lower value gives a higher sensitivity. You have to find a suitable value for your
motor by trial and error, 0 works for most motors.The following meanings are defined for the elements of this function:
For current_up_step_width:
For current_down_step_width:
For minimum_current:
For stallguard_mode:
BrickSilentStepper.
get_coolstep_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_coolstep_configuration
.
The following meanings are defined for the elements of this function:
For current_up_step_width:
For current_down_step_width:
For minimum_current:
For stallguard_mode:
BrickSilentStepper.
set_misc_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Note: If you don't know what any of this means you can very likely keep all of the values as default!
Sets miscellaneous configuration parameters.
BrickSilentStepper.
get_misc_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_misc_configuration
.
BrickSilentStepper.
get_driver_status
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current driver status.
Motor Run Current
as set by set_basic_configuration
. Example: If a Motor Run Current
of 1000mA was set and the returned value is 15, the Actual Motor Current
is 16/32*1000mA = 500mA.set_stealth_configuration
).The following meanings are defined for the elements of this function:
For open_load:
For short_to_ground:
For over_temperature:
BrickSilentStepper.
set_time_base
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the time base of the velocity and the acceleration of the Silent Stepper Brick.
For example, if you want to make one step every 1.5 seconds, you can set the time base to 15 and the velocity to 10. Now the velocity is 10steps/15s = 1steps/1.5s.
BrickSilentStepper.
get_time_base
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the time base as set by set_time_base
.
BrickSilentStepper.
get_all_data
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the following parameters: The current velocity, the current position, the remaining steps, the stack voltage, the external voltage and the current consumption of the stepper motor.
The current consumption is calculated by multiplying the Actual Motor Current
value (see set_basic_configuration
) with the Motor Run Current
(see get_driver_status
). This is an internal calculation of the
driver, not an independent external measurement.
The current consumption calculation was broken up to firmware 2.0.1, it is fixed since firmware 2.0.2.
There is also a callback for this function, see CALLBACK_ALL_DATA
callback.
BrickSilentStepper.
set_spitfp_baudrate_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 sent/received and decreased linearly if little data is sent/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
set_spitfp_baudrate
. If the dynamic baudrate is disabled, the baudrate
as set by set_spitfp_baudrate
will be used statically.
New in version 2.0.4 (Firmware).
BrickSilentStepper.
get_spitfp_baudrate_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the baudrate config, see set_spitfp_baudrate_config
.
New in version 2.0.4 (Firmware).
BrickSilentStepper.
get_send_timeout_count
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For communication_method:
BrickSilentStepper.
set_spitfp_baudrate
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the baudrate for a specific Bricklet port.
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 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 set_spitfp_baudrate_config
).
Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.
BrickSilentStepper.
get_spitfp_baudrate
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the baudrate for a given Bricklet port, see set_spitfp_baudrate
.
BrickSilentStepper.
get_spitfp_error_count
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.
BrickSilentStepper.
enable_status_led
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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.
BrickSilentStepper.
disable_status_led
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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.
BrickSilentStepper.
is_status_led_enabled
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns true if the status LED is enabled, false otherwise.
BrickSilentStepper.
get_chip_temperature
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 an accuracy of ±15%. Practically it is only useful as an indicator for temperature changes.
BrickSilentStepper.
reset
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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!
BrickSilentStepper.
get_identity
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 is the position in the stack from '0' (bottom) to '8' (top).
The device identifier numbers can be found here.
BrickSilentStepper.
set_minimum_voltage
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the minimum voltage, below which the CALLBACK_UNDER_VOLTAGE
callback
is triggered. The minimum possible value that works with the Silent Stepper
Brick is 8V.
You can use this function to detect the discharge of a battery that is used
to drive the stepper motor. If you have a fixed power supply, you likely do
not need this functionality.
BrickSilentStepper.
get_minimum_voltage
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the minimum voltage as set by set_minimum_voltage
.
BrickSilentStepper.
set_all_data_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the period with which the CALLBACK_ALL_DATA
callback is triggered
periodically. A value of 0 turns the callback off.
BrickSilentStepper.
get_all_data_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_all_data_period
.
BrickSilentStepper.
CALLBACK_UNDER_VOLTAGE
¶Function ID: |
|
---|---|
Response: |
|
This callback is triggered when the input voltage drops below the value set by
set_minimum_voltage
. The response value is the current voltage.
BrickSilentStepper.
CALLBACK_POSITION_REACHED
¶Function ID: |
|
---|---|
Response: |
|
This callback is triggered when a position set by set_steps
or
set_target_position
is reached.
Note
Since we can't get any feedback from the stepper motor, this only works if the
acceleration (see set_speed_ramping
) 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.
BrickSilentStepper.
CALLBACK_ALL_DATA
¶Function ID: |
|
---|---|
Response: |
|
This callback is triggered periodically with the period that is set by
set_all_data_period
. The response values are: the current velocity,
the current position, the remaining steps, the stack voltage, the external
voltage and the current consumption of the stepper motor.
BrickSilentStepper.
CALLBACK_NEW_STATE
¶Function ID: |
|
---|---|
Response: |
|
This callback is triggered whenever the Silent Stepper Brick enters a new state. It returns the new state as well as the previous state.
The following meanings are defined for the elements of this function:
For state_new:
For state_previous:
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.
BrickSilentStepper.
get_protocol1_bricklet_name
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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.
BrickSilentStepper.
write_bricklet_plugin
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Writes 32 bytes of firmware to the bricklet attached at the given port. The bytes are written to the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickSilentStepper.
read_bricklet_plugin
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Reads 32 bytes of firmware from the bricklet attached at the given port. The bytes are read starting at the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.