> 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.
>
Not sure if I understand the problem.
You can name ladder programs with different names and change the CL
loading line to use the new name. - of course only one program can run at a
time.
> 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.
>
Why can't you use CL to channel the estop signals? There is a sample
of estop control in PNCconf .
Chris M
------------------------------------------------------------------------------
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
