problems while probing
I currently have a setup, shown in the picture.
When I am calibrating my Z-axis, something weird happens. For the X-home and the Y-home, the two Z-axis moves up and down with no problems.
When performing a "True-bed-leveling" or a "Run Bed Mesh Compensation", the left axis (on the picture) has a ticking sound in the spindle, and also moving slower than the right axis. This causes the structure to bend and creating tension. I have to hit the emergency button everytime this happens to prevent the printer from tearing itself to pieces. I checked all the hardware like bearings/spindles etc.
I have a cable from the expansion breakout board to the pull- and the dir- inputs. I have external stepper drivers who work fine. Because I am using one signal, the signal is put in parallel over the Z1 and Z2 axis. Changing the cables (from Z1-Z2 to Z2-Z1) does not change the fact that the left side is not working correctly.
The strange thing I do not understand is why the stalling of the left axis only occurs while probing. Is there a possible explanation due to the current delivered?
Using firmware 3.1 and Duet wifi 2.03
Thanks in advance,
Sorry, duet web control 2.07
Here is my config.g file.
I found that in config, my max speed is limited to F180, while the X-home and Y-home use F6000. That works fine. In my config.g file I use F180, is that not good?
Did you find anything in the onfig.g file hat might explain the problem?
duet web control 2.07
the correct version dwc is 3.1.1 for firmware version 3.1.1
i dont have external stepper motors but i was always under the impression that you need to configure the timing for them
something like this (this depends on the stepper driver used,)
M569 P5 T2.5:2.5:5:0
yes, the timings need setting for them.
Which external drivers are you using?
peterartechno last edited by peterartechno
I am using ES-D808 external stepper drivers with Nema32 stepper drivers ( a closed-loop system).
The weird thing is that the left axis is not working, but the right one has no problems. This made me think that that was not the problem, the timing
For reliable response, pulse width should be longer than 2.5μs.
, DIR signal should be ahead of PUL signal by 5μs
yea, as @Veti says
you'll definitely need timings on those. you may think they are fine but then you'll have movement issues just like you're seeing.
I also use similar external drivers and definitely need timing to get consistent results.
You'll need M569 T2.5:2.5:5:5 on each driver thats external
Thanks! Do I need to change the M569 T2.5:2.5:5:5 to something like T2.6:2.6:65:5?
Where in the config.g file do I put this?
append T2.5:2.5:5:5 to the existing M569 entries
try with that for now
@peterartechno try out with the M569 timings I gave you above. that should be ok. Worst case you could add half a microsecond but I dont think it would be needed.
I would guess that your current M569 commands looks something like
M569 P0 S0
M569 P0 S0 T2.5:2.5:5:5
You only need to do this to the drive numbers that are the external drives
I use 2 X-motors, 1 Y-moor and 2 Z-motors, all with external stepper drivers but that particular one is the only one with problems. I am going to try it right now!
do add it to all the external drivers. it will save you headache in the long run