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

Object Model value never seems to change

Scheduled Pinned Locked Moved Solved
General Discussion
3
10
206
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
    fcwilt
    last edited by 23 Mar 2025, 10:09

    Hi,

    Using firmware 3.5.4 on a 6HC.

    There are values in the object model like this:

    tools[0].state
    tools[1].state
    tools[2].state
    tools[3].state

    On my printer they all show "standby" as the value and I have never seen them change.

    What does this value mean and when should it change?

    Thanks.

    Frederick

    Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

    undefined undefined 2 Replies Last reply 24 Mar 2025, 05:47 Reply Quote 0
    • undefined
      T3P3Tony administrators @fcwilt
      last edited by T3P3Tony 24 Mar 2025, 05:47

      @fcwilt see the documentation here:
      https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation-Beta-&-RC#toolsstate

      Should change when a tool cycles between active standby and off.

      www.duet3d.com

      undefined 1 Reply Last reply 24 Mar 2025, 08:56 Reply Quote 0
      • undefined
        fcwilt @T3P3Tony
        last edited by 24 Mar 2025, 08:56

        @T3P3Tony said in Object Model value never seems to change:

        @fcwilt see the documentation here:
        https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation-Beta-&-RC#toolsstate

        Should change when a tool cycles between active adrandby and off.

        Thanks I will check the documentation.

        But so far I have not be able to do anything that makes that value change.

        Frederick

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators @fcwilt
          last edited by 24 Mar 2025, 09:02

          @fcwilt it's working for me using 3.6.0-rc.1 on a 6HC in standalone mode. All tool states are initially "off". If I select a tool its state goes to "active", if I select another tool then that one goes "active" and the one that was selected before goes "standby". Reselecting the first tool swaps their active/standby states.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          undefined 1 Reply Last reply 24 Mar 2025, 09:45 Reply Quote 0
          • undefined
            fcwilt @dc42
            last edited by 24 Mar 2025, 09:45

            @dc42 said in Object Model value never seems to change:

            @fcwilt it's working for me using 3.6.0-rc.1 on a 6HC in standalone mode. All tool states are initially "off". If I select a tool its state goes to "active", if I select another tool then that one goes "active" and the one that was selected before goes "standby". Reselecting the first tool swaps their active/standby states.

            On my 3.5.4 machine I see that happening in the DWC but I haven't seen the value in the object model change.

            I will keep testing.

            Thanks.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            undefined 1 Reply Last reply 24 Mar 2025, 14:17 Reply Quote 0
            • undefined
              dc42 administrators @fcwilt
              last edited by dc42 24 Mar 2025, 14:17

              @fcwilt it's conceivable that it's a bug in 3.5.x that was fixed in 3.6 but it's not listed at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#bug-fixes-since-354. When the states are shown incorrectly in the DWC Object Model Browser, if you then click the Refresh button or (if running in standalone mode) reload the browser tab, do they change to the correct values?

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              undefined 2 Replies Last reply 24 Mar 2025, 14:19 Reply Quote 0
              • undefined
                fcwilt @dc42
                last edited by 24 Mar 2025, 14:19

                @dc42 said in Object Model value never seems to change:

                @fcwilt it's conceivable that it's a bug in 3.5.x that was fixed in 3.6 but it's not listed at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#bug-fixes-since-354. When the states are shown incorrectly in the DWC Object Model Browser, if you then click the Refresh button or (if running in standalone mode) reload the browser tab, do they change to the correct values?

                Give me a few minutes and I will take a break to test it again.

                Frederick

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                1 Reply Last reply Reply Quote 0
                • undefined
                  fcwilt @dc42
                  last edited by 24 Mar 2025, 14:34

                  @dc42 said in Object Model value never seems to change:

                  @fcwilt it's conceivable that it's a bug in 3.5.x that was fixed in 3.6 but it's not listed at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#bug-fixes-since-354. When the states are shown incorrectly in the DWC Object Model Browser, if you then click the Refresh button or (if running in standalone mode) reload the browser tab, do they change to the correct values?

                  OK I've figured it out.

                  I was cycling the heaters from off > active > standby BUT I was looking at the tool settings in the object model.

                  When I changed which tool was active then the value in the object model was correct.

                  I've learned something new.

                  Thanks.

                  Frederick

                  Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                  undefined 1 Reply Last reply 24 Mar 2025, 15:13 Reply Quote 0
                  • undefined dc42 marked this topic as a question 24 Mar 2025, 15:11
                  • undefined dc42 has marked this topic as solved 24 Mar 2025, 15:11
                  • undefined
                    dc42 administrators @fcwilt
                    last edited by 24 Mar 2025, 15:13

                    @fcwilt object model field heat.heaters[N].state should change when you cycle the heaters in that way.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    undefined 1 Reply Last reply 24 Mar 2025, 16:31 Reply Quote 0
                    • undefined
                      fcwilt @dc42
                      last edited by 24 Mar 2025, 16:31

                      @dc42 said in Object Model value never seems to change:

                      @fcwilt object model field heat.heaters[N].state should change when you cycle the heaters in that way.

                      Yes I did locate that.

                      I was thinking (wrongly so) that if the tool heater was on standby the tool itself would have to be on standby.

                      It appears that the state of the tool being active/standby in my mind is more like selected/not selected

                      Thanks for the help in understanding things.

                      Frederick

                      Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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