Hello,
This is my first post on here. My Name is John, and I work at DP Tool & Machine in Avon, NY. Sorry for the length of this post, but I’m really stumped on this.
We are currently running 2 CMM's with PC-DMIS PRO 3.7 MR2 - a 1 - 2 year old Brown and Sharpe One, and a Sheffield Endeavor Series. 90% of the time we are running a program based off a variables list on the B&S and for the most part, it's total amount of glitches and restarts is pretty acceptable. Keep in mind its being run almost constantly over 3 shifts a day.
However on the Sheffield we experience almost daily shut downs with a number of different error messages. Sometimes this will happen repeatedly in the span of a few hours - other times things go well for the better part of a week.
I've had a problem where the software automatically triggers a hit upon start up and shows rapid movement in all 3 axis - only the controller is in "joy" and the probe head has not moved at all! It will then refuse to take any other hits.
If you restart the PC and turn the CMM off, and then back on, and re-zero everything, sometimes the software loses track of which tip it has, and never bothers to ask you either. So again, if you aren't careful, you will start checking your part with the wrong tip, only to smash up because of an extra extension or something like that.
We've had a few instances of the program skipping over clear planes that are marked active. I've also had the machine completely lose it's zero and try to move over 40 inches - like it's skipped the grid or something. Often times the machine will end up missing a feature by 1 - 60 mm because it has lost track of where it is. If you restart the CMM and Software, usually it will be fine, but on occasion this takes more than 1 try before it will work.
Once the machine even moved by its self while nobody was touching the controller or PC. The controller was left in Auto mode, which we try to avoid, but because of this unexpected move, the probe head hit a fixture - luckily there was no damage, other than to my underwear.
We've also noticed a few sporadic changes to set nominal and / or tol in pre-existing programs.
This is really just a general overview of the many problems we've had on a regular basis over the last year that I've been here. I can't say for sure, but I have heard that the previous programmers here had many of the same problems.
We've been cautioned against upgrading to version 4 because of glitches, and there were a few problems my co-worker had when we installed 3.7 MR3 last month, so we were told to switch back to MR2.
Does anyone else have these kinds of problems, or have any idea how to stop some of these errors from occurring? I have a feeling a lot of it is the software, or the PC, but I wouldn't fault the CMM itself either, since everything seems more reliable on the newer Brown and Sharpe.
Any help would be great!
Thanks,
John
This is my first post on here. My Name is John, and I work at DP Tool & Machine in Avon, NY. Sorry for the length of this post, but I’m really stumped on this.
We are currently running 2 CMM's with PC-DMIS PRO 3.7 MR2 - a 1 - 2 year old Brown and Sharpe One, and a Sheffield Endeavor Series. 90% of the time we are running a program based off a variables list on the B&S and for the most part, it's total amount of glitches and restarts is pretty acceptable. Keep in mind its being run almost constantly over 3 shifts a day.
However on the Sheffield we experience almost daily shut downs with a number of different error messages. Sometimes this will happen repeatedly in the span of a few hours - other times things go well for the better part of a week.
I've had a problem where the software automatically triggers a hit upon start up and shows rapid movement in all 3 axis - only the controller is in "joy" and the probe head has not moved at all! It will then refuse to take any other hits.
If you restart the PC and turn the CMM off, and then back on, and re-zero everything, sometimes the software loses track of which tip it has, and never bothers to ask you either. So again, if you aren't careful, you will start checking your part with the wrong tip, only to smash up because of an extra extension or something like that.
We've had a few instances of the program skipping over clear planes that are marked active. I've also had the machine completely lose it's zero and try to move over 40 inches - like it's skipped the grid or something. Often times the machine will end up missing a feature by 1 - 60 mm because it has lost track of where it is. If you restart the CMM and Software, usually it will be fine, but on occasion this takes more than 1 try before it will work.
Once the machine even moved by its self while nobody was touching the controller or PC. The controller was left in Auto mode, which we try to avoid, but because of this unexpected move, the probe head hit a fixture - luckily there was no damage, other than to my underwear.
We've also noticed a few sporadic changes to set nominal and / or tol in pre-existing programs.
This is really just a general overview of the many problems we've had on a regular basis over the last year that I've been here. I can't say for sure, but I have heard that the previous programmers here had many of the same problems.
We've been cautioned against upgrading to version 4 because of glitches, and there were a few problems my co-worker had when we installed 3.7 MR3 last month, so we were told to switch back to MR2.
Does anyone else have these kinds of problems, or have any idea how to stop some of these errors from occurring? I have a feeling a lot of it is the software, or the PC, but I wouldn't fault the CMM itself either, since everything seems more reliable on the newer Brown and Sharpe.
Any help would be great!
Thanks,
John
Comment