Topics created by CaiJonas

@CaiJonas @dc42 has replied with the following regarding hiccups and late steps:

Re hiccups, in 3.5 and earlier the number displayed is the number of delays introduced by the board that is reporting during its generation of step interrupts. A hiccup is inserted when the ISR has been looping for more than a particular amount of time because additional step keep becoming due.
In 3.6 the main board M122 report shows two values. The first is hiccups introduced while preparing moves for execution. These should be rare. The second is hiccups generated in the step ISR as before.
In 3.6 two figures are also shown for total hiccup duration in milliseconds. The first is for hiccups introduced by the reporting board; the other is for hiccups introduced by other boards.

Regarding the "max steps late" figure, when RRF calculates when the next motor step is due, it checks that the calculated time is no later than the time at which the current move segment is supposed to be complete. Due to floating point rounding error, it sometimes happens that the calculated time is slightly later than the intended segment completed time. RRF generates any such steps at the intended segment completed time, and records how many steps it needed to generate to complete the segment. It's normally only the vary last step of the segment that is "late" in this way, so maxStepsLate is typically 1, although it may be 0 if there has not been much movement.

So it's the hiccup figure we need to keep an eye on, and 'max steps late 1' is generally okay.

@CaiJonas said in Bug on 3.6.0? Layershifts & stuttering on arc travel moves:

Is there any option to manipulate the segmentation of duet3d firmware? As I understood the firmware itself generates short segmets out of g2/g3 code?

Yes, with M669 S and T parameter (see https://docs.duet3d.com/User_manual/Reference/Gcodes#m669-set-kinematics-type-and-kinematics-parameters). However, it can't make longer moves out of short segments, it can only split up long moves into shorter segments. Yes, the firmware generates short, straight segments from G2 and G3 arcs. The minimum arc segment length was reduced in RRF3.5.1 from 0.1mm to 0.02mm. I think it also scales with the radius of the arc.

Ian

@CaiJonas both (a) and (b) will work. If you are using G30 to set Z=0 then don't use S-2 or S-3 in the G30 command. See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#description-3.

You need to go to the Machine Settings page and a tab for accelerometer will be there.

@jay_s_uk can you post your config please. Also if possible try a simple hollow cube to see if that also displays the issue please.

@caijonas said in Acclerometer on a Delta printer:

Is it possible to eleminate more than one frequenzy? E.g. M593 P1 F30 F60?

Also interested in that... is it even possible, and will it be in 3.4 firmware?

Pin one is oriented to the lower right corner in that picture, yes, and should line up with the dot on the new chip. (oh, and good job!)

661e5e4c-4d12-4301-8f09-c87495f01226-image.png

"ups, my bad. Where can I find it?" found it, thanks

@Tinchus Yes the extrusion needs to happen on a combined XY move.

G91
G1 X100 Y100 E50

for example.

I changed the idler pulleys to printed ones and as aspected, the artifact are less visible and look different. So I have to change the pulleys. They have a wobble. Thanks guys, I will try the ones from robotdigg.

@DocTrucker
Thanks for your advice. I installed an shielded stepper wire without grounding it and now it works great.

@dc42 Thanks, that was it what I was looking for