hexagon logo

Adding tracefield on subsequent run

If one adds a tracefield for Job number on a subsequent run to the same part number, Does datapage update for the original run?
  • If one adds a tracefield for Job number on a subsequent run to the same part number, Does datapage update for the original run?

    NOPE, but it WILL 'add' the tracefield to the database so you can edit it in in DPEditor for that previous run.
  • Serialization restarts at #1 for each lot and I am intending on entering the job number (which seperates the lots) to give it the seperation, Will this work?
    I F'in hope so. (Monday ugh)
  • Serialization restarts at #1 for each lot and I am intending on entering the job number (which seperates the lots) to give it the seperation, Will this work?
    I F'in hope so. (Monday ugh)

    Yes, sort of.

    When using a tracefield to sort data, you MUST create a QUERY (in Dpeditor) for each tracefield and tracefield value. So, yes, you can do it. You can create the query at any time and you can add them later.

    So, you will have a tracefield "JOB_NUMBER" and a value, lets say 12345 (for job #12345). You run the parts. You make a QUERY called 12345, select the TRACE NAME of JOB_NUMBER set the OPERATOR to "=" and enter the trace value (12345). Now, no matter WHAT data "part" the info is stored under, you select QUERY 12345 and it will ONLY show the data for JOB_NUMBER 12345 (tracefield) that has been saved.

    Did ya follow that?

    Then, anytime you add a new JOB_NUMBER, you add a new query for it and BINGO!, Bob's yer Uncle.
  • Thanks Matthew> Anyway can I enter the Job number at the start of the program and not wait till it hits the stats on Command? I know the tracefield must be after the stats on command just hope there is a work around to get it in at program start.
  • Thanks Matthew> Anyway can I enter the Job number at the start of the program and not wait till it hits the stats on Command? I know the tracefield must be after the stats on command just hope there is a work around to get it in at program start.

    Well, you can put the stats-on command ANYWHERE in the program, as LONG AS IT IS BEFORE the first thing you want sent to the stats. I always put my stats-on right at the beginnning of the program.

    STARTUP    =ALIGNMENT/START,RECALL:, LIST= YES
                ALIGNMENT/END
                MODE/MANUAL
                PREHIT/ 4
                RETRACT/ 4
                MOVESPEED/ 80
                TOUCHSPEED/ 1
                LOADPROBE/27577
                TIP/T1A0B0, SHANKIJK=0, 0.047, 0.999, ANGLE=0
                FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, , 
                PROBECOM/ON
                WORKPLANE/XPLUS
                STATS/ON,DATAPAGE,$
                DIRECTORY=G:\DATAPAGE\PART,$
                DIRECTORY=,$
                READ=10,WRITE=20,MEMPAGES=64,FEATURE NAME,CONTROLCALC ON,$
                STATS/END
    put tracefield here
                RECALL/ALIGNMENT,EXTERNAL,alignlh02,27577-LH:alignlh02
                MODE/DCC
    
  • Thanks again Matt> Does the tracefield show up in the ASCII dump even thou the query for it has been, as of yet, set-up in the DPeditor?
  • Thanks again Matt> Does the tracefield show up in the ASCII dump even thou the query for it has been, as of yet, set-up in the DPeditor?

    The tracefield will "appear" just like any other data in Datapage when you dump the ASCII file. So, all the tracefield data will dump in the ASCII file just like the individual data does. The QUERY will not show up in the ASCII file since it is part of the DATABASE and NOT of any individual part in the database.
  • In addition, a new tracefield can be added directly in DPeditor.
  • In addition, a new tracefield can be added directly in DPeditor.


    The tracefield will "appear" just like any other data in Datapage when you dump the ASCII file. So, all the tracefield data will dump in the ASCII file just like the individual data does. The QUERY will not show up in the ASCII file since it is part of the DATABASE and NOT of any individual part in the database.


    Thanks Guys