Error #438

[Deon Gerber]

Hi Dave

Upgraded to the newest version.
Want to start using Probing and TLO but get the above error. Full error is as described below.
"User Escape Key or Probing Function runtime error #438, Object doesn't support this property or method"

Started off by setting the touch Plate position.
Activated the TP installed button.
Used the go to TP position button.
Did the TCP TP calibration sucsesfully.

Now if you do a tool change it moves in position but as soon as it starts the probing routine it gives out above error.
Same go's for probing the part Z height.....same error.

Need to add that after I upgraded I had a hard time with the licencing but after a couple of uninstalls, re-installs and a couple of restarts that was sorted.

Did not find much on the forum about this topic. Only 2 posts that ended inconclusive.

Mach3 ver xxxxxx66
Windows XP

[DaveCVI]

Hi,
I'm pretty sure this is a something is not installed correctly issue. Most often this happens if someone got a mismatched set of MSM files - some from one version, some from another.
Please run the MSM installer to reinstall MSM. You can just let it install on top of itself to get all the pieces in the right places.
Please let me know if that solves the problem.
Dave

[Deon Gerber]

Hi Dave

Still the same. After about 6 re-installes.
I do find that after a restart the first tool change go's down without a hitch but after that every time I get the same error.

Tool moves to the correct Tool Change Position but as soon as the Z probe event starts I get the error.

I will keep on experimenting and give you more feedback if something pops up.

Thx
Deon

[Deon Gerber]

Hi Dave

Re installing Mach 3 seems to have solved the problem for now.
In a couple of tests up to now I did not receive the error again.

Something that I do get every now and then is "surface not found" on the 2nd slow probe.
Are there a relation in MSM's code between the first and second probe or do you think I have a wiring issue.

By relationship I mean is there a spesiffic tolerance that has to be met between the first touch and the second touch.

Thanks
Deon.

[DaveCVI]

Hi,

Hi Dave

Re installing Mach 3 seems to have solved the problem for now.
In a couple of tests up to now I did not receive the error again.

I'm happy that the mach reinstall fixed things for you. A clean install would have been one of my next suggestions. The error happens when a script calls a library which is mismatched for version. Usually it's an MSM library, but can happen if a mach library is bad too.

Something that I do get every now and then is "surface not found" on the 2nd slow probe.
Are there a relation in MSM's code between the first and second probe or do you think I have a wiring issue.

By relationship I mean is there a specific tolerance that has to be met between the first touch and the second touch.

Thanks
Deon.

Yes, there are several probing parameters which can interact. You can look at all the Probing Op Parameters in the MSM manual. Example: XY clearance and XY max distance - if clearance is > Max xy distance the 2nd op would fail all the time (A sort of extreme case).

Honestly, I recommend that you turn off the 2nd probe operation. Really just turn it off and don't use it (Set Probe Slow FR to 0). There are several post on this board where I note that I have never, ever been able to measure any increase in accuracy from using the 2nd probe op. Never.
So why is that feature there you may wonder? Because it's a religious issue to some early users - they think it will make things better. They have seen the feature on commercial systems and want to have it too on their small mach based system.

Perhaps it matters if you are using a renishaw probe setup.... but for the types of probes typically used with mach and MSM? I have never been able to measure that and neither has any other MSM user been able to supply me with a test procedure and resulting data to show that it helps. Worse, Probe slow feed rate is almost never achieved. Most people set the back off distance from the first probe very small (as they don't like re-transversing a larger distance). Accell limits on most machines means the 2nd op never gets to the input feed rate. Thus the fed rate (and hence the repeatability) becomes a function of the back off distance instead of the 2nd probe feed rate.

You can also get false triggers from probing too slow. Most think that slower is better, but that's not so. the slow false triggers can stop the probe motion, then when the probe scripts look at the state of the probe after the motion is stopped by mach, they see that the probe is not triggered - and you get the "Face not found" condition.

While the feature works every time I try it, many years ago, I turned it off for my regular work as it's just wasted time the machine does not need to spend.

Dave

[Deon Gerber]

Thanks for your time and explanation Dave.
Its really apreciated.
Will report back on my progress.

Thanks
Deon