Re: [CAD_CAM_EDM_DRO] Re: stable EMC version?

Tim Goldstein wrote:

> No not actual run away. The problem that had me diving for e-stop is related
> to offsets. In the balsa cutting I do I use a lot of G92 offsets (or what I
> think is the same by right clicking on the coordinates in manual mode and
> setting the coordinate value). What was happening is that I would set the
> coordinate to what I want and then when I would run the program it would
> decided that the current displayed 0 (that I had just set) was really not
> zero at all. With my first move being a rapid to 0 I would have the blade
> diving for the table at full tilt. Not a pretty sight. A couple times of
> that I was rapidly back to the old build. There were also a number of small
> bugs particularly with steppermod.o. I use steppermod.o because I am running
> G320 drives and they need a high pulse rate and don't care about the pulse
> pacing.
>
> The main reason I was interested in the BDI was for the 4 axis capability.
> Unfortunately that also has a major bug that causes follow errors in many
> conditions making it less that production ready.

Whew! Is this still the current condition of the latest BDI? I am starting to
set up to port all my parallel port hardware to BDI, but maybe I should
reconsider. I have BDI 2-12.

Do you know if the coordinate offset from the screen is the problem, or does
a G92 entered in the MDI window cause the same problem?

I had a problem once where interrupting a programmed 2 (or 3) axis move
could cause a later jog operation to move more than the axis you were jogging.
The motion code was trying to complete the interrupted move on the axis
you were not jogging. I think that one was cleared up, but rumors are that it
shows up once in a while.

Jon