Re: [CAD_CAM_EDM_DRO] Re: G92

> 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?

>

No

> or
>
> B. enter the G92 command in MDI mode?
>

Yes (Used too, use G10 now)

>or
>
> C. use G92 in your program code directly (this shouldn't be a

problem)?
Yes (Only on non EMC machines now...)
Mostly as a way to quickly re-use code with a multiple part fixture...

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

(BDI 2.04)

I've run into problems with the M01 command. Every so often it will
apparently not recognize an 's' keystroke to resume. But instead it has
'double buffered' the keystroke, so that it doesn't pause for the next M01.

The .ini G-code initialization doesn't happen until F6 is pressed.

The .var file requires MM for the machine coordinates. (perhaps related to
the above G-code init thing.)
Or, maybe that's just Paul's BDI 2.04 revenge? :)

The G54+ coordinate systems don't activate on startup - have to cycle out of
a system (g54, etc) and back in again.

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

I like the RH6.2 system. I'd really like it if I could skip KDE and still
have something like the current interface running in X by itself, w/
Midnight commander for file ops. Have to look into it.

- Keith