↧
Article 6
↧
Beggining to practice on CMM Global Performance
How to hide/delete this?
We only want to see the probe.
We only want to see the probe.
↧
↧
Article 4
Hello
↧
Piezo Touch Error While Calibrating
Hi all,
New member to the forum here and just started programming CMM's. My company hired me 3rd shift to measure and program on night shift while I go to school so I don't have a ton of support on my shift.
Once in a while I run into a Piezo touch error and it is usually when the part is able to wobble(Using superglue to hold most our parts). Tonight I experienced it while calibrating for one of our programs. The total calibration has 60 or 70 tip angles all on 1 probe and any angle that had an angle of 15 or 90 (in both A and B) would error out. Any ideas on how to get around this? This calibration worked fine every day for the last month or so. Any help is appreciated!
Specs:
2018r2
Cordax RS50
PH10MQ, TP7M, 50mm ext, 1x20
New member to the forum here and just started programming CMM's. My company hired me 3rd shift to measure and program on night shift while I go to school so I don't have a ton of support on my shift.
Once in a while I run into a Piezo touch error and it is usually when the part is able to wobble(Using superglue to hold most our parts). Tonight I experienced it while calibrating for one of our programs. The total calibration has 60 or 70 tip angles all on 1 probe and any angle that had an angle of 15 or 90 (in both A and B) would error out. Any ideas on how to get around this? This calibration worked fine every day for the last month or so. Any help is appreciated!
Specs:
2018r2
Cordax RS50
PH10MQ, TP7M, 50mm ext, 1x20
↧
Write measurement data to csv file
We want to write a subroutine which can write all our data to a csv file.
We did this with 'ascii_file.exe' and got the results needed, but we want some more variables (V1, V2, V3, V4 and V5) inserted in the data.
We receive the data like seen in the photo now.
![Click image for larger version
Name: 1.png
Views: 8
Size: 26.3 KB
ID: 457979]( "1.png")
What we want is the result in the next picture:
![Click image for larger version
Name: 2.png
Views: 7
Size: 19.7 KB
ID: 457980]( "2.png")
When we run the above code with the tweaked csv file, everything runs OK, but we want to let it run OK for the first time.
This because we got many PC-DMIS programs (like 1800-2000) and insert this in a subroutine which is already available in all programs.
When the adjusted subroutine runs for the first time, it has to make the file first.
The 'ascii_file.exe' is making the document and filling it: the first line in the first picture as well as the first results (second line) in the first picture.
Can anyone help us with this?
We did this with 'ascii_file.exe' and got the results needed, but we want some more variables (V1, V2, V3, V4 and V5) inserted in the data.
We receive the data like seen in the photo now.
Code:
STARTUP =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
ALIGNMENT/END
MODE/MANUAL
PREHIT/3
WORKPLANE/ZPLUS
RETRACT/3
CHECK/5,1
MOVESPEED/ 300
FLY/ON,3
FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS,SD;NOM,MEAS,TOL,DEV,OUTTOL, ,
LOADPROBE/T4BY50
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
WORKPLANE/ZPLUS
SUBROUTINE/STATISTIEK,
OPERATOR = "" : ,
MEETMACHINE = "" : ,
TYPE_METING = "" : ,
BEWERKINGSMACHINE = "" : ,
OPMERKING = "" : ,
MALPOSITIE = "" : ,
PARTNAME = "" : ,
=
ASSIGN/MALPOSITIE=MALPOSITIE
ASSIGN/OPERATOR=OPERATOR
ASSIGN/MEETMACHINE=MEETMACHINE
ASSIGN/BEWERKINGSMACHINE=BEWERKINGSMACHINE
ASSIGN/TYPE_METING=TYPE_METING
ASSIGN/OPMERKING=OPMERKING
ASSIGN/PARTNAME=PARTNAME
ASSIGN/VRALL_COMPLEET=MALPOSITIE+";"+BEWERKINGSMACHINE+";"+MEETMACHINE+";"+TYPE_METING+";"+OPMERKING
ASSIGN/FILEPATH="K:\\"+PARTNAME+".CSV"
VEXIST =FILE/EXISTS,FILEPATH
IF/VEXIST==0
EXTERNALCOMMAND/NO_DISPLAY, WAIT ; K:\ASCII_FILE.EXE
FPTR =FILE/OPEN,FILEPATH,READ
V1 =FILE/READLINE,FPTR,
FPTR =FILE/OPEN,FILEPATH,APPEND
ASSIGN/V2="MALPOSITIE;BEWERKINGSMACHINE;MEETMACHINE;TYPE METING;OPMERKING;"
FILE/WRITELINE,FPTR,V2
FILE/WRITELINE,FPTR,VRALL_COMPLEET + ";"
FILE/CLOSE,FPTR,KEEP
END_IF/
IF/VEXIST==1
FPTR =FILE/OPEN,FILEPATH,APPEND
FILE/WRITE_BLOCK,FPTR,VRALL_COMPLEET + ";"
EXTERNALCOMMAND/NO_DISPLAY, NO_WAIT ; K:\ASCII_FILE.EXE
FILE/CLOSE,FPTR,KEEP
END_IF/
What we want is the result in the next picture:
When we run the above code with the tweaked csv file, everything runs OK, but we want to let it run OK for the first time.
This because we got many PC-DMIS programs (like 1800-2000) and insert this in a subroutine which is already available in all programs.
When the adjusted subroutine runs for the first time, it has to make the file first.
The 'ascii_file.exe' is making the document and filling it: the first line in the first picture as well as the first results (second line) in the first picture.
Can anyone help us with this?
↧
↧
Reporting out of tolerance results in yellow
Hi all,
very new here. i am working on a new part that we haven't made before, and since we're still in the beginnings of the project i was asked if i can somehow report some of the results in yellow-not as in OOT. Give them a bit of extra tolerance i guess.
For example - i have a True Position called out .003 to A and B datums. So whenever it is over .003 it will show OOT, but they want me to show it in yellow if it's not over .01. I'm not sure i'm explaining it well. is there any IF/GOTO commands i can use or something?
Any help is greatly appreiciated
D
very new here. i am working on a new part that we haven't made before, and since we're still in the beginnings of the project i was asked if i can somehow report some of the results in yellow-not as in OOT. Give them a bit of extra tolerance i guess.
For example - i have a True Position called out .003 to A and B datums. So whenever it is over .003 it will show OOT, but they want me to show it in yellow if it's not over .01. I'm not sure i'm explaining it well. is there any IF/GOTO commands i can use or something?
Any help is greatly appreiciated
D
↧
Manual temperature compensation in PC-DMIS CAD++
Dear PC-DMIS users,
our supplier uses a DEA GLOBAL 07-10-05 to check aluminium parts with PC-DMIS CAD++. They tell us that the machine does not have the possibility to automatically compensate for part or axes temperature, nonetheless they are operating the CMM in a lab with temperatures between 23 and 24 degrees, apparently they cannot do better during the summer. The part is laid down on the surface plate without fixturing. I asked the operator to manually check the temperature of the part, define a variable to scale the measurements down (alpha*delta_T), run the program using this variable to scale all the measurements down to the reference temperature of 20 degrees and generate the report using the scaled down measurements, but he does not know how to do it. Would it be possible at all?
Thanks in advance!
our supplier uses a DEA GLOBAL 07-10-05 to check aluminium parts with PC-DMIS CAD++. They tell us that the machine does not have the possibility to automatically compensate for part or axes temperature, nonetheless they are operating the CMM in a lab with temperatures between 23 and 24 degrees, apparently they cannot do better during the summer. The part is laid down on the surface plate without fixturing. I asked the operator to manually check the temperature of the part, define a variable to scale the measurements down (alpha*delta_T), run the program using this variable to scale all the measurements down to the reference temperature of 20 degrees and generate the report using the scaled down measurements, but he does not know how to do it. Would it be possible at all?
Thanks in advance!
↧
Graphical Report control
I am dimensioning a scanned line across the face of a part using Profile of a Line. I have a dozen or more to do like this and it slows the report down considerably. Is there a way to turn on the graphical ONLY when at high limit or over tolerance??
Thanks!
Thanks!
↧
True position of slot
How can I find the true position of the slot with respect to cylinder datum. I have attached a picture for reference.
I have tried by constructing a width feature using the planes of the slot and called the cylinder as datum C and generated the true position dimension call out involving both the dimensions. but i am not getting any results. Am i missing anything.
Thank you.
I have tried by constructing a width feature using the planes of the slot and called the cylinder as datum C and generated the true position dimension call out involving both the dimensions. but i am not getting any results. Am i missing anything.
Thank you.
↧
↧
Issues moving from 2018r1 to 2019r1
First off, hello, I'm new to the forum. I have been programming PCDMIS for 3 years, but have really ramped up the level of programming in the last 5 months. I have the level 1 and 2 training from hexagon.
I recently updated the software from 2018r1 to 2019r1 SP3. It was my first time doing this, as previously there was a different guy that was lead on the CMM's. After updating I am now finding a few issues here and there in "proven" programs, when the measurement routine is finished we insert a few move points to bring the probe up and to the back of the machine, to get it out of our way for part loading. For some reason the upgrade to 2019 has it trying to move out of the machine limits, and I get a "TR_OUTOL, Machine Parameter out of Tolerance !" Error.
The set up is a clear plane move which works fine, then an incremental Z+100mm, followed by a move point to <-500,800,475>
The problem starts with the incremental move, and doesn't seem to go away no matter how short I make it. The part is not tall so it is definitely not going to overtravel.
I guess I'm trying to figure out if there is a setting that might have changed in the switch to 2019 that makes it move relative to the part? Or is there something else going on and I'm just blind?
Jordan
I recently updated the software from 2018r1 to 2019r1 SP3. It was my first time doing this, as previously there was a different guy that was lead on the CMM's. After updating I am now finding a few issues here and there in "proven" programs, when the measurement routine is finished we insert a few move points to bring the probe up and to the back of the machine, to get it out of our way for part loading. For some reason the upgrade to 2019 has it trying to move out of the machine limits, and I get a "TR_OUTOL, Machine Parameter out of Tolerance !" Error.
The set up is a clear plane move which works fine, then an incremental Z+100mm, followed by a move point to <-500,800,475>
The problem starts with the incremental move, and doesn't seem to go away no matter how short I make it. The part is not tall so it is definitely not going to overtravel.
I guess I'm trying to figure out if there is a setting that might have changed in the switch to 2019 that makes it move relative to the part? Or is there something else going on and I'm just blind?
Jordan
↧
Access Probe Changer Mount Point From Inside Program
Hi Everybody,
Does anyone know if there's a way to access the probe changer mount point (where it goes immediately before and after changing tips with the rack) in the code for a program? I'm thinking of shaving off a few seconds by using a MOVE/ALL command on the way to and from a tip change, but I need to know where to send it to. It would also be nice to be able to send it to that point at the end of the program without having to actually change tips.
Thank you!
Matthew
Edit: Upon further investigation, it's more complicated then I thought: it looks like the XYZ numbers in the "Mount Point" tab under Calibrate/Edit > Probe Changer are to the end of the quill, not the position of the probe tip. This would fit with how the machine moves prior to a tip change; however, replicating that action in the program requires either getting the machine to move the end of the quill to a point or manually de-compensating for the length of the probe (a big pain).
Does anyone know if there's a way to access the probe changer mount point (where it goes immediately before and after changing tips with the rack) in the code for a program? I'm thinking of shaving off a few seconds by using a MOVE/ALL command on the way to and from a tip change, but I need to know where to send it to. It would also be nice to be able to send it to that point at the end of the program without having to actually change tips.
Thank you!
Matthew
Edit: Upon further investigation, it's more complicated then I thought: it looks like the XYZ numbers in the "Mount Point" tab under Calibrate/Edit > Probe Changer are to the end of the quill, not the position of the probe tip. This would fit with how the machine moves prior to a tip change; however, replicating that action in the program requires either getting the machine to move the end of the quill to a point or manually de-compensating for the length of the probe (a big pain).
↧
CMM Probe in offline mode incorrect size
This might not be a big deal, but is there any way to change was the probe looks like in offline mode to reflect its actual size. I'm using a 3mm x 30 probe and a 0.3mm x 30 probe and they both look the same during programming and simulation. It's kind of a pain to take hits in these tiny holes when I'm programming the 0.3mm probe and it looks like the 3mm probe.
↧
Article 5
Thank you for the 2019 R1 test, that is what I was expecting. I am suspecting a timing issue with 2019 R2 on your system. As a test, we re going to try to slow it down a bit. I am sending you a new EXE to try. Just backup or rename your old exe and copy this one into the same folder, then try with 2019 R2 again.
↧
↧
Saving .pdf reports
I have PC-DMIS CAD++ 2018 R2
I recently updated my service pack and now when I save my report as a .pdf a second save menu wants me to save it again. But, this save menu has some crazy symbol after the .pdf
How do I get rid of this second save menu?
![Click image for larger version
Name: PC-DMIS SAVE.PNG
Views: 33
Size: 37.8 KB
ID: 458032]()
I recently updated my service pack and now when I save my report as a .pdf a second save menu wants me to save it again. But, this save menu has some crazy symbol after the .pdf
How do I get rid of this second save menu?
↧
Best way to measure a Profile.
We received a program from a third-party for the profile of a part we are having trouble with. They have taken 19 separate points along the area for the profile check. The way they are measuring this profile is using "T" for a Location Dimension. I used the same program but changed the way of measuring by setting up the datum's and using the Profile measurement. The profile from both ways of measuring are different (using the actual Profile Dimension is reading more nominal than the Location Dimension). I'm wondering which measurement is the correct one to use.
↧
Profile to replace Position/Size
I have a large radius (>3") on a part but I only have about 5degrees of arc. We are supposed to hold +/-.005 on size and a .005 Position. We cannot measure this on anything we have.
I am suggesting a composite Profile control of .005 to the same DRF and .010 to no DRF. Will this accomplish the same thing?
I am suggesting a composite Profile control of .005 to the same DRF and .010 to no DRF. Will this accomplish the same thing?
↧
Vector Point Problem
I have a problem with vector points today. For some reason PC-DMIS is offsetting the hit target parameters which causes the machine to crash. The hit target parameters must match the X,Y,Z location of the point. It only happens on some points. If I manually correct it and execute it then it works until the program is closed and re-opened. Then it crashes again. It's driving me crazy. Wrote the program in 2019R2.
↧
↧
2019 r2 sp1
https://www.wilcoxassoc.com/public/P...19_R2/SP1/x64/
Release Notes - 2019 R2 SP1
• PCD-36046 - Fixed an issue where the find hole option would not work with
the Wenzel interface.
• PCD-109698 - Fixed an issue where performance was decreased during the
execution of a laser scan and COP commands in a loop.
• PCD-132016 - Fixed an issue where PC-DMIS stopped responding when you
ran the Zeiss interface on new computers. This fix also enhanced the
performance of the execution of many independent features.
• PCD-156784 - Fixed a crash that occurred when you used a 4 bit-per-pixel
bitmap for the CAD texture.
• PCD-158609 - Added support for DEVA 037 Manual Counter Card. To use this
interface, you must rename MANUALCMM.DLL to INTERFAC.DLL, and
GMS_for_Deva_EncLib.XML to GMS.XML. All files related to the DEVA card are
installed with the DEVA driver.
• PCD-158646 - Fixed an issue where the pointcloud cross-section Show/Hide
distance gages button was disabled in the Slideshow view.
• PCD-167625 - Improved compatibility with some USB serial cables used to
connect the HP-C-VE controller to the PC via USB.
• PCD-169328 - Fixed an issue where PC-DMIS did not pass the surface ID to
the command when you created a 3D Laser QuickFeature and had to re-pick
the CAD surface from the Laser Auto Feature dialog box.
• PCD-169386 - Fixed an issue where the points went to the wrong surface
when you picked point pairs in a pointcloud to CAD alignment. This issue
depended on the view orientation.
• PCD-169906 - Fixed an issue where pointcloud stripe IJK information was not
included in the Pointcloud | Export XYZ file format.
• PCD-170207 - Added a change for the PointcloudOperator |
ExportXYZSeparator registry entry to define one or more separator
characters used for the Pointcloud XYZ export.
• PCD-171304 - Fixed an issue where PC-DMIS reported the worst point instead
of the measured centroid for non-plane features.
• PCD-171381 - Fixed an issue with a Chinese operating system where settings
to execute the collision avoidance during calibration were not read correctly
from the registry on machines.
• PCD-171396 - Fixed an issue where the Mesh colormap annotation points
were not created unless the measurement routine was closed and then reopened.
• PCD-172057 - Fixed an issue where the news feed on the Home page was
empty for Chinese (Simplified). It now uses Chinese (Traditional).
• PCD-172202 - Fixed an issue where PC-DMIS did not obey the marked set's
output settings when PC-DMIS executed a marked set.
• PCD-172853 - Fixed an issue where the execution of laser probe calibrations
from the auto-calibrate command didn’t finish. The Execution dialog box
had to be closed through the Stop button.
• PCD-173186 - Fixed an issue where the Home page was switched off when
the Part/Machine Setup tab was the active tab in the Setup Options dialog
box.
• PCD-173227 - Fixed an issue for laser auto cylinders and spheres where the
CAD offset value was incorrectly applied for inch units.
• PCD-173264 - Fixed a timer functionality for the CMM-OS interface.
• PCD-173687 - Fixed an issue that occurred when you executed toolkit
module features.
• PCD-173721 - Fixed an application error that occurred when you created a
linear open scan with a CWS probe, and the Measure option was selected in
the Linear Open Scan dialog box.
• PCD-173743 - Fixed an issue where the measurement routine stopped
responding if you opened the Tilt Readouts window (Tracker | Nivel | Start
Tilt Readout) for the Leica ATS600 Tracker.
• PCD-174456 - Fixed an issue where the Home page overrode PC-DMIS locale
enforcement for decimal numbers, which caused issues with entering
numbers of specific locales.
• PCD-174671 - Fixed a Vision probe-focus calibration error that occurred
when the Find Surface (Focus) parameter was incorrectly enabled.
• PCD-174797 - Fixed an issue where the Tracker Operation toolbar was
missing the measurement profile buttons for the AT40x Leica Tracker
interface.
• PCD-175045 - Fixed an application error that occurred when you edited or
executed a Vision feature with multiple hit targets.
• PCD-175460 - Fixed an issue where, after the machine left a probe change
rack, PC-DMIS computed an incorrect mount-point move. This issue caused
either an incorrect movement or an "out of machine limits" error
Release Notes - 2019 R2 SP1
• PCD-36046 - Fixed an issue where the find hole option would not work with
the Wenzel interface.
• PCD-109698 - Fixed an issue where performance was decreased during the
execution of a laser scan and COP commands in a loop.
• PCD-132016 - Fixed an issue where PC-DMIS stopped responding when you
ran the Zeiss interface on new computers. This fix also enhanced the
performance of the execution of many independent features.
• PCD-156784 - Fixed a crash that occurred when you used a 4 bit-per-pixel
bitmap for the CAD texture.
• PCD-158609 - Added support for DEVA 037 Manual Counter Card. To use this
interface, you must rename MANUALCMM.DLL to INTERFAC.DLL, and
GMS_for_Deva_EncLib.XML to GMS.XML. All files related to the DEVA card are
installed with the DEVA driver.
• PCD-158646 - Fixed an issue where the pointcloud cross-section Show/Hide
distance gages button was disabled in the Slideshow view.
• PCD-167625 - Improved compatibility with some USB serial cables used to
connect the HP-C-VE controller to the PC via USB.
• PCD-169328 - Fixed an issue where PC-DMIS did not pass the surface ID to
the command when you created a 3D Laser QuickFeature and had to re-pick
the CAD surface from the Laser Auto Feature dialog box.
• PCD-169386 - Fixed an issue where the points went to the wrong surface
when you picked point pairs in a pointcloud to CAD alignment. This issue
depended on the view orientation.
• PCD-169906 - Fixed an issue where pointcloud stripe IJK information was not
included in the Pointcloud | Export XYZ file format.
• PCD-170207 - Added a change for the PointcloudOperator |
ExportXYZSeparator registry entry to define one or more separator
characters used for the Pointcloud XYZ export.
• PCD-171304 - Fixed an issue where PC-DMIS reported the worst point instead
of the measured centroid for non-plane features.
• PCD-171381 - Fixed an issue with a Chinese operating system where settings
to execute the collision avoidance during calibration were not read correctly
from the registry on machines.
• PCD-171396 - Fixed an issue where the Mesh colormap annotation points
were not created unless the measurement routine was closed and then reopened.
• PCD-172057 - Fixed an issue where the news feed on the Home page was
empty for Chinese (Simplified). It now uses Chinese (Traditional).
• PCD-172202 - Fixed an issue where PC-DMIS did not obey the marked set's
output settings when PC-DMIS executed a marked set.
• PCD-172853 - Fixed an issue where the execution of laser probe calibrations
from the auto-calibrate command didn’t finish. The Execution dialog box
had to be closed through the Stop button.
• PCD-173186 - Fixed an issue where the Home page was switched off when
the Part/Machine Setup tab was the active tab in the Setup Options dialog
box.
• PCD-173227 - Fixed an issue for laser auto cylinders and spheres where the
CAD offset value was incorrectly applied for inch units.
• PCD-173264 - Fixed a timer functionality for the CMM-OS interface.
• PCD-173687 - Fixed an issue that occurred when you executed toolkit
module features.
• PCD-173721 - Fixed an application error that occurred when you created a
linear open scan with a CWS probe, and the Measure option was selected in
the Linear Open Scan dialog box.
• PCD-173743 - Fixed an issue where the measurement routine stopped
responding if you opened the Tilt Readouts window (Tracker | Nivel | Start
Tilt Readout) for the Leica ATS600 Tracker.
• PCD-174456 - Fixed an issue where the Home page overrode PC-DMIS locale
enforcement for decimal numbers, which caused issues with entering
numbers of specific locales.
• PCD-174671 - Fixed a Vision probe-focus calibration error that occurred
when the Find Surface (Focus) parameter was incorrectly enabled.
• PCD-174797 - Fixed an issue where the Tracker Operation toolbar was
missing the measurement profile buttons for the AT40x Leica Tracker
interface.
• PCD-175045 - Fixed an application error that occurred when you edited or
executed a Vision feature with multiple hit targets.
• PCD-175460 - Fixed an issue where, after the machine left a probe change
rack, PC-DMIS computed an incorrect mount-point move. This issue caused
either an incorrect movement or an "out of machine limits" error
↧
Refresh FCF using automation...
Im doing some automated reconfiguring of true position FCFs. In a single case(so far) the values of the FCF has not been updated correctly after changing used axis and calling .execute. It has added the missing axis, but the reported deviation values are not correct. I tried toggling the Text field to trigger a refresh, it works if done manually in the edit window, but not if done by automation. Just opening the FCF with F9 and confirming causes it to refresh to correct values. Calling .Compute doesn’t work either.
I detect when it happens now with a control calculation I set up recently so it’s not a huge issue, mostly annoying. I have a suspicion it may be related to the bug that sometimes causes FCFs with local references to report against a nominal reference rather than the measured.
I detect when it happens now with a control calculation I set up recently so it’s not a huge issue, mostly annoying. I have a suspicion it may be related to the bug that sometimes causes FCFs with local references to report against a nominal reference rather than the measured.
↧
CMM does not work after calibration
The following situation occurred during the shift. There was a strong deviation during the last measurement, after which it was decided to calibrate the probe. During calibration, the machine went the other way from the sphere. We canceled the calibration and tried to bring the cmm to zero, but it produced the following error: Error CE, S%1, TR_CE .0x14000034 Command argument out of limit.
I clicked the OK button to see the coordinates of the home position and they were x: 1.034 / y: -8.1141 / z: -9.0364
An interesting point, when moving the pinole along Z, displacing it by 2-3 cm, according to the coordinates of cmm it shifts by 0.5-0.7 mm![Click image for larger version
Name: Untitled.png
Views: 43
Size: 33.7 KB
ID: 458113]()
I clicked the OK button to see the coordinates of the home position and they were x: 1.034 / y: -8.1141 / z: -9.0364
An interesting point, when moving the pinole along Z, displacing it by 2-3 cm, according to the coordinates of cmm it shifts by 0.5-0.7 mm
↧