Hello Guest it is April 20, 2024, 02:00:37 AM

Author Topic: Time estimation until next Tool Change  (Read 8739 times)

0 Members and 1 Guest are viewing this topic.

Re: Time estimation until next Tool Change
« Reply #10 on: November 15, 2011, 09:09:42 PM »
Tip: If you will make it a HABIT after loading your gcode file into Mach3, to navigate to the Toolpath Screen, and click on Simulate Program Run you can get a fairly accurate estimate of time until the various tool changes (IF your CAM software has added comments in the gcode such as Roughing, Finishing, etc. at the location of the M3's) by watching the elapsed time in the Simulation text box. You have to watch the Status field at the bottom of the screen closely, and when you see the message change from Roughing Cut, to Finishing Cut IMMEDIATELY glance up at the Simulator text box to read the elapsed (estimated) time. It's not an exact method, but it will get you in the ballpark of estimating when the toolchanges will occurr. Just be sure to read the elapsed time IMMEDIATELY after the message changes in the Status field, because it continues to run the Simulation (and the elapsed time is still flying by). As I said, it's not exact. But it will get you within a couple of minutes of WHEN you need to be there. I still like the idea of a DRO box which gives you a count down to next tool change - Additionally, it would be nice if Mach3 also included a box which lists line numbers of all tool changes. In case of inacurate Re-Zero of the Z axis happens during a tool change (for quick reference of where to set next line to Run From Here, after subsequently correcting the Z Zero). For those of us not yet equipped with digital probes for setting the Z Zero......

Offline BR549

*
  •  6,965 6,965
    • View Profile
Re: Time estimation until next Tool Change
« Reply #11 on: November 15, 2011, 09:47:18 PM »
It is possible to do something like that now but it would be a bit cluncky.

The is a routine you can use to time the toolchanges as the program runs then store that time in a Gcode var in the program. Then when the M6 is triggered it starts a coutdown timer with the included time. As the Tool changes occur it constantly loads the next variable and continues.

Might not be perfect but it would work. Just depends on how many would actually use it.

(;-) TP
Re: Time estimation until next Tool Change
« Reply #12 on: November 16, 2011, 06:57:01 AM »
It think those are both good ideas for long programs.  It gives us a way to estimate it until maybe someday it is more automated.  Thanks guys.