jepler: you around?
mozmck: I am now
mozmck: I think you can ignore that warning
ok. I didn't know if a different directory name would be better
the source package will be created with the directory name it said, linux-2.6.32
the standard debian/ubuntu way is for the source package name and the source directory name to be the same
if I look in the .tar.gz the root directory is ubuntu-lucid
ah, it's the extraction process that gives it the right name
I never knew that
so yeah I guess it would be a tiny bit better if you renamed the source directory to linux-2.6.32
another question: how in the world is the 99-rtai.rules file created in the rtai package??? I used the debian directory from the rtai y'all did with hardy, and I can't find any reference in the 4 files to 99-rtai.rules, but it creates it anyhow!
Ok, I'll look at changing the dir name. Will it mess up git or does it care?
git shouldn't notice
oh, I forgot something. you probably actually want to build the source package with dpkg-buildpackage -S -i
otherwise it includes the .git dir which is generally not what is desired
actually, check the tar to make sure that's right..
anyway, the 99-rtai.rules file is created by 'make' I think
GNUmakefile.am: grep -q RTAI:`basename $$b .udev` $(DESTDIR)/etc/udev/rules.d/99-rtai.rules || \
GNUmakefile.am: $$sudo sh -c "( echo ; cat $$f ) >> $(DESTDIR)/etc/udev/rules.d/99-rtai.rules" ; \
The reason I ask about the 99-rtai.rules file, is that I get this error " trying to overwrite '/etc/udev/rules.d/99-rtai.rules'" etc if I try to install two versions of rtai-modules (for 2 different kernels)
so it's part of rtai?
yeah, I think you'll have to remove the old kernel before installing the new one
er, old rtai-modules
those lines I pasted were from the rtai makefiles
well, since rtai is installed in separate directories named after the kernel version, I would think you should be able to have multiple copies
there's no place you can put a udev rule besides /etc/udev/rules.d
we've always had one realtime kernel per distro so it's never been a problem, and I don't think it will be on most users' machines
ok. I'll just force it or remove the old. just a minor nuisance.
an actual problem for a few people, like those building the kernels
Yeah, if I could tell dpkg not to error out on that file, like only install it if it's not there, that would be great
here's the line I used to build source like you posted earlier: dpkg-buildpackage -S -us -I.git -I.gitignore
I think that covers it too
when using update-dch-from-git, how do I tell it to use my actual name and email instead of my login name.
mozmck: hmmm let me check
mozmck: set the environment variables DEBEMAIL and DEBFULLNAME to the values you want
I guess I should do that in .bash_profile?
I think that'll make it stick in all terminals
export DEBEMAIL="..."; export DEBFULLNAME="..."
thanks. I wasn't even sure where to look to find that info.
update-dch-from-git uses the program dch and it's documented in the dch manpage
I see. Thanks.
EMC: 03cmorley 07v2.4_branch * rae79deea7e24 10/src/emc/usr_intf/pncconf/pncconf.py: create a desktop entry in the right Desktop directory
anyone have suggestions what is best way to multiplex position commands from axis?
jepler, cradek, etc, I put a complete new set of packages up at http://www.linuxcnc.org/mozmck/newest
The only change to the kernel is the version number from 2.6.32-22 to 2.6.32-122, and then a recompile and rebuild of packages.
I had to rebuild rtai and emc for that kernel as well, and there are source packages for everything there as well.
do you want me to try them on that dual p3?
I built a livecd with these packages and did some preliminary testing and it all seems to work.
I guess so! did the previous ones work?
cool. if you can upload it, I can try it on several machines
yes the previous ones are fine - that's what it's currently running (this is max, the little mill)
It will take about 4 or 5 hours for me to upload, so I'll probably have to do that tonight.
did you get the cd install to point you at the linuxcnc apt repository automatically?
Someone here mentioned removing openoffice and putting the devel packages on the livecd, so since I had already removed openoffice I put on all the dev packages and had a little room to spare.
As a result, I was able to compile and use a couple of .comp components directly from the livecd
you mean all the build deps fit?
(or just enough to run comp?)
yup. and the gnumeric spreadsheet
g++, gcc, build-essentials, etc. I think everything needed to build emc
I'm shocked it all fits in place of open office (with lyx etc)
no lyx :)
That's only needed to build the docs.
oh ok, not full build-dep for the package rebuild then
not for package rebuild, but it should be fine for emc2 rebuild
I can't wait to try it.
that is excellent news
but at least people can build components without having to install a bunch of extra stuff.
I'll work on putting those packages in the right form for an apt repository
I didn't get the linuxcnc repo in apt-sources on the livecd yet. I forgot last night, but that is minor.
it stinks that minor things cost you another 4 hour upload :-/
working with cd images is no fun
cradek: I did get your truetype tracer on there, and the firmware packages from hardy
cool! did you use the one from http://timeguy.com/cradek/01276453959
that's one reason I didn't upload the cd image yet. I can make a few changes in 5 minutes.
hm, since I don't have those in an apt repository, I wonder how to point people to the corresponding source
heh, ask on irc?
(other than just letting google do it...?)
why not put it in the lucid repo?
good idea, I will
I can test it on a bunch of computers also. (when the image is uploaded)
cradek: I'll put it in the lucid package repository on linuxcnc if that's OK with you
truetype-tracer, that is
yes please do
then people will automatically have access to the source in the most natural way
mozmck_work1: oh, have you put the emc2 board signing key on the cd as a key trusted by apt-get?
uh, I don't remember.
Where do I check that again?
I'll make a list of these things and do them before I upload.
sudo apt-key list
pub 1024D/8F374FEF 2008-04-15
uid EMC Archive Signing Key <email@example.com>
sub 2048g/17BAA37C 2008-04-15
One thing I did do is a full-upgrade so all the packages on the CD are the latest from ubuntu as of last night.
I'll probably have the package repository working within 20 minutes
it is important that this works right after installation from the live cd
mozmck_work1: will you please test that before uploading?
ok, I may not have time tonight, but I can tomorrow anyhow.
The emc2 packages on there right now are from last nights git. I think you mentioned that we may want another point release before the final CD?
yes, the problem being I won't have time before this weekend
I don't mind uploading more than once either. I'll upload what I have for testing tonight or tomorrow.
ok, that works for me too
no problem. That will give a little more time to test the pre-release cd.
where can we get together to celebrate? looks like Tulsa is about midway. I've never been there.
:) It's only about 4 hours from me.
hm, it's 7 from here. wichita?
with stuart's long list of machines needing retrofits, we should go to wichita anyway and kick him in the pants to get started
this one especially: http://mpm1.com/enshu.html
hey - that looks like yours
yeah it's similar. very slightly bigger I think.
carousel is much bigger - it's a long chain
so - now that you have done 1 jr.. this one should take about 3 days. ;)
he says this is one of the machines they used constantly, and it is dead
haha, yeah right
do they know what the issue is?
his jr's currently dead too
all the I/O is flaky - it is fiber optic (??)
fanuc doesn't have any clue and wants to randomly try replacing boards at great expense
the enshu's I/O is fiber optic?
yes that's what he said
he said it is 3 boards - one is $10k - then he stopped looking
good retrofit candidate. nice console for touchy. nice random toolchanger.
all of the k&t i/o is optical.. ;) (opto22's)
heh, that's slightly different from fiber optic...
cradek: have you played with the amc drives yet?
I would be interested in how the encoder feedback works for velocity control. (initally we are going to use the tachs - but it would be cool to know the encoder feedback works well also)
(our big amps will do both)
skunkworks: yes - I tuned one to a little 10A servo motor I have - it works great
encoder velocity feedback seems to work great
did you tune the velocity loop first? with a battery or such and scope?
when giving a step change in velocity command I get a velocity overshoot of maybe 15% but then it settles perfectly. no oscillation
I could not get rid of that - it is surely integrator windup - if I ramp the velocity so it can always keep up, I bet it doesn't do it
OK, I think the lucid package repository is live now
skunkworks: yes just scope on velocity monitor output and ear
it seems to think it's able to install emc2-dev on this lucid system that's never had emc2 installed yet: http://pastebin.ca/1910158
it took a while. lots of fiddly switches and knobs and not very good instructions.
cradek: yeah, that's legit. It's required by python-numpy
emc2 (image2gcode) -> python-numpy -> libblas3gf -> libgfortran3
neat! is the repo address the same as you gave me yesterday?
mozmck_work1: the repo address is shown here:
[14:58:45] <jepler> http://pastebin.ca/1910159
I think it's the same as I had told you
it matches my memory
haven't tested it, but I also put this up: http://www.linuxcnc.org/lucid/emc2-install.sh
and I noticed the hardy install.sh was still pointing at 2.3 and changed it to 2.4.
is anyone interested in developing a universal machine configuration gui?
I'm interested in coding up a dxf to g-code generator for lathes and or plasmas :)
why not python? I think a ton of work is already done here... http://sourceforge.net/projects/vec2ngc/
dunno why, I kinda thought c++ would be faster somehow I guess
it is :)
not to write though...
I didn't know micges had done that
moopy: I've been rolling around ideas in my head for a universal machine configuration gui, but haven't had time to do much with it.
I did write some of the g-code generators on the wiki in python
I'll take a look at his work this evening thanks for the link skunkworks