Hi Jeff,
> Stepconf's "Charge pump" is an output activated when the PC is running
> and you click the "estop reset" button or press F1; it deactivates if
> you activate that button again.
>
That is what I expected but in practice the charge pump never activates.
> With "ESTOP in" (i.e., you have a real external estop chain) the GUI
> "estop" button has no function, but another consequence of this is that
> the charge-pump.enable is never driven TRUE by anything.
>
Umm, I have a real estop chain but the Axis EStop enable button still
works as expected. Is there any situation when using an axis drives
enable rather than user-enable-out would not work? Currently a Stepconf
generated config that uses an external EStop chain will not work. I have
to admit I haven't tested without an EStop input.
> or to use the estop_latch
> component so that F1 is still required to be pressed after the external
> estop condition is removed
Why do I need an estop_latch component? My EStop chain drives the EStop
input. If the chain is closed, the buttons in Axis work as expected, if
the chain is open the buttons are disabled, which is correct. My EStop
chain works as follows:
Estop switches---Charge pump driven relay ----contactor
|
EStop input
The contactor has a separate 'on' button to latch it on, which is not
shown for clarity.
Les
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
