#emc | Logs for 2009-02-26

Back
[00:03:38] <toastydeath> lol
[01:58:55] <LawrenceG> damn I hate leaky capacitors...
[02:00:25] <LawrenceG> $0.50 parts destroys a $3000 radio
[02:01:44] <JymmmEMC> destorys?
[02:02:19] <LawrenceG> leaky cap ate a hole in the PA board
[02:02:33] <JymmmEMC> ouch
[02:03:14] <LawrenceG> the brown slime eats right through the soldermask and the copper
[02:03:41] <dareposte> sometimes u can repair that with a good iron and magnifying glass
[02:04:01] <LawrenceG> not sure if cleanup with alcohol will stop corrosion effects
[02:05:28] <dareposte> so there used to be a tarball of the cvs-head version... did those go away?
[02:05:31] <JymmmEMC> baking soda
[02:06:21] <JymmmEMC> make a paste of making soda and a lil water, use a acid brish or wtip and scrub awat the corrosion
[02:06:31] <LawrenceG> maybe, but I'm not sure if the slime is caustic or acidic
[02:06:34] <JymmmEMC> rinse clena with denatured alcohol
[02:06:59] <JymmmEMC> baking soda should clean both and act like a mild abrasive
[02:26:47] <UncleGemc> Anyone familiar with dacport IC's? Lets say this one for example. http://www.datasheetcatalog.org/datasheet/analogdevices/AD7248AQ.pdf
[03:21:05] <jmkasunich> * jmkasunich is making steel wool
[03:22:09] <jmkasunich> actually, making a steel "cup" that is 0.875" diameter, 1" deep, with 0.020 thick walls and bottom
[03:23:03] <UncleGemc> dang small walls
[03:23:07] <UncleGemc> what for?
[03:23:22] <jmkasunich> a magician
[03:23:29] <UncleGemc> neat :)
[03:23:37] <UncleGemc> hidden compartment or something?
[03:23:47] <jmkasunich> yeah, something like that
[03:24:04] <UncleGemc> I been running the index b60 all night
[03:24:16] <jmkasunich> one piece slips over another, and looks like there is only the one
[03:46:24] <dgarr> i'm running trunk and noticing that halscope is segfaulting frequently often when a button pushed or cursor moved, hard to reproduce.
[03:46:48] <dgarr> sometimes there are messages before it crashes: http://pastebin.ca/1347450
[03:47:42] <cradek> ewww
[03:47:53] <dgarr> when it faults, the halscope application cannot be restarted (unloadrt cant unload it) so I have to restart machine
[03:49:11] <cradek> there has been a bug lurking in halscope for a while, I think since roll mode was added. are you using roll?
[03:49:44] <cradek> (darn, I wish those assertions meant something to me)
[03:50:01] <dgarr> i sometimes use roll and often start with roll but the fault can occur when not in roll mode
[03:50:37] <dgarr> i updated libglib and libgtk today -- nohelp
[03:51:02] <cradek> ack, I need to go to a faster machine, brb
[03:54:25] <cradek> ahhh
[03:54:32] <dgarr> this evening i was testing with emc-machine in garage and running halscope with
[03:54:34] <dgarr> its X display directed to my laptop in the house. i can still get some
[03:54:34] <dgarr> assertion errors (they may be different): http://pastebin.ca/1347455
[03:54:34] <dgarr> but it doesn't crash (as much? not sure)
[03:55:00] <cradek> so you think it might crash more with a slow X display?
[03:55:17] <cradek> if you get a sig11 even remotely repeatably, you should run it in gdb, or get a core dump
[03:55:26] <dgarr> or xsyncing --
[03:55:41] <cradek> ... a backtrace is worth a lot
[03:55:46] <cradek> do you know how to do that?
[03:55:55] <cradek> pretty sure it's already built with debugging
[03:55:58] <dgarr> i did that once but there were no symbols in the lib,
[03:56:35] <cradek> oh, hm. the sig11 is inside some gtk library?
[03:57:16] <dgarr> yes libgtk i think (not sure i'm remembering right, it was a few days ago i ran with gdb)
[03:59:07] <dgarr> i installed a debug package: libgtk2.0-0.dbg but haven't understood how to use it
[04:05:18] <cradek> the stuff is /usr/share/doc/libgtk2.0-0-dbg is no help at all
[04:06:51] <dgarr> yeah -- that's what i thought too
[04:07:09] <dgarr> it seems the problem must be recent because i
[04:07:37] <dgarr> never had a problem with halscope before running trunk (i've been using 2.2.6 i think)
[04:09:29] <cradek> the gtk libs are in such sorry shape that valgrind is useless
[04:12:26] <UncleGemc> Do any of you use rfqwork.com?
[04:12:40] <cradek> nope
[04:14:15] <UncleGemc> I been quoting some jobs for my index-werke b60 but the jobs are few and far between mostly less than 200 pcs. I been looking for an alternative Request For Quote website, hoping someone in here would know of one.
[04:14:57] <UncleGemc> I have this machine retrofitted with a CNC, if any of you guys need some production parts done. http://www.youtube.com/watch?v=AdxQLEOqed4
[04:22:59] <dgarr> running halscope with gdb just now (remote X display):
[04:23:15] <dgarr> Program received signal SIGSEGV, Segmentation fault.
[04:23:15] <dgarr> [Switching to Thread 0xb744a6c0 (LWP 13265)]
[04:23:15] <dgarr> 0xb777fe66 in ?? () from /lib/tls/i686/cmov/libc.so.6
[04:23:45] <dgarr> roll mode was not involved in this instance
[04:24:28] <cradek> would you put the whole backtrace on pastebin please
[04:28:04] <dgarr> ok, another occurrence, no roll mode involved, with backtrace: http://pastebin.ca/1347483
[04:28:48] <cradek> yuck, that is a very screwy stack
[04:28:57] <dgarr> years ago i did a lot of debugging of threaded code (solaris) and sometimes the error reported is not that close to the real fault
[04:29:08] <cradek> yes very true
[04:29:23] <cradek> but half the time you get lucky and the backtrace shows exactly the bug
[04:29:29] <cradek> I wish it was more than half...
[04:36:19] <cradek> ==14771== More than 100000 total errors detected. I'm not reporting any more.
[04:36:52] <toastydeath> sassy
[04:37:36] <cradek> it's pretty clear to me that scope is attempting to draw unitialized/uncaptured data sometimes
[04:38:32] <dgarr> what is this error report from?
[04:38:40] <cradek> valgrind
[04:38:51] <dgarr> ah, thanks
[04:39:47] <JymmmEMC> 21kfps
[04:40:17] <dgarr> trying again with gdb, same setup as 12 minutes ago, can't make it fault so far
[04:40:48] <dgarr> but can stimulate similar assertion errors
[05:06:02] <dgarr> got this backtrace and more closing the app : http://pastebin.ca/1347503
[05:06:51] <cradek> jeez
[05:08:24] <dgarr> wondering if i am the only one seeing problems with halscope?
[05:08:44] <cradek> no, I've seen it crash a few times too.
[05:09:00] <cradek> I'm 100% confident it has something wrong
[05:09:03] <cradek> it's just very obscure
[05:09:09] <dgarr> ok, i was wondering if i had messed up something on my machine
[05:13:00] <JymmmEMC> cradek: it's the flux capacitor that is the issue
[05:13:41] <JymmmEMC> it's flixing instead of fluxing
[05:21:54] <cradek> ack, goodnight
[05:22:04] <dgarr> gnight
[05:22:08] <cradek> dgarr: I'm not finding it... maybe jmk or jepler will have some insight.
[05:22:30] <cradek> any way you can find to trigger it reliably would be very helpful.
[05:23:11] <cradek> (as I'm sure you already know)
[05:23:14] <dgarr> its hard to reproduce now.
[05:23:21] <dgarr> i know -- these are difficult problems
[05:23:29] <dgarr> thanks for looking at it
[05:23:38] <cradek> welcome - I'll keep trying.
[06:58:29] <q0r3> hey all. i have a crazy neighbour that yells at her tv. i have an exam tomorrow, and i really need to get to sleep, except that i can't because all i hear is her tv blaring and her screaming at it. is there any way i can interfere with her coaxial signal somehow? the wire runs down the side of the building, and i have access to the bit that services her directly.
[06:58:37] <q0r3> i started cutting through it, but then thought against it. i was thinking maybe there was a way to short it out? an aluminium pin, perhaps?
[07:03:56] <toastydeath> no, it doesn't work that way
[07:04:10] <toastydeath> they're transmitting RF on the copper
[07:04:26] <toastydeath> plus you know, messing with everyone else on your local catv ring
[07:04:41] <toastydeath> i suggest not messing with it
[07:13:16] <eric_unterhause1> best way to interfere with tv screaming is to call the cops
[07:13:31] <eric_unterhause1> always worked for my neighbors when we were having a party in college
[07:39:33] <toastyde1th> toastyde1th is now known as toastydeath
[08:44:13] <pjm_> good morning
[10:42:16] <pjm_> archivist btw not cnc but have u seen http://www.sdr-kits.net/VNWA/VNWA_Description.html - looks quite an interesting kit
[10:44:01] <archivist> I like all the warnings :)
[10:44:36] <pjm_> they are dealing with hams!
[10:46:03] <archivist> bunch of amateurs!
[10:46:24] <archivist> I would love to test against the real thing
[10:46:36] <archivist> shame about the windaz only
[10:47:19] <pjm_> well again, its for hams - the art of self improvement / learning / experimentation has been totally removed from the hobby
[10:48:28] <archivist> did you go for the cheap 8410 system on fleabay I pointed to you?
[10:54:46] <pjm_> archivist no i didnt, i found out that the guy locally who had one give it to the local ham radio club, so i can get access to it there
[10:54:52] <pjm_> plus no one else there knows how to use it
[10:56:24] <archivist> even cheaper I suppose
[11:21:55] <archivist> I wonder if one could use http://emcar.sourceforge.net/ and parts of it with that project
[11:22:49] <pjm_> ah yes i saw that before, an excellent project
[11:23:00] <pjm_> i did a similar one in turbo pascal a few years back
[11:23:30] <pjm_> btw archivist on your machine, do u have emc controlled spindle speed?
[11:23:39] <archivist> not yet
[11:23:48] <archivist> I need it
[11:24:27] <archivist> drive has 0-10 volt in so it wont be too hard
[11:26:04] <pjm_> yeah i'm currently using a variable freq pulse train output from the PC to drive my vfd
[11:26:15] <pjm_> but gonna try the pwm output instead
[11:26:20] <pjm_> see if its a little smoother
[11:27:01] <pjm_> i need to put a breaking resistor on the vfd too, but my last experiments resulted in a crater forming in the switcher module in the vfd
[11:27:35] <archivist> ew
[11:28:07] <archivist> I have a different drive that I could use with a braking R
[11:29:19] <pjm_> yeah as far as i understand, i take the DC bus voltage / motor current to give R
[11:29:28] <pjm_> then find a high wattage R of about the right value
[11:30:04] <pjm_> i did have a selection of those big green ceramic R's about 6" long and 1" dia, but buggered if I can find them
[11:30:50] <archivist> gah TV dropper resistors
[11:31:17] <pjm_> heh not seen those for a few years
[11:31:17] <archivist> * archivist was a TV engineer early 70's
[11:31:21] <pjm_> but its a good idea
[11:41:10] <archivist> I have a few power R's available
[11:42:38] <archivist> ignore prices http://www.part-number.co.uk/partsubindexE1RES.html and I may have raided and used since I listed
[12:49:49] <pjm_> archivist ok i will have a pick through that list, i need to calc the value first
[12:52:36] <archivist> pjm_, its how I get rid of surplus, about 2 sales a year :(
[12:53:03] <pjm_> excellent idea
[12:53:07] <pjm_> i should do the same
[12:53:18] <pjm_> i have far too much crape here
[12:53:26] <pjm_> just none of it useful ;-)
[12:53:29] <archivist> with impending redundancy I need to make it work
[12:53:34] <pjm_> ah yes
[12:53:49] <pjm_> a mate of mine found a bag of 200 opto switches at work in the weee bin
[12:53:59] <pjm_> so i should be getting those for encoder making etc
[12:54:29] <archivist> "none useful" is what I thought of 100+ video tape motors, but I sold the lot to Poland
[12:54:29] <pjm_> i did all the mechanics for a simple 8 ppr + index encoder just to have a play with closed loop spindle speed before I get a mesa card
[12:54:34] <pjm_> wow
[12:54:56] <archivist> and he didnt haggle at the price :))
[12:55:42] <archivist> some stuff like the resistors I use myself and dont regard as a sellable item
[12:56:45] <archivist> any way off outside for a bit of yard clearing here
[12:57:26] <pjm_> ok cul
[13:02:09] <pjm_> rob btw are u the guy that posted the question on spindle load monitoring to the list?
[14:02:58] <rob> hi PJM yes i am
[14:03:59] <rob> pjm_, ill be back around later
[14:04:04] <pjm_> ok
[14:54:09] <stustev> good morning
[14:55:51] <stustev> gdb is not showing all the variable with 'info locals' - it shows some of them - it gives no explanation why it does not show the others - any ideas?
[14:57:08] <cradek> are you compiling with -O0?
[14:57:14] <cradek> also, good morning
[14:59:19] <stustev> no - will try it - compiling with --enable-run-in-place --enable-simulator
[14:59:31] <stustev> bbiam
[14:59:36] <cradek> in the Makefile replace any -Os with -O0
[14:59:42] <cradek> (it's not a configure option)
[15:00:47] <stustev> I remember now - you said to do that before - thanks
[15:23:29] <stustev> cradek: that did it!!!! - many many thanks
[15:37:22] <dgarr> jepler: re the [DISPLAY]GEOMETRY: i verified that cvs checkout was unmodified, but same misbehavior
[15:37:22] <dgarr> on two machines: one RIP using simulator (not RTAI kernel), the other RIP (and RTAI).
[15:37:22] <dgarr> then, I did make clean; make and display with liveplot on or off seems ok on both machines.
[15:37:30] <dgarr> biab
[15:50:38] <cradek> dgarr: neither jepler nor I can reproduce a problem now. can you give a careful step-by-step for me to follow, please
[16:16:44] <dave_1> hmmmm .... pretty quiet!
[16:17:06] <dave_1> not that I have anything very exciting.
[16:17:37] <dave_1> However I do need to know what branch of the cvs to download to make certain I get the hm2 support
[16:24:37] <dgarr> cradek: understood. to clarify: after make clean && make i see no problem. didn't understand that make clean would be needed for this case
[16:24:46] <dgarr> sorry for the trouble
[16:33:47] <jepler> ugh, a bug went away with "make clean"? that makes me unhappy :(
[16:34:09] <cradek> dgarr: is your clock set right, and has it always been recently?
[16:34:27] <dgarr> clock is right on both machines
[16:34:58] <dgarr> it's always been right as far as i know
[16:37:20] <Kohlswa> hello everybody, donno if anyone remeber me (wasnt here that long). im however glad to be back and recovering from shouder surgery. I had promised to compleat the swedish translation and intend to do so.
[16:40:16] <cradek> neat, it's great to have translators. glad you're doing well.
[16:40:22] <Kohlswa> last time around i was about to try useing a single signal per rev spindle sensor and think someone told me i would need to recompile emc with some exsperimental code, yes ?
[16:40:51] <cradek> yes that's not in a released version yet. it will be in 2.3.0 which is due soon.
[16:43:07] <Kohlswa> allright, the code was hosted somewhere temporearly before i think ? where can i get it now.
[16:43:59] <cradek> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Installing_EMC2
[16:45:04] <jepler> "encoder23" is the version of the enhanced encoder component that can be compiled to work with emc2.2 using "comp". http://media.unpythonic.net/emergent-files/sandbox/encoder23.c Instructions on compiling a component: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?ContributedComponents#How_to_compile_and_install_a_component
[16:45:42] <jepler> or you can follow cradek's instructions and upgrade to the CVS version of emc, which is getting close to "beta release" status
[16:46:45] <Kohlswa> thanks for the info
[16:46:58] <jepler> I think that the last time, encoder23.c is the route you were trying. Here's the old IRC log, maybe it helps jog your memory too: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emc/2008-10-19.txt
[16:47:19] <Kohlswa> thanks
[16:47:25] <jepler> starting at around 14:37 it looks like
[16:56:48] <stustev> now I am recovered to where I was two weeks ago. we just received a package of work to quote - 1000 part numbers - darn work - I will be BUSY the next two weeks
[16:57:17] <cradek> busy is good
[16:57:26] <archivist> sure is
[16:57:45] <stustev> busy is very very good BUT this means no EMC stuff - ugh!
[16:58:15] <stustev> I would rather have it this was as no work also means no EMC stuff
[16:59:30] <stustev> we are preparing a room for the intense quoting - it is good to see people scrambling around with something to do
[16:59:38] <stustev> now we have to WIN some of this work
[17:19:18] <Kohlswa> when is 2.3.0 estimated to be released ?
[17:21:57] <cradek> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Emc2.3Status
[17:22:01] <BJT-Work> cradek: I've been using your roll the dowel method to set my Z on my mill and like it better than the paper trick.
[17:22:53] <Kohlswa> thanks cradek
[17:23:04] <BJT-Work> however my Anilam control is not as good as EMC and I have to do the math in my head for the dowel thickness
[17:23:17] <BJT-Work> after touching off
[17:23:37] <eric_unterhause1> what's the roll the dowel method?
[17:24:11] <cradek> stuart showed me that trick. it's better to move up than down - you can't break a point off the tool.
[17:25:07] <BJT-Work> I put a 0.500" dowel on the work and lower the tool to just below and push the dowel up to the tool then raise it 0.001 steps until the dowel just rolls under the tool
[17:25:28] <eric_unterhause1> cool, thanks
[17:25:59] <BJT-Work> as you get close to the 0.500 the dowel really moves
[17:26:32] <cradek> yeah that's why I like to use a big size. it's really easy to feel
[17:27:41] <cradek> bbl
[18:17:50] <alex_joni> away
[18:18:01] <alex_joni> meh.. crappy keyboard
[18:26:30] <stustev> I have a keyboard like that also. It types the keys I hit instead of the ones I want to hit. :)
[18:28:46] <alex_joni> stustev: indeed that was the case ;)
[18:29:04] <alex_joni> how can it not know I want to type /away
[18:30:12] <alex_joni> (especially since I type that daily)
[18:32:05] <stustev> maybe we need some 'hot' shorthand keys - that won't help - the shorthand will just be wrong :)
[18:33:13] <stustev> I don't want a keyboard to type what I think - that would be very dangerous :)
[18:33:14] <alex_joni> I saw some nice CNC machine today
[18:33:22] <alex_joni> some Mori Seiki iirc
[18:39:51] <BJT-Work> heh
[19:00:08] <alex_joni> http://sos.noaa.gov/equipment/
[19:10:42] <Kohlswa> cradek/jepler, i must be doing something wrong, ive added the encoder23 and ive added the bits and peaces i found at http://www.mailinglistarchive.com/emc-users@lists.sourceforge.net/msg01003.html im however reading very low values from the hal meter when probeing spindle-speed
[19:21:14] <alex_joni> Kohlswa: is the read/update function connected to the base thread?
[19:21:33] <Kohlswa> addf encoder.update-counters base-thread
[19:21:33] <Kohlswa> addf encoder.capture-position servo-thread
[19:22:54] <alex_joni> what is your base-thread period?
[19:23:38] <Kohlswa7578> ugh, sorry, got disconnected,
[19:23:38] <Kohlswa7578> [20:21] alex_joni: Kohlswa: is the read/update function connected to the base thread?
[19:23:47] <Kohlswa7578> [20:21] Kohlswa: addf encoder.update-counters base-thread
[19:23:47] <Kohlswa7578> [20:21] Kohlswa: addf encoder.capture-position servo-thread
[19:23:53] <alex_joni> saw that
[19:23:55] <alex_joni> what is your base-thread period?
[19:25:34] <Kohlswa7578> umm
[19:27:06] <Kohlswa7578> Realtime Threads:
[19:27:06] <Kohlswa7578> Period FP Name (time, Max-Time)
[19:27:06] <Kohlswa7578> 99733 NO base-thread ( 5433, 30687)
[19:27:30] <alex_joni> how about in the ini?
[19:28:28] <Kohlswa7578> BASE_PERIOD = 100000
[19:28:42] <alex_joni> that's awfully slow
[19:29:02] <alex_joni> 100.000 usec = 100 msec = 0.1 sec
[19:29:16] <alex_joni> that means that your BASE thread updates 10 times / second
[19:29:24] <Kohlswa7578> oh ? ive just used the setup wizard to create the configureation.
[19:29:32] <alex_joni> so you can count encoders up to 5Hz speed
[19:30:20] <jepler> alex_joni: Kohlswa7578 is trying to use 1PPR threading, so the signal frequency is probably not the problem
[19:31:19] <jepler> Kohlswa7578: the "position-estimated" output of encoder is in revolutions and "velocity" is in revolutions per second (not RPM); is it possible that everything is OK, but you were expecting to see RPM?
[19:31:36] <alex_joni> 5Hz means max 300 RPM..
[19:32:06] <Kohlswa7578> well under spindle-speed useing the hal meter shouldent that be rpm ?
[19:32:20] <alex_joni> what is spindle-speed?
[19:32:21] <jepler> and BASE_PERIOD = 100000 means 100us -- are you sure you had your coffee today, alex_joni ?
[19:32:30] <alex_joni> jepler: I had a long time ago :)
[19:32:38] <alex_joni> sorry :/
[19:33:22] <Kohlswa7578> max speed my small spindle should be about 2800rpm.
[19:34:23] <Kohlswa7578> this is what i added to my hal file.
[19:34:23] <Kohlswa7578> loadrt encoder23
[19:34:23] <Kohlswa7578> setp encoder.0.counter-mode true
[19:34:38] <Kohlswa7578> setp encoder.0.position-scale 1.0
[19:34:38] <Kohlswa7578> addf encoder.update-counters base-thread
[19:34:56] <Kohlswa7578> addf encoder.capture-position servo-thread
[19:34:56] <Kohlswa7578> net spindle.phase-A parport.0.pin-15-in => encoder.0.phase-A encoder.0.phase-Z
[19:35:18] <Kohlswa7578> net spindle-index-enable motion.spindle-index-enable <=> encoder.0.index-enable
[19:35:18] <Kohlswa7578> net spindle-speed encoder.0.velocity => motion.spindle-speed-in
[19:35:28] <Kohlswa7578> net spindle-pos encoder.0.position-interpolated => motion.spindle-revs
[19:36:58] <alex_joni> spindle-speed is in RPS then
[19:37:34] <Kohlswa7578> ah, that adds up
[19:40:32] <Kohlswa7578> Kohlswa7578 is now known as Kohlswa
[19:41:38] <Kohlswa> thanks.
[20:12:35] <Kohlswa7578> well im off to bed, thanks again for all the help
[20:14:15] <SWPadnos_> SWPadnos_ is now known as SWPadnos
[21:38:24] <Jon_geo01005> I made a new entry on the wiki for adding SPI support on to hostmot2. It is under "Misc stuff" in the table of contents.