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

    Mysterious Z150!

    Scheduled Pinned Locked Moved
    General Discussion
    3
    7
    290
    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.
    • handyandyundefined
      handyandy
      last edited by

      Hi I am trying to find a Z150 command that gets executed every time I start print.
      I have looked in the Cura startup code, start.g and pretyty well everywhere else!
      What is the start sequence of files called when starting a print? Or could this be in the firmware?

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @handyandy
        last edited by

        @handyandy start.g is executed before anything else and then its whatever is contained within the gcode file

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        handyandyundefined ctilley79undefined 2 Replies Last reply Reply Quote 0
        • handyandyundefined
          handyandy @jay_s_uk
          last edited by

          @jay_s_uk Thanks for that.

          handyandyundefined 1 Reply Last reply Reply Quote 0
          • handyandyundefined
            handyandy @handyandy
            last edited by

            @handyandy This still does not explain why when starting a print the nozzle goes up to Z150 (shown on the console) There is not one mention of Z150 anywhere in the macros, system files that I cant find!
            Still puzzled... must be in the firmware coding?

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @handyandy
              last edited by

              @handyandy post your homeall, homez, first lines of your gcode file up to the point it starts extruding and anything else thats called

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              1 Reply Last reply Reply Quote 0
              • ctilley79undefined
                ctilley79 @jay_s_uk
                last edited by

                @jay_s_uk This is somewhat related, but can you send parameters from your slicer start code to /sys/start.g? The only way I've found to do it so far is to create a separate macro and call that via

                M98 P"/macros/whatever.g" H[hotend_temp] B[bed_temp]

                However there doesn't seem to be a way to pass that parameter to the start.g in the sys folder that is executed automatically.

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @ctilley79
                  last edited by

                  @ctilley79 you can't send parameters to start.g as it's executed before the gcode is

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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