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

Duet 3 asynchronous queries

Scheduled Pinned Locked Moved
Firmware wishlist
2
4
232
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
    LindsayC
    last edited by 12 Jan 2024, 21:00

    Duet 3s have dual asynchronous movement queues in development. Would it be possible to allow through the usb serial port or telnet port, the querying of the object model in an asynchronous manner?

    Essentially be able to use the first queue to have move commands and second queue for relaying core information about the duet while the move commandsare working.

    undefined 1 Reply Last reply 13 Jan 2024, 07:52 Reply Quote 0
    • undefined
      dc42 administrators @LindsayC
      last edited by 13 Jan 2024, 07:52

      @LindsayC it's already possible to query the RRF Object Model asynchronously with respect to the commands being executed. You just need to send the queries on a different input channel from the one that is executing the commands.

      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 19 Jan 2024, 16:46 Reply Quote 0
      • undefined
        LindsayC @dc42
        last edited by LindsayC 19 Jan 2024, 16:46

        @dc42 OK thanks yes it does work, so I can send a home command through the usb serial device and query the object model through the telnet port. So the only small issue here is having to have 2 physical connections.

        undefined 1 Reply Last reply 15 Apr 2024, 17:24 Reply Quote 0
        • undefined
          LindsayC @LindsayC
          last edited by 15 Apr 2024, 17:24

          @LindsayC Just an update on what I've ended up doing. As we wanted to use the ethernet connection as our main comms, we've implemented the DuetHTTPclient and telnet connection together.

          The DuetHTTPclient has the full object model updating in the background that can be queried regularly with less time-critical stuff like reporting in the UI things like temperatures of chambers etc.

          The telnet allows more time-critical comms without the overhead of the DuetHTTPClient like needing to wait for update of the object model.

          Single cable solution with a lot of flexibility.

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