I am trying to report a true position of a diameter. The diameter spec is Ø 4.0 - 0.004 / -0.016. When I input this info the report shows the Dia. out of tolerance. How do I make my report recognize the - / tolerance?
↧
Diameters with -/- or +/+ tolerances
↧
Missing profile section on Report.
Hi,
Please see images attached.
Same Program run however different report results for this profile section,
Any reasons why?
Thanks.
Please see images attached.
Same Program run however different report results for this profile section,
Any reasons why?
Thanks.
↧
↧
Probe wont take manual hits on the Pin
I have a very very weird issue. I have a part with a threaded hole in it, I put the gage pin inside the hole. When I try to take manual hits on around the pin, it will not register.
The weird thing is that it only does it on the gage pin. if i try to take manual hits on anything else, it registers hits no problem. It will even take a hit on the gage pin, if I put it in the different hole.
just random crap
The weird thing is that it only does it on the gage pin. if i try to take manual hits on anything else, it registers hits no problem. It will even take a hit on the gage pin, if I put it in the different hole.
just random crap
↧
Probe Orientation mismatch of results
We have had multiple occurrences when referencing a datum measured in one orientation to a feature measured in another does not yield the proper values. We have double checked with dial indicators and proven the CMM wrong.
The first was with a deep motor bore. We measured the top labyrinth with the probe at (0,0) and defined it as datum A. Then we rotated the probe to (15,0), (15,90), (15,180), (15,-90) and formed a circle to measure a deep motor bore so we did not shank out. . When we referenced the bore to datum A, the true position was off by .030ish.
The next experience was with measuring run out of a bore. We elevated the part to find the bottom surface and measured it at a probe angle of (90,180). We then rotated the head and measured a bore using a probe orientation of (0,0). When referencing the bottom surface to the runout of the bore, again we got a value off by .030ish.
Was wondering if anyone has had the same problem or has some insight how to solve this problem without fixturing our parts horizontally to access both sides of the part.
Yes all tools have been calibrated...
Thanks in advance.
The first was with a deep motor bore. We measured the top labyrinth with the probe at (0,0) and defined it as datum A. Then we rotated the probe to (15,0), (15,90), (15,180), (15,-90) and formed a circle to measure a deep motor bore so we did not shank out. . When we referenced the bore to datum A, the true position was off by .030ish.
The next experience was with measuring run out of a bore. We elevated the part to find the bottom surface and measured it at a probe angle of (90,180). We then rotated the head and measured a bore using a probe orientation of (0,0). When referencing the bottom surface to the runout of the bore, again we got a value off by .030ish.
Was wondering if anyone has had the same problem or has some insight how to solve this problem without fixturing our parts horizontally to access both sides of the part.
Yes all tools have been calibrated...
Thanks in advance.
↧
SP25M auto-calibration program calibration issues
Okay, so we replaced our SM25-1 and I needed to do a full calibration of our probes in the rack.
Made sure I un ticked the use partial calibration routine in all the probe files.
When the auto cal program got to #4 it pulled up the probe and gave me an error stating that I can't do a partial until a full has been done. (I had reset all the tips beforehand).
It gave me the option of printing partial results and when I stated no, the whole program froze up and gave me no option but to control alt delete which shut all down.
Needless to say I had to start over from the beginning. I made sure again that the use partial was not ticked in the probe options window.
This time (after several hours since we have a large number of angles that get calibrated) it loaded probe #4 and immediately unloaded it and loaded #5. This is where it sits.
The blue shaded edit window content indicates at it should be starting the calibration of #4 but it instead has loaded #5 and wont do anything. I'm afraid that if I choose continue, stop, or end that all will freeze up again and I will once again lose hours of calibration accomplished thus far today. Any ideas anyone?
Made sure I un ticked the use partial calibration routine in all the probe files.
When the auto cal program got to #4 it pulled up the probe and gave me an error stating that I can't do a partial until a full has been done. (I had reset all the tips beforehand).
It gave me the option of printing partial results and when I stated no, the whole program froze up and gave me no option but to control alt delete which shut all down.
Needless to say I had to start over from the beginning. I made sure again that the use partial was not ticked in the probe options window.
This time (after several hours since we have a large number of angles that get calibrated) it loaded probe #4 and immediately unloaded it and loaded #5. This is where it sits.
The blue shaded edit window content indicates at it should be starting the calibration of #4 but it instead has loaded #5 and wont do anything. I'm afraid that if I choose continue, stop, or end that all will freeze up again and I will once again lose hours of calibration accomplished thus far today. Any ideas anyone?
↧
↧
scans
relatively new to PC-DMIS (as are most people that start writing questions in here right?) and am filling in for our normal operator because he tore his rotator cuff. Our arm is a romer infinite 2.0 and im using 2015 sp 5. We do a lot of one off parts and I have been taught to use the scan function to get a general idea of how our profile is fitting in relation to our tolerances. My question then is what is the best way to do this where it will actually give me usable data that I can then relay back to the programmers? What I guess I'm asking is how I use the scan function? We do not have a CMM just the portable.
↧
2015.1SP7 is on...
Just a news, all is in the title !
↧
Article 1
Jim,
It's been a bit over a year since I've used the SP-25. I have a calibration question. Are you able to offset the start and end angle when using an SP-25 set-up?
thank you
{"data-align":"none","data-size":"medium","data-attachmentid":390633}
It's been a bit over a year since I've used the SP-25. I have a calibration question. Are you able to offset the start and end angle when using an SP-25 set-up?
thank you
{"data-align":"none","data-size":"medium","data-attachmentid":390633}
↧
Datum to feature/Feature to Datum?
Can anyone explain why when I am reporting concentricity from feature A to feature B I get X reading, and when I report from feature B to feature A I get a completely different reading.
This problem occurs in both Xact measure and Legacy mode. Both features are datums and measured as auto cylinders.
I am using CAD 2014.1
T.I.A.
This problem occurs in both Xact measure and Legacy mode. Both features are datums and measured as auto cylinders.
I am using CAD 2014.1
T.I.A.
↧
↧
Probe Head hand controler stuck in manual mode
The yellow manual mode light on the Probe head controller unit will not go off.
Does anyone know what I need to do to turn it off?
Does anyone know what I need to do to turn it off?
↧
Error messages TR_FG_152, TR_FG013, bad archives, and calibration failures
I realize that each of these topics alone could start a lengthy discussion. I have gotten them all today. At one point I was getting both error messages at the same time. I opened a new program to calibrate my probes (thinking the one I usually use may have gotten corrupted somehow) and now can't open it ...."File closed because of a bad archive"......I am ready to pull my hair out! The CMM worked fine the last time I used it....no crashes...no error messages... nothing hinky.......any suggestions? .....Exorcism?
↧
PPAP report decimal place issue
I can only get more than one decimal point value to read and/or print on the PPAP report. All others work fine.
I have went into Edit: Preferences: Setup: Dimensions. Applied defaults to decimal places and have number of decimal places at 6.
Still only 1 point on the report.
I am running 2010 MR1.
I have went into Edit: Preferences: Setup: Dimensions. Applied defaults to decimal places and have number of decimal places at 6.
Still only 1 point on the report.
I am running 2010 MR1.
↧
2016 error on global
I am getting error when opening any program in 2016 SP4 on my Global machine " ERROR PI ,S%1 ,TR_PI ,0x1200001 a Command argument has an invalid value" tech support has been no help I have 2016 on my other cmm and it does not show this error any ideas we have reinstalled PC-DMIS and still have this error
↧
↧
Reasons to Update Software
If any of you would like to take the time to help me out with information to bring to the people up front, the advantages of updating software it would be greatly appreciated. Any and all posts welcome.
↧
PC DMIS won't go into DMIS Mode
We normally use PC-DMIS 2014 in "DMIS-mode" ; however, we were programming a part and now the DMIS Mode is greyed out, so that you cannot select it. We are only allowed to select summary mode or command mode. We have tried rebooting both the PC and CMM. The CMM does have connection to the computer. Any ideas?
↧
CAD file could not be read (2016) ??
I’m trying 2016. I have a program and CAD file created in 2015.0 SP4.
When I try to open the program in 2016 I get this message...
"CAD file could not be read. Attempted to access an unnamed file past its end"
The part file opens; but there is no cad.
Any ideas?
When I try to open the program in 2016 I get this message...
"CAD file could not be read. Attempted to access an unnamed file past its end"
The part file opens; but there is no cad.
Any ideas?
↧
Distance between a hit and a cone (surface)
Just a funny code to calculate the distance of the hits of a cone to the cone surface :
DECIMAL PLACE,6 (metric, more if inches...)
ASSIGN/V1=CON1.HIT[1..CON1.NUMHITS].XYZ-CON1.XYZ.......................................... ......array of vectors between each hit and the cone summit
ASSIGN/L_V1=SQRT(DOT(V1,V1))............................. .................................................. ..............array of lengthes of vectors
ASSIGN/H_V1=DOT(V1,CON1.IJK)............................. .................................................. ..............array of lengthes projection of hits along cone axis
ASSIGN/R_V1=SQRT(L_V1^2-H_V1^2)........................................... ..........................................array of radial distances between hits and cone axis
ASSIGN/A_V1=ASIN(R_V1/L_V1)-DEG2RAD(CON1.A/2)................................................ ......array of angles
ASSIGN/T_VAL_HIT=L_V1*SIN(A_V1).......................... .................................................. ...........array of distances of each hit to the surface (like a T_value for each hit)
Then calculate max, min max index....
Not sure it's usefull, not sure there's not an easiest way to do it, just funny to program using a little trig and the assignments tool box !
DECIMAL PLACE,6 (metric, more if inches...)
ASSIGN/V1=CON1.HIT[1..CON1.NUMHITS].XYZ-CON1.XYZ.......................................... ......array of vectors between each hit and the cone summit
ASSIGN/L_V1=SQRT(DOT(V1,V1))............................. .................................................. ..............array of lengthes of vectors
ASSIGN/H_V1=DOT(V1,CON1.IJK)............................. .................................................. ..............array of lengthes projection of hits along cone axis
ASSIGN/R_V1=SQRT(L_V1^2-H_V1^2)........................................... ..........................................array of radial distances between hits and cone axis
ASSIGN/A_V1=ASIN(R_V1/L_V1)-DEG2RAD(CON1.A/2)................................................ ......array of angles
ASSIGN/T_VAL_HIT=L_V1*SIN(A_V1).......................... .................................................. ...........array of distances of each hit to the surface (like a T_value for each hit)
Then calculate max, min max index....
Not sure it's usefull, not sure there's not an easiest way to do it, just funny to program using a little trig and the assignments tool box !
↧
↧
Scan to point all by itself
More of an FYI
I am writing a program offline and got to a point I wanted to see it execute offline also.
Ran thru no real problems but did a couple tweaks on the output, reran the program again offline.
It "PC DMIS" converted all my scans to points; thousands of them.
I was able to save that off with a new name leaving me with my old correct program.
I ran that program now with out the tweaks I had made and it again converted all my scans to points.
Could have been a huge problem if I had not have seen it.
I am writing a program offline and got to a point I wanted to see it execute offline also.
Ran thru no real problems but did a couple tweaks on the output, reran the program again offline.
It "PC DMIS" converted all my scans to points; thousands of them.
I was able to save that off with a new name leaving me with my old correct program.
I ran that program now with out the tweaks I had made and it again converted all my scans to points.
Could have been a huge problem if I had not have seen it.
↧
Article 1
vpt!! your 'Posh Jarcenter' post is hilarious! And your FIFY about updates bringing more bugs and issues is SPOT ON. I see no TechPrev for 2017 yet, but since my company stopped our SMA in July, I cannot join anyway. Also, great topics on that new suggestion board. I've still got all 3 of my votes...... just figuring out which of the many i'll cast my ballots on. (have a few of my own as well)
hope all is good with you, my friend.......
hope all is good with you, my friend.......
↧
Reporting the difference between two diameters
Good Day, All:
I have a situation that I believe has an easy solution...I just don't know it. The probe I am using is pushing the limits of my machine. In order to make sure the program is executing properly, I measure the same diameter, at the beginning and the end of the program. Reporting the difference in X and Z is easy. How do I report the difference between two diameters? I created this Variable:
ASSIGN/V1=CIR_T1A0B0_PRE.DIA-CIR_T1A0B0_POST.DIA
The nominal value is 0. It's literally the same feature measured twice. This will show me if I'm falling out of calibration. I just don't know how to report "V1". Any suggestions?
I have a situation that I believe has an easy solution...I just don't know it. The probe I am using is pushing the limits of my machine. In order to make sure the program is executing properly, I measure the same diameter, at the beginning and the end of the program. Reporting the difference in X and Z is easy. How do I report the difference between two diameters? I created this Variable:
ASSIGN/V1=CIR_T1A0B0_PRE.DIA-CIR_T1A0B0_POST.DIA
The nominal value is 0. It's literally the same feature measured twice. This will show me if I'm falling out of calibration. I just don't know how to report "V1". Any suggestions?
↧