hexagon logo
Register Sign in
  • Replies 21 replies
  • Subscribers 224 subscribers
  • Views 503 views
  • Users 0 members are here
Options
Related

Help guys!!!! 30pc study and runtime slowdown

Blackbowtie99
Ok here is my question, I have been given the task of running a 30pc study on a rear window of a car. Just explain our plant is an Auto glass supplier for North America. So these rear windows are put on a fixture that checks for curve and bend comparison between the pieces. Once we have a alignment established on the fixture using tooling balls. The glass will be placed on the fixture and ran using pre selected points on the glass surface in CAD so we can compare Nominal vs. Actuals after the run. Is there an easy way to run these 30pcs without separating the 30pcs into 30 different programs and report them separately. By doing it like this we have noticed the more pieces we ran the slower and slower the machine gets. By the time we get to 30th piece the probe may hover above the 1st data point for 3min before it starts running.

Machine: DEA Delta sp
PC-DMIS CAD++2013 MR1 (Release)
  • To skip doing manual alignment over and over.....I don't mess with IF/GO TO commands....I just highlight my manual alignment and hit F3......then just hit the execute button and it goes....
  • Ok here is my question, I have been given the task of running a 30pc study on a rear window of a car. Just explain our plant is an Auto glass supplier for North America. So these rear windows are put on a fixture that checks for curve and bend comparison between the pieces. Once we have a alignment established on the fixture using tooling balls. The glass will be placed on the fixture and ran using pre selected points on the glass surface in CAD so we can compare Nominal vs. Actuals after the run. Is there an easy way to run these 30pcs without separating the 30pcs into 30 different programs and report them separately. By doing it like this we have noticed the more pieces we ran the slower and slower the machine gets. By the time we get to 30th piece the probe may hover above the 1st data point for 3min before it starts running.

    Machine: DEA Delta sp
    PC-DMIS CAD++2013 MR1 (Release)

    You might get this if you run your program by some other method than 'File - Execute'. For example, if you use 'Run from Cursor' or 'Run from Startpoint' I believe the previous measurements are not cleared out and after your 30th measurement your program contains 30 sets of results hidden away somewhere. There is an option under the file menu to clear this (called 'Clear Execution List' or something like this. It is near the 'Execute' option in the menu.).
  • You might get this if you run your program by some other method than 'File - Execute'. For example, if you use 'Run from Cursor' or 'Run from Startpoint' I believe the previous measurements are not cleared out and after your 30th measurement your program contains 30 sets of results hidden away somewhere. There is an option under the file menu to clear this (called 'Clear Execution List' or something like this. It is near the 'Execute' option in the menu.).
    [/COLOR]

    There is a "Reset Execution List" option....is that it?
  • Guys thanks so much for all your input I will try a few of these options and let you all know my findings.
  • You might get this if you run your program by some other method than 'File - Execute'. For example, if you use 'Run from Cursor' or 'Run from Startpoint' I believe the previous measurements are not cleared out and after your 30th measurement your program contains 30 sets of results hidden away somewhere. There is an option under the file menu to clear this (called 'Clear Execution List' or something like this. It is near the 'Execute' option in the menu.).

    Yes, you have to add something like a dummy print/report command with previous runs delete instances. Although it may not always work
  • You might get this if you run your program by some other method than 'File - Execute'. For example, if you use 'Run from Cursor' or 'Run from Startpoint' I believe the previous measurements are not cleared out and after your 30th measurement your program contains 30 sets of results hidden away somewhere. There is an option under the file menu to clear this (called 'Clear Execution List' or something like this. It is near the 'Execute' option in the menu.).


    This was my guess. It looks like he's trying to run the program by "execute from cursor" instead of unmarking his manual alignment and executing the program.
  • [/COLOR]

    There is a "Reset Execution List" option....is that it?

    That is it.
  • That is it.

    This doesn't mess anything up does it....I mean...can you reset it anytime you want?......
  • This doesn't mess anything up does it....I mean...can you reset it anytime you want?......
    Depends on what 'mess anything up' means to you. Pcdmis keeps track of all commands that are executed. In the order they are executed. Performing an execute clears that list. If you stop execute, then start execute at a different location (execute from cursor), the prior commands executed are not cleared from that list. When you report, all items in the list are reported.

    If you want to report everything that was executed, the reset will 'mess things'. If you only want items that were executed from the cursor, reset first, then execute from cursor.
  • Depends on what 'mess anything up' means to you. Pcdmis keeps track of all commands that are executed. In the order they are executed. Performing an execute clears that list. If you stop execute, then start execute at a different location (execute from cursor), the prior commands executed are not cleared from that list. When you report, all items in the list are reported.

    If you want to report everything that was executed, the reset will 'mess things'. If you only want items that were executed from the cursor, reset first, then execute from cursor.

    I'll just leave it alone....hehehe
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement