FILE LOG of opened or machined files
Posted: Tue Jul 18, 2017 10:02 pm
(if this is already available in UCCNC, please forgive me...)
In a CNC controller of our company we used to have
a File log or list, it was only a txt file with a list
of all files opened and machined in our controller.
like that filelog.txt
content
mickymouse.nc 12/12/2015 08:15AM
pluto-xxx.nc 12/12/2015 13:30AM
minneyxxx.nc 04/03/2016 17:45PM
etc
etc
It was helpful in many situations, as a check for any problems in production
and also as a certification of machine use , it was helpful also for technicians
etc.
If this option would be available in UCCNC I also would be able to run a macro
that would navigate trought the top most used filenames / or the last used files
and have a fast start on machining jobs.
(Again It could be included an option in the "Appearance-tab" for this LOGbook filename,
and also the option to limit it to xxxx. number of entrys , or not)....
/// I suppose this could be resolved in form of a macro too, but as a User I do not
think any other way to implement this as a macro-loop, what would potentially
consume performance of g-code processing, polling all the time ... when it is not needed
It only must catch the file-open button -action, and only then write the result to the logbook file.
In case somebody knows how to this, I would be very grateful !
Best regards
MfG Guenther
In a CNC controller of our company we used to have
a File log or list, it was only a txt file with a list
of all files opened and machined in our controller.
like that filelog.txt
content
mickymouse.nc 12/12/2015 08:15AM
pluto-xxx.nc 12/12/2015 13:30AM
minneyxxx.nc 04/03/2016 17:45PM
etc
etc
It was helpful in many situations, as a check for any problems in production
and also as a certification of machine use , it was helpful also for technicians
etc.
If this option would be available in UCCNC I also would be able to run a macro
that would navigate trought the top most used filenames / or the last used files
and have a fast start on machining jobs.
(Again It could be included an option in the "Appearance-tab" for this LOGbook filename,
and also the option to limit it to xxxx. number of entrys , or not)....
/// I suppose this could be resolved in form of a macro too, but as a User I do not
think any other way to implement this as a macro-loop, what would potentially
consume performance of g-code processing, polling all the time ... when it is not needed
It only must catch the file-open button -action, and only then write the result to the logbook file.
In case somebody knows how to this, I would be very grateful !
Best regards
MfG Guenther