Q re. motion. function (output from pncconf)

More
30 Jul 2011 03:25 #12006 by 1:1
Setting up a pin for drive enable in pncconf I got:
setp    hm2_5i22.0.gpio.050.is_output true
net 	enable     =>  hm2_5i22.0.gpio.050.out
net	enable     =>  motion.motion-enabled

hmmmm,

The motion.9 manual page says motion-enabled is an input

Seems to me motion.motion-enabled as an input is expecting a value has been wired to a physical output than expects an input (to output) ... Ha ha, oh dear - the confusion! :silly:. At least the arrows seem to be indicate what I mean.

How does this work ? (it appears to work in the actual hardware)

Kind regards,
nick

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 06:37 #12008 by PCW
Just a general note about Mesa FPGA outputs: These should almost always be active low. This is because the default state of all I/O pins is high initially (as the system is booting and before the HAL file is loaded and outputs enabled). This standard is followed in all Mesa daughtercards, for example
the 7I37 isolated output switches are on when their logic input is low.

To make the internal hal signals be active high (true=on) the output should have the invert-output flag set true

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 06:52 #12009 by 1:1
This is why I like the idea of charge pump ;)

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 07:20 #12010 by cmorley
enable is the driving signal. it drives motion.motion-enable and it drives the gpio-50

if you look carefully somewhere there will be a pin driving the enable signal

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 07:25 #12011 by 1:1
I already searched for it - cant find it ...

searched for the string " enable" (with the space in front)

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 07:36 #12012 by 1:1
yup, did another output just now to check I hadn't deleted a line by mistake...

theres no pin driving it

found another glitch also - see the attached screen capture then look into the HAL file - you'll see both drive enable pins have been sent to the same I/O (and that opendrain issue which you know about already)

I'm trying to nut out a drive enable issue in case you're wondering why I had two outputs there ;)

File Attachment:

File Name: 4axis_check.hal
File Size:13 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 08:20 #12021 by cmorley
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.

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 08:27 #12022 by cncbasher
what exactly is your problem ? , Amplifier Enable pin selection ?
net enable is Amplifier enable in pncconf

works fine here , so you may need to invert the output to suit

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 11:50 - 30 Jul 2011 11:51 #12026 by 1:1
pncconf file attached

change .txt to .rar

File Attachment:

File Name: 4axis.txt
File Size:7 KB
Attachments:
Last edit: 30 Jul 2011 11:51 by 1:1.

Please Log in or Create an account to join the conversation.

More
30 Jul 2011 11:57 #12028 by 1:1
cncbasher wrote:

what exactly is your problem ? , Amplifier Enable pin selection ?
net enable is Amplifier enable in pncconf

works fine here , so you may need to invert the output to suit


The problem is that it appears pncconf has wired two inputs to nothing ...

I was using it to help learn to write my own hal but now I don't know what to do :dry:

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.349 seconds
Powered by Kunena Forum