@chrishamm

Ok - so it happend while I was using the filament-error to calibrate the E-Steps and non-linear extrusion. I set the error margin almost to zero +-0.5% and so there are a lot of events generated.

The following macro can trigger the bug
Content of 0:/macros/test-event-system.g

if !exists(global.ignoreMFMevents) global ignoreMFMevents = true else set global.ignoreMFMevents = true while iterations < 1000 M957 E"filament-error" D0 P4 S"tooLittleMovement - The movement is below the minimum set in the R value of M591"

Contnet of 0:/sys/filament-error.g

if exists(global.ignoreMFMevents) && global.ignoreMFMevents == true M99

Have at least one DWC session open.
Call the macro 0:/macros/test-event-system.g

Result in journalctl

Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Starting macro file filament-error.g on channel Autopause Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] M957: a similar event is already queued Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Received file abort request on channel Autopause for the last file Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Aborted macro file filament-error.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Starting macro file filament-error.g on channel Autopause Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] M957: a similar event is already queued Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Received file abort request on channel Autopause for the last file Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Aborted macro file filament-error.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Starting macro file filament-error.g on channel Autopause Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] Resending packet #1 (request GetObjectModel) Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [fatal] Abnormal program termination Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [fatal] Update task faulted Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: System.Text.Json.JsonReaderException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. LineNumber: 0 | BytePositionInLine: 0. Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes) Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at System.Text.Json.Utf8JsonReader.Read() Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at DuetControlServer.Model.Updater.UpdateModel(Int32 offset, Boolean last) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 150 Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at DuetControlServer.Model.Updater.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 296 Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] Resending packet #0 (request GetObjectModel) Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] M957: a similar event is already queued Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] Failed to find query for object model response Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Received file abort request on channel Autopause for the last file Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Aborted macro file filament-error.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] HTTP: Aborting orphaned macro file 0:/macros/test-event-system.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Aborted macro file 0:/macros/test-event-system.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] HTTP: ==> Cancelling unfinished starting code: M98 P"0:/macros/test-event-system.g" Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [warn] Daemon: Aborting orphaned macro file daemon.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Aborted macro file daemon.g Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Event logging stopped Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [fatal] Update task faulted Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: System.Text.Json.JsonReaderException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. LineNumber: 0 | BytePositionInLine: 0. Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes) Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at System.Text.Json.Utf8JsonReader.Read() Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at DuetControlServer.Model.Updater.UpdateModel(Int32 offset, Boolean last) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 150 Feb 20 09:33:57 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: at DuetControlServer.Model.Updater.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 296 Feb 20 09:33:58 Meltingplot-MBL-480-vaswsq DuetControlServer[405]: [info] Application has shut down Feb 20 09:33:58 Meltingplot-MBL-480-vaswsq systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE -- Subject: Unit process exited

EDIT: at the second attempt I was not able to reproduce it! Maybe it is related to [warn] Resending packet #1 (request GetObjectModel) as in the first try I saw many of these warnings and after a reboot, these warmings are gone and I can't reproduce the update thread bug.

@dc42 Will update and report back if the error repeats

@davidjryan I just implemented a change in DSF to avoid that re-racking problem.

@aetherialdesign please try this unofficial firmware build. Scratch that, there appears to be a second issue.

@bsilver8192 Please look at
https://forum.duet3d.com/topic/36364/feature-adaptive-feedforward-temperature-setpoint/21
You need to loosen heater check even more.

@droftarts said in 3.6.0-beta.2 Pressure Advance Issue?:

@T3P3Tony Maybe this one is related? https://forum.duet3d.com/topic/37435/extrusion-gaps-after-arcs

Checked the attached Gcode, all G1 moves not G2/3 arcs.

Ian

(OP from the linked topic) these still sound related: so far I've only tested with 3.5.2, and the problem in this topic was reported to also happen with G1 in 3.5.4. The big difference I see is that I have PA turned off completely though. I'm planning to test with 3.6.0-beta4 tomorrow, and I'll report back in my topic about how it goes.

Also hearing about issues with holes is helpful, I haven't tried printing any parts with large holes so I'll add that to my list now.

@davidjryan thanks, we are looking into this and the other report here:
https://forum.duet3d.com/topic/36866/multiple-motion-system/47

@dc42 said in [3.6] A very minor, cosmetic, DWC UI suggestion:

@stuartofmt that's one for @chrishamm.

Sorry - at the time of posting I conflated everything 3.6.0-beta in my mind. I'll repost in the DWC forum

@T3P3Tony @chrishamm @dc42
Hi Tony,
I think the bug is gone, to be honest.
I even deleted the overflow check as Chris suggested, and with the latest changes from Chris (OutputBuffer) and David (Stack of Main Task / M122) the bug is gone. I can construct a case where there is an SPI timeout – but that is far beyond normal use and a corner case. I tested it with this Git tag: https://github.com/Duet3D/RepRapFirmware/commit/4974c4cf3a4d1f1cd1fb1c28599e44ee2c412caa

I think the bug was related to the bug in OutputBuffer and filled the stack over time, causing the SPI timeout error from the RRF side – not WIFI. Now that the behaviour has been improved, I can no longer realistically reproduce the bug.

Although a M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 M122 can still sometimes trigger the timeout. If in doubt, do it twice and the printer is gone, but as I said this is unrealistic.

0 dc42 committed to Duet3D/RepRapFirmware Increased main task stack size

@MaxGyver thanks for reporting this. I confirm it is a bug, which will be fixed in the next build. Meanwhile I suggest you use a G92 Zxx command to adjust the height.

@SanderLPFRG to help tie this down do you know if this worked in 3.5.x firmware?

@Leonard03 please can you run 3.6beta4 and please get the full debug message from the web interface if you get another code7 error.

@Argo Please can you see if you still get these in beta4. dc42 has added extra debug info the beta 4 for code 7 halts.

@chrishamm @T3P3Tony
I just tested with 3.6.0-beta.4. I can no longer trigger the behavior.

Looks good!

@timschneider yes please