Re: [CAD_CAM_EDM_DRO] Why is a Gcode standard important???

From: "doug98105" <dougrasmussen@...>
To: <CAD_CAM_EDM_DRO@yahoogroups.com>
Sent: Tuesday, December 25, 2001 5:13 PM
Subject: [CAD_CAM_EDM_DRO] Why is a Gcode standard important???

> Group,
>
> There's been much discussion about what is "standard" and what is
> not.
>

My experience during my employed life was with fanuc and bos controllers,
dolphin and camtec, off line CAD/CAM programming. In my considerd opinion
'G' codes, in the "industrial sector" are standadised. and there are
several US and EU standards covering these codes. Since retiring I have used
Turbocnc, MAXNCPRO, and MAXNCDLX, all use what I consider STANDARD G CODES
for programming

> My questions....Why so much concern over standardizing Gcodes? Why
> does it matter? Who is adversely affected by non-standard Gcode?

If Mr Whitworth had not considered standardisation of screw threads it would
be impossible to purchase a "Standard" nut and bolt of any modern thread (
SAE, BS, or Metric)
Without a srandardThe user is affected by the use of "non standard" Codes as
he would be tied to the software provided by a single manuf( would consider
everone who use G codes
wouldmbe effeted>

> What about conversational programming? Why no efforts (to my
> knowledge) to standardize that?

I would think if you are using conversational programming there is no
requirements for a standard . Do we have a standard for conversation?

> thanks,
>
> Doug
>
>
>
>
>
> Addresses:
> FAQ: http://www.ktmarketing.com/faq.html
> FILES: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO/files/
>
> Post messages: CAD_CAM_EDM_DRO@yahoogroups.com
> Subscribe: CAD_CAM_EDM_DRO-subscribe@yahoogroups.com
> Unsubscribe: CAD_CAM_EDM_DRO-unsubscribe@yahoogroups.com
> List owner: CAD_CAM_EDM_DRO-owner@yahoogroups.com, wanliker@...
> Moderator: jmelson@... timg@... [Moderator]
> URL to this page: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO
> bill,
> List Manager
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>