Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Error Pop-up doesn't obey Screensaver or turn off screensaver

    Scheduled Pinned Locked Moved Unsolved
    PanelDue
    3
    11
    542
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • PDBealundefined
      PDBeal
      last edited by

      So I've noticed when a print finishes and I don't go back to the machine, the PanelDue is running the screensaver (which I happen to like). On my end g-code I have the filament retracted out of the nozzle (it's a revo nozzle), so I can pull back on the manual release and pull the filament out. When I do this, my filament sensor presents the error pop-up for no filament on extruder 0. This pop-up doesn't turn-off the screensaver and just shows up on top of it and you can clearly see the "Touch to Wake" move around behind it.

      Can this pop-up either show up under the screensaver or have it disable the screensaver until such a time the screensaver kicks in again? Or at least have it work better within the screensaver?

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Perhaps as a workaround you could disable the filament monitor as part of your end gcode? And re-enable it at startup and/or before a print.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • mfs12undefined
          mfs12
          last edited by

          @PDBeal Actually message with confirmation should quit the screensaver. It should end the pop-up. Please share the M291 gcode you are using for you popup.

          Which versions are you using? Does this problem persists with PanelDueFirmware-3.4.1-pre3?

          Visit me on github at https://github.com/mfs12/

          PDBealundefined 2 Replies Last reply Reply Quote 0
          • mfs12undefined mfs12 marked this topic as a question
          • PDBealundefined
            PDBeal @mfs12
            last edited by

            @mfs12 I'm not using any M291 for the pop-up. In my case its the Out of Filament pop-up when I pull the remaining filament out of the extruder motor. Since I use the Revo, I extract 18mm while hot. At that point I can pull the remaining out at any time with the manual lever.

            This is on my machine with the 3.4.1-pre2 firmware currently. I'll try the pre3 and see if its any different.

            1 Reply Last reply Reply Quote 0
            • PDBealundefined
              PDBeal @mfs12
              last edited by

              @mfs12 the same issue still exists. Attached is a screenshot of the issue. It may make more sense if you can see what happens.

              1FE32232-66FE-47BB-8CE8-42583B36AFE7.jpeg

              You can see the screensave is still working in the background, but the popup for out of filament shows up on top and doesn’t stop the screensaver. If I click the red X in the corner, it stops the screensaver. I would have expected this particular popup to either popup behind the screensaver or cause the screensaver to be interrupted so the 120 timer starts again which would then cover this pop up if it wasn’t closed.

              This happens every time I take the filament out after a print is done. Since my end code extracts the filament beyond the Revo nozzle, I don’t have to heat anything to pull filament.

              1 Reply Last reply Reply Quote 0
              • mfs12undefined
                mfs12
                last edited by mfs12

                can you share the log from your printer which leads to this bug?

                BTW finally this is also a m291 popup message triggered from RRF.

                Visit me on github at https://github.com/mfs12/

                PDBealundefined 1 Reply Last reply Reply Quote 0
                • PDBealundefined
                  PDBeal @mfs12
                  last edited by

                  @mfs12 What do you mean log?

                  When I connect to the printer via HTML, the console is empty apart from the Connected message. The Diagnostics has some information, but since the printer is sitting idle when the screensaver is active and still idle when I pull the filament would it even have any useful information? And I don't see any other "log" file being written anywhere.

                  By the way, I may not have mentioned it until now, but the printer can be sitting idle with screensaver for several hours after the print is finished before I manually pull out the filament which triggers this message. I don't like to leave filament sitting on the machine overnight if its not printing.

                  1 Reply Last reply Reply Quote 0
                  • mfs12undefined
                    mfs12
                    last edited by

                    @Phaedrux could you reproduce this problem?

                    Visit me on github at https://github.com/mfs12/

                    1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator
                      last edited by

                      Well from what I can see the event popup for the filament error is popping up overtop of the screen saver.

                      @pdbeal said in Error Pop-up doesn't obey Screensaver or turn off screensaver:

                      I would have expected this particular popup to either popup behind the screensaver or cause the screensaver to be interrupted so the 120 timer starts again which would then cover this pop up if it wasn’t closed.

                      I'm not sure that would be preferable behaviour. If an error has occurred it's being displayed rather than hidden. I think some people would prefer the error shown until they notice it. So it's hard to say that changing the current behaviour would be universally preferable.

                      @mfs12 I guess the question is whether other similar error messages exhibit the same behaviour.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • mfs12undefined
                        mfs12
                        last edited by

                        @Phaedrux i was playing around with different m291 message triggered from DWC while PD having the screensaver active. I couldn't reproduce this behavior. So it seems to be something specific about the message.

                        Probably a github issue should be opened if there's interest in having this fixed for the next release.

                        Visit me on github at https://github.com/mfs12/

                        PDBealundefined 1 Reply Last reply Reply Quote 1
                        • PDBealundefined
                          PDBeal @mfs12
                          last edited by

                          @mfs12 @Phaedrux One thing to note, this Out of Filament message appears to have no way to acknowledge it, either from the DWC or from the PanelDue. So from that perspective, something around this message should probably be addressed, It doesn't re-occur on the PanelDue unless I pull out the filament again, but it always displays when connecting to the DWC.

                          One side note which probably isn't important, but the Duet 0.8.5 with Firmware 1.26.1 and PanelDue with firmware 1.25; this pop-up does not exist or is not triggered. In all honesty, its almost better that this message isn't presented as it's not a constant nag as it is with the newer firmware. The out of filament still works as expected and pauses properly, but without the contact nagging pop-up or DWC message.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA