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

Article 2

$
0
0
does anybody know how to make the image full screen in the comment box. i already checked the display full screen box. but my image comes out small. I would like to see full screen.Click image for larger version

Name:	Capture.JPG
Views:	2
Size:	24.6 KB
ID:	437750

enlarging photo on operator comment box

$
0
0
whats good everyone...
so I've ran programs before that have the display full screen image actually full screen. I would like to see my setup photo on the comment/operator/display full screen/ actually full screen
this is how my looks like right now... Click image for larger version

Name:	Capture.JPG
Views:	2
Size:	24.6 KB
ID:	437757
.
.
.would anybody be able to help me out making the image larger...

Not reading variables/assignments in program

$
0
0
We have one CMM running V2011MR1 and there is code at the beginning of each program for operator inputs to set what needs to be done. We have 3 other B&S CMMs running V4.3MR1 that we have never had an issue with this and this code has been used for along time before I got here. We can run programs all day long on this CMM then out of the blue it will not read the variable/assignment or it will not run according to the operator input. The only way I have found to clear this so it will work correctly is to reboot the PC.

Several things to know. This is on a new CMM with a Win10 box and V2011MR1 is running in compatibility mode.

I'm open for any suggestions

Code:
MENU       =LABEL/
MENU_SELECT =COMMENT/INPUT,NO,'1 - Probe Calibration
                             ,2 - Setup Information
                             ,3 - Manual Alignment
                             ,4 - Program Execution
                             ,5 - Quit'
            IF/MENU_SELECT.INPUT==1
            GOTO/PROBE_QUAL
            END_IF/
            ELSE_IF/MENU_SELECT.INPUT==2
            GOTO/SETUP_INFO
            END_ELSEIF/
            ELSE_IF/MENU_SELECT.INPUT==3
            GOTO/MANUAL_ALGN
            END_ELSEIF/
            ELSE_IF/MENU_SELECT.INPUT==4
            GOTO/EXECUTE
            END_ELSEIF/
            ELSE_IF/MENU_SELECT.INPUT==5
            GOTO/QUIT
            END_ELSEIF/
            ELSE/
            GOTO/MENU
            END_ELSE/
$$ NO,===============================================================
     ,PROBE QUALIFICATION
     ,===============================================================
PROBE_QUAL =LABEL/
            MODE/DCC
            LOADPROBE/5606_135_2
            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
                          SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,150>
            MOVE/INCREMENT,<0,200,0>
            PRINT/REPORT,EXEC MODE=END,$
              TO_FILE=OFF,PROMPT,$
              TO_PRINTER=OFF,$
              TO_DMIS_REPORT=OFF,FILE_OPTION=OVERWRITE,FILENAME=,$
              REPORT_THEORETICALS=NONE,REPORT_FEATURE_WITH_DIMENSIONS=NO,$
              PREVIOUS_RUNS=DELETE_INSTANCES
            EXTERNALCOMMAND/NO_DISPLAY, NO_WAIT ; C:\PROBES\5606_135_2.BAT
            MODE/MANUAL
            GOTO/MENU
$$ NO,===============================================================
     ,SETUP INFO
     ,===============================================================
SETUP_INFO =LABEL/
            COMMENT/OPER,NO,
                           ,
                           ,PROGNAME
                           ,Program Name:
                           ,Seed Program
                           ,"PART # " + PARTNUM
                           ,To Inspect:
                           ,PART # none
                           ,
                           ,You Need:
                           ,- 2mm x 40mm styli  
                           ,- Use fixture for scalloped Ø 10.9mm stem.
                           ,Insert part into fixture so the stem locking detail os the front
                           ,of the CMM and the offset head detail is aligned up / down
                           ,below the body of the stem
                           ,
                           ,Click "OK" when ready to continue
                           ,
                           ,
$$ NO,**************************************
     ,**************************************
     ,*****Setup picture link goes here*****
     ,**************************************
     ,**************************************
            GOTO/MENU
$$ NO,===============================================================
     ,MANUAL ALIGNMENT
     ,===============================================================
MANUAL_ALGN=LABEL/
            LOADPROBE/5606_135_2
            TIP/T1A90B180, SHANKIJK=0, -1, 0, ANGLE=180
            PREHIT/ 2
            RETRACT/ 2
            CHECK/ 3,1
            COMMENT/OPER,NO,
                           ,
                           ,Set the part into the fixture with the tapered end at 67mm
                           ,from the front side if the fixture
                           ,
                           ,Place probe at center and in front of
                           ,part head detail
                           ,
                           ,Click "OK" when ready.
                           ,
                           ,
READPOINT  =FEAT/POINT,CARTESIAN
            THEO/<ZERO,ZERO,ZERO>,<ZERO,ZERO,ONE>
            ACTL/<240.113,204.154,-570.034>,<0,0,1>
            READPOINT/
MAN_ALN1   =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
            ALIGNMENT/TRANS,XAXIS,READPOINT
            ALIGNMENT/TRANS,YAXIS,READPOINT
            ALIGNMENT/TRANS,ZAXIS,READPOINT
            ALIGNMENT/END
ZLIN       =GENERIC/LINE,DEPENDENT,CARTESIAN,$
            NOM/XYZ,<0,0,0>,$
            MEAS/XYZ,<0,0,0>,$
            NOM/IJK,<ZERO,ZERO,ONE>,$
            MEAS/IJK,<ZERO,ZERO,ONE>,$
            DISTANCE/0,0
            MODE/DCC
CIR_ST1    =FEAT/CONTACT/CIRCLE,CARTESIAN,OUT,LEAST_SQR
            THEO/<0,0,0>,<0,-1,0>,7.25,0,0,0
            ACTL/<0,0,0>,<0,-1,0>,7.25,0,0,0
            TARG/<0,0,0>,<0,-1,0>
            ANGLE VEC=<1,0,0>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=NO
MAN_AL     =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
            ALIGNMENT/TRANS,XAXIS,CIR_ST1
            ALIGNMENT/TRANS,YAXIS,CIR_ST1
            ALIGNMENT/TRANS,ZAXIS,CIR_ST1
            ALIGNMENT/END
            MOVESPEED/ 80
            MOVE/POINT,NORMAL,<0,-10,100>
            MOVE/POINT,NORMAL,<0,200,300>
$$ NO,************************************
     ,************************************
     ,*****Manual Alignment goes here*****
     ,************************************
     ,************************************
            GOTO/MENU
$$ NO,===============================================================
     ,EXECUTION INFORMATION
     ,===============================================================
EXECUTE    =LABEL/
JOBNO      =COMMENT/INPUT,NO,'
                            ,
                            ,Job Number
                            ,
                            ,'
STATSNO    =COMMENT/INPUT,NO,'
                            ,
                            ,What is the Stats Count?
                            ,
                            ,'
OPID       =COMMENT/INPUT,NO,'
                            ,
                            ,Operator I.D.
                            ,
                            ,'
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; Inspector : OPID.INPUT
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; Job Number : JOBNO.INPUT
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; Serial No : STATSNO.INPUT
$$ NO,===============================================================
     ,DCC INSPECTION
     ,===============================================================
            COMMENT/OPER,NO,==================================
                           ,READY FOR DCC INSPECTION 
                           ,==================================
                           ,
                           ,"Part # : " + PARTNUM
                           ,
                           ,Click "OK" when ready to continue
START_DCC  =LABEL/
            MOVESPEED/ 80
            LOADPROBE/5606_135_2
            TIP/T1A90B180, SHANKIJK=0, -1, 0, ANGLE=180

Global License

$
0
0

Hello guys,

we have 6 licenses online and 1 offline license, somebody know if hexagon allow a global license Price to a Company? Because in our case in some Country the yearly cost to maintain the license updated is 5000$ and in another country is around 3000$, my boss asked me to fix it and wants a standard cost in all countries, like a global license for our company.
Somebody know if is it posible to do it?

We contacted with our local hexagon provider and told us that is imposible to do it, but in a globalized world seems irreal, in the same way maybe in some country we can purchase some pc_dmis license more cheap than another countries. Somebody know some case?

Thank you

Using MSE with GD&amp;T selection

$
0
0
Hi,

I have set my preferences in the measurement strategy editor, but when I use GD&T selection, it just uses the standard strategy.. When I dont use GD&T selection, then I get the strategy from Measurement strategy editor.

does the GDT selection not work together with the measurement strategy editor?? That would be strange, because then you would still have to check every feature for the correct strategy :S

Finding spline issue

$
0
0
Hello.

Using Quindos 7 with gear pack. I am trying to fix a recurring issue with an existing program.

The part is a cylinder with a flange at one end, the flange is comprised of four pads, each with a hole through. The cylinder has an internal 39 tooth spline shaped through it. The pitch diameter of the spline is datum A. The surface on each pad of the flange is datum B. The program then uses a rotation between one of the holes and datum A. All these features, plus the pitch of the spline, are probed with the single 1mm stylus with no issue.

The program then pulls in a 4 way stylus with 4 x Ø1mm tips, each at 90° which each have a very short stem, approx. 4mm. This is used to check the profile and helix. This tip will now crash at the gear command, even if I have find activated. When attempting to find the gear, it will generally take 1 point, then take an unusual path, skipping past 4 or 5 teeth and crashing into the spline in a diagonal path. I have never had any real issues with the find gear before this. It is using the same alignment and same SETCMPAR as the pitch gear command. The machine has been qualified.

Is there anything I could be missing here?

Also, I was attempting to scan the spline to find a valley, then rotate to it to try running the gear command with the new alignment to figure if there is something suspect with the probe configuration / parameters etc. I used ME2DE to scan a segment of the spline, however I'm not sure how to extract points from the scan. I would like to extract the point with the highest X value, this would equal the valley, then use COLPTS to create a line between -A- and the extracted point. If everything is where it is meant to be, the gear command should run in this alignment.

How do I extract the point with the highest value in X from the scan?

Thanks.

Boundary Option in Position Dimension Window

$
0
0
Hello All

Could you be so kind and explain me how "Boundary" option in Position Dimension window works when a slot with M related to the three datums is selected, please? I have an idea how Planar Zone works when it is selected, but no idea what an algorithm is doing with Boundary option.

Thank you in advance to all!

Probe Not going Home

$
0
0
I am using PC Dmis 16 and all of a sudden when I make my program and use the auto wrist feature to get all my probe angle. Then I go and calibrate all the ones I am using. When the probes switch angle it goes up and rotates and going through the calibration. One it has calibrated the probes I want it all of a sudden goes straight to the Table! I have not changes anything that i am aware of and it is fine as it rotates between angles. It is the the very last move before completing the calibration it BOOM crash into the table and will not complete the calibration.

Thank you for the Help!

Probe readouts seem off

$
0
0
I just homed my machine through pc dmis.

So when I start a new program I open a new and the readouts are almost at zero - which is what I would expect

When I open a program that is giving me problems calibrating the probes It opens and the readout is 143 in X 271 in Y and -77 in Z


I have not moved the probe at all. What could cause this.

PCDMIS 2015 nominal change will not save.

$
0
0
Upgraded to PCDMIS 2015 a year or so ago & I have noticed on some parts when I try to update a nominal & save it it changes back. Is there a setting causing changes to not save somewhere?

Datapage Refresh Rate

$
0
0
Thought I'd use Datapage to manually input a single callout in a 30 part study. Setup the PCD 2018r1 program to feed Datapage 5.2. Ran through my 30 single callouts. Datapage only recorded 5. So, I set the refresh rate to 1 second, so as to have it keep up with my lightning like data entry. Nope. Only caught 5, again.

But now that Dp is set to refresh at one second, I can't change it back ( its in :tools - manual ( or ) automatic )

I did a reload of DP.
I did an un-install, download and reload.

Still can not alter the refresh rate back to, say 30 seconds.

My work is piling up. - I have an SMA - no response for two days, now.

What to do?

Running selected steps

$
0
0
Hello,
this is a problem that i've just recently stumbled, (upgraded to pcdmis cad++ 2017 R2 SP 10) there are times when we just need to run certain points of a program, ot maybe a hole wasnt perfectly clean and need to reinspect it, so we would go to the summaty mode screen, and with the Ctrl key pressed select the desired commands we needed (see screenshot) and press Ctrl L to run just that, now it wants to run everything in between, is there a new shortcut keys to run?

Dimension diameter to bottom of radii

$
0
0
I need to dimension a diameter to the bottom most part of several radii, as crudely shown on the attached. Ideas?
Click image for larger version

Name:	scallops.jpg
Views:	1
Size:	23.7 KB
ID:	437840

Datum definition axis vs. surface

$
0
0
Hello PC-Dmis magicians!!

How do I tell PC-Dmis whether I want the axis or the surface of an zylinder as the datum definition?

Help me please...need variable expression

$
0
0
I will be the first to admit that I am not up to using expressions. Have this situation where I need to measure a depth of a ring groove and subtract a known radius value from the measured z value. Not enough room to create a radius at the bottom or I'd use that route. Basically I am looking for a Assign V1/ option to let me take the measured pnt.z and subtract a radius .022 and use that value to define a distance from point to surface. Any help is most appreciated. Thanks in advance.

Radius Mathemagics

$
0
0
edit: To clarify things, this is a "1" point measurement of any radius joining two tangent and straight faces.
Rarely does a drawing give coordinate data for radius features, but with this math it is not needed as long as the two tangent faces can be measured/determined. 1 point is taken on the mid line of the two faces to determine the excosec and a little bit of algebra later you have a radius.
Click image for larger version  Name:	New Bitmap Image.jpg Views:	1 Size:	12.5 KB ID:	437876

Code:
$$ NO,
      ASSUMPTION: BOTH FACES ARE CO-TANGENT TO RADIUS
      edit: i suppose the second assumption would be "the radius has perfect form"
$$ NO,
      Two line measurements are taken.
            One on either tangent of the corner radius with
            vectors pointing towards the radius being measured.
            The vector nominals in the command block screw with
            the construction of LIN3, otherwise the code as is would not
            matter what orientation it is in.
            (wont be a problem in real program)
            Could probably fix with expressions in vectors
            Manual mode for demonstration purposes only.

LIN1       =FEAT/LINE,CARTESIAN,UNBOUNDED
            THEO/<18.839,0,10>,<1,0,0>
            ACTL/<-119.063,-114.215,11.302>,<0.4934556,0.869771,0>
            MEAS/LINE,2,ZPLUS
              HIT/BASIC,NORMAL,<18.839,0,10>,<0,1,0>,<-119.063,-114.215,11.337>,USE THEO=YES
              HIT/BASIC,NORMAL,<108.2,0,10>,<0,1,0>,<5.926,106.092,11.266>,USE THEO=YES
            ENDMEAS/
LIN2       =FEAT/LINE,CARTESIAN,UNBOUNDED
            THEO/<100,-103.413,10>,<0,1,0>
            ACTL/<121.972,-136.12,11.265>,<-0.4351452,0.9003603,0>
            MEAS/LINE,2,ZPLUS
              HIT/BASIC,NORMAL,<100,-103.413,10>,<1,0,0>,<121.972,-136.12,11.265>,USE THEO=YES
              HIT/BASIC,NORMAL,<100,-23.975,10>,<1,0,0>,<17.756,79.513,11.265>,USE THEO=YES
            ENDMEAS/
            MODE/DCC
$$ NO,
      Construct the point of intersection

PNT1       =FEAT/POINT,CARTESIAN,NO
            THEO/<100,0,10>,<1,0,0>
            ACTL/<5.377,105.125,11.284>,<0.4934556,0.869771,0>
         CONSTR/POINT,INT,LIN1,LIN2
$$ NO,
      Construct a mid line to use for vectors on pnt2.

LIN3       =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
            THEO/<54.527,-45.473,10>,<0.7071068,0.7071068,0>
            ACTL/<-2.198,-124.836,11.284>,<0.0329234,0.9994579,0>
         CONSTR/LINE,MID,LIN1,LIN2
$$ NO,

      This constructed line isnt necessary and could be removed.
            A replacement could be the use of ANGLEBETWEEN()
            but the result would need converted back into vectors.
            Dont care enough to do that atm.
            Something with UNIT() maybe. note to self, wtf is CROSS(,)

            CHECK/100,1
            TOUCHSPEED/ 20
            PREHIT/2
$$ NO,
      Flip pnt2 vector expresions to negative and add a large
            complimentary PREHIT distance if you would like this
            to measure inside rads
            ... pretty sure that should do it.

PNT2       =FEAT/POINT,CARTESIAN
            THEO/<120,0,10>,<LIN3.I,LIN3.J,LIN3.K>
            ACTL/<3.513,48.49,11.281>,<0.0329234,0.9994579,0>
            MEAS/POINT,1,WORKPLANE
              HIT/BASIC,NORMAL,<PNT1.X,PNT1.Y,PNT1.Z>,<LIN3.I,LIN3.J,LIN3.K>,<3.513,48.49,11.281>,USE THEO=YES
            ENDMEAS/
            CHECK/0,1
DIM LOC1= POSITION OF POINT PNT2  UNITS=MM ,$
GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=NONE  FIT TO DATUMS=OFF  DEV PERPEN CENTERLINE=OFF  DISPLAY=DIAMETER
AX       MEAS    NOMINAL       +TOL       -TOL      BONUS        DEV     OUTTOL
X       3.513  PNT1.X                                      -1.864          
Y      48.490  PNT1.Y                                     -56.635          
TP    113.331        RFS  80085.000                 0.000    113.331      0.000 -------->
END OF DIMENSION LOC1
$$ NO,
      LOC1 is only used to get the distance from the intersecting point
            to the measured point. However, loc1.tp.meas will always return
            the diametric true position even if you change the display to radius.
            Divide by 2

RAD1       =GENERIC/CIRCLE,DEPENDENT,CARTESIAN,OUT,$
            NOM/XYZ,<0+0,0+0,0+0>,$
            MEAS/XYZ,<PNT2.X+(-LIN3.I*RAD1.RADIUS),PNT2.Y+(-LIN3.J*RAD1.RADIUS),PNT2.Z>,$
            NOM/IJK,<0,0,1>,$
            MEAS/IJK,<0,0,1>,$
            RADIUS/0,(LOC1.TP.MEAS/2)/((1/SIN(DEG2RAD(ANGLEBETWEEN(LIN1.IJK,LIN2.IJK))/2))-1)
$$ NO,
      ^^The Bees Knees^^

            That Parenthesis Pasta is ugly but it still works.

            In the pursuit of visually displaying the radius in the correct position,
            I have accidently measured the center of the radius as well. No, I dont know
            why a feature referencing itself works.

DIM LOC2= LOCATION OF CIRCLE RAD1  UNITS=MM ,$
GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH  HALF ANGLE=NO
AX       MEAS    NOMINAL       +TOL       -TOL        DEV     OUTTOL
R       49.163  RAD1.RADIUS  ****  ****      0.000      0.000 #--------
END OF DIMENSION LOC2
$$ NO,
      was getting measurements under .001" deviation

            Id give her a +/- .002" accuracy.
            (as a complete guess, haven't done study yet)
            Should be most accurate at 90 degrees total angle
            with exponential increase in error at both limits.
            Smaller internal angle will be affected by line measurement acc.
            Larger internal angle will be affected by rad point measurement acc.
            Outside radius should be slightly more accurate for smaller -wait... no one cares

Reminder to save prompt

$
0
0
We all know ctrl+s is are best friend but even then we forget to use it. Solidworks has a neat feature where if you haven't saved while working on a document in a set duration "20min" a small notification pops up in the corner reminding you that you haven't saved in set time. Does anyone know if PC-DMIS has something similar?

PCD2Excel not exporting concentricity

$
0
0
I'm having issues getting concentricity to export using PCD2Excel. I'm using PC-DMIS Version 2014 service pack 5. I have other programs that report this dimension but for some reason I can't figure out why this isn't being exported. The screen shows that it is while exporting but the excel file does not contain the data.

Thank you,
Kevin

CMM and Vision System Correlation

$
0
0
Good Morning,

I would like to start a discussion in regards to CMMs and Vision Systems and trying to correlate between the two.

Basically what im wondering is, realistically, how close should you be able to get data to match between a CMM and a Vision system.

Some more information...i work in plastics. Since i was sent to training at Hexagon my boss wants me to keep practicing on the CMM, so what we have been doing lately is when i get parts that need to be measured for a first article or whatever the case may be, 9 times out of 10 we will use our Vision system (Micro-Vu Vertex 220). But what my boss has been having me do first so i can get more practice is first write a program on the CMM and then write a program on the Vertex, we are doing this, 1) to get me more practice on the CMM and 2) to gain confidence in our numbers.

So again what im wondering is how close, REALISTICALLY, should i be able to get the two machines to correlate. For example, two critical dimensions im measuring are a hole to hole which is 2.577" ±.005" and a line to line dimension which is 4.234" ±.005". On the CMM i am getting roughly 4.228 and some change, and on Vision roughly 4.227 and some change. For the other dimension, on the CMM i am getting roughly 2.577 and on Vision 2.575.

So the biggest range being ~.002", is that pretty bad? Or is that relatively good correlation between the two technologies?

What would you people suggest is a good range to aim for? Should i be aiming for dead on? Or close? And which number would you trust the most?

THANKS!

Comment Box Behavior

$
0
0
I have 3 comment boxes at the start of a program. Each requires a different input.
Upon execution, the boxes are already populated with the previous entry from the previous run.
Is there a way to have the comment box show up empty so that the operators must input a new (ie. current) value?
Viewing all 11658 articles
Browse latest View live


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