FILE LOG of opened or machined files

[Guenter_Schmied]

(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

[cncdrive]

Guenter,

You could write a plugin to log the file datas.
There are 2 plugin templates in the plugins folder, one in C# and the other in VB language.
To write a plugin like this you only have to add some code to the button call event.
You can add a check there to see if the Load file button was pressed and then wait while the file gets loaded and then write some text in a log file.
We could also add it as an integrated UCCNC feature. We also planning to add a detailed debugging option, but the details are not worked out yet.

[Robertspark]

I think I can write a macro loop for you which will do what you want.... Let me have a go this evening....

[Robertspark]

Macroloops placed here in the toolbox thread...

http://www.forum.cncdrive.com/viewtopic.php?f=15&t=671

Let me know if you need anything else...

[Guenter_Schmied]

Hi CNcdrive, Hi Robert,

Many thanks for your answers !

Yesterday I wrote a macro for myself that writes down all the names of files used in a ..txt file
(Robert I used your example of writing TXt in one of your entrys in this forum!)
Then I replaced the button of LoadFile withanew button and the same Icon.
this button does 2 things , it calls Loadfile and writes simultaneously the name of the current
file to the LOG TXT file.
It was no need to make a macro-loop.

I recommend as a possibility for future versions of UCCNc,
cause we used this feature with date and time stamp, in another
CNC controller, and was very useful as history of parts.

It can be used also to create a control of production sheet /report -and history of files machined adding
any necessary info to it. Since it is a Txt file, it can be imported easily to Excel.

In my case is practicall to have this, because if I am machining 4 or 5 different parts each day,
after 4 days I can not recall which one is which.

Regards
Guenther

[Robertspark]

No problem, but with the macroloops you do not need to modify the button for loadfile,

Just load the macroloop and it will log when you open a file and when you run the file.

The problem with uccnc (as I am learning) is every time there is an update of the software the screenset can change and is being developed, hence using another profile or screenset other than the default one means your screenset is stagnant so as things like tool offset compensation come on line which will require things like tool diameter to be added , these will not be available in your screenset (and therefore not saved to the profile to celebrate called and used via macros or plugins)

I try to avoid altering the default screenset and am looking for ways that the run screen can be changed once (centrally) if you need a custom screenset.

Honestly... I'd use the macroloop m1003.txt in the other link if I were you... Forget changing buttons.

[Guenter_Schmied]

excellent ! thank u !