Extra axies not interpolatedduring G2 and G3 moves

dc42

@kulitorum said in Extra axies not interpolatedduring G2 and G3 moves:

I am still waiting for a new firmware

I just updated to RC4a to check if the fixes were implemented, and noticed that there are a few other problems:

G2 and G3 moves are moving too slow. The command

G1 x0 y0
g2 x1000 y000 i500 j000 f16000

Takes 43 seconds to execute, and should take 31.4 second.

At the same time, the axies are very noisy. I think the axies are accelerating and decelerating all the time, leading to slow move speed and noisy steppers. If I increase acceleration to 50000 (from 400) the time matches the 31.4 sec and the axies are not noisy.

Any idea when you are releasing the next RC?

Kulitorum

Can you confirm that G2 and G3 moves are extruding correctly in RC4a?

If it's printing circles too slowly then you probably need to increase the XY jerk setting.

Kulitorum

Extrusion works, but U interpolation does not work.

Changing XY jerk makes no difference, but changing acceleration does.

Kulitorum

dc42

@kulitorum said in Extra axies not interpolatedduring G2 and G3 moves:

Extrusion works, but U interpolation does not work.

Changing XY jerk makes no difference, but changing acceleration does.

Kulitorum

Can you give me a small example of the sort of G2 or G3 move with U movement that you are making? I was planning to do a release later this afternoon but I'll try to fix this issue first when I am sure I understand what it is.

Kulitorum

I assume you are doing some kind of piecewise linear move, and if you use the start AND end position of each piece, you will get double coords (end is the same as start) and this leads to constant acceleration and deacceleration. Maybe you just need to use the end points and this will fix it?

Kulitorum

Kulitorum

G1 x0 y0
g2 x000 y1000 i00 j500 u9000 e9 f6000

Kulitorum

After a demo of x and y axis, I execute the G2 command I pasted here:
https://youtu.be/g3Q2_Sx2frY

dc42

@kulitorum said in Extra axies not interpolatedduring G2 and G3 moves:

G1 x0 y0
g2 x000 y1000 i00 j500 u9000 e9 f6000

What was the U coordinate before you executed that command?

EDIT: ignore that, I found the problem.

Kulitorum

Any progress?

Kulitorum

whosrdaddy

I believe @dc42 fixed this problem in 2.0RC5...

Kulitorum

Just tested RC5, the missing axis problem has been fixed.

Thanks

Michael

dc42

Thanks for confirmation.