PCM & Subsequent Evaluation

[[Ri...]]

I wrote a program that has X amount of groups of features, and inside of each group there are "check features" that probe around to find out which version this particular group belongs to (so essentially every group can be its own configuration of nominals). The PCM code lies in the pre-settings of the first measured feature after the check has been performed. Each group has its own PCM code.  

I'm trying to take measured points and perform some analysis offline, but the first issue that I'm running into is that it does not execute the pre-setting code, so it never does the comparisons to determine which configuration it is - it just leaves the values to what it set at the program level inside of the Parameters setting. 

Does anyone have a good way to force it execute the code again during Subsequent Evaluation?

[[Ch...]]

PCM does appear to behave a bit different offline and during subseq eval rather than online with a machine and during a CNC run.

Is there anyway you can have it read a file instead if machsn="000000" etc ?

 

Can you re-run with our clearing results instead of subsq eval ?

[[Je...]]

Is it the pre-setting of the group you are talking about?

If so, then your "check features" shouldn´t be inside the group, but before, because if they are inside the group, the pre-settings are executed before the "check features" run.

If you want to have them all inside a group, you can make something like a "master group" for the group with pre-settings and the "check features".

 

Alternatively you can do it like I do (works only while run from feature): set a theoretical feature (point in my case, but should work with every theoretical feature) where you need your code, and in the pre- or post-settings of this feature place your code. To get it executet, you need to place "addMe("feature1", "feature2"...)" in the pre-settings of your plan or in your "inspection_start_pcm.txt".

 

Edited Tuesday at 06:03 AM