Q re. motion. function (output from pncconf)

"This is why I like the idea of charge pump"

Having a charge pump is additional insurance against inadvertent output actuation
but it does not change the fact that outputs should be active low (unless you want to build external logic that gates _all_ outputs)

Also the built in watchdog (which has the same function as a chargpump) is not useful unless active low outputs are used.

cmorley wrote:

try changing the signal name 'enable' to 'xenable' by hand.

The two signals being on the same pin number is an issue without a simple answer.
maybe i should have separate enable output signals for each axis available....

Please post your pncconf file. archive (zip) it first. I'm off to bed will look at it in morning.

Did you see the pncconf file a few posts back ?

I would change it to xenable - but thing is, pin 50 is working with it the way it is - how ?!

I can't down load the pncconf file the way you posted it.
either archive it and upload it or rename it with .txt ending and upload it .
doing both makes it not usable.

does your charge pump get enabled? check using halmeter

if I change it to .txt its too big
if I change it to .rar its not allowed ...


ok, lets try this...

change it to 4axis.rar though!

cmorley wrote:

does your charge pump get enabled? check using halmeter

I'm finding this hard to follow - the estop thread was filled up with discussion re. the issues pertaining to this thread - now stuff from the e-stop thread is being discussed here ??

The chargepump is in another HAL file - the one outlined at the other thread ...



I'm a beginner - I have to read up and remind myself on halmeter/halscope and get back to you - in the other thread ...

Ok sorry about mixing your threads

BUT here is the story on motion-enabled.

Looks like you found a bug in EMC.
In the manual motion-enabled is mentioned as an output:
www.linuxcnc.org/docs/2.5/html/config/emc2hal.html#_pins
every where else it says it's an input (including HALwhen the motion component is loaded)
But in fact even as it's called an input it works as an output.
turning the machine on and off with the GUI button changes the output of this pin.
trying to set it with
setp motion.motion-enabled true
does nothing.
I will report this bug and see what we find out.
Anyways thats why it works.

cmorley wrote:

Ok sorry about mixing your threads

BUT here is the story on motion-enabled.

Looks like you found a bug in EMC.
In the manual motion-enabled is mentioned as an output:
www.linuxcnc.org/docs/2.5/html/config/emc2hal.html#_pins
every where else it says it's an input (including HALwhen the motion component is loaded)
But in fact even as it's called an input it works as an output.
turning the machine on and off with the GUI button changes the output of this pin.
trying to set it with
setp motion.motion-enabled true
does nothing.
I will report this bug and see what we find out.
Anyways thats why it works.

heh heh...

bug in pncconf
bug in EMC

so what next ?

bug in planet earth ?



Ok - well, its nice to know whats going on though ! I don't have much time to look into it now (you've linked through yet another manual page I've yet to see by the way) - but is it actually a 'bug' or just a typo in the docs ?

a bug I think. The reason it's not been found is because it works as it's supposed to.
It's just reported as an input when its not.

But I will check into that.