> Date: Thu, 18 Jun 2009 19:45:59 -0500
>
> Chris,
>
> I've been meaning to reply to this. I experimented with it quite a
> bit and noticed some rough edges but I bet you know about them. About
> the overall design I'm pleased by how you split up the very complex
> task of configuring things. The step-by-step that you've chosen makes
> sense to me. The number of possible combinations of settings seems
> mind-boggling but you have made it so that earlier choices can limit
> later choices so they make sense.
Yes That was exactly what I was trying to do. Glad that the idea was
along the right track.
>
> I had trouble with the pinout pages - I could not tell if I was doing
> it wrong, or if it is not quite finished. I could not set up an
> encoder input because I could not figure out how to set channels other
> than "A".
I need to make a help page for that I think. Unlike the parport page you do
not choose which pin is channel A or channel B etc. You just set channel A
to the signal you want it to represent eg X axis encoder. If you look carefully
when you choose X encoder A the other related pins change - to x encoder b
x encoder I and (possibly) x encoder M . The pin numbers on the page represent
the physical pins on the card. After that pncconf knows that axis X has an
encoder (which ever encoder instance you chose). Basically you choose which
of the available encoder instances will follow the X axis (for example).
Now if you choose a custom signal name - you will find that pncconf makes
signals
that bear the signalname plus endings. eg if you choose 'my-custom-encoder' as
a signal name pncconf makes the following signals available:
my-custom-encoder-position
my-custom-encoder-counts
my-custom-encoder-velocity
my-custom-encoder-reset
my-custom-encoder-index-enable
You can connect them to hal components in a custom hal file.
later if you decide you would rather encoder 2 tracks the 'custom encoder'
instead
of encoder 0, just change the signal name 'my-custom-encoder' from encoder 0
to encoder 2. When you reload the config you will notice any custom signal names
will be added to the available signals in the combo box.
>
> Like with stepconf I bet it's hard to choose the correct scope because
> you can't handle everything. One part I see that I will probably not
> ever use is the parallel port stuff.
Yes Its hard to keep It general without making it complex. Also as I am the
only one
working on it at the moment so it only has my perspective and ideas. Hence why
I asked
for opinions.
The parport page originally was to support software encoders and software pwm
so one could have run a servo with just a couple of parports but it will have
to wait - I had to
draw a line somewhere :) For now it is just extra I/O .
>
> I'm not sure how much help this was, but I wanted to give some
> encouragement either way.
>
> Chris
Thanks Chris - Just to hear someone checked it out and could see potential is
encouraging.
I actually added the 5i20 firmware with encoder mask pins just because you
might need it to
try it out a config.- was a bit of work but forced me to generalize my mesa
routines which
is better in the long run.
Now that a few people are actually looking at it I will have to work harder to
get to beta
stage :)
Chris Morley
_________________________________________________________________
Create a cool, new character for your Windows Live™ Messenger.
http://go.microsoft.com/?linkid=9656621
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
