I have not had the chance to run a dual turret lathe with a FANUC control, but I have a few thousand hours on a OKUMA dual turret.
Currently LCNC treats each axis as a reserved word and you can't duplicate axis. Okuma's Method to work around this used G13 & G14 to define what the program code would apply to. G13 was for the upper turret, G14 for the lower. By adding P000xx codes ( "Priority code" ) you were able to define which moves were independant and which could be executed simaltainiously. (adding this might require a GUI mod of a split screen for the different turret programs, even though its all one top down program in the file.) So far LCNC has been able to move forward as a "one size fits all" program package, where the only major divergant config is the type of KINS file the user chooses. The ability to map/remap codes sounds like an important way to allow different machine type to move to more machine specific gcode structures. At the initial config a install script could be called to sell the interpreter for "lathe", or "mill" etc. While the ability to define a multi turret or multi mill head type machine is likely a LCNC v2.8 or later type project, I would like the option of having G12/G13 pocketing in milling and G13/G14 for lather turret designation at some future time. Code mapping may be the first step in that direction. Greg ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
