On 07/13/2015 10:27 AM, Gene Heskett wrote: > I am not worried about vandals in my shop, but swarf is a major PITA, and > the only keyboard I have found to be useful in that dirty environment is > the logitech K360, which has keytops with vertical sides.
I use Logitech K400 wireless keyboards with silicone overlays. They aren't coolant proof (at least not flood coolant) but they're swarf proof and very convenient. I use them as keyboards for entering and editing G code, but this keyboard is small enough to also use as a wireless jog pendant at the machine, and the wireless communications seem robust and reliable even in an electrically noisy environment. http://www.amazon.com/Logitech-Wireless-Keyboard-Multi-Touch-Touchpad/dp/B005DKZTMG http://www.amazon.com/silicone-keyboard-Logitech-Wireless-Keyboard/dp/B00DE7SHII > On Monday 13 July 2015 10:11:40 andy pugh wrote: >> the Vandal-proof keyboard I use on the lathe has no "Ctrl" key. >> Yes, that is quite inconvenient. And yes, Andy, the nearly vandal resistant K400 has a Ctrl key. :-) As for the original topic, I think it would be great if there was a key like the escape key that would always get the attention of LinuxCNC and force it to stop whatever it's doing and return to an idle state. The escape key seems to work for me in most/all instances I've tried, but I doubt I've ever had two subroutines with the same name to confound the G code parser. I do a lot of cut and paste G code too, but I'm fairly fussy about making sure the subroutines are all named uniquely, etc. Even though I can't program my way out of a wet paper bag now, I wrote a lot of code in my youth, and good habits are as hard to break as bad habits. I try to have a good zoomed out understanding of how the code works, and that requires a manual attempt to parse the code to detect any problems like subroutines with the same name before I try to run it. I'm even more careful about verifying code that moves machinery. Nevertheless, I think LinuxCNC would be more robust if it could make a first pass through the code looking for this type of obvious error, with a controlled exit and an appropriate error message rather than locking up, even if I don't plan on ever testing that error checking capability. :-) ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
