M572 ignored by RRF
It's me again with another fresh issue from today.
My config.g has M572 D0 S0.16 since the first time I tuned the printer (V-Core 3 with Duet 3 6HC, RRF 3.2.2) and the filament I am using (DevilDesign Black PETG). The same command is in both the filament config itself and in config.g and it had been working well with no problems.
I started a print as I always do, left it alone and minded my own business. After it finished, I came to realize there was layer shifting starting with layer 4, something which had never happened before. I started printing the same model again, and I quickly realized Pressure Advance was no longer applied. This resulted in thicker extrusions where the bottom layer full infill was meeting the perimeters, raising the layer enough to snag the nozzle after a few layers and create layer shifting.
If I enter the command manually in the console while printing is in progress, it works and it is applied correctly.
Correct filament is loaded (it's the only one I've been using, there is one filament folder), config.g has no errors.
Question is: why is M572 being ignored unless I enter it manually, despite it existing both in config.g and filament configuration file?
You can check the current pressure advance settings by sending M572 with no parameters. If it reports zero, then most likely your M572 command in config.g is not being acted on. One possible reason is that it is earlier in config.g than the M584 command that creates the extruder drive.
The M572 command is at the bottom of the file. Here's the tail of the config.g:
G31 P500 X-28 Y-28 Z2.22 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed ; Pressure Advance M572 D0 S0.16 ;Taper Height M376 H20 ; PanelDue 5i for Duet 3 6CH M575 P1 S1 B57600 T0
After a full shutdown (power off) and a restart (power on), M572 is working again. However, since a few days ago (could be a week), PanelDue is stuck "Connecting". It used to work intermittently, not anymore.
I'll create a macro to check all these settings upon boot.
No, that is not the case. I have verified by running g-code files from yesterday and the same issue was still occurring.
Nothing overrides M572 for a very simple reason: my slicers are always kept free of extra G-Code with very specific exceptions (Temp Towers and PA calibration, which are in their own separate profiles).
There are several unexpected behaviors leading me to believe the Duet + SBC don't really like reboots using power-off from outlet. Could be the 24V PSU not being the best (Weho 350W). I will replace it with a Mean Well 240W and see what happens.