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

    RRF OM Request

    Scheduled Pinned Locked Moved
    Firmware wishlist
    2
    3
    199
    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.
    • gtj0undefined
      gtj0
      last edited by

      @dc42 Can we get the following OM objects moved to the "not normally returned" category?

      • inputs
      • move.kinematics
      • seqs
      • state.restorePoints

      Just trying to cut down the length of the "normal" response.

      @chrishamm Not sure if DWC uses any of those in standalone mode.

      1 Reply Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators
        last edited by

        It's generally a bad idea to query the full object model at once because the full object model tends to exceed the maximum output buffer size (see also my comment on GitHub). This problem becomes even worse on other boards because they don't have as much RAM as the Duet 3. DWC and DSF normally query the live values from the object model (via d99fn) and update the corresponding keys from seqs only if a change is detected (via d99vn).

        Duet software engineer

        gtj0undefined 1 Reply Last reply Reply Quote 0
        • gtj0undefined
          gtj0 @chrishamm
          last edited by

          HA! That's what seqs does!! OK, this becomes much less important then. Thanks @chrishamm.

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