you guys are awesome.
do we still need bot INPUT_SCALE and OUTPUT_SCALE in the ini?
or is that only used in HAL config now?
if it's still somewhere in EMC, it should probably be removed ...
there are a few remains
a couple of the guis do use INPUT_SCALE
./emc/usr_intf/xemc.cc:// the size of the smallest increment to jog, = 1/INPUT_SCALE
bummer. that's non-intuitive for stepper configs
axis does something like that too
what do you mean? (if it works) it lets you jog one step at a time
it's an OUTPUT_SCALE in stepper configs ...
(for people who don't know that emc still tracks the position based on stepgen output)
maybe we should (one day) call it SCALE
yeah. and possibly get rid of the offset
though it's probably still used in analog servo systems
eh. that can wait for a redo of the config system
argh. lyx-qt is being annoying
I can't view as PDF because there are several errors:
Font T1/cmr/m/n/12=ecrm1200 at 12.0pt not loadable: Metric (TFM) file not fou
(yes, the error is cut off mid-word)
any suggestions? I haven't changed fonts at all, except to select "title" for the title, and bold for some other text
can you view-as-pdf any of the other fiels?
do you have tetex-extra installed?
I can't view others, but it 's due to style "bookman" not installed ..
ah - no
is there going to be a separate emc-doc package?
that would make build-dep a little easier to manage :)
yeah but people (especially upgraders) wouldn't have the docs we'd like them to have
it may be useful anyway, since people without emc may want to be able to read the docs ...
damn. it's already almost a page using the default style
and I've only gotten through the formula for INPUT_SCALE
btw I figured that out with "apt-file search crm1200"
I'm still hoping for one page quickstarts :-)
I don't think that search would have worked for me since the package wasn't installed
yep - working on it :)
I'd like it to be at least somewhat useful, not just a ghost placeholder
yes, that's the point of apt-file
it gets the list from the repositories
I use it all the time
which pdf output do you usually use? (pdflatex, ps2pdf, dvipdfm)
I only know to type 'make'
err - the document generator ;)
I have no idea how to use lyx
I used to write LaTeX by hand but I'm rusty (and I didn't care about pdf at the time)
hmmm. well, it uses lyx --export=pdf2
whatever that means
it might be latex2pdf - I got errors about that being missing. I think I was running configure when I got those errors.
thanks. it seems to be working with whichever one I clicked a couple of minutes ago :)
oops, it was when I ran apt-get install latex2html - didn't have the multiverse repository enabled.
SWPLinux: I'm working on some notes to put in standard_pinout.hal (in the stepper sample config). would you give me your comments: http://pastebin.ca/324220
cradek: on my system, tetex-extra was already pulled in by latex2html -- any idea why that wasn't working for others?
Depends: perl, netpbm (>= 2:9.20), gs, tetex-bin (>= 1.0.7+20001218), tetex-extra
hmm, no idea, looks like it should have been.
cradek: looks good to me
SWPLinux: I wonder how/if this fits in with your quickstart
my thinking is this might help with more common questions
well, I hadn't gotten to the pin configs yet - mostly scales
back in a sec
am I missing anything obvious?
you could use net instead of newsig/link
do we have net now?
but the latter might be nicer for an introductory doc
yes, its backported
so for the last command, the equivalent command would be net Xlimits parport.pin-13-in axis.0.neg-lim-sw-in axis.0.pos-lim-sw-in?
or do I need to say 'bit' somewhere?
no need to say the type
net declares the signal type to match the pin(s)
you can add an arrow if you like: net Xlimits parport.pin-13-in => axis.0.neg-lim-sw-in axis.0.pos-lim-sw-in
to be honest, for people who don't yet "get" hal, the newsig and link might be better
[02:55:19] <cradek> http://pastebin.ca/324226
might rephrase the comment, it sort of implies that you can only use net in this specific case
lemme take a stab at it
huh, we had spindle-on => parport.pin9 by default, I wonder if that's good or bad
[02:57:44] <jmkasunich> http://pastebin.ca/324228
hmmm. unfortunately, a one-page guide doesn't leave a lot of room for examples. and I think the HAL config needs examples
I notice a _lot_ of stuff is being done in the 2.1 branch, instead of in trunk and then backporting
yeah that's going to bite us, isn't it
its gonna be a bit of a chore figuring it out
I understand the deb system being in 2.1, once its working good, move it as a lump
but these scattered improvements would be a shame to lose because we forget to move them
I should have kept the emails, but I deleted them all
maybe someone who kept them all can easily spot the things we need to move
I kept them
they might be on the sf archive if it's working these days
I didn't even know commit was arhcived
I guess I just assumed all lists were archive
yeah, but that is painfull to use (as is my webmail) when you need to review many messages
I'm pretty sure commit is archived
* jmkasunich checks
that's a good fallback then
and its pretty up to date
what I need now is a nice relaxing weekend
not perfect, maybe 8 hours old
I can write an mbox of commit mails in a date range pretty easily
wow... the users archives (going back several years, since it was moved from NIST) has 7922 messages
the commit list, which is newer, has 7849
the dev list has 3947
we have 640 subscribers to -users
I remember when it was less than 300
argh. it's hard to decide what's important for the quickstart (other than a list of pointers to other docs, once I figure out how to make those :) )
I think the list is units, scale, parport setup, stepgen setup
though stepgen setup also includes machine limits, and I don't want to write a primer on determining the limits of the machine
and, speaking of limits, there are axis home and limit switches, travel limits ...
you have the honor? of writing the one document that most people will actually look at
err - yay
I'm not sure it can be kept to one page, expecially because I'm wordy :)
if you like, I'll help you take out words (really)
sometimes I'm ok at boiling things down
lemme commit what I have. there isn't anything (useful) about stepgen or parport yet
yep. a blank page is so intimidating. it's much easier for me to edit ...
thats why I'm making each new manpage by editing the prior one ;-)
I think the secret is don't worry about writing the first thing first, just write something you know needs to be there
retch... function pid.0.do-pid-calcs.... what was I thinking
today it would be "pid.0"
names are only needed when there are multiple functions for a component
I knew I forgot something
maker of fine quality machine tool accessories (the ones that are too cheap to have come from india)
must be a new day on CIA - my reign is over
I had a brief but glorious reign at number 3
a friend of mine was in the Philippines while in the air force. he had to get the drivers side door repaired on his Jeep, so he brings it to the shop. When he got it bach, they had fixed that door, by scavenging the hinge from the passenger side :)
I think that's when he bought the Haines manual :)
(/even worse than India story :) )
and they probably had to mount the passenger side hinge upside down to make it fit on the drivers side
something like that, though they may not have bothered
it is a Jeep, so they may be the same
(an older CJ-7)
dunno - I wasn't there (thankfully)
do you have to add a new dir to CVS separately? (or is it automatic when you add a file in the dir)
I've always done it separately
gah. of course I forgot to save the latest version before copying it
it's not too different - just got rid of the step N stuff and changed the wording of the steps
it wasn't immediately obvious to me how to get that converted to pdf by make
normally I just add new chapters to one of the master docs
but I guess that isn't appropriate for a quick start gude
i kan spel gude
ah. it looks like adding the file to both the DOC_SRCS and PDF_TARGETS would do it
dang pid has a lot of parameters :-(
I think I'm too tired to figure it out tonight.
good night all
I think I'm going to have to call it a night too
I was hoping to finish the pid manpage, but I have to catch an early flight tomorrow
I thikn all the swimming and hiking this weekend tired me out
only a one day trip fortunately
SWPLinux: were you workign on getting it to build?
sorry, I misunderstood, I would have helped
if I understood makefiles, it would probably help :)
no problem. I didn't say much about it
(or ask for help)
hmm. could you correct the spelling of my name on the CVS server?
the first last name is "Wille" - no second 'i'
(happens all the time :) - I can tell when people re-key my name ;) )
huh, as long as I've known you, I assumed that was a middle name, and it was Willie
dual last names, just like my wife
(and I thought it a little strange that a grown man would be named Willie ;-)
did they call you willie pete in the service, or was that before you had two last names?
waaaay before :)
they called me "the brain" in basic training
it probably wasn't always complementary
dammit, man formatting is a pain
there's a package called something like "manedit", but it's nearly useless
.TP gives you a paragraph where the first line starts to the left (title line) and the rest is indented
or it was when I looked at it last
used for hal pins - the pin name, and its type and direction, are on the first line, the rest is the description
works fine when you have one name per description
but if you want to put "phase-A" and "phase-B" as a two line "title" with a single paragraph afterwards, it seems impossible
(at least without having a blank line between the two titles)
SWPLinux: I got it to build the pdf - want me to check it in?
can it easily be made to do all the .lyx files in the quickstart dir? (or is that what you did?)
you'll have to add some bits, but you'll be able to see what to do now that there's an example
welcome, and goodnight
ah. I was missing the quickstart dir in the new target
(plus I missed the clean target additions)
not sure I got it all right - I think it's not getting made into html
I'm not here, but it's only in the pdf targets, not the HTML targets
oh, yes it is, it's fine
ok, goodnight again :-)
heh - see you. I'll try and un-crapify it a bittomorrow
huh, here I don't get the applications/cnc menu
I thought I had that all wored out :(
I do have all the files... very strange
skunkwork: did you lose an "s"?
:) either way. Very nice work - and the code looks so short ;)
(on the preview)
for what it does. - god I am not making any sense.
not even after a gnome-panel restart?
works ok here
this is running gnome, right?
the help file for tkemc/xemc is not ok
I have 2 options to fix it #1 (install the help files to $(DESTDIR)$(docsdir) instead of $(DESTDIR)$(docsdir)/help )
or #2 change configure to set HELP dir to /usr/share/doc/emc2/help instead of /usr/share/doc/emc2
I'll do #1 unless someone has an objection
I don't know the problem in detail but that sounds OK to me
it's no big thing, but I feel more comfortable touching Makefile than configure atm
less breaking-prone :)