Voron Corexy weired x/y movement
-
@timtom all your entries for Z after M584 should only have one value
M92 X160.00 Y160.00 Z400.00:400.00:400.00:400.00 E420.00
is incorrect and should be
M92 X160.00 Y160.00 Z400.00 E420.00
M350 E64:64:64:64 I0
is also incorrect as you only have one extruder. it should be
M350 E64 I0
-
@jay_s_uk
Thanks Jay, updated that, tried many many different configurations, just adapted your changes, I'm currently not worried about correct stepping.
The erratic behavior is still there.For the record here the updated config.g file:
; General drive config like speeds, accel, jerk, etc M350 E16 I0 ; configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z900.00:900.00:900.00:900.00 E120 ; set maximum instantaneous speed changes (mm/min) M203 X60000.00 Y60000.00 Z60000.00:6000.00:6000.00:6000.00 E120.00 ; set maximum speeds (mm/min) M201 X6000.00 Y6000.00 Z4000.00:4000.00:4000.00:4000.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200:1200:1200:1200 E400 I100 ; set motor currents (mA) and motor idle factor in per cent M84 S30
-
@timtom your other lines need changing, so M566, M203, M201 and M906
-
Thanks for the quick reply, unfortunately still no success
for the record:
; General drive config like speeds, accel, jerk, etc M350 E16 I0 ; configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z900.00 E120 ; set maximum instantaneous speed changes (mm/min) M203 X60000.00 Y60000.00 Z60000.00 E120.00 ; set maximum speeds (mm/min) M201 X6000.00 Y6000.00 Z4000.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E400 I100 ; set motor currents (mA) and motor idle factor in per cent M84 S30
-
@timtom definitely sounds quite mechanical in nature.
what firmware are you running? -
That's my fear, that x or y motor has a defect. . .
Currently I use RepRapFirmware for Duet 3 Mini 5+ 3.4.0beta6 (2021-11-06)
But previously I also had the latest stable --> same issue. -
This post is deleted! -
@arnold_r_clark
Thanks for the hint, will check this evening to be sure.On the other hand I somehow doubt that to be the reason:
- There are also clean movement (sometimes x and y works just fine, to just instantantly switching to the erratic behavior).
- While recrimping I made sure that "colors" match. These are genuine LDO/Voron motors bought from a European distributer, so the risk should be comparably low.
-
@timtom just to give you a bit of reassurance its not firmware, I run 2 corexy's on 3.4b6 and one of them is a Voron V0 using LDO motors
-
@timtom said in Voron Corexy weired x/y movement:
That's my fear, that x or y motor has a defect. . .
Have you tried testing the motors independently? E.g. releasing the belt tension and issuing manually G1 command with H2 parameter.
If the motors are ok, make sure your gantry is de-racked (nero3dp has an instruction video) , the belts seat properly and that there are no mechanical friction or binding.
A stepper motor analyzer would help https://forum.duet3d.com/post/262112
-
@timtom said in Voron Corexy weired x/y movement:
checked configuration from https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_coreXY all fine.
Can you make a video showing you going through the motion testing section of this guide to show correct movement?
From your video it really seems like a motor direction is incorrect and is fighting the other motor.
-
OK shame on me!
While I wanted to replace the x/y motors I detected that the belt was misguided and rubbing on plastic!So please excuse my "wrongly" reported issue.
Bear with me, I had so many external issues during the build (badly soldered hall effect platines, badly soldered extruder pcb's, broken duet board, wrongly configured wiring loom).
Everything took me several hours to identify (I ordered all parts in Europe, with the hope to avoid Chinese quality issues - wrong assumption).After days of troubleshooting I stopped to challenge my own work, sorry for that.
-
@timtom, that's normal. We all struggle with similar problems.
-
-