2012/5/2 Michael Haberler <mai...@mah.priv.at>: > The only change wrt to the interpreter is the access modality for tool length > offset and tooldiameter parameters (#54xx): so far those were considered > untainted because no entity except the interpreter could change them. They > now can change at any motion (due to toolchange during pause), which is why > came up this state reference model in the first place - they are now 'tainted > by motion'. > > That said, the only execution difference will be: if you refer to a #54xx > parameter, a sync will happen before the referencing block is executed. So > far it didnt. But that shouldnt cause any user-visible behavioural change > except that 'current tool parameters as seen by the interpreter are "more > correct"' ;).
Thank You, seems like I start to understand! The only question is - how is user supposed to change #54xx parameter values as new tool is inserted in spindle? Viesturs ------------------------------------------------------------------------------ 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-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
