G0 should not be used for cutting. It is only for positioning when the tool is at safe Z height (out of workpiece and clamps etc.). I have worked with Fanuc and Siemens controllers. In these controllers when G0 move is programmed, all the axis used in G0 move starts moving at rapid feeds (set in the parameters of the controller) and the axis that achieve the position just stops and others continue to run. So G0 move produces a non-linear move. This is normal behaviour.
So G0 move should finally achieve the target position not the linear path. That is why it must be used for positioning. Thanks Shabbir Hussain --- On Fri, 6/12/09, Eric H. Johnson <ejohn...@camalytics.com> wrote: > From: Eric H. Johnson <ejohn...@camalytics.com> > Subject: Re: [Emc-users] Subject: Re: Successive G0 moves > To: "'Enhanced Machine Controller (EMC)'" <emc-users@lists.sourceforge.net> > Date: Friday, June 12, 2009, 1:48 PM > Dave, Alan, Andy, > > Thanks for the replies. I have read all of those things > too. I would > reiterate that this is something that occurs very rarely, > but when it does > happen it is very damaging. I have two basically identical > machines which > have been running for the last 7-9 months, and this problem > has only > occurred a handful of times over that span. > > It is also easily remedied in the G-Code, but the > application is basically a > once and done type, which means I need to in some way > anticipate the > conditions under which it occurs. My current brute force > approach is to > insert an additional line of G-code between consecutive G0 > moves any time > the distance of the first G0 move exceeds some threshold. > Even though > 99.9999% of the time, the extra line of code is > superfluous. > > But without being able to quantify exactly when it will > occur, there is no > guarantee that my brute force fix will in fact prevent it > from occurring > under any circumstance. > > Regards, > Eric > > For rapid linear motion, program G0 X- Y- Z- A- B- C-, > where all the axis > words are optional, except that at least one must be used. > The G0 is > optional if the current motion mode is G0. This will > produce coordinated > linear motion to the destination point at the current > traverse rate (or > slower if the machine will not go that fast). It is > expected that cutting > will not take place when a G0 command is executing. > > It is an error if: > > . all axis words are omitted. > If cutter radius compensation is active, the motion will > differ from the > above; see Appendix B. If G53 is programmed on the same > line, the motion > will also differ; see Section 3.5.12. > > > > Somehow the definition and the described motion don't seem > to > match. Bug? > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited > royalty-free distribution of the report engine for > externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
