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

PanelDue v3.2.0 release panel not updating after STOP

Scheduled Pinned Locked Moved
PanelDue
3
7
229
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.
  • undefined
    Cheule
    last edited by 10 Nov 2020, 16:28

    Re: Soft-reset PanelDue

    The issue I'm having is that the PanelDue is not reporting correct info after an Emergency Stop. I can start heating or printing, and the panel is basically frozen as far as stats goes (showing old temps, not showing the print job). The paneldue interface still responds to touch, basically the paneldue FW isn't connected to what the Duet3 board is doing.

    In a perfect world, this sort of stuff wouldn't be happening, but in the short term is there a way to set up a macro, and perhaps get the paneldue to soft reset and pick up the board again?

    I'm running PanelDue v3 board with firmware v3.2.0
    Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 3.1.1
    Firmware: RepRapFirmware for Duet 3 MB6HC 3.1.1 (2020-05-19b2)

    undefined 1 Reply Last reply 10 Nov 2020, 16:59 Reply Quote 0
    • undefined
      jay_s_uk @Cheule
      last edited by 10 Nov 2020, 16:59

      @Cheule this is from the paneldue thread for 3.2

      This release is compatible with RepRapFirmware 3.2-beta1 or later. It will partially work with RepRapFirmware 3.1.1 but not with any older version.

      I guess this falls under the list of partially working.
      3.2.0 changed from using M408 to M409 (the object model).

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 2
      • undefined
        Phaedrux Moderator
        last edited by 10 Nov 2020, 20:12

        In the meantime it's probably best to stick to 1.24 on the Panel and wait for 3.2 stable release.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 1
        • undefined
          Cheule
          last edited by 10 Nov 2020, 21:02

          Thanks, both of you.

          1 Reply Last reply Reply Quote 0
          • undefined
            Cheule
            last edited by Cheule 11 Oct 2020, 22:28 10 Nov 2020, 22:26

            @jay_s_uk @Phaedrux I downgraded to v1.24, and everything is snappier, working better. But I was sad to see no screen saver function. I had hoped it was in v1.24 (I know it wasn't in whatever the paneldue shipped with).

            My cheapo LCD panel from Filastruder has been burning in. Upgrading to v3.2.0 immediately solved the issue.

            So now I suppose I have to choose between screen burn in or glitchy interface.

            How stable is RRF 3.2b? Is that something I should consider?

            undefined 1 Reply Last reply 10 Nov 2020, 22:38 Reply Quote 0
            • undefined
              jay_s_uk @Cheule
              last edited by 10 Nov 2020, 22:38

              @Cheule what are you currently running?
              If you're running with an SBC connected I'd say steer clear a little longer.
              If you're running a standalone board I'd say you're pretty safe to upgrade.

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              undefined 1 Reply Last reply 10 Nov 2020, 22:39 Reply Quote 1
              • undefined
                Cheule @jay_s_uk
                last edited by Cheule 11 Oct 2020, 22:40 10 Nov 2020, 22:39

                @jay_s_uk I'm running SBC on a RasPi 4B, thanks for the advice.

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