Nico Tonnhofer

@ me Not that big issue. Precalculate `F_CPU * F_CPU / (ACCELERATION * STEPS_PER_M_X)` and then it's just: ``` static const axes_uint32_t PROGMEM temporal_const_P = { (uint32_t)((double)F_CPU * F_CPU *...

> Unless I'm mistaken, you apply the same acceleration to each individual axis here. The math is really simple in it. Take the fast axis. Accelerate it by its constant....

This part of Teacup could become some kind of a unique feature in the current reprap community. I just started with it. A first fast duty test with temporal/schoolphysics/dda_clock only...

Just a short sentence for the first post. Hardware-Debugging >> all. Short delays is everything < 160 not 100. I made some measurements and it took 130 to 152 cycles...

I start counting in `timer_set()` [just before](https://github.com/Traumflug/Teacup_Firmware/blob/arm-stm32f411-port/timer-arm_stm32f4xx.c#L177) the if statement and stop couting in the IRQHandler [just after](https://github.com/Traumflug/Teacup_Firmware/blob/arm-stm32f411-port/timer-arm_stm32f4xx.c#L135) `queue_step()`.

> Is testing four 32-bit values against zero that much work? Well, I'm little bit unsure from where to where I should measure. The part between while(set_timer()) and unstep() is...

While looking again into the temporal code because I what to work with the TODO: ``` // TODO: instead of calculating c_min directly, it's probably more simple // to calculate...

Verified. Fix comes soon.

@Traumflug you can pick https://github.com/Traumflug/Teacup_Firmware/commit/ae2604cccd6afd and maybe also https://github.com/Traumflug/Teacup_Firmware/commit/848825b35. Ramps for temporal are not final working.

When you have a lot time while traveling to work, you could get nice ideas. I think I can introduce ramps and lookahead soon to acceleration temporal. :)