I am working on the finishing touches of an Anilam 1100 knee mill conversion to EMC2, with details here:
http://code.google.com/p/sector67-sandbox/wiki/ProjectSheetCake Over the last couple of months our spindle VFD (a Compumotor SpindleBlok) has faulted 5 or 6 times (a description of that particular problem can be found at http://code.google.com/p/sector67-sandbox/wiki/1100SpindleBlok, but that is not really central to the issue). The spindle and EMC2 to this point have not been integrated at all. However, I am hoping to integrate a spindle fault signal to put EMC2 to an estop state, or to at least stop milling. This has been somewhat complicated as the previous Anilam system simply switched 240V on and off to the spindle on machine enable. The 240V also powers the VFD logic, and so when the machine is off it appears to be in the faulted state. I've worked through this particular problem by creating a classicladder program that takes in a delayed enable signal as input and my custom spindle-fault as an input and outputs a signal that appropriate signals a spindle fault when the machine is enabled. So far so good. Now, I want to integrate that spindle faulted signal into EMC2 and am somewhat struggling with the "best" way to do that. The machine is a CNC mill for a hacker space and we'll likely be running it in multiple configurations, e.g. normal 3-axis milling, different 4th rotary axis configurations, etc. I am hoping to make the configuration somewhat modular so that alternative configurations don't have to be copy and paste but rather can include files as needed. I've been using the hal "source <filename>" command to include other files with custom hal commands (an analog joystick jog and a custom servo-reset signal that Anilam used), and this has so far worked to make the configuration somewhat modular. Now I find myself with two ladder logic programs and needing to add a new way to get to the estop state. I don't seem to be able to determine a clean, modular way to do that. I can run the two classicladder programs in one file and hook up the inputs and outputs as necessary of course, and that is not such a big deal (but if there was a way to load individual classicladder programs that would be great). However, the bigger challenge is now to add a new way to get the machine to estop when the spindle faults. It seems the normal way to do this would be to take the input to the existing estop-ext signal put that into an or or component and link that with the spindle fault and the link the or component to the estop-ext. However, that can't be done in a very modular way from what I can see. Any opinions on the best way to integrate multiple external estop signals? Thanks in advance, Scott ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
