Hello Guest it is April 13, 2021, 04:33:44 AM

Author Topic: ESS + Mach4 + Clearpath = Motor error input goes where?  (Read 4064 times)

0 Members and 1 Guest are viewing this topic.

Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #10 on: June 06, 2018, 05:22:30 AM »
Hi,
just noticed a mistake with the bias and load resistors.

Craig
My wife left with my best friend...
     and I miss him!

Offline thosj

*
  •  432 432
    • View Profile
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #11 on: June 06, 2018, 08:28:01 AM »
Thanks for all the effort you've put into this, Craig. I'll ponder it all but I'm leaning toward and simpler input solution. BTW, I have 4 axes, not three, not that that matters!!

My physical Estop button has two contacts, one to the PMDX-126 and one to the ClearPath power supply. I also have a latching relay on the power supply input, I press a momentary button to activate the power supply. I can start the PS either before or after Mach4 is running, doesn't matter. But if, like you say, the ClearPath's are "de-asserted" and Mach4 is started first, I can understand there might be an issue.

I won't have time in the very near future to get at this, but definitely will get to it. Reading your advice, I'm leaning toward the inputs/programming method and not trying to use the Gecko ERR/RST input/outputs.

Thanks again,

Tom

Offline Chaoticone

*
  • *
  •  5,626 5,626
  • Precision Chaos
    • View Profile
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #12 on: June 06, 2018, 09:36:18 AM »
I have used the enable ready signals of drives in a daisy chain, one ready signal goes to the next enable. That whole circuit controls a SS relay whos controlled contacts are in the estop loop.
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!

Offline Chaoticone

*
  • *
  •  5,626 5,626
  • Precision Chaos
    • View Profile
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #13 on: June 06, 2018, 09:52:40 AM »
I posted this example before but can't find it now.
« Last Edit: June 06, 2018, 09:54:42 AM by Chaoticone »
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #14 on: June 09, 2018, 11:38:36 PM »
Hi,

I am using clearpaths with pmdx-126 and ESS. I have the HLFB lines wired in series to a single input on the PMDX-126. The input I believe is configured as active high on ESS, red arrow up, and mapped to input 0 in mach.
The following code is used in the signal script of your screen set. The code just activates a cycle stop if the HLFB is tripped. I have had the HLFB trip quite a few times and the machine has always stopped as desired.


-------------------------
-- HLFB Error --
-------------------------
if (sig == mc.ISIG_INPUT0) and (state == 1) then
    local inst = mc.mcGetInstance()
    mc.mcCntlCycleStop(inst)
    mc.mcCntlSetLastError(inst, "HLFB Servo Error");
end

SignalTable = {
    [mc.ISIG_INPUT0] = function (on_off)
        if (on_off == 1) then
            mc.mcCntlCycleStop(inst)
            mc.mcCntlSetLastError(inst, "HLFB Servo Error");
        end
    end
}
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #15 on: June 10, 2018, 12:09:25 AM »
Hi Dusty,
given the number of circumstances that HLFB can trigger other than a fault I think your choice to have it CycleStop is better than Estop. Otherwise
your machine would Estop all the time....a real PITA

I'm a bit bemused by this piece of code:
Quote
if (sig == mc.ISIG_INPUT0) and (state == 1) then
    local inst = mc.mcGetInstance()
    mc.mcCntlCycleStop(inst)
    mc.mcCntlSetLastError(inst, "HLFB Servo Error");
end
I presume you have it in the PLC script so it reads the signal repeatedly? If that is the case its redundant.
The entry in the Signal Library should do the job on it own. Every time a one of Machs signals changes state the Signal Library table is scanned
to see if the signal which has changed is a signal of interest, in this case ISIG_INPUT0.

I note also that you hooked all your HLFBs in series so that you could squeeze it down to one input. Is there any particular reason to do so.....the ESS when suitably
equipped with BoBs offer us swags of inputs....is there any need to economise?

Craig
My wife left with my best friend...
     and I miss him!

Offline thosj

*
  •  432 432
    • View Profile
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #16 on: June 10, 2018, 08:17:50 AM »
Following with interest!

Isn't the serial wiring of the HLFB signals what Brett was alluding to when he said "daisy chain"?

And, is it not simpler to have, in my case FOUR, drives wired to one input, one set of code, or is there some reason to use 4 inputs and 4X the code just because you have these inputs available? What is to be gained with the multiple input method?

Dusty, where IS your code in the screen set?

Tom
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #17 on: June 10, 2018, 08:27:42 AM »
Hi,

Quote
What is to be gained with the multiple input method
Using one input per drive would allow you tell which drive faulted.

Quote
and 4X the code just because you have these inputs available
Four or five lines of code per input is hardly a big effort

Quote
you have these inputs available
Why not use them...they are after all available...or were you planning to use them for something else?

Craig



My wife left with my best friend...
     and I miss him!
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #18 on: June 10, 2018, 08:38:01 AM »
Hi,
just as a matter of interest if each phototransistor is on with a saturation voltage of 0.25V then four in series will put the input to your BoB a 1V.
That's awfully close, or maybe even greater, than the TTL low threshold voltage.

Craig
My wife left with my best friend...
     and I miss him!
Re: ESS + Mach4 + Clearpath = Motor error input goes where?
« Reply #19 on: June 10, 2018, 09:09:39 AM »
.... and that is why PMDX has not recommended the approach of wiring the HLFB signals in series.
Steve Stallings
www.PMDX.com
For PMDX product support, please use PMDX forum or direct email for quickest response. We do not use this forum as our primary product support site.