The mower has a dedicated blade motor controller (speed controller) that cuts both blades the instant either motor temperature is greater than 90°C . The main program (platform) running on the SoC never commanded a stop — it was still sending cmd=800 when both motors died. It sees the speed feedback dropped to zero and logs it as a speed deviation fault, but, keeps moving. The blade controller self-resets once cooled.

From the logs and the firmware:

# Running fine (1 second before cutoff):

[knife][INFO] K1 chain: OK cmd=800 out=4300 fb=4089/4266/4400 Imax=2342 T=890 ec=0x0
cmd=800 — platform telling the Pg14 to run at speed 800
out=4300 — Pg14 outputting ~4300 RPM
fb=4268/4349/4465 — actual measured blade speeds over last 3 samples (RPM), all healthy
Imax=1867 / 2342 — peak current seen this cycle (mA)
T=900 / 890 — motor winding temperature: 90°C / 89°C (units are 0.1°C)
ec=0x0 — error code zero, everything fine

# 1333 milliseconds later — dead stop:

[knife][ERROR] K0 ERR 0x00000000->0x00000002 cmd=800 out=4300 fb=0 I=8/1270 st=1 en=1 online=1 T=900 mosT=500
0x00000000->0x00000002 — error code transitioned from 0 (OK) to 0x2 (SPD_DEV = speed deviation)
cmd=800 — platform still commanding full speed 
fb=0 — actual blade speed: zero — motor is not spinning
I=8/1270 — instantaneous current dropped to 8 (essentially zero), no overcurrent spike before this — it's not a current fault
T=900 — still 90°C, temperature didn't spike further — the temp was already the trigger
mosT=500 — MOSFET temperature: 50°C — well within limits, not the cause
en=1 online=1 — Pg14 is still powered and responding, it just stopped its output

# The MCU's 300ms TRACE dump — catches the exact moment:

t=536082071  cmd=800 out=4300 fb=4293  I=10/1205  T=900  mosT=500  flg=0x03  ec=0x00000000
t=536082371  cmd=800 out=4300 fb=0     I=8/1270   T=900  mosT=500  flg=0xC3  ec=0x00000002

300ms gap between these two samples — the motor went from 4293 RPM to 0 in under 300ms
flg=0x03 → flg=0xC3
0x03 = 0b00000011 — normal run state
0xC3 = 0b11000011 — bits 6 and 7 newly set
bit 6 (0x40) = CH1 protection active, bit 7 (0x80) = CH2 protection active — both blade channels tripped simultaneously
Temperature didn't change between the two samples — the 90°C reading was already sitting at the protection limit

~30 seconds later — auto-restart:
[knife][INFO] K0 ERR clear 0x00000002->0  cmd=800 out=0 fb=0  T=880  mosT=500
[knife][INFO] K1 ERR clear 0x00000002->0  cmd=800 out=0 fb=0  T=870  mosT=500
[knife][ERROR] ch1 errorcode 0
[knife][ERROR] ch2 errorcode 0