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

    What is the invocation rate of daemon.g?

    Scheduled Pinned Locked Moved
    General Discussion
    3
    5
    296
    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.
    • zaptaundefined
      zapta
      last edited by

      The documentation suggests 1 sec but I think I am getting 10 secs with a simple echo command.

      "once the end of file is reached it waits for a second and then executes it again"

      https://duet3d.dozuki.com/Wiki/Macros#Section_daemon_g

      942eb67d-de99-414d-a1d3-d00d04a3d06f-image.png

      22e94d98-625f-4a49-9fab-1ed5c43f949b-image.png

      fcwiltundefined dc42undefined 2 Replies Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @zapta
        last edited by fcwilt

        @zapta

        I seem to recall that it was changed from 1 sec to 10 sec to reduce the load on the processor.

        Frederick

        Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

        1 Reply Last reply Reply Quote 0
        • zaptaundefined
          zapta
          last edited by zapta

          Thanks @fcwilt.

          Edit: I want to use it to update the neopixel color based on status and temperatures but I can force an immediate response when start printing by calling the update macro also from my print start gcode.

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @zapta
            last edited by

            @zapta yes it's 10 seconds. If you need a higher rate, use a while-loop within daemon.g. That is more efficient because it avoids re-opening the daemon.g file on each iteration.

            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

            zaptaundefined 1 Reply Last reply Reply Quote 0
            • zaptaundefined
              zapta @dc42
              last edited by

              Thanks @dc42, I can live with 10 secs. This is to update the neopixel color and I can force additional updates on events such as starting a print.

              BTW, may be useful to update the documentation, including with the loop idea.

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