Re: [CAD_CAM_EDM_DRO] Re: G92

Here's my take on this:

I. G92 has changed from being completely "sticky" to being reset by M2 and
M30. (This is essentially the core of Tim & Jon's posts.)

This was caused by Tom Kramer's rigorous interpretation of a standard which
many people feel is irrelevent (they may be right), and which contradicts
"traditional" machine control behavior (they are almost certainly right about
this). The problem arises when G92 is used as the offset method to set "part
zero". After the first pass through the program, G92 is reset ,which causes a
crash on subsequent runs (or at least considerable operator consternation).

Some questions are:

1. When you use G92, do you:

A. right click on the axis display and set the axis value using the GUI?

or

B. enter the G92 command in MDI mode?

or

C. use G92 in your program code directly (this shouldn't be a problem)?

2. Other than the G92 problem, are there any other problems with the new
interpreter?

3. Other than interpreter problems, are there any reasons not to upgrade
from RH5.2 systems to BDI (RH6.2) systems?

Please post answers if you have time! Short pithy answers are fine! I said
P_I_T_H_Y, not ...

Some possible solutions are:

1. If the problem is only with situation "1A", we could change the GUIs to
use G54 (or whatever offset is in effect), rather than using G92.

2. If the problem is with situation "1B", we could add an ini file
parameter like G92_BEHAVIOR = TRADITIONAL or CONTEMPORARY so the user can
have it the way they want.

3. If there are other interpreter problems (situation "2") we could make it
easy to specify which interpreter you want to use, the old or the new (ini
parameter rather than recompiling).

4. If there are other OS problems (situation "3") we'll have to do some
more thinking... ;)

II. Les described some discrepancies which, if verified, are bugs and need
fixing. They sound pretty serious, especially the "offset in effect but not
displayed" one...

III. Joel agreed with Tim & Jon, plus, I think his "backlash value is added
to the home position every time you rehome an axis" bug is still in there as
well, which must add to his frustration (although I think he told me he
changed to ballscrews to get past this problem). Needless to say, this needs
to be fixed as well...

I've been putting a lot of hours in on a contract to help get a CD labeling
plant running smoothly, but I read the list every night.

Thanks,
Matt