[BUG] x-y motor clicking during diagonal movement with bed leveling

[emaayan]

Bug Description

when both motors operate at the same time a faint clicking sound is heard from both motors.

My Configurations

16-12-2019.ZIP
TopCover.txt

Steps to Reproduce

1. run the attached TopCover.gcode it will reset the eeprom for default and generate a debug mesh

Expected behavior:
printing with no clicking

Actual behavior:
faint random clicks

Additional Information

with no bed leveling is enabled the clicks won't be heard
i've replaced firmware, various mks gen 1.4 boards, drivers (2100,2208) , motor cables, motors, tried with or without SD cards. it still goes on .

[Powerprobot]

Your Z-Axis have not enough speed and acceleration to compensate these stuttering. to test it, set the Z-Axis on 150 movement and 300 acceleration and you wil see that is no more stuttering.

[emaayan]

Your Z-Axis have not enough speed and acceleration to compensate these stuttering. to test it, set the Z-Axis on 150 movement and 300 acceleration and you will see that is no more stuttering.

not sure i follow, the clicks are coming from the x and y motors not z one. they also come when there's no z motor actually attached.

[Powerprobot]

With Bed-Level On, marlin will try to compensate the Z-differences. But if the Z-Axis to slow, marlin will wait to finish the move on Z-Axis and stop or deaccelerate XY-Axis during this process.

[emaayan]

this is my current acceleration settings, so you're saying i should run them higher?

#define DEFAULT_MAX_ACCELERATION { 1500, 1000, 100, 10000 }
#define DEFAULT_ACCELERATION 1000 // X, Y, Z and E acceleration for printing moves
#define DEFAULT_RETRACT_ACCELERATION 1500 // E acceleration for retracts
#define DEFAULT_TRAVEL_ACCELERATION 1500 //

[Powerprobot]

If your steps in XY are 80 and Z 400 then divide them = 5
So divide 1000 / 5 = 200 . Set Z acceleration to 200 and what are the mm/s ?
If your mm/s in XY = 300 then 300 / 5 = 60. Also 60mm/s for the Z-Axis.
Test it. But it is not for Prduction use. No one use higher rates than 80mm/s in the first ~3 layers.
Use Z-Fading by Bed leveling max 3mm.

[emaayan]

If your steps in XY are 80 and Z 400 then divide them = 5
So divide 1000 / 5 = 200 . Set Z acceleration to 200 and what are the mm/s ?
If your mm/s in XY = 300 then 300 / 5 = 60. Also 60mm/s for the Z-Axis.
Test it. But it is not for Prduction use. No one use higher rates than 80mm/s in the first ~3 layers.
Use Z-Fading by Bed leveling max 3mm.

my #define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,1600,812.56}
are you talking about max z acceleration or default acceleration ?

[emaayan]

If your steps in XY are 80 and Z 400 then divide them = 5
So divide 1000 / 5 = 200 . Set Z acceleration to 200 and what are the mm/s ?
If your mm/s in XY = 300 then 300 / 5 = 60. Also 60mm/s for the Z-Axis.
Test it. But it is not for Prduction use. No one use higher rates than 80mm/s in the first ~3 layers.
Use Z-Fading by Bed leveling max 3mm.

my #define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,1600,812.56}
are you talking about max z acceleration or default acceleration ?

btw should i return to classic jerk?
https://www.reddit.com/r/3Dprinting/comments/dx8bdb/here_is_why_you_should_disable_junction_deviation/

[emaayan]

this is an update there seem to be a difference in sounds in 1200 feed rate

G1 X63.740 Y35.648 Z0.5 F4800
G1 X63.852 Y35.760 F1200
G1 X63.852 Y36.439
G1 X63.061 Y35.648
G1 X62.382 Y35.648
..
https://www.youtube.com/watch?v=hQeY35qkp7w

and 600 feedrate
G1 X63.740 Y35.648 Z0.5 F4800
G1 X63.852 Y35.760 F600 (feed rate changed )
G1 X63.852 Y36.439
G1 X63.061 Y35.648
G1 X62.382 Y35.648
...

https://www.youtube.com/watch?v=27qj_1KE3KQ

[boelle]

@emaayan is the issue still the same with all the updates in the last 6 days?

[emaayan]

yes, although i think if i decrease the feedrate from 1200 to 600 it might be weaker.. i'm trying skr mini and skr 1.3 to see if this is an 8bit vs 32 bit issues (or maybe i'ts just a bug in how marlin handles mks gen 1.4 , or maybe a bug how it handles mega cpu in general i dunno)

…

On Tue, Dec 24, 2019 at 2:40 PM Bo Herrmannsen ***@***.***> wrote: @emaayan <https://github.com/emaayan> is the issue still the same with all the updates in the last 6 days? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MD4JLJOYYBLXF33IU3Q2H7NDA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTEYRI#issuecomment-568740933>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MAI5XZBSKI6EPJVBXDQ2H7NDANCNFSM4J4DC66A> .

[boelle]

1200 for feedrate seems crazy high try with { 200, 200, 12, 120 }

[Vertabreak]

for sure that is way to high feed rate, i run (250,250,5,30)

[emaayan]

if i recall correctly this was the original value from the g-code file i've striped down that was for 9 rectangle for bed leveling model, it was created s3d, andi think my speed back then was 80mm/s (i don't recall what percentage for other speed types in it) what values are those?

…

On Tue, Dec 24, 2019 at 3:25 PM Vertabreaker ***@***.***> wrote: for sure that is way to high i run (250,250,5,30) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MCO3VZTQ2DY3RDUBLTQ2IEURA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTGQRQ#issuecomment-568748102>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MBWFINZTO3INOHQKRDQ2IEURANCNFSM4J4DC66A> .

[boelle]

those are values we use

yours is just to high no matter how you got them

[emaayan]

wait are you talking about marlin firmware values or the actual feedrate, cause i'm was talking about the actuall feed rate i meant to say that in here intead of using 1200: G1 X63.740 Y35.648 Z0.5 F4800 G92 E0.0000 G1 X63.852 Y35.760 *F1200* G1 X63.852 Y36.439 G1 X63.061 Y35.648 i use 600 G1 X63.740 Y35.648 Z0.5 F4800 G92 E0.0000 G1 X63.852 Y35.760 *F600* G1 X63.852 Y36.439 G1 X63.061 Y35.648

…

On Tue, Dec 24, 2019 at 3:30 PM Bo Herrmannsen ***@***.***> wrote: those are values we use yours is just to high no matter how you got them — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MEREG6HWCNNREI6PRTQ2IFFVA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTGWJA#issuecomment-568748836>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MEPUFWCB4HHFORY24TQ2IFFVANCNFSM4J4DC66A> .

[boelle]

wait are you talking about marlin

what ever is highest

[emaayan]

if you look at the configuration.h in my attachment you'll see i'm using #define DEFAULT_MAX_FEEDRATE { 200, 150, 10, 50 }

…

On Tue, Dec 24, 2019 at 4:11 PM Bo Herrmannsen ***@***.***> wrote: wait are you talking about marlin what ever is highest — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MA7LIO6FY4XSYP54O3Q2IKAJA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTIIVI#issuecomment-568755285>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MCB4JXRGQIPGEMBLPTQ2IKAJANCNFSM4J4DC66A> .

[boelle]

and your slicer? some slicers override firmware

[boelle]

and eeprom values?

[emaayan]

oh i got burned with eeprom values before, the script i'm using always resets using m502 the feedrate on the g1 codes are expressed in mm/min while the ones in the firmware are expressed in mm/s so 200 mm/s should be 12000 mm/min so i'm well below the limit ;READ: I0 I1 ;READ: J0 +0.925 +0.191 ;READ: J1 +0.652 +0.565 ;READ: M502 G28 ; home all axes G29 C1

…

On Tue, Dec 24, 2019 at 4:19 PM Bo Herrmannsen ***@***.***> wrote: and eeprom values? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MD45F7UHKXXSTMZHBTQ2IK73A5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTITZA#issuecomment-568756708>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MHPUJL5EPFZAAMTYNDQ2IK73ANCNFSM4J4DC66A> .

[boelle]

@emaayan still no good news with the latest bugfix 2.0.x?

[emaayan]

it's like a never ending swamp of goo, i'm attempting to see if i can use an SKR 1.4.. but the only usable drivers i have right now are TMC2100, but there doesn't seem to be any configuration options on how to use them

…

On Wed, Jan 8, 2020 at 6:14 PM Bo Herrmannsen ***@***.***> wrote: @emaayan <https://github.com/emaayan> still no good news with the latest bugfix 2.0.x? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MFV3ZH3ONU3FLDNWRTQ4X3WHA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEINDC7Q#issuecomment-572141950>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MDGHBR2ITJZHWOD7BLQ4X3WHANCNFSM4J4DC66A> .

[emaayan]

@emaayan still no good news with the latest bugfix 2.0.x?

well after many many many hurtles, i've managed to get marlin 2.0.1 working with skr mini e3 version
1.2
i still get clicks.. this is a recording of the x-motor for better hearing
https://www.youtube.com/watch?v=5dpWGD_DE2s

[boelle]

completely noiseless, i would love to have it so good

[emaayan]

then check this out, i think i've managed to get rid of them, this is SKR 1.4 with TMC2208 16 steps and 256 interpolation https://www.youtube.com/watch?v=AXEL_f_rkj4 but i discovered another problem un-related, i can't use baby-stepping, if try to turn the knob 2 twice, the z-axis just responding, and from then on , the z-axis doesnt' move at all. (even after the print)

…

On Sun, Jan 19, 2020 at 12:45 AM Bo Herrmannsen ***@***.***> wrote: completely noiseless, i would love to have it so good — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16248?email_source=notifications&email_token=ADGP5MA63HRI2PLE6OILORLQ6OA6ZA5CNFSM4J4DC66KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJKDS3I#issuecomment-575945069>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGP5MHSFSIDXDBLQBPTBIDQ6OA6ZANCNFSM4J4DC66A> .

[boelle]

no difference to me

please create a new issue if there is an unrelated issue, just so we dont mix oranges and potatos :-)

[emaayan]

no difference to me

please create a new issue if there is an unrelated issue, just so we dont mix oranges and potatos :-)

already did, issue 16617 was confirmed by scott. but at least i have workground for that one.

and i was so hoping it would solve my original bed leveling issue because i thought those were mis-steps

[boelle]

a lot of updates and fixing has happend in the last week, is the problem still there?

[boelle]

Lack of Activity
This issue is being closed due to lack of activity. If you have solved the
issue, please let us know how you solved it. If you haven't, please tell us
what else you've tried in the meantime, and possibly this issue will be
reopened.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.