Your Products have been synced, click here to refresh
You will need to control it with a variable. This if grouping will exist within the loop itself.
If loop=="1"
assign/Edit_Val={original value here}
Endif
If loop=="2"
assign/Edit_Val={change val}
Endif
Once you complete the loop run, the scan data will only represent the last measured unit. It doesn't store the part1 data for you to manipulate after.
I would recommend 2 separate scans, you can control which one runs using the if style I previously shared.
If you want independent ability to rerun aspects of your program file, it may make more sense to have individual sections of code.
However, if you want to be able to rerun segments for part1 vs part2, you may need to look into flow control (IF_GOTO/labels). The problem you may face is that you will not rerun the scan to the identical datum pick up 1 run to the next, it should be a small amount of deviation, but it will be deviation none the less.
Paste w/ Pattern is a built-in feature with PC-DMIS, so that is not a bad practice. Just be sure to have an indexable value at the end of every feature you are copy/pasting to prevent archaic naming from occurring to your freshly pasted features. (I add '_1' to every feature/alignment I plan to use paste w/ pattern on, if reporting/constructing features later in the program, it is now very easy to find which points go together to build/report)
I suppose in rereading this, you could potentially store the alignment for part1 as an 'external' alignment, then save part2 as another 'external' alignment, using the flow control (IF/ENDIF) you can manage which alignment should be used and recall them explicitly. I believe this would enable you to remeasure a scan, but it would cause a restructure of your current program.
Loop processes do not lend themselves to be helpful when you need to rerun a specific feature for anything other than the last unit.
IF_GOTO/lables can enable you to jump through your program isolating only the data you need to remeasure. This could be something to speed up your over-checks, but it takes a great deal of forethought and architecture in your program.
Paste w/ Pattern is a built-in feature with PC-DMIS, so that is not a bad practice. Just be sure to have an indexable value at the end of every feature you are copy/pasting to prevent archaic naming from occurring to your freshly pasted features. (I add '_1' to every feature/alignment I plan to use paste w/ pattern on, if reporting/constructing features later in the program, it is now very easy to find which points go together to build/report)
I suppose in rereading this, you could potentially store the alignment for part1 as an 'external' alignment, then save part2 as another 'external' alignment, using the flow control (IF/ENDIF) you can manage which alignment should be used and recall them explicitly. I believe this would enable you to remeasure a scan, but it would cause a restructure of your current program.
Loop processes do not lend themselves to be helpful when you need to rerun a specific feature for anything other than the last unit.
IF_GOTO/lables can enable you to jump through your program isolating only the data you need to remeasure. This could be something to speed up your over-checks, but it takes a great deal of forethought and architecture in your program.
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |