Quantcast
Channel: PC-DMIS User Forum - Forums
Viewing all 11658 articles
Browse latest View live

Hard coding (I think?) Question...

$
0
0
Hello

CAD 2018R2 SP4.....

I have auto circles that all share the same centroid...I'd like to "construct" the points FROM these auto circles together to create ONE constructed circle.

I know about the "to points" option...but I don't want to use that. I was once shown a method where you measure the auto features..select the auto featres for construction...PC DMIS gives you an error message but will still put the invalid constructed feature in your edit window..then you type something like "numpnts.." It was called "hard coding" when it was shown to me.I was only exposed to it briefly & that was a long time ago..can someone help me out?

Please see code below.



Code:
            MOVE/CLEARPLANE
CIR3       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,OUT,LEAST_SQR
            THEO/<0,0,0>,<0,0,1>,1.7848,0
            ACTL/<0,0,0>,<0,0,1>,1.7848,0
            TARG/<0,0,0>,<0,0,1>
            START ANG=-30,END ANG=30
            ANGLE VEC=<1,0,0>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              NUMHITS=4,DEPTH=0,PITCH=0
              SAMPLE METHOD=SAMPLE_HITS
              SAMPLE HITS=0,SPACER=0
              AVOIDANCE MOVE=NO,DISTANCE=0.3937
              FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
            SHOW HITS=YES
              HIT/BASIC,<0.7879,-0.419,0>,<0.8829476,-0.4694716,0>,<0.7879,-0.419,0>
              HIT/BASIC,<0.8806,-0.1447,0>,<0.9867615,-0.1621779,0>,<0.8806,-0.1447,0>
              HIT/BASIC,<0.8806,0.1447,0>,<0.9867615,0.1621779,0>,<0.8806,0.1447,0>
              HIT/BASIC,<0.7879,0.419,0>,<0.8829476,0.4694716,0>,<0.7879,0.419,0>
            ENDMEAS/
CIR4       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,OUT,LEAST_SQR
            THEO/<0,0,0>,<0,0,1>,1.7848,0
            ACTL/<0,0,0>,<0,0,1>,1.7848,0
            TARG/<0,0,0>,<0,0,1>
            START ANG=30,END ANG=60
            ANGLE VEC=<1,0,0>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              NUMHITS=4,DEPTH=0,PITCH=0
              SAMPLE METHOD=SAMPLE_HITS
              SAMPLE HITS=0,SPACER=0
              AVOIDANCE MOVE=NO,DISTANCE=0.3937
              FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
            SHOW HITS=YES
              HIT/BASIC,<0.7568,0.4729,0>,<0.8480481,0.5299193,0>,<0.7568,0.4729,0>
              HIT/BASIC,<0.6769,0.5815,0>,<0.7585136,0.6516572,0>,<0.6769,0.5815,0>
              HIT/BASIC,<0.5815,0.6769,0>,<0.6516572,0.7585136,0>,<0.5815,0.6769,0>
              HIT/BASIC,<0.4729,0.7568,0>,<0.5299193,0.8480481,0>,<0.4729,0.7568,0>
            ENDMEAS/
CIR5       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,OUT,LEAST_SQR
            THEO/<0,0,0>,<0,0,1>,1.7848,0
            ACTL/<0,0,0>,<0,0,1>,1.7848,0
            TARG/<0,0,0>,<0,0,1>
            START ANG=60,END ANG=90
            ANGLE VEC=<1,0,0>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              NUMHITS=4,DEPTH=0,PITCH=0
              SAMPLE METHOD=SAMPLE_HITS
              SAMPLE HITS=0,SPACER=0
              AVOIDANCE MOVE=NO,DISTANCE=0.3937
              FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
            SHOW HITS=YES
              HIT/BASIC,<0.419,0.7879,0>,<0.4694716,0.8829476,0>,<0.419,0.7879,0>
              HIT/BASIC,<0.2954,0.8421,0>,<0.3310634,0.9436085,0>,<0.2954,0.8421,0>
              HIT/BASIC,<0.1652,0.877,0>,<0.1850949,0.9827206,0>,<0.1652,0.877,0>
              HIT/BASIC,<0.0311,0.8919,0>,<0.0348995,0.9993908,0>,<0.0311,0.8919,0>
            ENDMEAS/
CIR6       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,OUT,LEAST_SQR
            THEO/<0,0,0>,<0,0,1>,1.7848,0
            ACTL/<0,0,0>,<0,0,1>,1.7848,0
            TARG/<0,0,0>,<0,0,1>
            START ANG=90,END ANG=120
            ANGLE VEC=<1,0,0>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              NUMHITS=4,DEPTH=0,PITCH=0
              SAMPLE METHOD=SAMPLE_HITS
              SAMPLE HITS=0,SPACER=0
              AVOIDANCE MOVE=NO,DISTANCE=0.3937
              FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
            SHOW HITS=YES
              HIT/BASIC,<-0.0311,0.8919,0>,<-0.0348995,0.9993908,0>,<-0.0311,0.8919,0>
              HIT/BASIC,<-0.1652,0.877,0>,<-0.1850949,0.9827206,0>,<-0.1652,0.877,0>
              HIT/BASIC,<-0.2954,0.8421,0>,<-0.3310634,0.9436085,0>,<-0.2954,0.8421,0>
              HIT/BASIC,<-0.419,0.7879,0>,<-0.4694716,0.8829476,0>,<-0.419,0.7879,0>
            ENDMEAS/

Scan point vectors not normal to the surface

$
0
0
Hello,

I`m trying to measure line profile of a feature. I`m using section scan to generate points from the cad (touch-trigger probe). So in the beginning of the scan everything looks fine but somewhere in the middle the tip does clearly not move perpendicular to surface when taking points. It gets so bad that the tip is basically "skiding" on the surface (at about 45 degrees angle). And it gets better in the end of the scan again.
I tried to use individual vectorpoints in tha same area (of the surface) and the situation is practicaly the same.
The results show that the profile is within 0.04 mm tolerance.
What could cause this? Any ideas?

BR,
Peter

Perimeter Scanning

$
0
0
Can someone please give me some pointers on perimeter scanning? I'm trying to scan the perimeter of this part. Thanks. Click image for larger version

Name:	5165T54P01.PNG
Views:	45
Size:	66.4 KB
ID:	443400

Custom interface - Reporting

$
0
0
I am working on a custom GUI that will run PC-DMIS. It is a simple (open program, run program, close program) interface designed to keep operators away from the code. I am developing in VB.NET. When it comes time to showing/printing the report, I take advantage of the OnEndExecution event and use the ReportWindow object method PrintReport. I am not seeing any report, even when I run PC-DMIS as Visible. Does anybody know how to force the report on the screen through scripting/VB.NET?

Grapically show point on live view

$
0
0
Does anyone know of a way to grapically show point on live view.

using .all from a scan to create a point.

$
0
0
So, I have a scan (F23), which I'm trying to extract the point that equates to the max X value.
Code:
ASSIGN/V1=F23.HIT[MAXINDEX(F23.HIT[1..F23.NUMHITS].X)].XYZ
this works perfectly, with the .xyz suffix, but I want Theo's and vectors applied to a generic point.

looking at help file, they added .all to the assignment id for some reason, and of course applied .all to the end.
Code:
ASSIGN/V1.ALL=F23.HIT[MAXINDEX(F23.HIT[1..F23.NUMHITS].X)].ALL
if I push this into a generic feature, the results don't populate like I presume they should.
Code:
F26        =GENERIC/POINT,DEPENDENT,CARTESIAN,$
            NOM/XYZ,<V1.TX,V1.TY,V1.TZ>,$
            MEAS/XYZ,<V1.X,V1.Y,V1.Z>,$
            NOM/IJK,<V1.TI,V1.TJ,V1.TK>,$
            MEAS/IJK,<V1.I,V1.J,V1.K>
2018R1 SP5, if that may have a contribution here...

What am I doing wrong, to keep the .ALL from working in the generic?

Grouping Features Together

$
0
0
Anyone ever use "GROUPS?"
I sometimes have a lot of similar features that I would like to group together and collapse
so that my programs will be shorter.
needing to know how to get it to work.
I've typed in "Group" and tabbed over then at the end of what I'm wanting to group
I've also keyed in "EndGroup" and then chose "NO" on both for show all.
but It's not working.
Think I'm missing something simple here.
Thanks

Nominal profile shift

$
0
0
So I created two different scans (two individual areas of a "complex" surface) and out of those two scans I created a single "compound" scan with Cosntructed Set Feature (the aim is to create the common zone condition as per ISO 1101). The scans are all on one plane (section scan). I dimensioned the compound scan with Line Profile , first with Profile Only+ Use Best fit and then with Form and Location.
I thought that if you use Profile Only + Use Best Fit, then it will move (translate&rotate) the tolerance zone to best accomodate the points inside the zone. But. If now I create the Form and Loc additionaly, I can see that the black line that should represent the nominal profile frome the CAD, has also moved slightly ??? Why is that??? Why is everything moving.

BTW I`m using the prehistoric 3.7 MR3.

BR,
Peter

Scripting for 'to points'

$
0
0
Good Morning

I have several linear scans that I would like to break the hits out of into individual points. I was aware that there might be a script that was able to do this?

I have been searching on and off for a hour now and don't seem able to find it.

Does anybody out there know if this script still exists and if it does where might I be able to find it?

Thanks in Advance





Scanning along a IGES defined Curve

$
0
0
I'm working on a program that needs to follow a variable helix groove. The customer only provided a CAD file that contains a line defining the root of groove. It's contained in an IGES file. I don't have much experience with advanced scanning, and I'm having problems figuring out how to use this geometry to drive the scan.

Essentially what I'm looking for is to make a scan that follows the root profile of the groove and report profile of a line on the report.

Getting the alignment to their datums isn't an issue, as I've put their provided geometry into a solidworks model i've drawn from their print. Any help would be great.

Screenshot of the IGES drawing:

Click image for larger version

Name:	groove gmty.jpg
Views:	18
Size:	8.6 KB
ID:	443459

Quindos Training Class

$
0
0
Anybody been to the Level 1 Quindos training class? I am scheduled to go to RI in March. Just looking for some input as to how it went.


Thanks.

missing window

$
0
0
this will be an easy fix for someone out there but it's driving me nuts.

during DCC mode, my window that prompts "take 3 hits...blah etc" is missing. Please tell me how to bring that back.

thanks in advance

saving all the data

$
0
0
hello everyone i was asked to look in to saving each part run as its own serial number for ex. part#_Rev_001 reasoning being we are a aerospace job shop with a few production jobs running long term my boss would like me to be able to edit the part run as if it was saved and copied for every part up to a point in case of a rev. change, and then is there a way to say only save a 100 and then start over

Min of Multiple Dimensions

$
0
0
My print calls for the surfaces of four bosses be co-planar within .010 TIR. So I would like to have PC-DMIS calculate the Min and Max and output a report comment with the difference between the min and max. Thanks!

Datapage+ 2011 mr1 Error

$
0
0
Get the following error with a new install of Datapage+ onto a Windows 10 machine. Any thoughts would be extremely helpful.

" The version of target database (V4.36) does not match the requested (V4.25), please upgrade your application. "

Rookie analog scanning question

$
0
0
How do you make the scan path contact the part if it's a lesser material condition than expected? My probe is missing the part by about .002 while performing a defined path perimeter scan, but when using normal TTP and honoring the check distance results come out in tolerance. Looking for the equivalent of a check distance while an analog scan...

Qualify long/thin probes on Global S

$
0
0
I'm setting up several project part programs here in Vietnam which was running on a ZEISS CMM with Q7 back home before.

I have big problems with long/thin probes, for example 3.5mm ball, 2mm shaft and around 100mm long.
Calibration itself is working, but when rechecking on the reference sphere it always give me an "Invalid reading of the measured point" error.
I tried lower the max. force and probing speed with only mixed results (very often still get that error).

I discovered that the weight balance may be off in Z -0.01 to -0.02 after 1-2 minutes after each probe change:

Click image for larger version

Name:	Probe_deflection.png
Views:	20
Size:	126.5 KB
ID:	443514
If I turn OFF/ON probing now manually it will reset weight balancing and the probes would work (until next change only).
The probe rack is also aligned 100% (~0.01 deviation between all of them).

Have anyone suggestions how to get this problem solved?

Here's my configuration:

Hexagon Global S 12.15.10
Controller Type „Common”
FirmwareId: FDC
FirmwareVersion: 14.01/14.02

ProbeHead MT5/HP-S-X5
Quindos V7.13.17317 R3

Standard probing parameter in Q7:

Click image for larger version

Name:	Machine_parameters.JPG
Views:	11
Size:	29.2 KB
ID:	443515
Anyone with PC-DMIS parameter may also help me, as they can be calculated to Q7 parameters as well...

Article 4

$
0
0
I think I may have an addition to the "to points" script that was generously posted some time ago.
the one limitation that it had was in the case of features that had several layers of points like cylinders.

using the original script I added some code to pull in the layers as well as the number of hits.

'================================================= ==========================
' To Points
'
' Extracts hits from features And creates vectorpoints With
' the hits THEO's.
'
' The names are created from the source feature Name And a number that
' represents the hit index.
'
' Idea taken from 'to_points.exe' from the Wilcox Script Repository

'================================================= ==========================

Sub Main()
Dim PCDApp, PCDPartPrograms, PCDPartProgram, PCDCommands, PCDCommand
Dim PCDFeatCmd
Dim prbhit
Dim numhits, numlevels, totalhits As Integer

Set PCDApp = CreateObject("PCDLRN.Application")
Set PCDPartPrograms = PCDApp.PartPrograms
Set PCDPartProgram = PCDApp.ActivePartProgram
Set PCDCommands = PCDPartProgram.Commands

Dim cmd As Object
Dim Fcntr As Integer
Dim FeatureList$(999)

Dim hX As Double, hY As Double, hZ As Double, hI As Double, hJ As Double, hK As Double

Dim MyList$ (10)
MyList (0) =612
MyList (1) =615
MyList (2) =616
MyList (3) =614
MyList (4) =617
MyList (5) =618
MyList (6) =605
MyList (7) =619
MyList (8) =613
MyList (9) =602
MyList (10) =596

Begin Dialog DIALOGNAME1 60,60, 240, 184, "Select constant name or value"
ComboBox 14,10,64,150, MyList$(), .Combo1
CancelButton 174,164,40,12
OKButton 26,164,40,12
Text 88,20,121,12, "CONTACT_CIRCLE_FEATURE"
Text 88,28,121,12, "CONTACT_CONE_FEATURE"
Text 88,36,121,12, "CONTACT_CYLINDER_FEATURE"
Text 88,44,121,12, "CONTACT_LINE_FEATURE"
Text 88,52,121,12, "CONTACT_PLANE_FEATURE"
Text 88,60,121,12, "CONTACT_SLOT_ROUND_FEATURE"
Text 88,68,121,12, "CONTACT_ANGLE_POINT_FEATURE"
Text 88,76,121,12, "CONTACT_SLOT_SQUARE_FEATURE"
Text 88,84,121,12, "CONTACT_SPHERE_FEATURE"
Text 88,92,121,12, "CONTACT_VECTOR_POINT_FEATURE"
Text 88,100,121,12, "CONST_SET"

End Dialog

Dim Dlg1 As DialogName1
Dlg1.Combo1 = "Select Feature Type"
button = Dialog( Dlg1 )

'***** Predialog START
Fcntr = 0
' Enumerate commands
For Each cmd In PCDCommands
' Autofeature (flagged As DCC feature)
If cmd.Type = Dlg1.Combo1 Then
FeatureList(Fcntr) = cmd.ID
Fcntr = Fcntr + 1
End If
Next cmd
'*****

'***** Dialog START
Begin Dialog DIALOG_2 31,48, 172, 387, "Feature to points"
ListBox 68,8,96,368, FeatureList$(), .ListBox
PushButton 8,120,52,12, "To points", .PointsBtn
PushButton 8,304,52,12, "Cancel", .CancelBtn
End Dialog

Dim Dlg2 As DIALOG_2
button = Dialog( Dlg2 )
' button 1 = To points, button 2 = Cancel
'*****

'***** Vectorpoint generation
If button =2 Then
GoTo Label1
End If
Fcntr = 0
If button = 1 Then
Set PCDCommand = PCDCommands.Item(FeatureList(Dlg2.Listbox))
Set PCDFeatCmd = PCDCommand.FeatureCommand
numhits = PCDCommand.GetText(N_HITS, 0)
numlevels = PCDCommand.GetText(N_ROWS, 0)
totalhits = numhits * numlevels
Set prbhit = CreateObject("PCDLRN.PointData")

For Fcntr = 1 To totalhits
' Get the probehits - XYZ
Set prbhit = PCDFeatCmd.GetHit(Fcntr, FHITDATA_CENTROID, FDATA_THEO, FDATA_PART, AlignID, PLANE_TOP)
hX = CDbl(prbhit.X)
hY = CDbl(prbhit.Y)
hZ = CDbl(prbhit.Z)
' Get the probehits - IJK
Set prbhit = PCDFeatCmd.GetHit(Fcntr, FHITDATA_VECTOR, FDATA_THEO, FDATA_PART, AlignID, PLANE_TOP)
hI = CDbl(prbhit.X)
hJ = CDbl(prbhit.Y)
hK = CDbl(prbhit.Z)
' Create vectorpoints
Set cmd = PCDCommands.Add(602, True)
cmd.Marked = True
'Featurename is "sourcefeaturename-hitnumber" -> PLANE1-1
retval = cmd.PutText (PCDCommand.ID & "_" & Fcntr, ID, 0)
'Theo's
retval = cmd.PutText (hX, THEO_X, 0)
retval = cmd.PutText (hY, THEO_Y, 0)
retval = cmd.PutText (hZ, THEO_Z, 0)
retval = cmd.PutText (hI, THEO_I, 0)
retval = cmd.PutText (hJ, THEO_J, 0)
retval = cmd.PutText (hK, THEO_K, 0)
'Targ's
retval = cmd.PutText (hX, TARG_X, 0)
retval = cmd.PutText (hY, TARG_Y, 0)
retval = cmd.PutText (hZ, TARG_Z, 0)
retval = cmd.PutText (hI, TARG_I, 0)
retval = cmd.PutText (hJ, TARG_J, 0)
retval = cmd.PutText (hK, TARG_K, 0)
cmd.ReDraw
PCDPartProgram.RefreshPart

Next
End If
'*****
Label1:
'***** Cleanup
Set PCDApp = Nothing
Set PCDPartPrograms = Nothing
Set PCDPartProgram = Nothing
Set PCDCommands = Nothing
Set prbhit = Nothing
'*****

End Sub

Article 3

$
0
0
Okay ... I understand, thank you.

How do I start a new thread?

Unable to move path lines.

$
0
0
I am trying to use autocone and the probe hits the part at start and finish of measurement. I am unable to put a move command in and when I click on the path line the little box does not appear to let me adjust the path. What is going on??
Viewing all 11658 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>