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

Mysterious Z150!

Scheduled Pinned Locked Moved
General Discussion
3
7
272
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
    handyandy
    last edited by 20 Jul 2023, 10:20

    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?

    undefined 1 Reply Last reply 20 Jul 2023, 10:40 Reply Quote 0
    • undefined
      jay_s_uk @handyandy
      last edited by 20 Jul 2023, 10:40

      @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

      undefined undefined 2 Replies Last reply 20 Jul 2023, 13:11 Reply Quote 0
      • undefined
        handyandy @jay_s_uk
        last edited by 20 Jul 2023, 13:11

        @jay_s_uk Thanks for that.

        undefined 1 Reply Last reply 21 Jul 2023, 15:07 Reply Quote 0
        • undefined
          handyandy @handyandy
          last edited by 21 Jul 2023, 15:07

          @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?

          undefined 1 Reply Last reply 21 Jul 2023, 15:52 Reply Quote 0
          • undefined
            jay_s_uk @handyandy
            last edited by 21 Jul 2023, 15:52

            @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
            • undefined
              ctilley79 @jay_s_uk
              last edited by 21 Jul 2023, 19:49

              @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.

              undefined 1 Reply Last reply 21 Jul 2023, 19:55 Reply Quote 0
              • undefined
                jay_s_uk @ctilley79
                last edited by 21 Jul 2023, 19:55

                @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
                1 out of 7
                • First post
                  1/7
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA