Ugh... I realized I was trying to reply on this thread from a different
email account and the mails didn't come through. In any case, I ended up
solving this with a classicladder program for estop and a separate one to
delay the spindle fault estop signal until one second after the machine was
On 11/8/11, Karl Cunningham ka...@keckec.com wrote:
On 11/06/2011 08:36 PM, Scott Hasse wrote:
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
On 11/06/2011 08:36 PM, Scott Hasse wrote:
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
On 11/06/2011 10:36 PM, Scott Hasse wrote:
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
On 11/06/2011 11:47 PM, Kirk Wallace wrote:
I read a little more from your website. I see your chicken and egg
problem, even with the independent loop I would think the VFD's fault
relay would be open until the VFD powers up, but you can't power up
until the loop is closed. Obviously, I don't
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
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
On Sun, 2011-11-06 at 22:36 -0600, Scott Hasse wrote:
... snip
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
On Sun, 2011-11-06 at 21:28 -0800, Kirk Wallace wrote:
... snip
EMC2's e-stop out signal should be in the
loop as peer, but the loop should be the mechanism that breaks to power
to the dangerous bits. You might also look into a charge pump which can
monitor a PC or software fault.
