Nico Tonnhofer

You could upload your gcode with gist. so I could check your code. How do you create the gcode? In Slic3r e.g. you can explicitly teacup as gcode version.

GCC

No, just test it. This won't work. In some cases the CCR1 is that much bigger, that `(uint32_T)CNT - (uint32_T)CCR1 + 100 > delay`. But in this case we don't...

I need some time for cleaning the mess on my desktop. But I will upload the code soon. :)  ![screenshot at 2016-08-01 18 49...

Yes, you are right. I have some ideas. The problem seems to be occur only at the first step. Thanks for pointing me in the right direction!

Looks like the issue is only on my STM. When CCR1 is

> How is CCR1 > 0xFFFFFFFF? Is it a 64-bit variable? Ah sorry. Correct it to '

I opened a new branch: https://github.com/Traumflug/Teacup_Firmware/tree/acc_temporal This is currently on experimental + some stm32 and other stuff. I will rebuild this later on the current experimental. Because the current code...

Uh... Not that slow as I thought. The issue is different. ``` dda->step_interval[axis_to_step] = dda->step_interval[axis_to_step] - (dda->step_interval[axis_to_step] * 2) \ / ((4 * (dda->delta[axis_to_step] - move_state.steps[axis_to_step])) + 1); ``` This...

Traumflug: > you should do all these calculations in dda_clock() Wurstnase: > only every 1-2ms Sure :) School physics looks like simple, but currently I can't see any benefit: ```...