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

    Setting up Cartesian Printer.

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    9
    98
    15.0k
    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.
    • T3P3Tonyundefined
      T3P3Tony administrators
      last edited by

      The direction of the drives depends on the wiring of the stepper motors so if they are going the opposite way to expected then simply use M569 P1 S0 or M569 P1 S1 to change the direction of drive 1. Change the inner after the P parameter to.select the drive.

      The Z offset is set using G31 but first setup your probe type using M558. Have a look at the RepRap wiki for more gcode information:
      http://reprap.org/wiki/G-code#M558:_Set_Z_probe_type

      www.duet3d.com

      1 Reply Last reply Reply Quote 0
      • Corexyundefined
        Corexy
        last edited by

        @T3P3Tony:

        The direction of the drives depends on the wiring of the stepper motors so if they are going the opposite way to expected then simply use M569 P1 S0 or M569 P1 S1 to change the direction of drive 1. Change the inner after the P parameter to.select the drive.

        The Z offset is set using G31 but first setup your probe type using M558. Have a look at the RepRap wiki for more gcode information:
        http://reprap.org/wiki/G-code#M558:_Set_Z_probe_type

        Thank you.

        I already had selected the IR probe via the configurator, and it looks like I have it set correctly in M558 (P1 unmodulated IR probe?).

        I'm not sure what to type in to G31 It does seem to be triggering at about 2.5mm…do I need to enter an offset value?

        G31 P600 X1 Y1 Z2.5 ; Set Z probe trigger value, offset and trigger height

        Should X and Y be 0 not 1, as I don't use the IR probe for those axis'?

        1 Reply Last reply Reply Quote 0
        • perolalarsundefined
          perolalars
          last edited by

          Hi Corexy
          dont know so much about this but I found the section "Setting probe parameters" at https://duet3d.com/wiki/Setting_up_automatic_probing_of_the_print_bed very helpful!

          1 Reply Last reply Reply Quote 0
          • T3P3Tonyundefined
            T3P3Tony administrators
            last edited by

            Yes X0 and Y0
            Z2.5 means the trigger height is 2.5mm

            Test far away from you bed to avoid crashing your nozzle

            www.duet3d.com

            1 Reply Last reply Reply Quote 0
            • Dougal1957undefined
              Dougal1957
              last edited by

              And if your using DC42's excellent Mini IR Sensor then the P parameter should be P500

              Doug

              1 Reply Last reply Reply Quote 0
              • Corexyundefined
                Corexy
                last edited by

                @perolalars:

                Hi Corexy
                dont know so much about this but I found the section "Setting probe parameters" at https://duet3d.com/wiki/Setting_up_automatic_probing_of_the_print_bed very helpful!

                Thanks very much!

                1 Reply Last reply Reply Quote 0
                • Corexyundefined
                  Corexy
                  last edited by

                  @T3P3Tony:

                  Yes X0 and Y0
                  Z2.5 means the trigger height is 2.5mm

                  Test far away from you bed to avoid crashing your nozzle

                  And trigger height is used to set the offset?

                  By that I mean if I'm crashing the nozzle I increase the trigger height?

                  I know it sounds dumb, but I thought the trigger height and offset were 2 different things.

                  All of this is language/terms I haven't heard used before.

                  1 Reply Last reply Reply Quote 0
                  • Corexyundefined
                    Corexy
                    last edited by

                    @Dougal1957:

                    And if your using DC42's excellent Mini IR Sensor then the P parameter should be P500

                    Doug

                    I am, and I will change that. thank you as well.

                    And that all helped.

                    Possibly the P500 setting, but I changed the trigger height to 4mm to be safe and it ended up about there.

                    So now according to the wiki I have to set the height so as to pin a sheet of paper to the bed and enter "G92 Z0".

                    Will I insert that code just after G31?

                    I'll clean and level the bed properly before I carry out that step tomorrow.

                    Cheers again

                    1 Reply Last reply Reply Quote 0
                    • Dougal1957undefined
                      Dougal1957
                      last edited by

                      see DC42's post in https://www.duet3d.com/forum/thread.php?id=358 which should explain how to determine your Z Param for the G31 line.

                      Basically home the printer
                      move the nozzle to the bed using the paper test
                      send G92 Z0
                      move the nozzle up 5mm or so
                      send G30 S-1 to probe the bed read the Z height of either the web IF or PanelDue and note down

                      Repeat a few time to ensure repeatability and you should have found your Z Trigger height (This is actually the height of the nozzle when the probe triggers.)

                      Hope this helps.

                      Doug

                      1 Reply Last reply Reply Quote 0
                      • Corexyundefined
                        Corexy
                        last edited by

                        This might be a blunder on my part, or a mistake in the config tool, but check this out:

                        On the lower board, the terminal blocks labelled RTD1 and RTD2 will be temperature measurement channels 200 and 201 respectively.

                        I entered RTD1 into the config tool and ended up with:

                        M305 P1 T100000 B4138 C0 R4700 L0 H0 X201 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 201

                        This might explain why my hot end is reading at 2000degC at room temp??

                        I'll try changing it to 200 and see what happens.

                        And yes, that put me with 0.5degC of the bed temp
                        Which would also mean that David's estimated settings for the bed thermistor were pretty good as well.

                        1 Reply Last reply Reply Quote 0
                        • Dougal1957undefined
                          Dougal1957
                          last edited by

                          That would make a difference yes

                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            Regarding G31 P600 X1 Y1 Z2.5 ; Set Z probe trigger value, offset and trigger height:

                            1. Increasing the probe trigger height (G31 Z parameter) will make a bed crash more likely, because after the probe triggers, the firmware will think it can go down further before it reaches Z=0. You need to measure the trigger height as described in the IR sensor fitting instructions, and use that value.

                            2. The X and Y parameters are the offsets of the sensor sensitive area (just below the black capacitor) from the nozzle. They get subtracted from the XY coordinates in your bed.g file, so that the sensor is over those points during probing, not the nozzle.

                            3. You must always use P500 with the IR sensor.

                            HTH David

                            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
                            • Corexyundefined
                              Corexy
                              last edited by

                              @dc42:

                              Regarding G31 P600 X1 Y1 Z2.5 ; Set Z probe trigger value, offset and trigger height:

                              1. Increasing the probe trigger height (G31 Z parameter) will make a bed crash more likely, because after the probe triggers, the firmware will think it can go down further before it reaches Z=0. You need to measure the trigger height as described in the IR sensor fitting instructions, and use that value.

                              2. The X and Y parameters are the offsets of the sensor sensitive area (just below the black capacitor) from the nozzle. They get subtracted from the XY coordinates in your bed.g file, so that the sensor is over those points during probing, not the nozzle.

                              3. You must always use P500 with the IR sensor.

                              HTH David

                              Thank you. I'll read the wiki a bit more.

                              Just starting to get my head around it all.

                              1 Reply Last reply Reply Quote 0
                              • Corexyundefined
                                Corexy
                                last edited by

                                With my homing I am concerned whether I entered the right information in the config tool.

                                I am pretty sure I entered "high" for all axis'.

                                My X and Y limit switches are both in the front/left corner, and I had to reverse/enter a 0 value all 3 drives to get them to home to the right position.

                                Moving them manually with the paneldue I have to use + movement to move towards the homing position.

                                Is that correct?

                                It does seem so according to the wiki (I think), and I just want to be sure before I set the Z home position, which is currently in the right rear corner and I'd like to move it to the center

                                Here's how I'm set up at the moment:

                                ; Endstops
                                M574 Z0 S0 ; Define active low and unused microswitches
                                M574 X2 Y2 S1 ; Define active high microswitches
                                M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
                                G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height

                                ; Drives
                                M569 P0 S0 ; Drive 0 goes forwards
                                M569 P1 S0 ; Drive 1 goes forwards
                                M569 P2 S0 ; Drive 2 goes forwards

                                1 Reply Last reply Reply Quote 0
                                • Corexyundefined
                                  Corexy
                                  last edited by

                                  Re run the config tool and left the high/low settings at their defaults.

                                  Still had to reverse 2 steppers, but I realize this would be just due to wiring connections.

                                  It now homes Z in the back/left corner, and I'd like to set my Z probe height/offset in the center.

                                  My question is: Do I have the correct high/low settings for my machine which has the limit switches in the front/left corner of the gantry?

                                  If not, could someone show me what changes to make?

                                  I've gone through the wiki but am unsure.

                                  Here's where I'm at now:

                                  ; Endstops
                                  M574 Z0 S0 ; Define active low and unused microswitches
                                  M574 X1 Y2 S1 ; Define active high microswitches
                                  M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
                                  G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height

                                  ; Drives
                                  M569 P0 S1 ; Drive 0 goes forwards
                                  M569 P1 S0 ; Drive 1 goes backwards
                                  M569 P2 S0 ; Drive 2 goes backwards
                                  M569 P3 S1 ; Drive 3 goes forwards

                                  1 Reply Last reply Reply Quote 0
                                  • StephenRCundefined
                                    StephenRC
                                    last edited by

                                    Edit homez.g and homeall.g to put the probe/hotend where you want it to be for homing.

                                    1 Reply Last reply Reply Quote 0
                                    • Corexyundefined
                                      Corexy
                                      last edited by

                                      @StephenRC:

                                      Edit homez.g and homeall.g to put the probe/hotend where you want it to be for homing.

                                      Nice!

                                      I was only doing it in homez.g. Didn't realize it had to be done in both.

                                      Could someone confirm my X Y axis high/low settings in my question above please?

                                      1 Reply Last reply Reply Quote 0
                                      • dc42undefined
                                        dc42 administrators
                                        last edited by

                                        You need to decide where you want X=0 Y=0 to be. That in turn will fix which is the X axis and which is the Y axis. If you choose front left, X will be left-right and Y will be front-back. If you choose rear left then X will be back-front and Y will be left-right.

                                        Having chosen where the origin will be, set the X and Y motor directions so that +X and +Y move the head away from that corner. You may need to swap the X and Y motor connections over to achieve this.

                                        Then use config tool to specify whether each homing switch is at the low or the high end of its axis, to generate the correct M574 command and homing files. You don't need to home to the origin, you can home to zero on some axes and to max on others.

                                        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
                                        • Corexyundefined
                                          Corexy
                                          last edited by

                                          My understanding is that the standard configuration is that X=left to right, and y=front to back. If that is the case I'd rather keep it that way.

                                          X0 and Y0, by which I assume you mean home/limit switch are in the front/left of the gantry.

                                          It's almost correct…+ve moves X out of the home/corner, and moves the Z/build plate down.

                                          The only problem is Y, which needs -ve to move out the the home/corner.

                                          Is there anything I can change here in config.g that will fix that? Would M574 X1 Y1 S1 do it? nope, doesn't

                                          M574 Z0 S0 ; Define active low and unused microswitches
                                          M574 X1 Y2 S1 ; Define active high microswitches
                                          M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
                                          G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height

                                          ; Drives
                                          M569 P0 S1 ; Drive 0 goes forwards
                                          M569 P1 S0 ; Drive 1 goes backwards
                                          M569 P2 S0 ; Drive 2 goes backwards
                                          M569 P3 S1 ; Drive 3 goes forwards

                                          1 Reply Last reply Reply Quote 0
                                          • dc42undefined
                                            dc42 administrators
                                            last edited by

                                            With that configuration, the origin will be at the front left. As your limit switches are also in the front left corner, they are both low end switches. So use M574 X1 Y1 S1.

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