Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layer shifting #9487

Closed
Tamonir opened this issue Feb 5, 2018 · 21 comments
Closed

Layer shifting #9487

Tamonir opened this issue Feb 5, 2018 · 21 comments

Comments

@Tamonir
Copy link

Tamonir commented Feb 5, 2018

Hi everybody,

  • Description:
    i recently switched my MKS-Base 1.4 (TEVO Tarantula) for a MKS GEN L 1.0 with FYSETC TMC2130 on all axes/E0/E1. With MKS Base, everything worked fine, even on Long Printjobs - perfectly aligned, no steplosses - of course, I did't change any mechanics when changing the board.
    Yesterday, I did the final calibration (steps/mm) and printed the first 202020 test cube. As you can see in the Picture attached, I got "some" issues on my y-Axis while the X-Axis is perfectly fine (20.01 mm). Z-Height of cube is 18.5 mm I will look for that later).

img-20180204-wa0004

Do you have any idea on what may cause the y-issues? In Detail, you can say that the whole layers are shifted so the shift is caused at the beginning of a layer. Within one layer, y-axis perfectly fits to the (shifted) Position. Shouldn't TMC2130 recognise the missmovement and compensate?

  • Actual behaviour:
    Whole Layers get shifted at the beginning of a layer

  • Desired behaviour:
    No shift :)

  • Steps to reproduce:

Thanks in advance

Tamonir

@Athemis
Copy link

Athemis commented Feb 5, 2018

I saw something similar on my delta when I switched to TMC2130. My guess was that the driver current was too low, hence leading to skipped steps. After I increased the current, the problem went away.

@Tamonir
Copy link
Author

Tamonir commented Feb 5, 2018

Hi Athemis,

thanks for your idea, I will test it today But as i dont have any step losses during the print of a layer, it cannot be a general step loss. I just talked to a colleague of mine who had the idea, that the accelleration (and thus deceleration) might be too strong to handle. This might also be related to the low current but drivers are allready getting very hot with 0.8 A.

As this happens only when starting a new layer, the shift might be related to the high y-travel speed and hence strong accelleration. As accelleration (a) is proportional to Force (f) and force F is related to Current, I will try to decrease accelleration (which will in this case mean the same as setting a higher current).

I will report back soon and I am open for further ideas :)

Regards

Tamonir

@ikarisan
Copy link

ikarisan commented Feb 5, 2018

@Tamonir I have similar problems. For me everything is working fine with 750mA... as long as the printer uses StealthShop. But when using StealthShop together with hybrid threshold (100mm/s) the layers are shifting on larger object. If I use spreadCycle instead of StealthShop the layers are not shifting.

@Tamonir
Copy link
Author

Tamonir commented Feb 6, 2018

Hi everybody,

@ikarisan: Nice thought, I will try to disable hybrid mode and see what happens. Allready thought about that but forgot :)

For now, i lowered "a max X" and "a max Y" from 3000 (Standard) to 500 and that allready gave me huge improvements as you can see in the picture. Have some widening at the edges though but this might be related to the begins/ends of Extrusion which are distributed over all edges. With that low accelleration, the drives wont reach 100 mm/s so they arent changing to spreadcycle.

img-20180205-wa0006

I will do some further tests with old accelleration and forced stealth chop

@ikarisan: how fast can you go at 750 mA and what are your accelleration and jerk settings?

Best regards

Tamonir

@ikarisan
Copy link

ikarisan commented Feb 6, 2018

My values are set to:

#define DEFAULT_MAX_ACCELERATION { 1000, 1000, 100, 10000 }
#define DEFAULT_ACCELERATION 400 // X, Y, Z and E acceleration for printing moves
#define DEFAULT_RETRACT_ACCELERATION 1000 // E acceleration for retracts
#define DEFAULT_TRAVEL_ACCELERATION 1000 // X, Y, Z acceleration for travel (non printing) moves
#define DEFAULT_XJERK 10.0
#define DEFAULT_YJERK 10.0
#define DEFAULT_ZJERK 0.3

But I can see that you have the same "bleeding corner" problem as I have... :(
#9494

@floyd871
Copy link
Contributor

floyd871 commented Feb 11, 2018

I can confirm this Issue, but only the Y-Axis is affected. Increasing the current to 1000 does not help. Decreasing the acceleration seems to help.
(I3 Clone with Ramps 1.4)

@Roxy-3D
Copy link
Member

Roxy-3D commented Feb 11, 2018

It would be helpful if you checked the .gcode file to make sure everything is reasonable and there is no shifting. Can you feed the .gcode file into: http://gcode.ws/# and check that it's layers don't shift?

@floyd871
Copy link
Contributor

Just check it the gcode with http://gcode.ws/#, all fine

@Roxy-3D
Copy link
Member

Roxy-3D commented Feb 11, 2018

OK... That helps isolate the problem to the machine. Does it shift the same way if you print multiple times? I'm wondering if the stepper motors are losing steps????

@floyd871
Copy link
Contributor

floyd871 commented Feb 11, 2018

Yes, the shift is always the same way Y-Axis increases, never decreases.
When i increase the current the shifting is less, but overheating warnings in the console. Decreasing the acceleration to 1000 (from 3000) help. Shifting ist gone.

@Tamonir
Copy link
Author

Tamonir commented Feb 11, 2018

@ikarisan: Thanks, I will try these higher amounts soon, I am now going with 500 accelleration and its perfect (despite the bleeding corners). I had some issues though (horizontal artifacts) which were caused by some layers beeing thicker than the others. This was caused by inconsistant z move (I am using 2 z steppers). I set the current for z to 1200 (isnt moving that much...) and now it works like a charm - despite bleeding corners.

@Roxy-3D
Copy link
Member

Roxy-3D commented Feb 11, 2018

You also might want to try reducing your Max Feed Rates to 1/2 of their current values and see if that makes things better. If it totally fixes the problem, you can start bumping the Feed Rates up until you start seeing the problem again.

@floyd871
Copy link
Contributor

And the Acceleration back to default 3000!?

@Roxy-3D
Copy link
Member

Roxy-3D commented Feb 11, 2018

I wouldn't do that... Even with a very low acceleration, the extruder gets up to speed pretty quickly.
(But that is me... I don't care if a print takes 4 hours... Or if it takes 4 hours and 10 minutes. I care more that the print finishes and is correct.)

@floyd871
Copy link
Contributor

floyd871 commented Feb 11, 2018

I think this is really a problem with the TMC2130. Left one 800mA (skipping Z-Axis) , Right 1000mA (No skipping)
img_20180211_194221
I thought Z axis is not so so problem with current, because of the reducers of the leadscrew..

@Tamonir
Copy link
Author

Tamonir commented Feb 11, 2018

I thought Z axis is not so so problem with current, because of the reducers of the leadscrew..

And maybe thats the reason Maybe the very short turning of the steppers leads to stalling. Yesterday, I changed the microstep settings of y and x from 16 to 32 - so the distance got devided by 2. What was remarkable was, that the sensorless homing triggered immediately when homing (which was calibrated well for 16 steps) - as sensorless homing is provided by motor current, maybe that the load vor minor changes causes the stepper to stall. Its only a guess...

@ floys: do you have two or one z stepper?

@floyd871
Copy link
Contributor

floyd871 commented Feb 12, 2018

Good point, yes i am using standard Ramps with two motors on one driver on the z-axis.
So the default setting to 800mA for z-axis might not be enough....

@Lyr3x
Copy link

Lyr3x commented Mar 29, 2018

I'm running my Z axis @700mA without any shifting problems (nearly the same acceleration, jerk and feedrate). Do you use stealthchop or spreadcycle?

You need fairly high currents with the TMC2130 in stealthchop mode to prevent skipping steps

@boelle
Copy link
Contributor

boelle commented Feb 20, 2019

@Tamonir Please post your question either on discord: https://discord.gg/n5NJ59y or on facebook: https://www.facebook.com/groups/2080308602206119/
The issue list is for bugs and feature requests only
Please close this issue once you have posted it on one of the 2 links
Thanks :-D

@boelle
Copy link
Contributor

boelle commented Mar 6, 2019

@thinkyhead i think we can close this one

@Tamonir Tamonir closed this as completed Mar 7, 2019
@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants