Does Centroid CNC (or Acorn) keep track of jobs?
My old software did, and it included start time/date, end time/date, total time and machine time.
It was super handy. I found myself checking it often to see what my guys were up to when I was gone and also to check actual cutting times to help with my estimating. It seems like it would be a very basic feature. Is it saving this data and it's just a matter of knowing how to access it?
Thank you!
Job History
Moderator: cnckeith
-
- Posts: 25
- Joined: Thu Oct 26, 2023 2:14 pm
- Acorn CNC Controller: No
- Plasma CNC Controller: No
- AcornSix CNC Controller: No
- Allin1DC CNC Controller: No
- Hickory CNC Controller: No
- Oak CNC controller: No
- CNC Control System Serial Number: none
- DC3IOB: No
- CNC12: No
- CNC11: No
- CPU10 or CPU7: No
Job History
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Re: Job History
No, but if you have control of your G codes (i.e. your postprocessor) you could make it do that yourself.
See M120, M121, M223, M127 and similar codes.
You could use M121 open a common log file and add to the end of it.
You can use M223 and literal text from the postprocessor to insert the job name.
You can use M127 to insert the date and time.
You will probably want to wrap your start-of-job logging codes all up in one subprogram or M function; and wrap up the end-of-job logging codes in another; then just call those subprograms or M functions from the main CNC job (perhaps having stored the job name in a #300-series string variable). That will make the programs more concise, and will make it easier to skip over the logging during Search and Graph operations.
See M120, M121, M223, M127 and similar codes.
You could use M121 open a common log file and add to the end of it.
You can use M223 and literal text from the postprocessor to insert the job name.
You can use M127 to insert the date and time.
You will probably want to wrap your start-of-job logging codes all up in one subprogram or M function; and wrap up the end-of-job logging codes in another; then just call those subprograms or M functions from the main CNC job (perhaps having stored the job name in a #300-series string variable). That will make the programs more concise, and will make it easier to skip over the logging during Search and Graph operations.
1 user liked this post
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 25
- Joined: Thu Oct 26, 2023 2:14 pm
- Acorn CNC Controller: No
- Plasma CNC Controller: No
- AcornSix CNC Controller: No
- Allin1DC CNC Controller: No
- Hickory CNC Controller: No
- Oak CNC controller: No
- CNC Control System Serial Number: none
- DC3IOB: No
- CNC12: No
- CNC11: No
- CPU10 or CPU7: No
Re: Job History
Thank you!
I had hoped that Centroid might have already done that, but I guess it will be good learning experience for me.
I had hoped that Centroid might have already done that, but I guess it will be good learning experience for me.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 725
- Joined: Fri Nov 30, 2018 1:04 pm
- Acorn CNC Controller: Yes
- Plasma CNC Controller: No
- AcornSix CNC Controller: No
- Allin1DC CNC Controller: No
- Hickory CNC Controller: No
- Oak CNC controller: No
- CNC Control System Serial Number: none
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
- Location: Thorp WI
Re: Job History
Here are a couple of links to some related info where I was working on some part file logs that I've implemented in my post processor for Vectric products.
viewtopic.php?f=60&t=2973&hilit=log
viewtopic.php?f=60&t=3008&hilit=log+29953
viewtopic.php?f=60&t=2973&hilit=log
viewtopic.php?f=60&t=3008&hilit=log+29953
Scott
(Note: Liking will "up vote" a post in the search results helping others find good information faster)