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

    sleep.g

    Scheduled Pinned Locked Moved
    Documentation
    3
    8
    238
    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.
    • DonStaufferundefined
      DonStauffer
      last edited by

      SD Card documentation, "SD card structure", /sys folder does not describe sleep.g.

      soare0undefined 1 Reply Last reply Reply Quote 0
      • soare0undefined
        soare0 @DonStauffer
        last edited by

        @DonStauffer As it is supposed to be done by user, for the event when a M1 is invoked, outside a pause. Different machines, different users, different sleep files. It is empty by default, at least mine was, so the same is the description.
        See here.

        DonStaufferundefined 1 Reply Last reply Reply Quote 0
        • DonStaufferundefined
          DonStauffer @soare0
          last edited by

          @soare0 I didn't say "does not define sleep.g". I know the user is supposed to define it. The same is true of pause.g, start.g and stop.g, for instance, each of which is mentioned with a short description of when it runs. That's essential information in order to know how you can use it. In other words, I'm not saying we should be told what to put in the file. I'm saying it would be useful to know how it functions regardless of what's in it.

          gloomyandyundefined 1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy @DonStauffer
            last edited by

            @DonStauffer I don't think the documentation you are referring to is intended to be a complete description of all of the files you can have in the sys directory. In particular for the sys directory it states:

            It should contain at least the following files

            There are other files, like mesh.g, the various tool change files and probably more that can be present, but these like sleep.g are not essential. They are currently documented in the gcode dictionary (as is sleep.g).

            Perhaps @droftarts would consider producing a complete list of the possible system macro files?

            DonStaufferundefined 1 Reply Last reply Reply Quote 1
            • DonStaufferundefined
              DonStauffer @gloomyandy
              last edited by

              @gloomyandy Anyway, for those other files it's useful to have their behavior completely described in one place, because otherwise you'd have to look all over the GCode docs to find that information and never know if you missed some. Seems like that would be useful for sleep.g.

              soare0undefined 1 Reply Last reply Reply Quote 0
              • soare0undefined
                soare0 @DonStauffer
                last edited by soare0

                @DonStauffer There are many explanations in GCode Dictionary, but they may need some hunter skills (for beginners, like me). For example, when you asked for it, I searched for sleep word there, and this got me to G1. So search function was my hunting tool.
                And now it will get me to bed, as I again, am searching for sleep.

                DonStaufferundefined 1 Reply Last reply Reply Quote 0
                • DonStaufferundefined
                  DonStauffer @soare0
                  last edited by

                  @soare0 Make sure you level the bed first! 🙂

                  soare0undefined 1 Reply Last reply Reply Quote 0
                  • soare0undefined
                    soare0 @DonStauffer
                    last edited by

                    @DonStauffer It is a small bed, and kept leveled often, in many steps, so it has a good mesh file already, but thanks for the wishes, I know somebody who will be happy for them...

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