Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Change Log


GGraham
 Share

Recommended Posts

Is there a way to document your programming changes inside of mastercam.  For ISO we have to better our document and data control.  With this they are telling us we need to use a separate Excel spread sheet to document our programming changes. 

 

Thanks

Link to comment
Share on other sites

I would just put a revision at the top of the program. Every time you post it just update the rev (If you made a change of course). Then you are keeping track of the programs themselves, not the MC file. If you think about it, MC is just a tool to create the program, not the actual program...

 

As far your question goes...  I don't know.. Sorry!

  • Like 1
Link to comment
Share on other sites

For ISO, what is most commonly done for CNC/CMM programs is to do rev control/change logs of the posted code, and NOT the actual file- as Tinger mentioned above. A good ISO implementation of change control will shift the records requirements downstream to the simpler file to manage, and keep you from expending enormous amounts of effort for no reason. Remember, YOU write your ISO document control standards, so take some time to write them sensibly or they'll end up being a pile of rope long enough to hang yourself several times over.

  • Like 3
Link to comment
Share on other sites

Total BS and not required for ISO at all. A customer maybe demanding this specifically for their approval, but I doubt it.

I would have written in your procedures something like:-

 

Program Amendments

Amendments may be required for many reasons (part change, continuous improvement etc).
If it is deemed necessary to modify the program, it is changed by the following process;-

a) Edit the NC Program 
b) Run the part program to prove the amendment
c) ‘Cut metal’ to produce the part.
d) Verify it is correct by Inspection.
e) If correct, save the NC Program to the computer Network, overwriting the original.
f) Amend any associated documents (if necessary).

 

What I will add is:-

The above can only be done by approved people (your training matrix will show who is approved to do which tasks)

Within your procedure should (IMO) be a statement which says something along the lines that you have a folder called Customer Part Number and Revision, and within that is everything to make the part including an OOI (out of issue) folder, and within there, is the previous Revision folder with everything in there (including your old program).

So if you ever need to see changes, you can run file compare to see.

HTH

 

 

  • Like 1
Link to comment
Share on other sites

I added this process to the post at one place years ago.

# mr9 - Control Program Revision A to Z control in the post.
#       0 = N/C
#       1 = A
#       2 = B
#       26 = Z
#
# mr10 - Customer Selection output when posted.
#       0 = ADD CUSTOMER
#       1 = BOEING
#       2 = FUJI
#       3 = LEFIELL
#       4 = GE AEROSPACE
#       5 = MITSUBISHI
#       6 = SPIRIT
#       7 = GOODRICH LANDING
#       8 = ROCKWELL COLLINS
#       9 = SPIRIT
#       10 = D.O.D.
#       11 = LOCKHEED
#       12 = VOUGHT
fstrsel smon00 month$ smonth 13 -1
# --------------------------------------------------------------------------
# Customer selector
scust0   : "ADD CUSTOMER"
scust1   : "BOEING"
scust2   : "FUJI"
scust3   : "LEFIELL"
scust4   : "GE AEROSPACE"
scust5   : "MITSUBISHI"
scust6   : "SPIRIT"
scust7   : "GOODRICH LANDING"
scust8   : "ROCKWELL COLLINS"
scust9   : "SPIRIT"
scust10  : "D.O.D."
scust11  : "LOCKHEED"
scust12  : "VOUGHT"
scust : ""

fstrsel scust0 mr10$ scust 13 -1
# --------------------------------------------------------------------------
# Program Rev Complience with Boeing/Spirit MBD Requirements
sr00  : "N/C"
sr01  : "A"
sr02  : "B"
sr03  : "C"
sr04  : "D"
sr05  : "E"
sr06  : "F"
sr07  : "G"
sr08  : "H"
sr09  : "I"
sr10  : "J"
sr11  : "K"
sr12  : "L"
sr13  : "M"
sr14  : "N"
sr15  : "O"
sr16  : "P"
sr17  : "Q"
sr18  : "R"
sr19  : "S"
sr20  : "T"
sr21  : "U"
sr22  : "V"
sr23  : "W"
sr24  : "X"
sr25  : "Y"
sr26  : "Z"
srev : ""

fstrsel sr00 mr9$ srev 27 -1
prdbcustp
     *scust

psrev
     *srev
      "(PROGRAM NAME - ", sprogname$, ")", e$
      "(CUSTOMER     - ", prdbcustp, ")", e$ # Added RDB
      "(PART NUMBER  - ", smachgrp_name, ")", e$ # ADDED Roger Martin
      "(MODEL #      - ", smachgrp_name, ".CATPART)", e$ # Added RDB         
      "(PROGRAMMER   - RON B)", e$ # Added RDB
      "(DATE         - ", *smonth,"-",day$,"-",*year2,")", e$ #Date output as month,day,year - Ex. Feb. 12 2005
      "(TIME         - ",ptime,")", e$  #12 hour time output 3:52 PM
      "(PROGRAM REV  - ", psrev, ")", e$
      "(TOOL LIST)", e$ #Giving it a title 
      "(--------------------------------------------------------------------------)", e$
      spaces$ = 1

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...