@dc42 hi

Have a backlash function been added for the X and Y axes?

I assembled a large 3D printer and in it I use 1: 4 planetary gearboxes for the X and Y axes. Due to play in the planetary gearboxes and the HTD-3M timing belt, layers are printed in waves. That is, they do not go one on top of the other, they are constantly shifted relative to the previous one. This can be seen in the photo.

Acceleration costs 900 mm / sec and jerks are malnye default. Filament PLA, fan on. I use feedback servo stepper motors and the print speed is only 40 mm / s so there can be no skipping steps.

I know that even in the match 3 program there is this function, since many use a gear rack and because of it there are backlashes. Also in planetary gearboxes there are backlashes.

backlash function implemented in mariln www. marlinfw.org/docs/gcode/M425.html

please tell me how to solve my problem?!!

X-axis offset occurs with the leadshine em705 driver.

print result, microstep 32.

If I use the Drv8825 driver, then there are no offsets. microstep 16.

What i use

1. Arduino DUE control board + RURAMPS4D
2. Digital driver leadshine em705 stepper motor.
3. 48 Volt driver power.
4. Power logic driver 5 volts. I use MKS sd 57/86
5. kinematika printer Cartesian.
6. The table goes up Z.

My changes in the config.
M569 P0 S1 T10: 10: 30: 30
M569 P1 S1 T5:10:10:0 ;Drive 1 goes forwards
M569 P2 S1 T5:10:10:0 ;Drive 2 goes forwards
M569 P3 S1 T5:10:10:0 ;Drive 3 goes forwards
M569 P4 S1 T5:10:10:0 ;Drive 4 goes forwards
M569 P5 S1 T5:10:10:0 ;Drive 5 goes forwards

M584 X0 Y1:2 Z3:4 E5 ;
M92 X177.77
M566 X900.00
M203 X12000.00
M201 X1000.00

I tried different timings M569 P0 S1 T5: 10: 10: 0.
There were no changes. No speakers.

There is a very interesting detail.
If I increase the micro step, then the offset becomes less.
But it remains.

There are no problems in mechanics. Most likely, the impulses of step or delay dir are wrong.

@dc42 said in Brobe sensor does not respond to touch if g29 a second time?:

What type of sensor is it, and how have you connected it to the Duet?
I use a weight sensor. It is triggered by touching the nozzle.
It works correctly. When you enter the m119 command, it responds.

I successfully started printing after g29. If you do not turn off the printer, the second time g29 will not work. The printer does not respond to pressing.

Maybe this is due to the fact that the grid is loaded? If the command is a grid I would try to use it.

The Brobe sensor does not respond to touch if g29 is used a second time.

My algorithm of actions.

1. I press g28, the X and Y axes go to the min switch.
   Z axis goes to limit switch Max.

2. I will press G29.
    The table starts to rise and at a distance of 100 mm from the sensor begins to act on the touch. At this distance of 100, I clicked on it. Make sure it works!

I immediately wanted to repeat the experiment
3) I pressed g28.
4) I pressed g29, the table was raised, but did not react to the touches until it approached the sensor. When the gap was 1 mm from the sensor, I had to turn off the printer.
To not break anything.

After that, I repeated everything first.
For the first time, the G29 all works.
The second time, the G29 does not react to touch.

My config.
; Axis limit
M208 X0 Y0 Z0 S1; Set axis minima
M208 X290 Y290 Z1025 S0; Set axis maxima

; Endtops
M574 X1 Y1 Z2 S0; Set active low and disabled endstops

; Z-probe
M558 P5 H100 F120 T6000 I1; Set the speed of the probe
G31 P500 X0 Y0 Z0; Set Z probe
M557 X15: 265 Y15: 265 S150; Define mesh grid

Homeall.
G91; relative positioning
; G1 Z5 F6000 S2; lift Z relative to current position
G1 S1X-305 Y-305 F1800; move to the X and Y axis thereto and stop there (first pass)
G1 X5 Y5 F6000; go back a few mm
G1 S1 X-305 Y-305 F360; move ()
G1 S1 Z1025 F1000; move up stopping at the endstop
G1 Z-5;
G1 S1 Z1025 F300
G90; absolute positioning
G92 Z1025; set Z to axis minimum (you may want to adjust this)

print height is large.
Autocalibration will be before each seal.
I use a nozzle as a sensor, use a tenzo.
It is necessary that g29 worked a lot on time.

Briefly.

1. g28

2. g29
   Ok

3. g28

4. g29

5. g28

6. g29 does not respond!

What are your thoughts on this? Where is my mistake?

I found a mistake. It was in the wrong pin step for the second driver Y.
I fixed it and it all worked.
Config as was and remained.

thank

@dc42 said in Dual Z endstop, and Dual Z motor:

Check that you have your M906 command to set motor currents after the M584 command, not before it. Likewise if you have a M350 command, it must be later in config.g than the M584 command.

It did not help.
My configuration options

M569 P0 S1 T5:10:10:0 ;Drive 0 goes forwards
M569 P1 S1 T5:10:10:0 ;Drive 1 goes forwards
M569 P2 S1 T5:10:10:0 ;Drive 2 goes forwards
M569 P3 S1 T5:10:10:0 ;Drive 3 goes forwards
M569 P4 S1 T5:10:10:0 ;Drive 4 goes forwards
M569 P5 S1 T5:10:10:0 ;Drive 5 goes forwards
M584 X0 Y1:2 Z3 E5 ;
M350 X16 Y16:16 Z16 I0 ; Configure microstepping without interpolation
M350 E16 I1 ; Configure microstepping with interpolation
M92 X88.88 Y53.33:53.33 Z1280.00 E92.60 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z300.00 E1200.00; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z100.00 E250.00; Set accelerations (mm/s^2)
M906 X800.00 Y800.00:800.00 Z800.00 E800.00 I30 ;Set motor currents (mA) and motor idle factor in per cent
M84 S30

Hello

I want to configure two engines on the Y axis and one endstop.

In config.g

M569 P1 S1 T5: 10: 10: 0; Drive y1 forwards
M569 P2 S1 T5: 10: 10: 0; Drive y2 forwards

M584 X0 Y1: 2 Z3 E5

But with this configuration, only one engine rotates, the second stands still.

what am i doing wrong?

Does the firmware support simultaneous use of the Dual Z endstop, Dual Z motor and Dual Y endstop, Dual Y motor.
Fee arduino DUE.
How to implement it.
It is also planned to do auto-calibration on an inductive sensor.
Will this all work in parallel.