Cannot be 1.7.2->1.7.3, look at the changelog, nothing touched even remotely related:
Smells of a printer or MMU firmware bug, because I see no reason that should make either stop responding on receiving either [ or ] as part of an M117 (and in fact I know of at least one other plugin that also happily uses them).
it's worked 100% over the last 6 months and then failed the day after the upgrade many times. The printer is working perfectly via SD card I tested that yesterday. Today I am testing with and without simplyprint to try to eliminate as much as possible.
Okay, from what version did you upgrade to 1.7.3 please?
ok. 1.7.2 > 1.7.3
Go to Settings > Software Update > Update log. If it was a recent version you updated from, it should show up in there.
I changed my previous reply after I found it. 1.7.2 > 1.7.3
Then sorry to say this, but it can't possibly be the update. The update 1.7.2 -> 1.7.3 pinned one dependency for python 2 only (you run Python 3) and it fixed a bug in blacklist processing (so plugin subsystem related, as to what may or may not load, and the bug allowed blacklisted plugins to load, it didn't prevent something like simplyprint to load or anything like that that would explain this). That is all. Nothing even remotely connected to printer communication was touched. It could be a plugin update, it could be a firmware update, but it cannot have been the OctoPrint core update. Correlation is not causation, and being intimately familiar with the commits that went into 1.7.3 I really can't see how it could be the cause here.
Well thank you for taking time to look at my problem. When I have more info I will report back.
with simplyprint enabled
[...]
Recv: echo:busy: paused for user
[...]
Recv: mmu_get_response - begin move: T-code
Recv: MMU <= 'T0'
Recv: Unloading finished 2
Recv: echo:busy: processing
[...]
Recv: mmu_get_response - begin move: load
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
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.
[...]
Recv: LCD status changed
Recv: ok
Send: N50 M117 [SP] Printing 0%*16
Recv: Full RX Buffer
Recv: LCD status changed
Recv: ok
[...]
Send: N51 M117 [SP] Printing 0%*17
Recv: Error:Line Number is not Last Line Number+1, Last Line: 18
Recv: Resend: 19
Recv: ok
[...]
Send: N50 M117 [SP] Printing 0%*16
Recv: LCD status changed
Recv: ok
Send: N51 M117 [SP] Printing 0%*17
Recv: LCD status changed
Recv: ok
Send: N52 M109 S240*89
Recv: LCD status changed
[...]
Recv: LCD status changed
Recv: ok
Send: N53 M117 [SP] Printing 1%*18
Recv: LCD status changed
but it is not resetting the printer and the print is working ok
After this I will turn off the feature to change the display.
I turned off the simplyprint screen update and the errors have gone away
Recv: T:22.7 /0.0 B:22.6 /0.0 T0:22.7 /0.0 @:0 B@:0 P:0.0 A:30.6
Recv: T:22.8 /0.0 B:22.5 /0.0 T0:22.8 /0.0 @:0 B@:0 P:0.0 A:30.4
Changing monitoring state from "Operational" to "Starting"
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from "Starting" to "Printing"
Send: N1 M73 P0 R173*17
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 173; Change in mins: -1
Recv: SILENT MODE: Percent done: 100; print time remaining in mins: 0; Change in mins: -1
Recv: ok
Send: N2 M73 Q0 S174*21
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 173; Change in mins: -1
Recv: SILENT MODE: Percent done: 0; print time remaining in mins: 174; Change in mins: -1
Recv: ok
Send: N3 M201 X1000 Y1000 Z200 E5000*10
Recv: ok
Send: N4 M203 X200 Y200 Z12 E120*8
Recv: ok
Send: N5 M204 P1250 R1250 T1250*80
Recv: ok
Send: N6 M205 X8.00 Y8.00 Z0.40 E4.50*57
Recv: ok
Send: N7 M205 S0 T0*36
Recv: ok
Send: N8 M107*45
Recv: ok
Send: N9 M862.3 P "MK3SMMU2S"*57
Recv: ok
Send: N10 M862.1 P0.4*91
Recv: ok
Send: N11 M115 U3.10.0*97
Recv: ok
Send: N12 G90*35
Recv: ok
Send: N13 M83*42
Recv: ok
Send: N14 M104 S240*86
Recv: ok
Send: N15 M140 S85*108
Recv: ok
Send: Tx
Send: N16 M190 S85*98
Recv: T:22.7 /240.0 B:21.9 /85.0 T0:22.7 /240.0 @:127 B@:127 P:0.0 A:30.6
Recv: echo:busy: paused for user
Recv: T:23.0 /240.0 B:22.1 /85.0 T0:23.0 /240.0 @:127 B@:127 P:0.0 A:30.2
Recv: echo:busy: paused for user
Recv: T:25.1 /240.0 B:22.3 /85.0 T0:25.1 /240.0 @:127 B@:127 P:0.0 A:30.7
Recv: echo:busy: paused for user
Recv: T:29.6 /240.0 B:22.6 /85.0 T0:29.6 /240.0 @:127 B@:127 P:0.0 A:30.5
Recv: mmu_get_response - begin move: T-code
Recv: MMU <= 'T0'
Recv: echo:busy: processing
Recv: Unloading finished 2
Recv: T:34.4 /240.0 B:22.0 /85.0 T0:34.4 /240.0 @:127 B@:127 P:0.0 A:30.7
Recv: echo:busy: processing
Recv: mmu_get_response - begin move: load
Recv: T:41.1 /240.0 B:23.8 /85.0 T0:41.1 /240.0 @:127 B@:127 P:0.0 A:31.0
Recv: LCD status changed
Recv: ok
Recv: LCD status changed
Send: N18 G28 W*93
Recv: T:239.8 /240.0 B:84.9 /85.0 T0:239.8 /240.0 @:35 B@:77 P:0.0 A:33.8
Recv: T:239.5 E:0 W:1
Recv: T:240.1 E:0 W:0
Recv: T:240.5 /240.0 B:85.1 /85.0 T0:240.5 /240.0 @:24 B@:62 P:0.0 A:34.0
Recv: LCD status changed
Recv: ok
Send: N19 G80*41
Recv: tmc2130_home_enter(axes_mask=0x01)
Recv: 0 step=30 mscnt= 480
Recv: tmc2130_goto_step 0 29 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x01
Recv: tmc2130_home_enter(axes_mask=0x02)
Recv: T:239.4 /240.0 B:85.3 /85.0 T0:239.4 /240.0 @:43 B@:42 P:0.0 A:34.3
Recv: echo:busy: processing
Recv: T:240.1 /240.0 B:85.4 /85.0 T0:240.1 /240.0 @:31 B@:31 P:0.0 A:34.2
Recv: echo:busy: processing
Recv: T:240.2 /240.0 B:85.6 /85.0 T0:240.2 /240.0 @:29 B@:18 P:0.0 A:34.1
Recv: 0 step=50 mscnt= 801
Recv: tmc2130_goto_step 1 49 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
Recv: echo:busy: processing
Recv: T:239.7 /240.0 B:85.6 /85.0 T0:239.7 /240.0 @:38 B@:34 P:0.0 A:33.7
Recv: echo:busy: processing
Recv: T:240.0 /240.0 B:85.7 /85.0 T0:240.0 /240.0 @:32 B@:34 P:0.0 A:34.1
Recv: echo:busy: processing
Recv: ok
Send: N20 G1 Y-3.0 F1000.0*26
Recv: T:240.0 /240.0 B:85.7 /85.0 T0:240.0 /240.0 @:32 B@:29 P:0.0 A:33.9
Recv: echo:busy: processing
Recv: T:239.8 /240.0 B:85.7 /85.0 T0:239.8 /240.0 @:35 B@:48 P:0.0 A:34.1
Recv: echo:busy: processing
Recv: T:239.8 /240.0 B:85.7 /85.0 T0:239.8 /240.0 @:36 B@:41 P:0.0 A:34.1
Recv: echo:busy: processing
Recv: T:239.8 /240.0 B:85.6 /85.0 T0:239.8 /240.0 @:36 B@:68 P:0.0 A:33.8
Recv: echo:busy: processing
Recv: T:240.2 /240.0 B:85.6 /85.0 T0:240.2 /240.0 @:30 B@:63 P:0.0 A:34.0
So far with the simplyprint screen updates turned off the printer is behaving and the terminal is not showing anything strange. I think I still have serial logging turned on so must remember to turn off.
M117 when used with Marlin software on an Ender 3 pro has a line length of 85 characters total. My use is the Cura extension Gcode Filename format which gets passed to the Post Processing Plugin Display Filename & Layer on LCD. I use "grep '.{85}' *.gcode" in my gcode folder each time I process new stl's If any are found rename and process again. Naled it by accident when layes thru 99 worked but 100 stopped the printer. Line length out of bounds & no caught is an all to common problem.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.