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

    what if Macros appeared in Console?

    Scheduled Pinned Locked Moved
    Duet Web Control wishlist
    4
    7
    378
    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.
    • r123undefined
      r123
      last edited by

      It seems strange to me that there's no mention of any of the activity generated by Macros in the Console. None whatsoever.

      How about if there were lines in the console like

      "13/04/2021, 20:42:43 Macro: reset probe"

      or

      "13/04/2021, 20:42:43 Macro:Dock and Wipe"

      ??

      oliofundefined o_lampeundefined 2 Replies Last reply Reply Quote 0
      • oliofundefined
        oliof @r123
        last edited by

        @r123 Macros are usually called via direct interaction, what would you use the logging information for?

        For those Macros I need output from, I use M117 or M118, which allows even more granular messaging than just that a Macro was started. So if you need a message on your particular system whenever a Macro is called, you could just start with one of these.

        <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

        1 Reply Last reply Reply Quote 0
        • o_lampeundefined
          o_lampe @r123
          last edited by o_lampe

          @r123
          what @oliof said.
          Also keep in mind, that a message sent by M117 pops up only once per session, while echo "message text" is sent everytime the macro runs

          oliofundefined 1 Reply Last reply Reply Quote 0
          • oliofundefined
            oliof @o_lampe
            last edited by

            @o_lampe in my experience, the echos only get output after the macro finishes, while the M117 is shown immediately.

            <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

            r123undefined 1 Reply Last reply Reply Quote 0
            • r123undefined
              r123 @oliof
              last edited by

              @oliof I reckon logging directly run macros is so that you can look back and see that you did (or did not) run bed levelling before that 5 hour print. For example.

              When we type Gcodes directly they land in the console, so why not macro filenames?

              Look forward to experimenting with M117, M118 - and "echo" @o_lampe ! - this weekend.

              Thanks.

              1 Reply Last reply Reply Quote 1
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Not a bad idea. Moved to the wishlist.

                Z-Bot CoreXY Build | Thingiverse Profile

                o_lampeundefined 1 Reply Last reply Reply Quote 0
                • o_lampeundefined
                  o_lampe @Phaedrux
                  last edited by

                  @phaedrux said in what if Macros appeared in Console?:

                  Not a bad idea. Moved to the wishlist.

                  While we are talking about wishlist in macro-context:
                  I tested a few things in macros and from time to time I made syntax errors or typos in variable names.
                  A vague warning popped up in the console about these errors, not naming the macro they happened in.
                  Was it t#free.g, t#pre.g or t#post.g?
                  Happy searching...

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