that doesn't count the DC bus supply for the spindle, probalby at least a 6" cube
or the DB resistors and such, another 6" cube
it is never big enough
I'm trying to figure out if it will be cool enough
did you decide on a motor mount? you didn't want it to stick out too far (x)
the spindle drive has a 9x12" (approx) heatsink that I was hoping to install with the fins outside and the sparky bits on the inside
gonna put the motor in the standard location
once I have the electrical box there, it isn't so bad - the chip guard can be installed from the top of the box
upon closer inspection of the spindle drive, it would be very hard if not impossible to have the fins stick out while keeping a seal
the electronics go too close to the edge of the heatsink, no place to seal it
your having too much fun. I am jelous
I don't think its fun right now
too many details
[00:28:57] <skunkworks> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?RtaiSteps
_that_ is too many details
is that where alex would have put the file if he had gotten to it?
are you doing that?
which file, the SMI thing?
the other box has been doing memtest for 2-1/2 hours with no probs, lemme reboot it and get the file from there
on the way
and so am I (to meet my wife for dinner)
Just this once .. here's the log: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2006-12-23.txt
So I sudo insmod rtai_smi.ko and ran the latency test all night. No overruns. ovl max was 26994.
I had to disable the screen saver - the second the screen would start to fade out - the overuns would increase by hundreds
now insmod was from my desktop. I don;t know where to put it. when I search for it I find it in /usr/realtime-2.6... but from what I read yesterday - it should be in the /lib/module
I did copy over the module in lib/modules - but after a reboot I was still getting latency errors. That is when I did the insmod - then no overruns. (no reboot yet)
seems to hover around 12000
most of the time
pretty cool - great work.
I think I was wrong about /lib/modules
I would put it in the realtime script
can you upload the binary rtai_smi.ko ?
[14:20:43] <alex_joni> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?action=upload
oh - cool - nice work
I did copy it into the /usr/realtime-2.6.15-magma/modules/rtai_smi.ko
but I thought after a reboot I still had overruns. It wasn't until I did a insmod did It stop.
(have not rebooted yet)
since the insmod
I am actually surfing and everything with now overruns
going to reboot and see
Ok the reboot I get overruns. until I do a insmod from the desktop
So I am guessing I have not coppied it correctily
it's not a matter of copying
you need to install it too
there are loads of modules available, but you only install the ones you need (think network drivers))
ok - makes sense
the fact that the rtai_smi.ko module exists doesn't mean it gets used.. you need to tell it that it should get loaded
there are various ways to do that
1. put it in some custom script, so that it gets insmoded at load time (e.g. make a small script in /etc/init.d/ and insmod it from there)
2. add it to /etc/init.d/realtime and have it loaded along with the other scripts
sorry - was away.
if you're going to load it with emc_module_helper, then you'll have to add it to the module whitelist
yeah, so #2 is nicer, but requires recompile
way over my head. I see the realtime file is scritp
skunkworks: do you run in place?
I just got head last night - and that is normmaly what I play with.
run in place
ok, that might be easy to change.. I'll add rtai_smi to the whitelist
skunkworks: for now add it manually :)
no problem - I can handle that :)
no overuns this mornings
you might want to check plugging in an USB stick
the two might be related
SMI is the one that handles some USB in some cases I think
looks like it isn't an issue on this machine.
I should be able to play with the pluto on this portable
cradek: mind if I add rtai_smi to the module_helper whitelist?
actually I think it should hold all rtai modules
sure, add that one, but I don't think it should hold anything not used with emc
[22:47:56] <alex_joni> http://rtai.dk/cgi-bin/gratiswiki.pl?Latency_Killer
this looks interesting enough
that looks like a nice page
yeah, I linked it from our Troubleshooting page
[22:54:52] <alex_joni> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TroubleShooting
cradek: the rtai_smi module fails if it doesn't find a chipset it knows
so we can't just blindly add it by default
../bin/emc_module_helper insert /usr/realtime-2.6.15-magma/modules/rtai_smi.ko
but we could compile and distribute it.
insmod: error inserting '/usr/realtime-2.6.15-magma/modules/rtai_smi.ko': -1 No such device
it is already compiled and distributed
but the RTAI people did something strange
[22:58:02] <alex_joni> http://cvs.gna.org/cvsweb/magma/base/arch/i386/calibration/smi-module.c?rev=1.7;content-type=text%2Fplain;cvsroot=rtai
that's the version that's beeing compiled and distributed
oh I see it's all disabled
which doesn't disable anything
it worked for JMK to turn on the ALL
we (you!) could easily do a new package.
same for skunkworks
_but_ I've seen at least 1-2 cases where it didn't work
yet it worked with turning all others on
some guys complaining on the rtai lists
rtai sure makes it hard to distribute anything but the source.
which makes me somehow weiry about distributing this
also.. there's a rather large FIXME comment at the end of the file
BIG FAT WARNING:
"this won't work in most cases, so why worry .."
at least that's how I read their attitude :)
I think the proper fix would be to have the CONFIG_* as an insmod param to the module
which might also break some things ..
although I don't expect many people to use the ubuntu packages for rtai for anything else then emc