so i have tried everything i can possibly think of to make an alignment on a part. i cant take screen shots of it unfortunately either... its pretty much has alot of flats with radius everywhere on it. there are good areas to pick up alignments tho. but every way i try one of my plans always ends up at a 0 location when trying to pick up any feature and the machine errors out saying that the zone is out of the machines limits or something along that lines. i have tried every alignment i this part and it just keeps happening. any thoughts on what this is from? thanks!
↧
alignment question
↧
2017 vs 2018
I am extremely new to the CMM world. I have started a new job in July and I have been playing around with the CMM machine trying to figure out how it is programmed/operated. We have recently upgraded to the 2018 R2 version of the software. My question to you guys is, could i still use a 2017 manual that I found online to learn or would I have to use the 2018 manual? I am not sure as to how much has changed from the different versions. I am trying to achieve as much book reading I can do off of company time. Please feel free if anyone has any other options on the best and fastest way to learn the machine.
↧
↧
radius question
↧
Which B&S cmm has the longest granite table
We are quoting business and my boss asked me to look into a new or pre-owned B&S cmm that could check a part that is 8 feet long. Any ideas?
↧
LOOP Position?
USE LOOP
WHY Position together
......
![Click image for larger version
Name: LOOP1.png
Views: 1
Size: 182.0 KB
ID: 441654]( "LOOP1.png")
WHY Position together
......
↧
↧
PC-DMIS Forms not shown in INSPECT
Hi all,
I have written a program in PC-DMIS 2017 R1 and while executing in the PC-DMIS my forms do show up, when running the program in INSPECT they do not!
Inspect is waiting for a continue command indicating the form is executed but does not show. Comments do work fine.
I am currently using PC-DMIS 2017 R1 with INSPECT 2.5.
I read there is an INSPECT 3.2 version out with PC-DMIS 2017 R1 add-on, but when I run the updater it says INSPECT is up to date. Is there a stand-alone download for INSPECT 3.2? Or does it only come with PC-DMIS 2018? Would upgrading solve my issue or are forms not compatible with INSPECT?
We also have the older "Operator Interface" installed and running the program with IO does open the forms.
I have written a program in PC-DMIS 2017 R1 and while executing in the PC-DMIS my forms do show up, when running the program in INSPECT they do not!
Inspect is waiting for a continue command indicating the form is executed but does not show. Comments do work fine.
I am currently using PC-DMIS 2017 R1 with INSPECT 2.5.
I read there is an INSPECT 3.2 version out with PC-DMIS 2017 R1 add-on, but when I run the updater it says INSPECT is up to date. Is there a stand-alone download for INSPECT 3.2? Or does it only come with PC-DMIS 2018? Would upgrading solve my issue or are forms not compatible with INSPECT?
We also have the older "Operator Interface" installed and running the program with IO does open the forms.
↧
CMM Running super slow
PcDmis 2017 R2 SP11 on a Brown and Sharp Mistral stops to 'think' for 20-30 seconds on every move, even between hits. Programs that ran for about 10-15 minutes total, are now a few hours.
Tried taking the CMM off the network and running everything off the local drive, different user logins and elevated the CMM user to admin. Had IT check to see if anything was changed from the computer, software, antivirus side and nothing.
Anyone experience anything similar and what was the solution? Tech support at Hexagon seems to be throwing darts now to try to solve the issue.
Tried taking the CMM off the network and running everything off the local drive, different user logins and elevated the CMM user to admin. Had IT check to see if anything was changed from the computer, software, antivirus side and nothing.
Anyone experience anything similar and what was the solution? Tech support at Hexagon seems to be throwing darts now to try to solve the issue.
↧
Barcodes in Reports
Morning Everyone,
I'm currently working on automating and error-proofing our production tooling inspection process. This involves the elimination of typos via bar codes when moving data to our SPC software.
My current attempt at this involves a free bar code software from here:
https://www.barcodesinc.com/free-barcode-font/
The font itself works but requires an asterisk (*) before and after the encoded text. This causes the PCDMIS report editor to have issues with drawing anything from my program. The formula drawing it from the routine fails and the barcode becomes a mile long. It stops behaving like an "expression" and more like "text". I've been selecting the measured value to be encoded via "drag and drop" from the program code in summary mode over to the report editor.
Current Expresion: =DATAFIELD("114337"), DIM_MEASURED, 0)
Attempted mod (FAILS): =*DATAFIELD("114337"), DIM_MEASURED, 0)* with font downloaded from prior link in use.
Anyone got an easier way to do this? I feel like there should be.
Currently running 2014 FYI.
Thanks ahead of time,
Conner
I'm currently working on automating and error-proofing our production tooling inspection process. This involves the elimination of typos via bar codes when moving data to our SPC software.
My current attempt at this involves a free bar code software from here:
https://www.barcodesinc.com/free-barcode-font/
The font itself works but requires an asterisk (*) before and after the encoded text. This causes the PCDMIS report editor to have issues with drawing anything from my program. The formula drawing it from the routine fails and the barcode becomes a mile long. It stops behaving like an "expression" and more like "text". I've been selecting the measured value to be encoded via "drag and drop" from the program code in summary mode over to the report editor.
Current Expresion: =DATAFIELD("114337"), DIM_MEASURED, 0)
Attempted mod (FAILS): =*DATAFIELD("114337"), DIM_MEASURED, 0)* with font downloaded from prior link in use.
Anyone got an easier way to do this? I feel like there should be.
Currently running 2014 FYI.
Thanks ahead of time,
Conner
↧
2017 R2 SP12 on ftp...
I found this service pack on the ftp website, but not on the usual http...
ftp://wilcoxassoc.com/PC-DMIS-Versio.../2017_R2/SP12/
Release Notes - 2017 R2 SP12
• PCD-145623 - Fixed an issue where clearance plane paths were drawn in the
wrong orientation.
• PCD-151203 - Fixed an issue where a Vision Auto Feature edge point with a
manual target and large crosshair had the crosshair shrink and disappear as
the rotary angle went to 90 degrees.
• PCD-151225 - Fixed an issue where the Pointcloud Colormap Max/Min
annotations were turned off when an Inspection Routine was closed, reopened, and then re-executed.
• PCD-151346 - Fixed an issue where PC-DMIS may have stopped working
when the XactMeasure GD&T dialog box was closed.
• PCD-151985 - Fixed an accuracy issue that occurred when using
compensation files.
• PCD-154463 - Fixed an issue that occurred when Vision Diagnostics was
turned on for features; a memory leak and resource leak occurred each time
the measurement routine was executed.
ftp://wilcoxassoc.com/PC-DMIS-Versio.../2017_R2/SP12/
Release Notes - 2017 R2 SP12
• PCD-145623 - Fixed an issue where clearance plane paths were drawn in the
wrong orientation.
• PCD-151203 - Fixed an issue where a Vision Auto Feature edge point with a
manual target and large crosshair had the crosshair shrink and disappear as
the rotary angle went to 90 degrees.
• PCD-151225 - Fixed an issue where the Pointcloud Colormap Max/Min
annotations were turned off when an Inspection Routine was closed, reopened, and then re-executed.
• PCD-151346 - Fixed an issue where PC-DMIS may have stopped working
when the XactMeasure GD&T dialog box was closed.
• PCD-151985 - Fixed an accuracy issue that occurred when using
compensation files.
• PCD-154463 - Fixed an issue that occurred when Vision Diagnostics was
turned on for features; a memory leak and resource leak occurred each time
the measurement routine was executed.
↧
↧
PC-DMIS 2013 MR1 Offline marks external command opening existing program first time
Good day all, I have come to find that the PC-DMIS offline suite is un-marking an external command we have in all our programs, one which outputs to QDAS at the end of the program, when I open an existing program for the first time. I have to remember to check for that and then mark and save otherwise it might just keep it that way and then when it's run on the CMM there will be no data output to QDAS. Is there anyone who possibly knows why this could be?
↧
Using Sub-programs
Hi Guys.
There is a first time for everything, I'm told.
I have never worked with sub-programming before, at least not with PC-DMIS.
I have 4 versions of a part, and some of the geometry are on all 4 versions, but not at the same place.
Other geometries are on 2 but not on the last 2 versions.
The geometries are holes that looks like tulips.
In the bottom, they have a cylinder, then a cone and finish of with the inside of a torus ( or donut).
I was wondering, if it would be smarter for me to make the items in a sub-program, so that when the customer make changes, I'll only have to make my changes in the sub-program, instead of having them changed I all 4 programs.
But, how di I do it?
I mean, how do I get the dimension out of hole number 1 and keep the measured data from hole number 2?
I have 4 holes looking the same, but on the report I'd like to have 4 different geometries measured and reported.
Do I have to ASSIGN some variables every time the sub-program return some values, or....?
If any one could post a screenshot of the concept, I'd be very happy.
Or help me in any other way with a few tips of tricks, maybe even traps....
There is a first time for everything, I'm told.
I have never worked with sub-programming before, at least not with PC-DMIS.
I have 4 versions of a part, and some of the geometry are on all 4 versions, but not at the same place.
Other geometries are on 2 but not on the last 2 versions.
The geometries are holes that looks like tulips.
In the bottom, they have a cylinder, then a cone and finish of with the inside of a torus ( or donut).
I was wondering, if it would be smarter for me to make the items in a sub-program, so that when the customer make changes, I'll only have to make my changes in the sub-program, instead of having them changed I all 4 programs.
But, how di I do it?
I mean, how do I get the dimension out of hole number 1 and keep the measured data from hole number 2?
I have 4 holes looking the same, but on the report I'd like to have 4 different geometries measured and reported.
Do I have to ASSIGN some variables every time the sub-program return some values, or....?
If any one could post a screenshot of the concept, I'd be very happy.
Or help me in any other way with a few tips of tricks, maybe even traps....
↧
PC-DMIS 2011 MR1 download
Does anybody know where i can download PC-DMIS 2011 MR1? Hexagon only goes back to 2012.
↧
Hexagon H007621 Air Dryer
Has anyone had experience with Hexagon's
H007621 - Multi-CMM Air Dryer / Filter (110V)?
My inquiry is not about the use or need of an air dryer ( its been covered many times over here). The question is to the actual Air dryer system itself and its a good one. I did a quick search using the tool bar for the part number and did not find anything. Thank you all in advance!
↧
↧
Which Probe Module?
I am going to put together our first star probe, for this company. We will be using a 6" extension from the module to the star probe connection block. Should I use a heavier force module than the standard TesaStar TP-20 SF module (yellow band) for this with the length of the extension? I would think we would get false readings on a standard force module. What do you guys think?
↧
Incorrect Bonus Tolerance on datums
Good morning everyone
anyone knows how to fix the incorrect bonus tolerance from datums? In D2 appears bonus tolerance of .016 (see attach picture), I can't understand why.
Thanks in advance.
anyone knows how to fix the incorrect bonus tolerance from datums? In D2 appears bonus tolerance of .016 (see attach picture), I can't understand why.
Thanks in advance.
↧
Axis Errors
We are getting a lot of X, Y, and Z Axis errors causing our machine to fault out in the middle of a program. It will even sometimes do this when the machine is not moving and no program is running. We cant figure out what it is and it seems to come and go. One month it will happen 5-10 times a day then the next month we wont have a single error. We have checked our air pressure and cleaned off our scales. Other than that i'm not sure what it could be. Anybody have any suggestions?
↧
Article 4
Sure thing - i would like to try it out if its possible.
↧
↧
Article 3
Actually NVM ... i got it sorted. Thx for the offer to help tho.
↧
Article 2
Hi Troy,
Here is my cell phone number 763-587-5107.
I do not have access to the server.
Here is my cell phone number 763-587-5107.
I do not have access to the server.
↧
CMM won't finish booting
Our Browne & Sharp Micro Xcel PFX 454 does not seem to fully "boot-up". We had an air system loss in the facility which resulted in an air fault/error on PC-DMIS. After air pressure was restored, we were still unable to perform a machine start and operate the machine. (At this point, the jogbox & LEDs were functioning, just no response from the cmm). We shutdown both the computer and CMM for the night. We turned them on this morning and ran into an issue where all of the hand control jogbox lights turned on as well as the probe head light, however the machine start button on the hand control kept flashing and all the LEDs on the hand control remained on. The PC-DMIS software displays a "CMM not responding" message. Typically, all of the jogbox lights come on momentarily, but then some of them go off indicating the machine is ready to go. At which point, a machine start and the homing process can be started.
Does anyone have any suggestions? The CMM power cord is plugged into a UPS with battery backup and surge protection so I don't think it is a power issue. I tried pressing the e-stop, powering down, restarting and disengaging the e-stop to no avail. I checked all of the connections, and tried unplugging & reconnecting the serial connector for the jogbox but that didn't work either. The error message is too general for me too fully understand what the issue is.
We are running PC-DMIS 2001 for Window (ver 3.2) on Windows XP. Any help would be greatly appreciated. Thanks-
Does anyone have any suggestions? The CMM power cord is plugged into a UPS with battery backup and surge protection so I don't think it is a power issue. I tried pressing the e-stop, powering down, restarting and disengaging the e-stop to no avail. I checked all of the connections, and tried unplugging & reconnecting the serial connector for the jogbox but that didn't work either. The error message is too general for me too fully understand what the issue is.
We are running PC-DMIS 2001 for Window (ver 3.2) on Windows XP. Any help would be greatly appreciated. Thanks-
↧