On 11/17/2012 6:05 PM, Eric H. Johnson wrote: > Kent, > > A heartbeat would be a nice feature although about the only circumstance I > can think of where loss of communication would be a problem is if it > occurred in the middle of a jog. Even there, the soft limit or end of travel > limit should stop the axis eventually, and worst case there should always be > a hard wired e-stop in close proximity to the operator station. > > So far I have found lcnc to be rock solid in the sense that it will run > <...>
Same here. It wasn't lcnc I was worried about but communications with and control of it. As you say, there's always the big red button. It would seem to me that the degree to which one worries about possible disruptions and their prevention or mitigation is a function of the degree to which the finished part is important. I look at your remark "because errors leading to reworking or scrapping parts can be expensive." It reminds me of my advice to my secretaries: never labor longer on a document/spreadsheet without saving than you would be willing to labor again if the system crashed. > > I want lcnc to do one thing, reliably control the machine, because errors > leading to reworking or scrapping parts can be expensive. Thus, where > possible, I prefer to offload any other functions not directly related to > controlling the machine. No problem here. I lean that direction too. Regards, Kent ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
