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

    Centering a print

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    33
    1.3k
    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.
    • Derek.Fundefined
      Derek.F @Derek.F
      last edited by

      @Derek-F I just made the edit to M208 and stored it in the printer.

      They now read:
      M208 X-202 Y-204 Z0 S1 ; set axis minima to end of safe travel.
      M208 X202 Y204 Z510 S0 ; set axis maxima to match endstop location.

      However, when I homed the printer (from the screen on the printer) the extruder went to the back right as usual, but instead of going to the center to establish the Z value, it descended in the back left corner and the nozzle CRASHED into the heat plate (because the BLtouch sensor was well behind the heat plate). I switched the printer off in this condition.

      What should I do when I next switch on?

      What have I missed? (why did it try to find Z at the back right corner - it is due to one of the figures I was concerned about in my previous post?)

      Cheers,

      Derek

      dc42undefined deckingmanundefined 2 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Derek.F
        last edited by

        @Derek-F said in Centering a print:

        why did it try to find Z at the back right corner - it is due to one of the figures I was concerned about in my previous post?

        Your homez.g file probably contains a G1 command to move the head to bed centre before doing a G30 probe. Bed centre used to be about X200 Y200, but it is now X0 Y0. So you will need to change those coordinates in homez.g, and also in homeall.g if that code is in that file too.

        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

        1 Reply Last reply Reply Quote 0
        • deckingmanundefined
          deckingman @Derek.F
          last edited by deckingman

          @Derek-F You'll need to redo all your homing files. The origin is now set as the centre of the bed so if you want to probe the bed in the centre, you'll need move the print head to X=0 Y =0. i.e this line "G1 X200 Y200 F6000 ; go to first probe point" needs to be changed to "G1 X0 Y0 F6000 ; go to first probe point

          Note that the position of the end stops can stay the same. Note also that any files you previously sliced with the origin set to one corner of the bed will need to be re-sliced because they will contain moves in the range zero to circa 400 whereas with the origin in the slicer set to the centre, the moves need to be in te range minus circa 200 to plus circa 200.

          Edit posted while DC was typing. also, it appears my PC has the wrong time set.

          Ian
          https://somei3deas.wordpress.com/
          https://www.youtube.com/@deckingman

          Derek.Fundefined 1 Reply Last reply Reply Quote 0
          • Derek.Fundefined
            Derek.F @deckingman
            last edited by

            @deckingman Thank you for your replies.

            Before I switch on the printer, I'd like to have some idea of the procedure I'm going to follow to recover from the crash. Some time after power off, I tried unsuccessfully to raise the gantry slightly and take the pressure off the nozzle. When powered up, I can't use the move buttons until a homing operation is performed first (which I obviously cannot do).

            If I opened the printer console and sent one of these commands, would it lift the gantry?

            G1 Z10 F300
            G1 Z+10 F300
            G1 Z10
            Or something else?
            Do I need a G90 or G91 first?

            I am seriously concerned that the gantry is no longer level (ie: parallel with the bed) since it crashed in one corner and I tried to lift it slightly.
            How should the gantry be leveled again?
            Will my Z offset be incorrect?

            Cheers,

            Derek

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @Derek.F
              last edited by

              @Derek-F use M564 H0 to allow jogging of the axis without homing

              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

              Derek.Fundefined 1 Reply Last reply Reply Quote 0
              • Derek.Fundefined
                Derek.F @jay_s_uk
                last edited by

                @jay_s_uk Thank you. That allowed me to move the nozzle away form the bed.

                I have changed my two M208 lines back to the 'as supplied' figures where the zero is at the front left corner. I think it prudent not to change to zero at the bed center until I understand every implication of doing so.

                How do I get the gantry parallel to the bed now?

                I see this code in config.g but when is config.g run? (is there a command in the print file?)

                ; --- z-axis stepper leveling configuration ---
                M584 X0 Y1 E3 Z6:5:8:7 ; four motors, at 5, 6, 7, and 8
                ;M671 X420:420:-100:-100 Y380:-115:-115:380 S20 ; Z belts at 4 corners
                M671 X-100:-100:420:420 Y380:-115:-115:380 S20 ; Z belts at 4 corners

                Does the above actually level the gantry?

                Finally, will the crash have affected my Z offset?

                Cheers,

                Derek

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @Derek.F
                  last edited by

                  @Derek-F config.g is ran at boot and loads all of your printers parameters into the firmware so it can be setup correctly.

                  G32 would go through the levelling process. This runs the bed.g file, which contains the locations to probe the bed for levelling

                  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

                  Derek.Fundefined 1 Reply Last reply Reply Quote 0
                  • Derek.Fundefined
                    Derek.F @jay_s_uk
                    last edited by

                    @jay_s_uk It's idle and powered on. Should I just send G32?

                    Or do I need to home it first?
                    Cheers,

                    Derek

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @Derek.F
                      last edited by

                      @Derek-F you need to home first

                      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

                      Derek.Fundefined 1 Reply Last reply Reply Quote 0
                      • Derek.Fundefined
                        Derek.F @jay_s_uk
                        last edited by

                        @jay_s_uk That was all successful. Thank you.

                        Do you think I need to reset my Z offset after the crash?

                        Cheers,

                        Derek

                        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                        • jay_s_ukundefined
                          jay_s_uk @Derek.F
                          last edited by

                          @Derek-F you may do depending how hard the nozzle crashed into the bed.
                          You should also be running G32 before a print as the gantry/bed may have dropped whenever power has been turned off

                          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

                          Derek.Fundefined 1 Reply Last reply Reply Quote 0
                          • Derek.Fundefined
                            Derek.F @jay_s_uk
                            last edited by

                            @jay_s_uk OK, I'll try a print and see how it goes.

                            Just checked and G32 is in my Start G-code routine.

                            BTW, is the following line bad to constantly write to memory (like the WiFi credentials)?

                            M550 P"VIVEDINO" ; Set machine name

                            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                            • jay_s_ukundefined
                              jay_s_uk @Derek.F
                              last edited by

                              @Derek-F no, thats fine. that just sets the machine name in the firmware

                              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

                              Derek.Fundefined 1 Reply Last reply Reply Quote 0
                              • Derek.Fundefined
                                Derek.F @jay_s_uk
                                last edited by

                                @jay_s_uk Everything is working again! Thank you!

                                Z offset looks ok. I'll monitor on further prints.

                                And I have centered the print, simply by changing the X5 to X0 in the 'M208 S1' line (M208 X0 Y0 Z0 S1) and adjusting the X size of the bed in the slicer. (I clearly don't know enough to safely set zero at the center of the bed at the moment).

                                The printer already had a macro for WiFi ON and I just had to change the credentials to my set. I have commented out M587 in config.g .

                                I do have a couple of other unrelated questions but I should probably start new threads for those (unless you want to continue here).

                                Thanks to both of you for your gracious replies and patience with my lack of knowledge.

                                Cheers,

                                Derek

                                jay_s_ukundefined 1 Reply Last reply Reply Quote 2
                                • jay_s_ukundefined
                                  jay_s_uk @Derek.F
                                  last edited by

                                  @Derek-F probably best to start a new thread. Then we can tackle the subject of getting you upgraded to 3.5.2

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