Resume.g activating twice With FW3.5

[Notepad]

Quick question in regards to a possible behaviour change with Resume.g with FW 3.5.0 and 3.5.1

When pausing and resuming a print, the retracted filament is reinserted as double the value causing a decent blob to form as the print restarts.
By feel, the Pause.g is activating correctly and retracting the correct amount in one action. However the Resume.g is noticeably doing two separate actions of extruding the filament causing double the amount to be extruded.

Its more than likely I just missed something in the firmware changelog notes for 3.5.x that affects the Resume.g.
What is interesting is when I delete the extrusion command in the Resume.g, no extrusion at all is completed, meaning a manual extrusion command is indeed required, however for now I have had to half the value for accurate re-extrusion when resuming.

pause.g
resume.g

[dc42]

@Notepad are you running in standalone or SBC mode?

[JayT]

@Notepad :

I noticed this too. I had set some extraction in pause.g to resume well. Now it creates blob.

IF you resume after power fail, does it resume well for you ?

[Notepad]

Apologies about the long delay in replying, Time has been slipping away quite easily over here

@dc42 Standalone mode, Behaviours seems consistent across a Duet 3 and a Duet 2.

@JayT I haven't tested the power resume behaviours as the current printers I use generally don't recover well from depowering the motors. Ill report back once I get some time in the workshop to setup a Power resume test.

[JayT]

@Notepad :

On resume, at times I see in 3.5.1, I see heater fault "temperature rising too slowly". This happens when after resuming on power failure, I set extruder temperature to 210degC. NOTE: This happens only during this resume sequence with 3.5.X. It does not happen in 3.4.6 ,...

[JayT]

This post is deleted!

[JayT]

@dc42 : Heater fault in my case was due to some interference from BLtouch wire., not due to RRF 3.5.1.. There was a change in wiring in addition to RR3.5.1 upgrade, but when I debugged further, the root cause was as stated.