Connection lost with Octoprint on Y crash detection
Hi,
I've recently updated my printer to the latest firmware (v3.2.1) and performed a factory reset. Now, I'm having communication issues with OctoPrint. After a false positive crash Y detection, printer automatically reset. I don't really care too much if it was a false positive, or a real crash (I got plenty of false positives on V3.1.3, but the printer continued working correctly afterwards). Here are my OctoPrint logs:
Send: N301036 G1 X129.109 Y148.424 E5.0250*106
Recv: ok
Send: N301037 G1 X130.471 Y148.274 E5.0591*96
Recv: ok
Send: N301038 G1 X131.828 Y148.081 E5.0933*98
Recv: echo:enqueing "G1 Z 18.550 E 0.000 F 800.000"
Recv: echo:enqueing "CRASH_DETECTEDY"
Recv: echo:enqueing "G28 X Y"
Recv: echo:enqueing "CRASH_RECOVER"
Recv: tmc2130_home_enter(axes_mask=0x01)
Recv: echo:busy: processing
Recv: 0 step=62 mscnt= 992
Recv: tmc2130_goto_step 0 46 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x01
Recv: tmc2130_home_enter(axes_mask=0x02)
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: 0 step=50 mscnt= 800
Recv: tmc2130_goto_step 1 17 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
Recv: echo:busy: processing
Recv: ok
Send: N301039 M105*31
Recv: start
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N301040 M105*17
Printer sent 'start' while printing. External reset? Aborting job since printer lost state.
Changing monitoring state from "Printing" to "Cancelling"
Recv: echo: 3.2.1-576
Recv: echo: Last Updated: May 18 2018 14:50:19 | Author: (none, default config)
Recv: Compiled: May 18 2018
Recv: echo: Free Memory: 1471 PlannerBufferBytes: 1392
Recv: echo:Hardcoded Default Settings Loaded
Recv: adc_init
Recv: CrashDetect ENABLED!
Recv: tmc2130_init(), mode=NORMAL
Recv: tmc2130_set_wave 3 0
Recv: factor: 0.000
Recv: tmc2130_init(), mode=NORMAL
Recv: tmc2130_set_wave 3 0
Recv: factor: 0.000
Recv: PAT9125_init:1
Recv: FSensor
Recv: DISABLED
Recv:
Recv: echo:SD card ok
Recv: Error:Line Number is not Last Line Number+1, Last Line: 0
Recv: Resend: 1
Printer requested line 1 but no sufficient history is available, can't resend
Changing monitoring state from "Cancelling" to "Error: Printer requested line 1 but no sufficient history is available, can't resend"
Changing monitoring state from "Error: Printer requested line 1 but no sufficient history is available, can't resend" to "Offline (Error: Printer requested line 1 but no sufficient history is available, can't resend)"
Connection closed, closing down monitor
Closing down send loop