Re: Why is a Gcode standard important???

Brian,

I think we have seen a lot more Gcode standardisation in the last ten
years than in the thirty before... And this is the nature of
developing vs. mature industries; i.e., divergence followed by
convergence.

The USA good-ole-boy network that is the machine tool industy has
been getting its' butt kicked, and I think they are noticing some of
the reasons why. After all, EMC was developed to address this "butt-
kicking"...

Since you DO agree that you would LIKE a GOOD standard, don't be
afraid to speak up! (to mfrs. at trade shows, letters to tech
support, help to control writers, etc.

Remember, one person CAN make a difference, EITHER WAY...

"for want of a nail, the shoe was lost..."

Let's get an update of 274D!

Ballendo


-- In CAD_CAM_EDM_DRO@y..., Brian Pitt <bfp@e...> wrote:

> Ballendo
>
> > Obviously I don't agree with you on this.
> >
> yup ,I didn't figure you would ,we'll just have to agree to

disagree :-)

>
> its not that I wouldn't LIKE to see a true standard ,it would
> make things much easier if there was one
> but unlike a data communications standard the code implementation
> is not in itself the product ,the major players in this market have

just

> enough incentive to make it recognizable to the user while still

being

> slightly incompatable with the compitition's product
> and that practice has WORKED for them all this time!
> so no I dont see it changing in the next 50 years ,if anything the
> confusion will get worse as the machine controls keep getting better
> (hey there is a bright side anyway :-)
>
> Brian