Open propcoder opened 8 years ago
Your guess about the interpretation of "G1 F10000" is approximately on target; the preview and bounds calculations assume that the start of a program is a number of preparatory G0 moves, which fully establish the starting coordinates; otherwise, some arbitrary value (possibly the origin of the active coordinate system?) is used instead.
Note that in linuxcnc there is no problem programming an F-number even when the active motion mode is G0 or G80, so if you can change your post to say "F10000" instead of "G1 F10000" you may be happier with how the preview and bounds check behave.
Revamping this code so that it does "something smarter" when the program doesn't start with a series of G0 moves that fully establish the starting position is a topic for development, unfortunately not a simple bugfix.
LinuxCNC 2.7.7
Steps to reproduce the issue: