Clear messages in WebUI
-
You can set a timeout for those messages in the UI settings. However, each popup should contain only the latest message, not older messages as well.
-
The timeout is set to 15s and this does work. But I keep getting 'old' messages, even in the G-Code Console, when I issue any command or get a message from the Duet:
16:07:59File bracket.gcode selected for printing
Warning: Macro file /macros/Layerscripts/PHA/0 not found.Resume-after-power-fail state saved
16:01:46File bracket.gcode selected for printing
Warning: Macro file /macros/Layerscripts/PHA/0 not found.Resume-after-power-fail state saved
16:01:45File bracket.gcode selected for printing
Warning: Macro file /macros/Layerscripts/PHA/0 not found.Resume-after-power-fail state saved
16:01:44File bracket.gcode selected for printing
Warning: Macro file /macros/Layerscripts/PHA/0 not found.Resume-after-power-fail state saved
These are the last three entries. I printed bracket.gcode yesterday. The warning is from my [c]M98[/c] in my slicers layer-change script. I just tried again, sending [c]M81[/c] through the G-Code Console and watched the Chrome-developer tools network tab.
[c]http://192.168.1.123/rr_reply[/c] gave me this in the 'Response'-Tab:File field_notes_pen_clips-PHA.gcode selected for printing
Warning: Macro file /macros/Layerscripts/PHA/0 not found.Resume-after-power-fail state saved
even though M81 should not trigger a response AFAIK
-
I just recorded a short animation of how this looks because today it got even more anoying - I always get the mesh view popup, too
-
The obvious question is: why haven't you adjusted your grid definition so that all the coordinates are reachable by the Z probe?
-
The obvious question is: why haven't you adjusted your grid definition so that all the coordinates are reachable by the Z probe?
Lazyness. I'm still trying out different mounts in differernt positions for the probe. When I find the perfect position I'll adjust the grid. But I don't think that this would cause the problem with the continous popups in the WebUI, because this also happens with other messages.
Edit: did you see the problem in the gif? Turning off the PSU results in the grid popup and the blue popup behind it containing all the messages, that are the same you can see before I click on the 'off' button.
-
I can't tell where the loop in your gif starts from, so I didn't understand what the problem was.
-
Yes, that was a bit confusing, sorry. I made a new one and wrote 'END' in the Send G-Code-box, also it shows that it happens on every command sent to the duet
-
I am experiencing a similar error.
After pausing and stopping a print the following message appears over and over again:[c]Resume-after-power-fail state saved
Printing paused
Cancelled printing file 0:/gcodes/[…].gcode, print time was […]h […]m[/c]This message does gets printed over and over again with inconsistent delays.
Whenever I send a g-code command, the message will be appended to the g-code message in the console. For example:[c]M915 X S9 F0 R1
Resume-after-power-fail state saved
Printing paused
Cancelled printing file 0:/gcodes/[…].gcode, print time was […]h […]m[/c]The only way to stop this is turning the printer off and on again.
Everything is at v1.20
-
Are you connecting with different browsers? I had a script polling the duet for the current status. After I added this line to it the problem disappeared:
curl --connect-timeout 5 -s http://<ip-of-the-printer>/rr_disconnect > /dev/null</ip-of-the-printer> -
No, there is no second browser connected.
Btw: I do not even have power fail saves enabled!
