I have a program that is in inches. Is there any way to change all the units to metric without re-writing the program from scratch? Or at the very least, output all of the dimensions on the report in metric?
↧
How to change units?
↧
PC-DMIS programs shown as type Adobe Acrobat
Hello everyone,
I have a question that maybe someone has run into before, in PC-DMIS 2011MR1 the program list shows all the programs as a Adobe Acrobat type, not PC-DMIS part program file like it's supposed to. I believe this happened because some operators are using the computer for other things other than Running programs. The programs run like they should, they are just showing the Adobe Icon and the type says Adobe Acrobat. The O.S. is Windows 7.
Thank for any help.
Greg.
I have a question that maybe someone has run into before, in PC-DMIS 2011MR1 the program list shows all the programs as a Adobe Acrobat type, not PC-DMIS part program file like it's supposed to. I believe this happened because some operators are using the computer for other things other than Running programs. The programs run like they should, they are just showing the Adobe Icon and the type says Adobe Acrobat. The O.S. is Windows 7.
Thank for any help.
Greg.
↧
↧
Need help with Best Fit Alignment, Please!!!!!
Please help me how to alignment with a Set (6 holes call as Datum -B-) and plane is Datum -A-.
I don't know the proper way to use Best Fit alignment. Need Pro Help. Thank you in Adv.
![Click image for larger version
Name: 123.JPG
Views: 1
Size: 11.4 KB
ID: 434706]()
I don't know the proper way to use Best Fit alignment. Need Pro Help. Thank you in Adv.
↧
2018 r2 sp1
Here :
http://www.wilcoxassoc.com/public/PC...e/2018_R2/SP1/
Release Notes - 2018 R2 SP1
• PCD-50401 - Fixed an issue where the Jump Hole functionality failed or
caused scans to fail.
• PCD-126983 - Fixed an issue where PC-DMIS stopped working if you reset the
execution list while a measurement routine was executing.
• PCD-135742 - Fixed an issue where path lines for probe head rotations were
not drawn for probe heads with a C-joint (heads with 6 axis).
• PCD-137806 - Eliminated a null pointer related to a commonly reported 2018
R1 issue where PC-DMIS stopped working.
• PCD-139668 - Fixed a crash that occurred when cast points were used in a
loop.
• PCD-140397 - Fixed an issue where Wcompens32_2.dll did not correctly load
the geometrical compensation map on DEA machines.
• PCD-140785 - Fixed the issue of an incorrect path for an auto feature cylinder
spiral scan.
• PCD-144198 - Restored functionality that existed prior to PC-DMIS 2017 R1 to
display the probe at the correct location in the Graphic Display window when
a MOVE command was edited.
• PCD-144358 - Thickness now works for Auto Cylinder and Auto Cone.
• PCD-145193 - Implemented a change as required by Q-DAS. K2110, K2111,
K2112, K2113, K2101, etc. should not be output to the DFQ or DFD/DFX file
when "Use TP for tolerance of location" is not selected.
• PCD-145787 - Fixed an issue where the Illumination tab did not appear in
the Probe Toolbox.
• PCD-146106, PCD-148762 - Fixed an issue that prevented setting Xact
Measure dimension IDs from the dialog box.
• PCD-146258 - Fixed potential 15-second delays or crashes when switching
between cameras on a multiple uEye digital camera system.
• PCD-146441 - Fixed an issue with the Custom Report Editor interface that
occurred after the Save dialog box was canceled.
• PCD-147189 - Fixed an issue where PC-DMIS stopped working when
switching dimension types from the toolbar.
•PCD-147291 - Features selected from the datum definition dialog box now
highlight in the Graphic Display window.
• PCD-147292 - Prevented lowercase datum letters from being defined in the
DATDEF command.
• PCD-147300 - Prevented a crash from occurring when the Vision laser (FLS)
gain in the Probe Toolbox was edited.
• PCD-147324 - Fixed an issue where an out-of-date Inspect icon was used on
the shortcut to Inspect within the PC-DMIS start menu group.
• PCD-147592 - Fixed an issue where the Edit window could not print to a file.
• PCD-147629 - Fixed an issue that prevented the Xact Measure feature list
from updating after a "per unit" flatness dimension was created.
• PCD-147762, PCD-148548 - Fixed an issue where the Pointcloud toolbar and
functions were not available for CAD and CAD++ licenses that did not have
the Laser/BigCOP option.
• PCD-147955 - Fixed an issue introduced by changes to the mouse controls,
which caused Marked Sets to fail when migrated from previous versions.
• PCD-148136 - Prevented a possible incorrect initialization of touch probes in
combination with VisionBox.
• PCD-148270 - An incorrect web store address that was used for testing
purposes was left out in the code. This fix removed the web store link to the
U.S. web site.
• PCD-148439 - Fixed the error of incorrect reporting of legacy True Position.
• PCD-148479 - The sequence of the axis in True Position output in the DFQ file
must be updated because O-QIS software from Q-DAS was not able to read
the original format.
http://www.wilcoxassoc.com/public/PC...e/2018_R2/SP1/
Release Notes - 2018 R2 SP1
• PCD-50401 - Fixed an issue where the Jump Hole functionality failed or
caused scans to fail.
• PCD-126983 - Fixed an issue where PC-DMIS stopped working if you reset the
execution list while a measurement routine was executing.
• PCD-135742 - Fixed an issue where path lines for probe head rotations were
not drawn for probe heads with a C-joint (heads with 6 axis).
• PCD-137806 - Eliminated a null pointer related to a commonly reported 2018
R1 issue where PC-DMIS stopped working.
• PCD-139668 - Fixed a crash that occurred when cast points were used in a
loop.
• PCD-140397 - Fixed an issue where Wcompens32_2.dll did not correctly load
the geometrical compensation map on DEA machines.
• PCD-140785 - Fixed the issue of an incorrect path for an auto feature cylinder
spiral scan.
• PCD-144198 - Restored functionality that existed prior to PC-DMIS 2017 R1 to
display the probe at the correct location in the Graphic Display window when
a MOVE command was edited.
• PCD-144358 - Thickness now works for Auto Cylinder and Auto Cone.
• PCD-145193 - Implemented a change as required by Q-DAS. K2110, K2111,
K2112, K2113, K2101, etc. should not be output to the DFQ or DFD/DFX file
when "Use TP for tolerance of location" is not selected.
• PCD-145787 - Fixed an issue where the Illumination tab did not appear in
the Probe Toolbox.
• PCD-146106, PCD-148762 - Fixed an issue that prevented setting Xact
Measure dimension IDs from the dialog box.
• PCD-146258 - Fixed potential 15-second delays or crashes when switching
between cameras on a multiple uEye digital camera system.
• PCD-146441 - Fixed an issue with the Custom Report Editor interface that
occurred after the Save dialog box was canceled.
• PCD-147189 - Fixed an issue where PC-DMIS stopped working when
switching dimension types from the toolbar.
•PCD-147291 - Features selected from the datum definition dialog box now
highlight in the Graphic Display window.
• PCD-147292 - Prevented lowercase datum letters from being defined in the
DATDEF command.
• PCD-147300 - Prevented a crash from occurring when the Vision laser (FLS)
gain in the Probe Toolbox was edited.
• PCD-147324 - Fixed an issue where an out-of-date Inspect icon was used on
the shortcut to Inspect within the PC-DMIS start menu group.
• PCD-147592 - Fixed an issue where the Edit window could not print to a file.
• PCD-147629 - Fixed an issue that prevented the Xact Measure feature list
from updating after a "per unit" flatness dimension was created.
• PCD-147762, PCD-148548 - Fixed an issue where the Pointcloud toolbar and
functions were not available for CAD and CAD++ licenses that did not have
the Laser/BigCOP option.
• PCD-147955 - Fixed an issue introduced by changes to the mouse controls,
which caused Marked Sets to fail when migrated from previous versions.
• PCD-148136 - Prevented a possible incorrect initialization of touch probes in
combination with VisionBox.
• PCD-148270 - An incorrect web store address that was used for testing
purposes was left out in the code. This fix removed the web store link to the
U.S. web site.
• PCD-148439 - Fixed the error of incorrect reporting of legacy True Position.
• PCD-148479 - The sequence of the axis in True Position output in the DFQ file
must be updated because O-QIS software from Q-DAS was not able to read
the original format.
↧
Copying and Pasting on those pesky nominals
Good evening,
I have never done any copying and pasting to a program. Never had a reason to. However, I am working with sister parts and was asked to copy and paste to the new part then add the new feature in the program. I was told the nominals needed to be locked. How do I do that? I know, Its a crazy question...… lol
I have never done any copying and pasting to a program. Never had a reason to. However, I am working with sister parts and was asked to copy and paste to the new part then add the new feature in the program. I was told the nominals needed to be locked. How do I do that? I know, Its a crazy question...… lol
↧
↧
How to Rotate this 6 hole pattern
How to Rotate this 6 hole pattern -C- to -B- as you see they are both @ zero -A- datum is surface?
↧
Measurement strategy editor does not perform the strategy
Hi everyone,
So I am new to the Measurement strategy editor and was trying to make a new group of strategy next to the default group, however, when I change something in my measurement strategy and apply this.. it will not use this!
After I change something in measurement strategy editor and the apply this change, I press shift and click on the CAD feature, but the measurement strategy is not what I want! When I choose, for instance, the amount of points for a circle and place it on 3 and the default user has it on 5, but after pressing shift + feature on CAD i get a circle which has 7 points??
Is there something what I have missed??
EDIT: If I press f9 and change the amount of points, to lets say 11, then the next time I make a circle feature it selects immediatly 11 points.. So it seems what I adjust in f9 is what changes the strategy
So I am new to the Measurement strategy editor and was trying to make a new group of strategy next to the default group, however, when I change something in my measurement strategy and apply this.. it will not use this!
After I change something in measurement strategy editor and the apply this change, I press shift and click on the CAD feature, but the measurement strategy is not what I want! When I choose, for instance, the amount of points for a circle and place it on 3 and the default user has it on 5, but after pressing shift + feature on CAD i get a circle which has 7 points??
Is there something what I have missed??
EDIT: If I press f9 and change the amount of points, to lets say 11, then the next time I make a circle feature it selects immediatly 11 points.. So it seems what I adjust in f9 is what changes the strategy
↧
Error Status : CPU_hw_Error (?????)
I came in this morning to "TR_TRMI1,RS232 ERROR : OVERRUN". Machine start will not turn on. I also "TR_INT,COM-CTL V43.00 XCEL SCAN". I thought maybe a air leak but I took all covers off & do not hear any leaks. I made sure all air bearings were moving freely & they were. I went to the "Connections/HyperTerminal" & typed in status & this is what I got (Below). "CPU_hw_Error scares me. Can anyone tell me whats going on here please?
PCDMIS 3.7MR2
Global performance 575
System Status
================================================== =====================================
Error Status : CPU_hw_Error Feedhold Station : Use Jogbox Rate
Sloop Status : in_estop Fgrnd_Status : Sloop in estop
Wrist Status : ph9_ok_manual Autzer_Done : FALSE
Probe_Type : pr_ren Probe_Seated : TRUE
PCDMIS 3.7MR2
Global performance 575
System Status
================================================== =====================================
Error Status : CPU_hw_Error Feedhold Station : Use Jogbox Rate
Sloop Status : in_estop Fgrnd_Status : Sloop in estop
Wrist Status : ph9_ok_manual Autzer_Done : FALSE
Probe_Type : pr_ren Probe_Seated : TRUE
↧
Assigning Variables
I've been using PcDmis for a few years now and have recently passed the 100 level class, Now awaiting to attend 200 level. This is all a breeze to me but recently I've discovered something called "VARIABLES" It has struck an interest with me and unfortunately my job doesn't see fit to send me to the 300 level class where I can learn this side. So I am hoping you guys can point me to the right direction to understanding variables so that I can begin utilizing them in my programs. Example includes: Finding the pitch dia. of a groove by creating a variable that will take the outer dia. and subtract it from the inner then divide it by 2. Then taking either the inner or outter dia. and either add or sub it to get the answer. If I could just get someone to either explain the functions or lead this young goat to the water, I'll lap it up, Thanks!
↧
↧
Auto position
I am having trouble with imported .igs files not centering on screen. Ctrl + z moves the model to a set position(off screen), and the mouse buttons will adjust the part, but it keeps jumping back to where it was. Is there a way to deactivate auto-position?
↧
CSV to XLSX
Hey
I'm looking for something on the forum for ripping to an exel file.
and this works well but I can not get it as an xlsx file.
I have a exel file where only nominal sizes want to append on a exel location
I'm looking for something on the forum for ripping to an exel file.
and this works well but I can not get it as an xlsx file.
I have a exel file where only nominal sizes want to append on a exel location
in the yellow boxes.
↧
Zoom graphics screen 2009
When I try to zoom in it will only zoom to a point and it stops. Not close enough to clearly see and pick points on small features. Drawing a zoom box or using the wheel will not zoom all the way.
TIA
PC-DMIS 2009
TIA
PC-DMIS 2009
↧
TP of a 75mm projected point
Hi Everyone,
I have a question concerning TP of a 75mm projected point from a weld nut. Let me explain, I use a thread center on a weld nut, the exit end due to no access on the entrance end, to get the X and Z axis in automotive. I also measure a plane around the nut, using the actual filter for material thickness. The result of the constructed intersected point between the thread center cylinder and plane is well in tolerance Ø2.5mm (X is -.357, Z is -.146 giving a TP of .772). When I project a constructed point 75mm I read the point as out of tolerance, X is -1.693, Z is -.221 for a TP of 3.415. All my other weld nuts are in tolerance. The projected point is from a constructed line of the cylinder and weld nut intersected point, using vector distance of 75mm. The Powers say the part pins on the fixture, my program is wrong. Looking at the part on the fixture, it's off in the TP direction, but does pin. Note, the pin goes through a bushing certified by me for location, but it passes the opposite way, or as the bolt will be installed on assembly. I know this seems confusing, especially when seven out of eight are in tolerance. I am going to check my plane hits, maybe I have a flyer offsetting the plane-line. On an off item, when I turned on the graph to note the deviation direction, I noticed the tolerance band was in the Z axis, not the Y axis, I adjusted the work plane, but no help. Is this due to using a constructed point?
Thanks for any help in advance.
Odda
I have a question concerning TP of a 75mm projected point from a weld nut. Let me explain, I use a thread center on a weld nut, the exit end due to no access on the entrance end, to get the X and Z axis in automotive. I also measure a plane around the nut, using the actual filter for material thickness. The result of the constructed intersected point between the thread center cylinder and plane is well in tolerance Ø2.5mm (X is -.357, Z is -.146 giving a TP of .772). When I project a constructed point 75mm I read the point as out of tolerance, X is -1.693, Z is -.221 for a TP of 3.415. All my other weld nuts are in tolerance. The projected point is from a constructed line of the cylinder and weld nut intersected point, using vector distance of 75mm. The Powers say the part pins on the fixture, my program is wrong. Looking at the part on the fixture, it's off in the TP direction, but does pin. Note, the pin goes through a bushing certified by me for location, but it passes the opposite way, or as the bolt will be installed on assembly. I know this seems confusing, especially when seven out of eight are in tolerance. I am going to check my plane hits, maybe I have a flyer offsetting the plane-line. On an off item, when I turned on the graph to note the deviation direction, I noticed the tolerance band was in the Z axis, not the Y axis, I adjusted the work plane, but no help. Is this due to using a constructed point?
Thanks for any help in advance.
Odda
↧
↧
Refresh Report script not working
I have been using a refresh report script I got off the forum.
It currently will not work in 2017R2 as the pcdlrn.application number is not correct.
2015.1 is at 10.1 and 2016 is at 11.0
Can someone tell me what 2017R2 is or where to find it.
It currently will not work in 2017R2 as the pcdlrn.application number is not correct.
2015.1 is at 10.1 and 2016 is at 11.0
Can someone tell me what 2017R2 is or where to find it.
↧
Installing Renishaw Probe Rack
Hello!
We've got a probe rack that was dismounted from the CMM from Hexagon, and due to some IT issues, they didn't screw it back on!
Any instructions available on how I'd go about that? I see some things screwed into the granite plate, but it doesn't just fit together, so I'd rather ask than try and break it![]( "Smile")
EDIT:
I'm fairly comfortable in my ability to define and calibrate the rack once it's mounted to the CMM, I'm looking for something on physically mounting it to the machine
We've got a probe rack that was dismounted from the CMM from Hexagon, and due to some IT issues, they didn't screw it back on!
Any instructions available on how I'd go about that? I see some things screwed into the granite plate, but it doesn't just fit together, so I'd rather ask than try and break it
EDIT:
I'm fairly comfortable in my ability to define and calibrate the rack once it's mounted to the CMM, I'm looking for something on physically mounting it to the machine
↧
Point vector issue
I'm having point vector issues on some of the programs I am running. We have 2 Global Advantage cmms, 1 Global Performance, 1 Global FX, and an old Mistral, all running 2018 SP4. I was running a part yesterday that was taking points with a theo and target vector of -1,0,0. The actual vector was showing perfect while having .005-.010 deviation in Y and Z locations. Any other program we have (will explain this in a moment) gives us a perfect or near perfect Y and Z while showing a difference in X and the vector. This is happening on programs that have been created/opened and resaved on the computer with the Mistral CMM. Every program ran on that computer/CMM shows this issue and any program running on any other computer/CMM that has been saved from the Mistral computer has the same issue. Any idea of what is going on here?
↧
Complicated PC-DMIS Licensing Issue
I've used PC-DMIS 2016 on my computer for well over a year with a floating license. I set the license server up, my computer was the host machine and everything worked fine. My department at my company purchased a new Romer RA-7525 SEI that came with PC-DMIS 2018 for Romer. I set the Romer arm up, activated the license on the same computer, and installed PC-DMIS 2018 for Romer and it worked fine. I opened PC-DMIS 2016 to write a program and noticed that my PC-DMIS 2016 displayed and acted as PC-DMIS 2018 for Romer. After long frustration with that I figured I would just replace the laptop since my company is conducting a PC refresh.
I now have the old laptop, a new laptop, and a new laptop for the Romer arm which now has PC-DMIS for Romer installed on it which was done by a representative from Hexagon as a courtesy yesterday. I am now having licensing issues with my PC-DMIS 2016 floating license on the new laptop. I am getting error messages such as Trusted Storage Load Failed and CLM Activate Failed. I have been on the phone with support, used the online support resources on the listed error messages and have been down for a couple weeks. I have a strong feeling that there is an issue with the EID even though the license has been returned and rehosted numerous times. I have even done the Reset Trusted Storage solution numerous times. A new EID would be great or a HASP but that's probably wishful thinking. Anyone know what's going on here? Any help is greatly appreciated.
I've attached a screenshot of the error message and license type![Click image for larger version
Name: Trusted Storage Load Failed_LI2.jpg
Views: 2
Size: 18.1 KB
ID: 434919]()
![Click image for larger version
Name: Trusted Storage Load Failed_LI2.jpg
Views: 2
Size: 18.1 KB
ID: 434921]()
![Click image for larger version
Name: PCDMIS License.jpg
Views: 3
Size: 22.6 KB
ID: 434923]()
![Click image for larger version
Name: PCDMIS License.jpg
Views: 3
Size: 22.6 KB
ID: 434922]()
.
I now have the old laptop, a new laptop, and a new laptop for the Romer arm which now has PC-DMIS for Romer installed on it which was done by a representative from Hexagon as a courtesy yesterday. I am now having licensing issues with my PC-DMIS 2016 floating license on the new laptop. I am getting error messages such as Trusted Storage Load Failed and CLM Activate Failed. I have been on the phone with support, used the online support resources on the listed error messages and have been down for a couple weeks. I have a strong feeling that there is an issue with the EID even though the license has been returned and rehosted numerous times. I have even done the Reset Trusted Storage solution numerous times. A new EID would be great or a HASP but that's probably wishful thinking. Anyone know what's going on here? Any help is greatly appreciated.
I've attached a screenshot of the error message and license type
↧
↧
Article 2
Welcome to the forum
↧
True Position - Small Arc of a Large Diameter
I have tried a multitude of things, hoping maybe I could get some feedback on the best way to accurately measure the small arc segment for True Position. I know how to measure a small arc as there are a ton of topics on this on the forums. But have not seen anything pertaining to measuring the True Position of such feature. Datum A is a plane and Datum B is a hole perpendicular to Datum A. This gets brazed onto a tube. Of course this is an SPC feature and currently I am not as repeatable as I want to be.
Let the conversation begin...![]( "Confused")
![Click image for larger version
Name: RD12765_SNIP.JPG
Views: 1
Size: 18.0 KB
ID: 434939]()
Let the conversation begin...
↧
Computer memory oversaturation
Greetings,
Can one calibrate one's probe tips too much or too often? Can this cause problems with the computer memory by "oversaturation"?
Asking for a friend,
i am curious
yellow
Can one calibrate one's probe tips too much or too often? Can this cause problems with the computer memory by "oversaturation"?
Asking for a friend,
i am curious
yellow
↧