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

    Multiple commands on single line bug RF3.5b3

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    3
    187
    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.
    • OwenDundefined
      OwenD
      last edited by

      There seems to be a bug in RRF3.5b3 (But it could also affect earlier versions) whereby multiple commands on a single line either aren't all executed, or they aren't executed in the correct manner.
      This came to light first with M703 not being executed when filaments are selected from DWC as in this thread

      However I note that for example
      M291 S3 P"test" G4 S1 G1 X50 Y50 M400 G1 X10 Y10 F1800 M118 S"Done"
      The M291 does not block.

      G28 M400 G1 X50 Y50 M400 G1 X10 Y10 F1800 M118 S"Done"
      Only the G28 is executed

      G1 X50 Y50 M400 G1 X10 Y10 F1800 M118 S"Done"
      Works correctly

      M701 S"test" M400 M703 M400 M118 S"Done"
      Only the M701 is executed

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

        @OwenD yes this is a known issue. In fact most 3D printer firmwares don't accept multiple commands on a line. The NIST standard for CNC GCode does allow them in certain circumstances, which is why RRF generally does allow them.

        The general rule for RRF is this:

        1. A T command must be on a line by itself.
        2. A G or M command that does not cause the state to be stacked can be followed by another command. The commands that cause the state to be stacked are commands that cause a macro file to be executed (e.g. G28, G29, G32, M24, M98, M226, M600, M701) and M291.

        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

        OwenDundefined 1 Reply Last reply Reply Quote 2
        • OwenDundefined
          OwenD @dc42
          last edited by

          @dc42
          Makes sense apart from DWC has always passed multiple M7xx commands for filament changes
          Putting M703 in Tnpost.g doesn't really work as many time's your changing filament but not tools.
          It could affect power loss scripts as well I guess?

          1 Reply Last reply Reply Quote 1
          • jay_s_ukundefined jay_s_uk referenced this topic
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA