exporting x,y,z values from points inside an analog scan

[charliejoe]

I need some help from people smarter than myself, i have linear open scan that is created on both sides of the wall of the part, and i need to export the location of each of 30 points in the scan, in order to see how the wall of the part is wearing under use. how do i write the code so it pulls the xy location of these points inside the scans? then what do ii need to be able to report them?

[louisd]

I would do something like this (pseudocode as I'm typing it from scratch, not near a pdcmis seat)

assign/count=1
assign/endcount=SCN1.numhits +1
do/
--(construct generic point PNT1)
---in PNT1, define all XYZ and IJK Theo and Measured values with the following:
SCN1.hit[count].TX,SCN1.hit[count].TY,SCN1.hit[count].TZ,
SCN1.hit[count].X,SCN1.hit[count].Y,SCN1.hit[count].Z,
SCN1.hit[count].TI,SCN1.hit[count].TJ,SCN1.hit[count].TK,
SCN1.hit[count].I,SCN1.hit[count].J,SCN1.hit[count].K,

Dim output location of PNT1
output x
output y
output z

assign\count=count+1
until/ count==endcount

your dim output should have labels that serialize the points with the hit number in brackets PNT1[1], PNT1[2], PNT1[3] etc...

[JEFMAN]

Another way is creationg a COP from the scan, then export it as a xyz file...

[Ego Murphy]

I need some help from people smarter than myself, i have linear open scan that is created on both sides of the wall of the part, and i need to export the location of each of 30 points in the scan, in order to see how the wall of the part is wearing under use. how do i write the code so it pulls the xy location of these points inside the scans? then what do ii need to be able to report them?

Your post contains two different approaches:

need to export the location of each of 30 points in the scan

and

need to be able to report them

But you also mentioned the core end-goal:

in order to see how the wall of the part is wearing under use

Always focus on the end-goal and make decisions based on that, don't get lost in the technical twists and turns of methods that may not get you there with a win.
The end-goal is reporting wall wear under use.

Right away, PC-DMIS sucks as it only generates a report for each program run: it cannot collect and compare historical data.
PC-DMIS can only use CAD surface or simple geometry (flat plane or circle/cylinder) for nominal, not imported text XYZIJK, when reporting deviation. This means each iteration of the wear test measurement can only show the current state of deviation from CAD nominal, so you would have to collect the individual reports in order to try and demonstrate the wear trend (good luck with an audience who can't read CMM reports...).

You can also export the measured data straight to an IGES file, import it into CAD system, and do comparisons there. Maybe the CAD software you (or your coworkers) are using is brilliant at making snazzy colorful screen-dumps showing the wear trend, maybe it sucks, but it's a valid method.

However, if you export the XYZ data into text as shown above ( props to louisd and JEFMAN ) then you can dive into the fun world of graphing in Excel where you can burn super amounts of time up creating beautiful color graphs flawlessly communicating the wear trend to all audiences.

[Kp61dude!]

Always focus on the end-goal and make decisions based on that, don't get lost in the technical twists and turns of methods that may not get you there with a win.

You're going to explode the wisdometer with this one!

[JEFMAN]

Ego Murphy : if you create the first scan as "master", isn't it a way to compare directly ? (not sure, I'd never tried, but Ithought it was made for it...)

[Ego Murphy]

Ego Murphy : if you create the first scan as "master", isn't it a way to compare directly ? (not sure, I'd never tried, but Ithought it was made for it...)

There really should be, unfortunately the Wilcox Wizards hard-coded in some sort of smoothing algorithyms that modify the "Master" scan by not-user-changeable parameters.