CMM GOING TO SPACE and WRONG TIP

[Jeffrey Lovely]

I am running 3.5 MR2
How often have you had ,if ever
Have you ever had the machine take off during a program
to an unknown move - that is not in the program
or had your tip not rotate and try to take a measurement
with the wrong tip ?

[J Temmen]

As far as the not rotating part, I have that happen every now and then, I just STOP the program and use the Renishaw HCU to change the angle manually and CONTINUE. The move into space i'm not familiar with.

[Mr.Natural]

Thru my experience PcDmis does what it's told to do 99.9% of the time. The exceptions i've had where it did stupid stuff, was when a board was going or had gone bad, excessive heat at the controller can make it do strange things & wiring problems, intermittent wire breaks in the energy trac, where during certin parts of the pgm it ran fine but once the energy track traveled past a certin area strange things would happen. But for the most part it did what it was told to do, Pgm wise that is.

[Paul Sarrach]

Never had that experance.

[rebeldude]

Jeffrey,
I have had that problem with 3.7 MR2. Since I upgraded to MR3 I don't have that problem anymore. Try MR3. It is more stable

[Hilton Roberts]

I have had the machine sometimes fail to read a probe rotation and try to do a swan dive into the plate. It does not happen often but will sure get your blood pressure up when it does. I still do not understand how that happens.....

H

[Craig H]

I had that problem a lot with 3.7 MR2, I would run a program several times fine, then it would just drive off somewhere???? I've upgraded to MR3 and it has not happened yet. B&S said it was something wrong in my programs, it did not do it in MR1, it did do it in MR2 and now it does not do it in MR3. Hmmmm

[Matthew D. Hoedeman]

Well, of COURSE it was YOUR program, it could NOT have been anything that WILCOX/B&S did to the software. Haven't you figured that out by now?

The problem with the wrong tip sprung up in V3.5, which is also when they added the function of changing the probe angle WHILE the machine was moving (I think), which, of course, only works with a few controllers and very few at that. NOT a function or feature I would ever have wanted added to the software, but that 1 user out there that has the ear of Wilcox (for the 'user-driven-improvements') wanted so it was added. I have not had it happen in the middle of a program, EXCEPT for the first tip change AFTER a DCC alignment. Quite often in manual mode for the manual alignments and in DCC for the beginning of the DCC alignments, but sometimes also for the first feature AFTER a DCC alignment.

[mtalla]

space cadet

Sometimes when I jump through a program, the machine will have a "left-over" incorrect tip angle present (not the one needed for that particular feature), and will move as though it had the correct tip angle. Sometimes this looks pretty spacey, but with the correct tip angle would otherwise be alright.

[kpayne]

I had a program this morning not rotate to correct tip angle a start of program and the program had measured at least 20 parts with no problems. I had this problem early last year when I first upgrade from 35mr2 to 37, but it only seem to miss the tip angle rotation occasionally on programs written in 35mr2 and executed in 37, and like others have said only at start of program or after probe change from the tool changer. I had a couple programs last year that had to insert a program pause to make sure probe was at correct position and would not attempt to drive into part or machine table. I am currently using 37mr2 and have not had a problem until today. I guess maybe I should look at 37mr3 according to some of the previous posts.

[GeoScans]

The only time I had that happen to me was I did not re-qualify the probes prior to running the program.

You might want to try that first.

[craiger_ny]

Did you try that Jeffrey Lovely? I certainly hope you have not been down with this problem since April.

[John Riggins]

I had a program this morning not rotate to correct tip angle a start of program and the program had measured at least 20 parts with no problems. I had this problem early last year when I first upgrade from 35mr2 to 37, but it only seem to miss the tip angle rotation occasionally on programs written in 35mr2 and executed in 37, and like others have said only at start of program or after probe change from the tool changer. I had a couple programs last year that had to insert a program pause to make sure probe was at correct position and would not attempt to drive into part or machine table. I am currently using 37mr2 and have not had a problem until today. I guess maybe I should look at 37mr3 according to some of the previous posts.

I have this problem with 3 or 4 different programs. I think it is definitely a "version" problem. The problem programs were written with V3.7 MR??

Since we upgraded to V3.7MR3 the problem has not occurred with any programs written with MR3. The older programs (written with MR??) still exhibit the problem. In other words, upgrading to MR3 will not fix the old programs.

I will need to re-write the problem programs some day. In the mean time I added a pause before every angle rotation so that the operator is given at least a chance to observe and prevent a crash.

I am not 100% certain of this conclusion, but I know the newer programs do not fail to change angles.

[Tony.Hirotec.Aus]

Hi mate
We had similar move problems with our machine. turns out it only happened after an E-stop but our Hexagon guy got a patch file in from Singapore to replace our dicky one. We are running V3.7mr3 and were told V4.0 had fixed the problem but having tried V4.0 for a couple of weeks we are not keen to go there again. We were told that this was only the second time in the world this had happened, pop the champagne corks if you're number3

[Paul Barriage]

We have 4 machines. It happens on 1. Go figure. 3.7 MR1. It started in 3.5MR1.

USUALLY, it happens only on the first probe rotation at the start. The person running it is there for the experience. Otherwise, we would be pulling our hair out like you. You might think of the upgrade mentioned, or get Tech to look at it. Our tech thought I was joking, till I showed him. It was always more inherent to certain programs, but not in a traceable fashion.