On 10/17/2011 6:51 PM, Len Shelton wrote: > I have witnessed that M64 seems to be turned on by default, even if the > M64 does not appear in your g-code or in the list of active g-codes on > the MDI screen - but with some really high unknown tolerance parameter. > Sometimes the machine will run for a few weeks on a fresh EMC2 install > before the M64 it seems to "turn itself on". And sometimes if you set > the P parameter to a low value in MDI, it will at some point (days or > weeks) lose the P parameter and return to the really high unknown value. > We install EMC2 on 40 or 50 machines a month and this condition appears > often. > > Any comments? > > >Len > Len:
I expect an EMC2 ninja will look into this. I'm just curious if you meant G64 (set path control code) rather than M64 (turn on digital output bit)? From your description, this sounds like one of those hard-to-diagnose situations where a bad pointer or buffer-overflow or the like results in the parameter getting overwritten. Good luck. Regards, Kent ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
