Hello Guest it is May 25, 2019, 01:56:17 AM

Author Topic: Why does the roadrunner.tap have an M99 at the end?  (Read 1317 times)

0 Members and 1 Guest are viewing this topic.

Why does the roadrunner.tap have an M99 at the end?
« on: March 12, 2015, 07:56:42 PM »
Hi Folks,

starting to get the hang of this finally and I've managed to get my mill to run roadrunner.tap and get the expected results.
But I'm curious as to why the gcode has an M99 at the end.

It makes the entire file run again from the top.
Wouldn't an M30 be more appropriate or is it looping for a reason?

I don't have an endmill in place yet, just a pen, so maybe it's increasing in depth or something but it doesn't look like it is.

I think once I get all this sorted I'll write some simple calibration gcode files for beginners. I know I would have loved to have found some.
Although, now I've mentioned it, someone will probably point me to some.  ;)

Online Tweakie.CNC

*
  • *
  •  7,765 7,765
  • Super Kitty
    • View Profile
    • Tweakie.CNC
Re: Why does the roadrunner.tap have an M99 at the end?
« Reply #1 on: March 13, 2015, 03:27:52 AM »
I think it was used as a Demo at events promoting Mach4 so it was convenient to have it re-run in an endless loop.

Tweakie.
Success consists of going from failure to failure without loss of enthusiasm.  Winston Churchill.
Re: Why does the roadrunner.tap have an M99 at the end?
« Reply #2 on: March 14, 2015, 12:40:25 AM »
Thanks Tweakie.CNC It's always good to know I'm actually learning and that something did, indeed, make sense.