Err 202 - Move < min time

Started by wallingd on Jul 24, 2019 in TinyG Support. 1 reply, last activity Jul 24, 2019.

wallingd Jul 24, 2019 #

Hi folks,

Doing intricate woodworking and getting the "Move < min time" quite a bit. Not concerned about part integrity and tinyg goes ahead and executes moves on okay (I'm sending via CNCjs, which doesn't ignore this error).

I saw Minimum Segment Time ($ms) here:
https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97

and I'm running Build 440.20 and firmware 0.97, but $ms is not recognized.

Wondering if anyone has run into this and come across a solution. With intricate pieces it's impossible to take you're eye off the box.

Thanks in advance.

cmcgrath5035Staff Jul 24, 2019 #

The comment here suggests that attempting changes to $ms will likely have negative impacts.

Is your Gcode created in inch or mm? Inch moves create some inaccuracy dues to conversion calculations, you could try mm but doubtful it will help.
You could also try turning off arc (G2 and G3 moves), which will generate just linear moves with different computations but nearly identical results.

It sounds like your Gcode is unnecessarily detailed, can you dial back the precision in the Gcode generator or it's post processor?

This topic is from the original forum (July 2019). Your reply starts a new discussion linked to it.

Different problem? Ask a new question