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

Reporting .. "0" in front of the decimal

$
0
0
I searched, I swear!
I'm exporting my reports as .cvs and then the results are dumped in to Discus and then uploaded to Net-inspect. I dimension using "Legacy".

I was told that I can't report having a "0" in front of the decimal as Net-inspect would bounce it. Example would be a measured value of .4500 is exported as 0.4500. They don't really want me going in and changing it manually, but that's what I'm doing now, removing the "0" when there is one in front of the decimal place.

Is there an "EASY" fix for this? Also, anyone familiar with Net-inspect, is this true?

Hexagon Sheet?

$
0
0
Quite a few years ago, Hexagon put out a sheet that stated where certain important files (tool.dat, toolc.dat, etc) were stored for each version of PCDMIS. Does anyone have a copy of this they could let me have? I had one and cannot locate it to save my life.

Thanks.

New to Fixtures

$
0
0
Hello!
Running PC-DMIS 2018 R2
--------------------------------------
I've got this subset of parts that requires a fixture in order to measure everything.

The fixture sticks into a horizontal rotary table, with a bolt through it to screw the part onto.

I've never done anything with a fixture before; I always just chuck the part in the rotary and start beeping.
I don't take any points on this fixture, I simply align to the part and start rotating.

I feel like I should be doing something? How can I make sure this is accurate?
Also, it causes a lot of tilt because of how little is actually grabbed; is there somewhere I can make or buy a fixture for it? I prefer something more precise...
--------------
Here's a quick explanation of how the "fixture" is;
It's nothing precision machined or fancy, literally a flat piece of metal, a threaded hole, a bolt, a washer, and a nut.
The rotary grips the nut, the part is screwed onto the bolt, and rests up against the flat metal piece. The washer is just a spacer

Article 1

$
0
0
Hello TWilton,

The company I work for is considering purchasing a Zeiss dual arm CMM with Caligo software. Another year or so has gone by since you posted in a discussion about Calypso vs. Pc-Dmis that your seat of Caligo is untouched. Is that still the case? If so, what software is running the machine that Zeiss provided Caligo for? What types of parts? Can you elaborate at all on what you don't like about Caligo or why it is not being used?

Many Thanks in Advance for your help.

By the way, if you know of anyone else who has used both Pc-Dmis and Caligo, please put me in touch with them.

-Wes

Slow Offline run

$
0
0
I have animation @ 100% when running my program offline, but it runs like it is set to 1%. The program runs fine online any reason or any oddball setting I'm missing here?
Thanks Crew

2018R1

Bonus on a threaded hole

$
0
0
How do you guys apply a bonus on threaded holes when allowed in true position? Is it the actual pitch diameter of the hole minus the MMC of whatever class thread is called out?

Offline programming question??

$
0
0
I am using PCDMIS 2017 R2. Sometime back when I first received the offline license and wrote programs I could see a virtual probe moving as the points where being take (running the program). Right now I can no longer see the probe at all and would like to know how to turn this feature back on; all help is most appreciated, thanks.

Attach External Part Program

$
0
0
I've tried this without much success in running a program offline. What I am trying to do is use one generic front end program for different CMMs, one with a TP20 and the other with the HP-S-X1H scanning probe, and I want the operators to use one program. I have the front end program set to read a text file with the CMM serial number that is on each hard drive and that will determine which program to run.

I'm running the front end program up to the point of saving the manual alignment externally, then attach the machine specific program after that. At the beginning of the attached program I recall that alignment.

When I execute the front end it goes through the motion of measuring the manual alignment then ends without opening and running the attached program. And I did verify the text file to be it was reading it correctly.

Code:
=LABEL/STARTUP    =ALIGNMENT/START,RECALL:,LIST=YES
            ALIGNMENT/END
$$ NO,========================================
     ,  PROGRAM HISTORY
     ,===========================================
     ,DATE Program Created by
$$ NO,=========================================
     ,CMM IDENTIFICATION
     ,============================================
FILE_CHECK =FILE/EXISTS,C:PC-DMIS V43CMMINFO.TXT
            IF/FILE_CHECK<>0
FILE_READ  =FILE/OPEN,C:PC-DMIS V43CMMINFO.TXT,READ
LINE1_READ =FILE/READLINE,FILE_READ,{line1}
            ASSIGN/CMM_NUMBER=LINE1
            FILE/CLOSE,FILE_READ,KEEP
            END_IF/
            ELSE/
            COMMENT/OPER,NO,Cannot read CMM info.
                           ,C:PC-DMISV43Cmminfo.txt
                           ,does not exist.
                           ,
                           ,Program will now exit.
            GOTO/QUIT
            END_ELSE/
$$ NO,===========================
     ,TP20 MODULE LOG CHECKER
     ,==============================
LOG_CHECK1 =FILE/EXISTS,C:PC-DMIS V431MMX40MM PROBE MODULE.CSV
            IF/LOG_CHECK1==0
            COMMENT/OPER,NO,Cannot read probe module log.
                           ,C:PC-DMIS V431MMx40MM Probe Module.csv
                           ,does not exist.
                           ,
                           ,Program will now exit.
            GOTO/QUIT
            END_IF/
$$ NO,=============================
     ,PART INFORMATION
     ,===============================
            ASSIGN/PART=STR(GETTEXT(191, 1, {FILEHEDR}))
            ASSIGN/PROGREV=STR(GETTEXT(192, 1, {FILEHEDR}))
            ASSIGN/SERI=STR(GETTEXT(193, 1, {FILEHEDR}))
            ASSIGN/STATSNO=STR(GETTEXT(194, 1, {FILEHEDR}))
            ASSIGN/PROGNAME="13-210-092-15."+PROGREV+"_TIB HLF BLK SZ J RL"
            ASSIGN/PARTNUM="42-5558-592-15"
            ASSIGN/PRINTREV="B"
            ASSIGN/PARTNAME="TIB HLF BLK SZ EF RL"
$$ NO,===========================
     ,MACHINE SETTINGS
     ,==============================
VIEWSET    =VIEWSET/
            RECALL/VIEWSET,VIEWSET
            MODE/MANUAL
            PREHIT/ 3
            RETRACT/ 3
            CHECK/ 5,1
            MOVESPEED/ 300
            TOUCHSPEED/ 10
            FLY/ON,3
            ASSIGN/ZERO=0
            ASSIGN/ONE=1
            FORMAT/TEXT, ,ID,HEADINGS,SYMBOLS, ;MEAS,NOM,TOL,DEV,OUTTOL, ,
            COMMENT/OPER,NO,Proceed to load probe?
$$ NO,===========================
     ,LOAD PROBE
     ,==============================
            LOADPROBE/5606_135_1
            TIP/T1A90B-90, SHANKIJK=1, 0, 0, ANGLE=-90
$$ NO,============================
     ,MENU
     ,===============================
MENU       =LABEL/
MENU_SELECT =COMMENT/INPUT,NO,'1 - Probe Calibration
                             ,2 - Setup Information
                             ,3 - Fixture Alignment
                             ,4 - Program Execution
                             ,5 - Quit'
            IF/MENU_SELECT.INPUT=="1"
            GOTO/PROBE_QUAL
            END_IF/
            IF/MENU_SELECT.INPUT=="2"
            GOTO/SETUP_INFO
            END_IF/
            IF/MENU_SELECT.INPUT=="3"
            GOTO/MANUAL_ALGN
            END_IF/
            IF/MENU_SELECT.INPUT=="4"
            GOTO/EXECUTE
            END_IF/
            IF/MENU_SELECT.INPUT=="5"
            GOTO/QUIT
            END_IF/
            GOTO/MENU
            IF/MENU_SELECT.INPUT<>"1" AND MENU_SELECT.INPUT <>"2" AND MENU_SELECT.INPUT <>"3" AND MENU_SELECT.INPUT <>"4" AND MENU_SELECT.INPUT <>"5"
            COMMENT/OPER,NO,   INPUT NOT VALID!!
            GOTO/MENU
            END_IF/
$$ 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,125>
            LOADPROBE/5606_135_5
            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,125>
            LOADPROBE/5606_135_1
            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,125>
            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:PROBES5606_135_1.BAT
            EXTERNALCOMMAND/NO_DISPLAY, NO_WAIT ; C:PROBES5606_135_2.BAT
            EXTERNALCOMMAND/NO_DISPLAY, NO_WAIT ; C:PROBES5606_135_5.BAT
            MODE/MANUAL
            GOTO/MENU
$$ NO,==============================
     ,SETUP INFO
     ,=================================
SETUP_INFO =LABEL/
            COMMENT/OPER,NO,===================================
                           ,Program Name:
                           ,PROGNAME
                           ,
                           ,To Inspect:
                           ,"PART # " + PARTNUM
                           ,
                           ,You Need:
                           ,- Insert required probe here  
                           ,- Insert fixturing data here
                           ,
                           ,Click "OK" when ready to continue
$$ NO,**************************************
     ,
     ,*****Setup picture link goes here*****
     ,
     ,**************************************
            GOTO/MENU
$$ NO,===============================
     ,MANUAL ALIGNMENT
     ,=================================
MANUAL_ALGN=LABEL/
            PREHIT/ 2
            RETRACT/ 2
            CHECK/ 3,1
            COMMENT/OPER,NO,Place probe at
                           ,
                           ,Click "OK" when ready.
READPOINT  =FEAT/POINT,CARTESIAN
            THEO/<ZERO,ZERO,ZERO>,<ZERO,ZERO,ONE>
            ACTL/<159.488,0,-144.02>,<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
            MODE/DCC
            WORKPLANE/XPLUS
LIN_Z      =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/1,1
            MODE/DCC
            MOVESPEED/ 200
CIR_ST     =FEAT/CONTACT/CIRCLE,CARTESIAN,IN,LEAST_SQR
            THEO/<0,0,0>,<1,0,0>,4.04,0,360
            ACTL/<0,0,0>,<1,0,0>,4.04,0,360
            TARG/<0,0,0>,<1,0,0>
            ANGLE VEC=<0,0,-1>
            DIRECTION=CCW
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=NO
MAN_ALIGN  =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
            ALIGNMENT/TRANS,XAXIS,CIR_ST
            ALIGNMENT/TRANS,YAXIS,CIR_ST
            ALIGNMENT/TRANS,ZAXIS,CIR_ST
            ALIGNMENT/END
            SAVE/ALIGNMENT,MAN_ALIGN,test.aln,MACHINETOPARTS
            GOTO/MENU
$$ NO,====================================================
     ,DIMENSIONAL REPORT
     ,====================================================
            COMMENT/REPT,"PROGRAM REVISION : "+PROGREV+"                   PROGRAM NAME : "+PROGNAME
            COMMENT/REPT,"CMM NUMBER       : "+CMM_NUMBER+"       INSPECTOR    : "+OPID.INPUT
            COMMENT/REPT,"PART NUMBER      : "+PARTNUM+"      JOB NUMBER   : "+JOBNO.INPUT
            COMMENT/REPT,"PRINT REVISION   : "+PRINTREV+"                   STATS COUNT  : "+STATSNO.INPUT
            COMMENT/REPT,"PART NAME        : "+PARTNAME
            COMMENT/REPT,
            DISPLAYPRECISION/3
            POSITIVEREPORTING/ , , /ALLDATA
            WORKPLANE/YPLUS
EXECUTE    =LABEL/
            IF/CMM_NUMBER==13-200-900-07
CS1        =ATTACH/N:70 - PERSONAL FOLDERSDUANE WADECMM PROGRAMS WIP - DO NOT USESUBROUTINE CALL TEST ATTACH1.PRG, Machine=
            EQUATE/LOCAL ALIGNMENT = MAN_ALN1, ATTACHED ALIGNMENT = TEST:man_align
            END_IF/
            IF/CMM_NUMBER==13-200-900-02
CS2        =ATTACH/N:70 - PERSONAL FOLDERSDUANE WADECMM PROGRAMS WIP - DO NOT USESUBROUTINE CALL TEST ATTACH2.PRG, Machine=
            EQUATE/LOCAL ALIGNMENT = MAN_ALN1, ATTACHED ALIGNMENT = TEST:man_align
            END_IF/
QUIT

How do I get PC DMIS to measure elements in correct orientation to model?

$
0
0
I need a little help getting the program to measure elements in the correct view, how do I change to say an ZX plane to measure a circle?
I have tried to change different workplanes and views such as Z-, Y- but feature is not aligning with model. see pic.

angle from hole to hole

$
0
0
Help me out real quick please... how do I get the angle from hole to hole all the way around? For what it's worth, there is no clocking requirement so we're manufacturing it to be clocked as modeled and I'm locking rotation on a datum hole that relates to these holes on the model. I'm probing the model and trying to dimension it every way I can think of, 3D lines built from a cylinder but they're coming up way wrong.
PCD legacy.
Thanks!


Click image for larger version

Name:	2019-01-31_11-15-51.jpg
Views:	23
Size:	21.0 KB
ID:	443236

Unexpected Touch &quot;dodge&quot; breaks styli's

$
0
0
Maybe this is something more unique to Sheffield controllers than B&S/Hexagon controllers? But I'm wondering if there is a setting to tell the cmm to NOT move way-way away from an unexpected touch. This can break a styli (especially the spindly and expensive Ø.5 styli's), or at least require a recalibration. I'm thinking of trying to reach into a .88 wide slot with a .5 styli and thinking its likely the parts will be different enough from time to time so that this doesn't work. Unexpected touches make the cmm "dodge" - I suppose the intent is to prevent damage, but it usually causes damage. I'd prefer it to just plain STOP, not dodge away from an unexpected touch by an inch or so.

Database read only

$
0
0
Hi. I am fairly new to the PC-DMIS world. I am able to log in to PC DMIS 2018 R1 and DATAPAGE+. When my coworker tries to log on to the same system it gets shows a check fault. Thanks
.Click image for larger version

Name:	Fault.jpg
Views:	4
Size:	43.5 KB
ID:	443256

Deviation of true position

$
0
0
Hi,

When i using True position of hole I get calculation of position and deviation of that hole in report.

At the and of report i want to keep track of deviation of True position but my measure of deviation is different from that i get in True position calculation.

Why is this happening?

New Toy

$
0
0
I just inherited a Romer Arm from a sister company that bought it in 2017. They never used it since the classes, so we now have it to put it to use. It's an Absolute Arm 7 axis 7525 SE with an external HP-L-20.8 Laser Scanning System.

I'm not counting on getting sent to classes, so I may have a "few" questions as I try to make this thing useful.

Any preemptive pointers are welcome.

Importing Data into Quindos 7

$
0
0
Can text and numbers be imported to Quindos 7 from MS Access and/or Excel?

I have an Access database containing information about a lot of parts. Currently, I have to manually access the database and write the info down that I need and manually enter it into my Quindos program.

I was thinking if I could figure out how to output the database information into some format that Quindos could read. I could import it automatically into Quindos.

I can create a text file and use the OPEN command to open it in Quindos, but I'm at a loss as to how to have Quindos bring the data in.

Any suggestions?

Thank you in advance,
Ken

New Little Feature

$
0
0
So here is something I came across. Just because sometimes I use Paste With Pattern. Apparently its something new in 2018.
So if you highlight say a surface that say all circles or Cylinders Share. Highlight that surface.

Click image for larger version  Name:	IMG_0517.jpg Views:	0 Size:	32.5 KB ID:	443327

Then take your mouse and place it above the top of the cylinder and hold down SHIFT it will then highlight all the same common circles.
Left click your mouse and it will create them.

Click image for larger version  Name:	IMG_0519.jpg Views:	0 Size:	33.8 KB ID:	443328

or if you highlight the inside and left click it will make Cylinders

Click image for larger version  Name:	IMG_0518.jpg Views:	0 Size:	29.9 KB ID:	443329

Alignments for parts whose orientation might change by more than 90°

$
0
0
I'm new here, so please be gentle. A search for all keywords I could think of didn't lead to any results.

We're using our CMM to build high-precision laser interferometers. One unique aspect to this application is that it requires us to measure the same types of components in ever changing orientations with respect to a baseplate. We do so by introducing custom manual 6-point alignments for each type of component and then doing a thorough DCC scan of them within this relative alignment. The problem we're facing with this approach is, that when such a component is rotated more than 90° with respect to the original orientation in which the 6-point alignment was defined (i.e. learned), strange things start to happen, e.g. for some features the hit points are calculated to take place on the opposite side of the probe ball or the direction of lines might switch, both of which mess up our 6-point alignments. Question #1: Is there an established way to counteract this problem?

What I tried so far to resolve this problem was to dynamically change a problematic measured feature's theoretical IJK vector on the fly based on previous measurements in order to trick PC-DMIS into thinking that the original definition more closely resembles the situation it will find during the next measurement. Doing so will indeed result in a correct 6-point alignment, BUT this also dynamically changes the target hit points in the following DCC measurements, which I don't understand. Question #2: Why is that and how can I prevent this from happening?

Here is a condensed-down version of my code. In the beginning, I'm asking the operator for the rough direction into which a mirror is pointing, the result of which is then used to define the theoretical direction of the first plane(MAC_PL) to be measured for a 6-point alignment. The alignment using this plane (MAC) is consistent for any orientation of the mirror, but the target hits of the plane which is to be measured directly after that in DCC mode (MAF_PL) is not. For instance, when the operator chooses the direction "-y" instead of "x", the x and z components of the target hit points of MAF_PL switch places (so the first hit point <-51.962,14.337,0> is modified to be <0,14.337,-51.962>) which is of course completely wrong.

Code:
PART NAME  : Test
REV NUMBER :
SER NUMBER :
STATS COUNT : 1

STARTUP    =ALIGNMENT/START,RECALL:,LIST=YES
            ALIGNMENT/END
            MODE/MANUAL
            PREHIT/ 1
            RETRACT/ 1
            MOVESPEED/ 100
            FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
            LOADPROBE/KU_5X50
            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
C_MIR_DIR  =COMMENT/INPUT,NO,What is the closest direction into which the
                            ,mirror's normal vector is pointing (x, y, -x, -y)?
            SELECT/C_MIR_DIR.INPUT
            CASE/"x"
            ASSIGN/V_MC_X=1
            ASSIGN/V_MC_Y=0
            END_CASE/
            CASE/"-x"
            ASSIGN/V_MC_X=-1
            ASSIGN/V_MC_Y=0
            END_CASE/
            CASE/"y"
            ASSIGN/V_MC_X=0
            ASSIGN/V_MC_Y=1
            END_CASE/
            CASE/"-y"
            ASSIGN/V_MC_X=0
            ASSIGN/V_MC_Y=-1
            END_CASE/
            DEFAULT_CASE/
            COMMENT/OPER,NO,Your input was invalid. Execution of the
                           ,program was stopped.
            PROGRAM/END
            END_DEFAULTCASE/
            END_SELECT/
MAC_PL     =FEAT/PLANE,CARTESIAN,TRIANGLE
            THEO/<-17.619,456.313,8.935>,<V_MC_X,V_MC_Y,0>
            ACTL/<21.77,282.52,-437.095>,<-0.999738,0.0227829,-0.0022153>
            MEAS/PLANE,3
            HIT/BASIC,NORMAL,<-29.398,456.309,-14.793>,<0,-1,0>,<21.302,263.763,-418.402>,USE THEO=YES
            HIT/BASIC,NORMAL,<-29.388,456.31,20.59>,<0,-1,0>,<21.673,275.779,-462.491>,USE THEO=YES
            HIT/BASIC,NORMAL,<5.775,456.281,20.753>,<0,-1,0>,<22.337,308.017,-430.393>,USE THEO=YES
            ENDMEAS/
MAC_LN     =FEAT/LINE,CARTESIAN,UNBOUNDED
            THEO/<-4.715,30.056,32.806>,<0,0,1>
            ACTL/<22.562,315.67,-453.449>,<-0.0021988,0.0007484,0.9999973>
            MEAS/LINE,2,FEATURE=MAC_PL
            HIT/BASIC,NORMAL,<-401.392,41.85,32.804>,<0.0165876,0.999862,0.0009411>,<34.512,315.398,-453.422>,USE THEO=YES
            HIT/BASIC,NORMAL,<-401.663,41.858,59.248>,<0.0165876,0.999862,0.0009411>,<34.506,315.427,-411.226>,USE THEO=YES
            ENDMEAS/
MAC_LN_P   =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
            THEO/<-4.715,456.313,32.806>,<0,0,1>
            ACTL/<22.562,315.67,-453.449>,<-0.0021988,0.0007484,0.9999973>
            CONSTR/LINE,PROJ,MAC_LN,MAC_PL,26.444
MAC_PT     =FEAT/POINT,CARTESIAN
            THEO/<398.275,41.058,38.046>,<MAC_LN_P.I,MAC_LN_P.J,MAC_LN_P.K>
            ACTL/<34.576,309.126,-403.854>,<-0.008759,0.034619,0.9993622>
            MEAS/POINT,1
            HIT/BASIC,NORMAL,<814.569,69.891,452.92>,<-0.0003062,0.9999995,-0.0009235>,<34.576,309.126,-403.854>,USE THEO=YES
            ENDMEAS/
MAC_PT_P   =FEAT/POINT,CARTESIAN,NO
            THEO/<-4.715,456.313,38.046>,<0,0,1>
            ACTL/<22.453,315.707,-403.886>,<-0.0021988,0.0007484,0.9999973>
            CONSTR/POINT,DROP,MAC_PT,MAC_LN_P
MAC        =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
            ALIGNMENT/LEVEL,ZPLUS,MAC_PL
            ALIGNMENT/ROTATE,YMINUS,TO,MAC_LN_P,ABOUT,ZPLUS
            ALIGNMENT/TRANS,XAXIS,MAC_PT_P
            ALIGNMENT/TRANS,YAXIS,MAC_PT_P
            ALIGNMENT/TRANS,ZAXIS,MAC_PT_P
            ALIGNMENT/END
            MODE/DCC
MAF_PL     =FEAT/PLANE,CARTESIAN,TRIANGLE
            THEO/<-33.047,33.159,0>,<0,0,1>
            ACTL/<-33.048,33.166,-0.001>,<0.0000168,0.0000094,1>
            MEAS/PLANE,3
            MOVE/POINT,NORMAL,<-33,-3,4>
            HIT/BASIC,NORMAL,<-51.962,14.337,0>,<-0.0004559,0.0001429,0.9999999>,<-51.963,14.345,0>,USE THEO=YES
            HIT/BASIC,NORMAL,<-39.735,58.465,0>,<-0.0004559,0.0001429,0.9999999>,<-39.733,58.472,-0.001>,USE THEO=YES
            HIT/BASIC,NORMAL,<-7.443,26.676,0>,<-0.0004559,0.0001429,0.9999999>,<-7.443,26.68,-0.001>,USE THEO=YES
            ENDMEAS/
Can you help me? Thank you very much!

Defaut rectitude axe cylindre

$
0
0
Bonjour,

Je suis nouveau sur le forum et voici ma première question.
Je souhaiterais mesurer le défaut de rectitude de l'axe d'un cylindre. Je voudrais savoir comment procéder avec le logiciel. Dois-je simplement palper le cylindre et demander le défaut de rectitude de l'axe de ce cylindre, est-ce que je ne risque pas d'obtenir "0" comme défaut de rectitude sachant que je palpe ce cylindre en automatique. Comment procéderiez-vous?

Merci par avance pour vos réponses.

A bientôt

Patrick

Labels in Report Template

$
0
0
Dear Colleagues

I can see in report template "TextOnly.rtp" that border lines of the labels "legacydimensions.lbl" are not overlapped enough and there are two lines between the labels. Could you advise if it is possible to set position of the next labels (2nd, 3rd, .... ) to have the border lines of the labels overlapped? I would like to see only one border line between two labels.

Thank you in advance.

Click image for larger version

Name:	Labels.png
Views:	24
Size:	39.0 KB
ID:	443384

Probe Changer and extensions

$
0
0
Hello,

Here is my situation / problem / question.

We have two CMM's. One with a TP20 and one with a TP200 system.
If I set up for a new product and I am using an extension 50 or 100mm and then change to no extension, PC_Dmis see's that, and I don't have to re-calibrate the probe changer.
With the TP200 system, I have to re-calibrate each time.
(For the measuring of the whole product, (product A) I use an extension 50, then clear away, and set up for a completely different product,( product B). This product only uses probes with no extension)
So the question is: is there somewhere in the set up a button that needs to be activated to make the two the same?

We are using PC_Dmis 2017 MR1

Cheers
Viewing all 11658 articles
Browse latest View live


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