Repository navigation
Doppelstep 0.2.0
Pre-releaseThe real-motor build drives a motor. Checked on the B-G431B-ESC1 with a 17HS19-2004S1 at
12 V and 24 V: all 20 GUI test scenarios in three runs, the hardware comparators, two minutes
of moves at 1.5 A, and the self-test against no supply, an open coil, no motor, a coil on the
wrong legs and swapped coils. The bridge and the motor are protected in layers, from
comparators into the timer break input to a self-test before the first Torque Enable. Torque
Enable is answered at once, as on an XM430. Motor control is Stepper-C 1.4.0. The tests on the
board and their results are in the test record.
Added
-
Protection of the bridge and the motor (Protection):
- Hardware trips on the B-G431B-ESC1: COMP1/2/4 watch the OPAMP inputs against DAC3
(10 A,hw-trip-current-milliamp) and COMP3 the bus divider against DAC1 (30 V,
hw-trip-vbus-mv); they drive the TIM1 break inputs, which switch the gates off within
0.5 µs without software. Reported asPOWER_STAGE_TRIP_HW_OC/_HW_OV, latched until a
reset. - The leg trip checks U, V and W in the interrupt (was W only), so the motor current is
also checked in voltage drive. - Current offset window (
current-offset-min-counts,-max-counts, 2300..2800): a broken
amplifier, shunt or bias network refuses the outputs; the bus keeps running and reports
Electrical Shock. - Torque Enable with the bus outside
vbus-min-mv..vbus-max-mvanswers Result Fail with
Input Voltage Error before anything is energised, and latches nothing. - Self-test of the bridge and the motor at the first Torque Enable
(CONFIG_SSTEP_MOTOR_SELFTEST,selftest-current-milliamp600 mA):sstep_selftest()of
Stepper-C gives each coil the test current at a slowly rising voltage, and the motor driver
adds up the three leg currents meanwhile (a broken sensor: above a quarter of the test
current for 2 ms in a row; one disturbed sample does not count). An open coil, a short, a wrong current sign, a coil
on the wrong legs, a broken current sensor or a leaking switch turns the torque off again
with Electrical Shock (SSTEP_MOTOR_FAULT_SELFTEST) and a log message that names the
cause. Torque Enable is answered at once, as on an XM430:stepper_enable()starts the
test, the slow loop ends it and runs a Goal Position written meanwhile (DynamixelSDK waits
only about 34 ms for the status packet; 2 ms on the board at 24 V). Off
in the simulated-motor build on the board (flash,CONFIG_SSTEP_SELFTEST=
SSTEP_CFG_SELFTEST), on innative_sim. i_aux(current of the shared leg) instruct power_stage_sample.
- Hardware trips on the B-G431B-ESC1: COMP1/2/4 watch the OPAMP inputs against DAC3
-
Sampling window and current slew (Stepper-C 1.3):
sample-window-nsof
the power stage node (2400 ns on the B-G431B-ESC1) keeps every leg on its low-side switch
around the samples;current-slew-ma-per-msof the motor node (30) lets the current rise
after Torque Enable. Found at the first run with the motor: Torque Enable at 1 A and 1.5 A
from 12 V tripped the undervoltage protection, because a duty cycle near 100 % corrupted the
bus voltage sample (Hardware).
power_stage_info.sample_window_ticksin the class API. -
Power stage temperature: the NTC of the B-G431B-ESC1 (TDK NTCG103JF103FT1 on PB14) is
converted in every PWM period and shown in Present Temperature (146) and in the GUI. Above
Temperature Limit (31, 80 °C) Overheating Error switches the torque off until a Reboot, as on
an XM430; an open or shorted NTC trips too.power_stage_get_temperature()in the class API,
NTC properties of the power stage node. -
Fast-loop overrun protection. When the fast loop does not finish within its PWM period,
the STM32 backend switches the outputs off in the interrupt and reports
POWER_STAGE_TRIP_OVERRUN; the motor faults (SSTEP_FAULT_HAL, Electrical Shock Error)
and the bus keeps answering. Before, an overrunning fast loop kept the interrupt busy for
good and stopped every thread, the bus included.power_stage_stats.overrunscounts them,
and the simulated-motor log prints the count. -
Hardware watchdog (IWDG, 500 ms):
main()feeds it only when the control and the
communication task have both run since the last check (app/src/supervisor.c). A fast loop
that leaves the threads no time, or a hung task, resets the MCU, and the outputs go off. The
log tells a watchdog reset; a debugger halt pauses the watchdog. -
Dead time of the power stage: the method behind the dead time, step by
step, with excerpts of schematic MB1419, a hand estimate, the ngspice sweep and its results.
tools/power/deadtime_sweep.pyrepeats the sweep, the figures and the schematic excerpts. -
output/with versioned images: every board build of the VS Code tasks copies the
merged HEX (first flashing), the signed update file for MCUboot, the signed HEX and the ELF
intooutput/(git-ignored), nameddoppelstep-<git describe>-b_g431b_esc1-…
(scripts/export_output.py). The GUI preselects the newest signed image there. -
GUI Motion tab: Goal Position and Goal Velocity are enabled only in the Operating Mode
in which they act (the device stores the other one and does nothing with it); Profile
Velocity and Acceleration show their physical value (2 = 0.458 rev/min); the Goal Velocity
frame fits in the window again. -
GUI torque button: one button in the Motion tab shows the torque state from the live
registers and toggles it: green TORQUE ON, red TORQUE OFF. It replaces Torque ON and STOP.
Fixed
- The Stepper-C options of Kconfig reached the library only by chance:
modules/stepper-c/CMakeLists.txtbuilt them inSSTEP_COMPILE_DEFINITIONS, but
sstep.cmakeapplies the variableCOMPILE_DEFINITIONS, so the library always had its
defaults. These equalled the Kconfig defaults untilCONFIG_SSTEP_SELFTESTcame. The glue
now setsCOMPILE_DEFINITIONS, whichsstep.cmakeputs on the library with its public
scope, so the driver that holds the instance sees the sameSSTEP_STATE_BYTES. - Firmware update over the bus failed (GUI). Three causes, each confirmed on the board:
smpclient was imported after the DYNAMIXEL Reboot, which took about 0.8 s on Windows, longer
than the 500 ms in which MCUboot waits for SMP; MCUboot answers the echo with rc 8 (echo not
built in), which the GUI took for no answer; and MCUboot received on USART2 at 1 Mbps
without the FIFO, so upload chunks were lost. The GUI now prepares the SMP client before
the Reboot and takes any answer as MCUboot listening, and MCUboot hasfifo-enable
(app/sysbuild/mcuboot.overlay). Three full updates in a row: 85 KiB in 5 s each. A board
with the old MCUboot needs the new merged HEX once through the ST-LINK. - Factory limits of the real motor: Current Limit 557 (1498 mA, the run current) and
Velocity Limit 1023 (234 rev/min, the largest X430 value) in place of the XM430 values
1193 (3209 mA) and 200 (45.8 rev/min), at the first start and after Factory Reset
(x430_servo_set_factory_value()). The servo node states the direct drive 1:1 of the
17HS19-2004S1. The voltage limits stay those of the XM430
(DYNAMIXEL emulation). - GUI: an answer that arrived after the poller's deadline was thrown away.
Bus.receive()
gave up before reading the port once more, so a poller thread held past its 0.1 s by the GUI
thread reported "no answer" although the answer was waiting (test_answer_waiting_after_the_deadline_is_not_lost). - GUI on Windows lost most answers of the board.
SerialLink.read()changed the port
timeout on every read; on Windows pyserial then reconfigures the port, and the ST-LINK
Virtual COM Port re-initialises its UART and loses the bytes in flight (12 of 100 answers
received). The timeout is now fixed when the port opens (tools/gui/tests/test_link.py).
Changed
-
Present Current is averaged over 8 ms and reads 0 with the torque off: on the board a single
sample moved by an ADC step (29 mA), and the sensor offset drift showed 30 to 60 mA with no
current flowing. -
Stepper-C v1.4.0 (was v1.2.0): the self-test, the bus voltage check of the enable
(SSTEP_ERR_VBUS→-ERANGE), the trip of the shared leg, the sampling window and the current
slew come from the library. 1.4.0 waits for the rotor to come to rest in every check of
the self-test: 1.3.0 reported a coil on the wrong legs once on the board, with the rotor a
full step away at 24 V.CONFIG_SSTEP_STALL=n(SSTEP_CFG_STALL, new in 1.4.0) removes the
unused stall detection: the real-motor image is 77 420 B (was 80 268 B), the
simulated-motor image 84 100 B with 3 612 B left. -
Torque Enable below
vbus-min-mvis refused at once; before, it was accepted and the
undervoltage trip latched a fault. -
Stepper-Lab pinned to
9fc2eef(wasmainduring development): its model change, one
sin/cosper RK4 step, takes the fast loop of the simulated motor from 47.5 to 37 µs
during a move. -
power_stage API: the fast-loop callback takes
uint32_t trips(POWER_STAGE_TRIP_AUX,
POWER_STAGE_TRIP_OVERRUN) in place ofbool aux_trip. Out-of-tree backends and callbacks
must be updated (Porting). -
Printf without floating point (
CONFIG_CBPRINTF_FP_SUPPORT=ninapp/prj.conf): no log
prints a float, and picolibc now links its integer printf. About 4.8 KiB less flash in every
board build; the simulated motor fits next to MCUboot again. -
Dead time set to 1200 ns (
dead-time-nsinapp/boards/b_g431b_esc1.overlay). The
real-motor build now enables the power stage on Torque Enable. The value comes from an
ngspice sweep of one leg with the gate circuit of schematic MB1419 rev C (L6387ED at 10 V,
33 Ω gate resistors, 1 Ω + 10 nF snubber): shoot-through up to 600 ns, the first clean value
at 900 ns, plus a margin of 1.3. It is not yet measured on the board: follow bring-up step 1
(Hardware and bring-up) before connecting a motor.
Known limits
- Dead time not measured on the board: 1200 ns comes from the ngspice sweep. The motor ran
at 12 V and 1.5 A without a fault or a hot switch, but confirm the value with an
oscilloscope before higher voltages (bring-up step 1). - Hardware checklist not complete: the current ripple and the vibration at rest (checks
15, 16), the NTC against a thermometer and the fast-loop time of the real-motor build are
open
(hardware checklist). - Once, in the first run of the GUI scenarios with the motor, Torque Enable was refused in the
Bus Watchdog scenario; it did not happen in the 13 runs after it, and the RTT log lost the
reason. - Lost steps are not reported (the motor has no encoder).
- The simulated-motor image with MCUboot leaves out the self-test, the hardware comparators
and the offset window, for flash (Simulated motor). - Development signing key: the images are signed with the public development key of
MCUboot; for a product, sign with your own key (Firmware update). - The X430 emulator, Stepper-Lab and sfs-stepper-power-spice have no releases yet:
west.yml
pins them to the tested commits.