Slowing down/plan ahead feature not working as well in 0.7 about repetier-firmware HOT 2 CLOSED

Hi,

the path planning is managed by these parameter:

/** \brief Number of moves we can cache in advance.

This number of moves can be cached in advance. If you wan't to cache more, increase this. Especially on
many very short moves the cache may go empty. The minimum value is 5.
/
#define MOVE_CACHE_SIZE 16
/ How many line segments can the path planner use for path optimization. The maximum possible
value is MOVE_CACHE_SIZE-2. Higher values need more computation time, which can cause blocking for many
short subsequent moves. If this happens you will see BLK messages in your log and then you now the
value is to high for your printer settings.
/
#define PATH_PLANNER_CHECK_SEGMENTS 12
/* \brief Low filled cache size.

If the cache contains less then MOVE_CACHE_LOW segments, the time per segment is limited to LOW_TICKS_PER_MOVE clock cycles.
If a move would be shorter, the feedrate will be reduced. This should prevent buffer underflows. Set this to 0 if you
don't care about empty buffers during print.
/
#define MOVE_CACHE_LOW 12
/* \brief Cycles per move, if move cache is low.

This value must be high enough, that the buffer has time to fill up. The problem only occurs at the beginning of a print or
if you are printing many very short segments at high speed. Higher delays here allow higher values in PATH_PLANNER_CHECK_SEGMENTS.
*/
#define LOW_TICKS_PER_MOVE 400000

Whats new is PATH_PLANNER_CHECK_SEGMENTS which limits the look ahead to x segments. Before it was simply the number of segments. Higher values give better look ahead with many short moves in a row. The main problem is, that computation time can increase significantly when increasing this value, so you get better look ahead but might get short stalls due to limited computation speed of the arduino. Especially samples like the one you said can get this problem, while most objects will have no problem. The problem gets worse with increasing print speed of course.

from repetier-firmware.

thanks I've managed to fix it now by tweaking these settings :)

from repetier-firmware.