alex do you have time to look at a manual change?
I added the home final vel to the manual
vs. an automatic change?
"manual change" vs. "automatic change" :)
[13:05:30] <BigJohnT> http://pastebin.ca/1035815
or you could talk Chris into adding me to the document team now that my spell checker works :)
BigJohnT: do you feel that you fit this? http://www.linuxcnc.org/content/view/50/13/
I feel that I can assist on the documents at the least for now
well.. then, you need to convince some of the board to bring it up :)
how does one go about that?
you ask me nicely :)
haha.. ok, that should do it ;)
what are your plans on docs?
(right now the biggest lacks are in the integrator and devel. manual)
users manual is pretty ok, although some parts might not be up to date (HAL tutorial & such)
as we talked about before I'd like to add an external hardware section or something like that
yes, some are out of date I noticed
the latency test for example still describes the old way
be back in a bit breakfast is ready
mmm, that was good
* BigJohnT reading it
if we had a synchronized public git repo, anyone could clone it and just start working
then they post to -dev saying 'lookiehere' and it gets merged into cvs
ok alex_joni I have it done
fenn is volunteering on classes on git?
its not any harder to learn than CVS
fenn: you really think that?
I tried to.. and failed
um, yeah, why?
it might have gotten easier in the meantime
for starters .. there are about 150 executables
i know there's been a lot of work on interface
that's actually useful
yeah, if you can remember what does what
there's man pages for each sub-command
fenn: right.. LOTS of them
I spent about 30 minutes last time for a very simple thing
but it makes it easy to figure out what the command does, instead of paging down through a huge long monolithic chunk looking for what you want
anyways, for now I don't like it.. maybe I'll look at it again in the future .. will let you know when I do
I tried git and also got lost somewhere between edit and commit.
I'm looking at the man page for lut5.
It says "The function is specified by the HAL pin function."
Seems to me this is a param named lut5.x.function.
I think lut5 is a component only a programmer could love
There you go.
I was thinking of it as a way around the single pin limit as home.
For a four axis mill I need to orr all the is homing and and the limit pin
anything lut5 can do, classicladder can do
each has pros and cons
seems a shame to have to edit a ladder if that is the _only_ logic you need
Yea. That is my first approach.
but if you have lots of logic, a ladder is easier to understand
We are thinking alike here.
A single rung of ladder handles this issue easily.
But I don't immediately see how a single lut5 can do it.
The 1 or 2 or 3 or 4 and 5 would pass the homing signal.
but not inhibit the limit
Want me to fix that man page?
you mean make it clearer? (or is there an actual factual error in naming? I didn't quite follow your original statement)
oh, it says "hal pin 'function'" and should say 'hal parameter 'function'"
The function that defines the logic is called a pin the the man page.
You got it.
sure, by all means fix it
alex_joni: should I email the id_dsa.pub file to you?
BigJohnT: to me or to cradek
I'd rather see it changed to a hal pin
alex_joni, So fix lut5 rather than the man page.
Is there some way to copy locally emc mailing list archives ?
rayh: it's both in the same file
the manpage is generated from the same comp file (emc2/src/hal/components/lut5.comp)
I see that. I won't do anything there and let a real programmer decide what it will be.
it's funny how much bigger the documentation for lut5 is than the implementation.
The source for the tables is way awkward. Looks like wiki junk.
its manpage junk
yeah, with a second html table version for the online documentation
alex_joni: exactly how far from "zero" do you think the odds are that someone would want to vary the value of a lut5's "function"?
I just went looking for it's author and it's jepler
jepler: I'm thinking about converting all params to pins
Now I'm confessing my ignorance but isn't the function the way that we tell lut5 how to relate the five pins to the output?
I believe that for the class I will use ladder instead of lut5.
like jmkasunich says, lut5 is something only a programmer could love
I think that probably says something about what I am not!
unloadrt lut5 -- that was easy enough.
EMC: 03jepler 07TRUNK * 10emc2/src/hal/components/lut5.comp: function is not (presently) a pin
(actually you would use function as a pin if you want a function of more than 5 binary inputs -- for instance, for a function of 7 inputs you'd use a u32-mux4 (which doesn't exist) for two of the inputs, giving one of 4 different lut5 functions for the remaining 5 inputs .. yeah, like anybody is going to want that instead of a custom component or a ladder rung)
The custom component idea was also a possibility.
I wrote one of those once. You guys made it very easy to do.
It's birthday party time for a grandkid bbl.
ooh I'd forgotten about this little toy: http://axis.unpy.net/01163779208
see you rayh
see you ray
jmkasunich: how about TP?
wouldn't that matter if it gets run at different times?