You are not logged in.
Hello.
I would like it very much if I could add comments to the .mch, .ctl and .tls files. This way, I could leave explanations for myself as far as why I did what I did. Notes like this are always helpful at a later point in time.
Thank You,
Robert Davie
Offline
Yeeeeeeeeeesssssssssssssss
I bought a couple of machines from CgTech
The machine builder (from earth, + humanoid ) supplied a complete document of everything I wanted to know, but was afraid to ask.
Very well done
But,.... your idea came up.
a ER was submitted, but I guess other emergencies, took priority.
soooooooo
if anyone else likes this, pile on here.
:twisted:
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline
I know it does not address all you request, but I have seen a neet trick to keep track of changes in the control file.
in the Event > Start Of Processing, call the macro MessageMacro
In the override text, you can enter : name, date, latest changes, version, etc...
The message type is specified by the input numeric value. 1= Error, 2=Warning, 3= Info, 4= Debug, 5= Input, 6=Output, 7= Macro Modal, 10= Error Continuation
Offline
Hi Serge,
Thanks, your idea is a good start. To me, your idea is analgous to having a MACHIN card at the beginning of a nc program source file.
But, even when using a graphical programming tool like UG, I periodically add programmer's comments between sequences and operations in the UG operation navigator.
e.g. $$ This would be a comment in the source file.
Have a nice weekend,
Robert Davie
Offline
Agreed, there needs to be a way to comment .mch and .ctl files. Some of these are complex and not easily understood without documentation. We also need to keep a rev history of changes in the file.
Offline
I know it does not address all you request, but I have seen a neet trick to keep track of changes in the control file.
in the Event > Start Of Processing, call the macro MessageMacro
In the override text, you can enter : name, date, latest changes, version, etc...
The message type is specified by the input numeric value. 1= Error, 2=Warning, 3= Info, 4= Debug, 5= Input, 6=Output, 7= Macro Modal, 10= Error Continuation
If you want to do it just for documentation, You can add a Text Override field to the NullMacro.
Offline