You are not logged in.
TIP: create directory and admin group for machine & control files
This is to ensure that no one accidentally overwrites machine & control files
(1) Create a Main Vericut Machines directory
(2) Create sub-directories for each machine, where you store all the files for that machine.
(3) Set up a Group call Vericut administrators, or whatever, using the operating system commands, and have read / write access for only those in that group
All other Users can read, but not write.
Of course, anyone can info> file summery> copy all files
then they can change at their own risk. But there should be no need to.
By building automation into the machines, like head changers, and commands to point the 90 heads in the proper angle, etc. there should be no reason to change a machine or control, except to enhance it.
I also write protect the files, so I don?t step on my own foot.
If I need to enhance it, I make a copy before I give myself write access
Those in the Vericut administrators group must have good programming habits like making copies of machine and control files before changing anything.
Cgtech has done a very good job separating what goes into machine files, and what goes into usr files, so the same machine can be used for infinite jobs.
Offsets, initial machine position, collision detection settings, are all stored in the user file
The only thing I have found that our programmers were changing in the machines is component visibility.
to see how I get around this, See:
http://cgtech.com/forum/viewtopic.php?t=384
:wink:
Have fun
Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."
Offline