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

script execution graph

Scheduled Pinned Locked Moved
General Discussion
4
5
241
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
    fšk
    last edited by 24 Apr 2020, 08:29

    Hello,

    I'm wondering if there is any documentation that describes an overview of how the different gcode scrpits are executed on startup and any later user input. I know all of this is described somewhere in the documentation, but it seems hard to get an overview of all of it. A simple chart of what happens when would be useful imho.

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by dc42 24 Apr 2020, 08:56

      They should all be listed at https://duet3d.dozuki.com/Wiki/Macros#Section_System_Macros.

      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 24 Apr 2020, 11:08 Reply Quote 0
      • undefined
        RS @dc42
        last edited by 24 Apr 2020, 11:08

        @dc42 said in script execution graph:

        They should all be listed at https://duet3d.dozuki.com/Wiki/Macros#Section_System_Macros.

        I think the daemon script is missing there.

        1 Reply Last reply Reply Quote 0
        • undefined
          Danal
          last edited by Danal 24 Apr 2020, 13:27

          Startup is easy, it runs config.g. There is nothing special about config.g beyond that it gets executed at startup. You can issue command that is 'normally' in config.g, at any time (with the normal caveats regarding ordering; you have to define an axis before you configure it, etc, etc).

          For example, you could have just enough config.g to get on the network, and then fully configure the machine by "playing" commands from some external source.

          The rest are in the link above.

          Delta / Kossel printer fanatic

          1 Reply Last reply Reply Quote 0
          • undefined
            fšk
            last edited by 24 Apr 2020, 14:25

            Thank you all for your answers.
            I was wondering since im trying to use the filament config.g but it doesn't seem to be called when the printer starts up. I figured out i need to put M703 in the main config.g after selecting the tool. I think this should be mentioned in the docs since just putting it in tpost0.g doesn't seem to do the job on startup .

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