Peter C. Wallace wrote: > > I think the saturated PID output is a fairly good way to detect this > condition > and certainly would have workied in this circumstance. No, I believe not. This happened probably before the LinuxCNC PID loop was even turned on. It was purely the G320 coming active and trying to null out a one-count offset from power on. The encoder was presumably not providing motion detection to the PC or the Gecko, and so LinuxCNC had no reason to have a non-zero PID output even if F2 had been pressed and it was in "machine on". > Errors when moving are easier to detect and handled by the built-in following > error limits. > Yes, that's true.
Jon ------------------------------------------------------------------------------ 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
