On 13 May 2015 at 02:50, <[email protected]> wrote: > It's not that I declined, it's that I already have 3 other CNC machining > centers from the late 90's in our shop that operate this way, so to have this > one run opposite of those, would mean that I would have to start buying > indexable holders by the pallet for every time they crashed the one that I > programmed.
The idea is not to run the _opposite_ way but to run an _offset_ way. For a machine with an example 48" Z travel... LinuxCNC convention is that Z = 0" is top of travel and Z = -48" is bottom of travel. You seem to be using top of table = 0 and top of travel = +48" (Or is the bottom of travel below the table?) In both cases Z+ is up and Z- is down. The only time that the difference is even noticeable is if someone explicitly programs a G53 move. Otherwise the difference is invisible, hidden by the G54/55 etc offsets. And, if the operator _does_ program a G53 G0 Z48 then he will just get an"out of bounds" error from LinuxCNC. (of course if he gets used to G53 G0 Z0 for retract in LinuxCNC and tries that on a machine set up differently then there might be problems) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
