#emc-devel | Logs for 2009-11-13

[00:27:31] <CIA-40> EMC: 03cradek 07master * r9594e83f6022 10/src/emc/usr_intf/touchy/touchy.py: more of the same
[00:32:02] <dgarr> so i need to support woffset s everywhere? what about u,v?
[00:32:26] <cradek> no, those don't exist yet
[00:32:41] <cradek> if GET_EXTERNAL_TLO_IS_ALONG_W() then the Z offset gets applied to the W axis
[00:32:50] <cradek> (what a swirl, jeez)
[00:33:24] <dgarr> before i work on that, please let me know if you have comments on the functionality so far
[00:34:08] <cradek> I have not run the latest one, but if it fixes those odd interactions I'm all for it
[00:34:30] <cradek> like you I'm becoming dismayed at how complicated it looks, but we have worse things
[00:34:52] <dgarr> its like playing bring me a different rock
[00:35:28] <cradek> I don't know that game - I hope you're not frustrated that I keep finding stuff wrong and then it all gets more complex
[00:36:00] <cradek> also, I'm a little surprised that nobody else has commented. do they think we're crazy, or do they just not care?
[00:36:10] <dgarr> no i'm ok with it but since i've never used tlo along z , i have to study it
[00:36:44] <cradek> tlo along w is a hack for 5 axis machines where the tool "length" moves around with the rotary axes
[00:37:01] <cradek> (well the idea isn't a hack - the implementation is)
[00:37:19] <cradek> I was too bashful at the time to just add TLO for all axes
[00:37:31] <cradek> (because it would screw up tool tables etc)
[00:38:12] <cradek> bbl
[00:38:15] <dgarr> in the patch, i also made some assumptions about when it was ok to accept #54xx writes to frontangle,backangle etc depending upon the orientation (mill==0, lathe!=0)
[00:38:36] <dgarr> so your comments on that are welcome
[02:43:50] <jepler> cradek: do you want me to commit the focus-line-width change? I verified it works on hardy too (first test was dapper)
[02:44:35] <jepler> http://pastebin.ca/1669256
[03:04:06] <dgarr> cradek: amended to support TLO_ALONG_W (i think): http://www.panix.com/~dgarrett/stuff/0001-Numbered-parameters-for-current-tool-items.patch
[03:07:58] <dgarr> jepler: thanks for applying recent patch on tooledit, this new one eliminates spurious warnings for mtime changes when the file contents are not changed: http://www.panix.com/~dgarrett/stuff/0001-preclude-warnings-when-file-mtime-changes-but-file-m.patch
[03:22:42] <jepler> dgarr: thanks, applied
[03:22:46] <jepler> .. and the focus thing too
[03:22:49] <CIA-40> EMC: 03jepler 07master * ra0fe985ecdbf 10/src/emc/usr_intf/touchy/touchy.py: focus line makes no sense without a keyboard
[03:22:54] <CIA-40> EMC: 03jepler 07master * r1ae3f96d336a 10/src/emc/usr_intf/tooledit.tcl: preclude warnings when file mtime changes but file md5sum is unchanged
[04:33:57] <cradek> jepler: thanks
[04:38:01] <cradek> jepler: cool, that is much better without the extra line
[06:18:03] <CIA-40> EMC: 03seb 07master * r84e73cbd5344 10/src/hal/drivers/mesa-hostmot2/encoder.c: Fix a bug in hm2 encoder velocity estimation
[06:19:14] <garage_seb> cradek, i'd like to know if that ^^^ fixes the hm2 encoder vel problem you saw yesterday
[06:48:52] <Jymmm> cradek: I have a Touch UI for ya.... http://link.brightcove.com/services/player/bcpid713271701?bclid=713073346&bctid=709364416
[11:46:52] <micges_work> hello
[12:05:44] <piasdom_> g'mornin all
[12:06:27] <piasdom_> just dropped in to see if there is anything i can do to help with emc2
[12:23:02] <jthornton_> morning
[14:12:54] <Dave911> Jymmm: Wasn't that the same screen they used in the Tom Cruise movie Minority Report ?? ;-)
[14:12:56] <Dave911> How long till Walmart has them?? ;-) After playing with that for a while I might forget that I really meant to actually run a machine that day...
[14:16:39] <Dave911> Guys, what is the most up to date source of documentation for EMC2 in general? The manuals are good in PDF and HTTP but is one updated first? Should the info be identical? Or should the Man pages in EMC be the first place to reference. Where would you go first?
[14:16:41] <Dave911> Normally I don't need to ask questions like this because documentation is typically bad and there is only one one source and it it lousy. So this is a good problem to have.... :-) Thanks for all of the hard work keeping the docs up! :-)
[14:28:39] <mozmck> Dave911: the source code itself is the _most_ up to date documentation... :)
[14:28:58] <SWPadnos> Dave911, the PDF and HTML docs should be the same, they're automatically generated from the same source code any time there's a change
[14:42:19] <SWPadnos> wow. in a burst of technological insight, some Microsoft programmer managed to forget to put a "square root" button on the Scientific view of the calculator
[14:42:33] <SWPadnos> luckily, it's there on the "basic" view
[14:42:52] <SWPadnos> unluckily, changing views also clears the "display"
[14:44:47] <Jymmm> SWPadnos: http://download.microsoft.com/download/whistler/Install/2/WXP/EN-US/PowerCalcPowertoySetup.exe
[14:45:10] <Jymmm> Power Calculator
[14:45:10] <Jymmm> With this PowerToy you can graph and evaluate functions as well as perform many different types of conversions.
[14:45:24] <SWPadnos> oh, all I wanted was a square root :)
[14:45:33] <SWPadnos> I wonder if that powertoy works on Win2K
[14:45:47] <Jymmm> I know, that'll give you a graphing calc too. It might.
[14:45:59] <SWPadnos> I gotta say - Karmic is working very very well on the couple of machines I installed it on
[14:46:05] <SWPadnos> (on the subject of OSes)
[14:46:35] <Jymmm> Yeah, I know what you mean.... MS-DOS 6.21 has been rock solid.
[14:47:06] <SWPadnos> yeah, but the memory management and multitasking weren't so good
[14:47:30] <Jymmm> You'll never need more than 640KB
[14:47:45] <Jymmm> Oh and DesqView FTW!
[14:48:13] <SWPadnos> and SideKick
[14:49:15] <Jymmm> For what it was, sure.
[14:52:50] <Jymmm> SWPadnos: did it work?
[14:52:57] <SWPadnos> what?
[14:53:06] <Jymmm> Calc toy on w2k
[14:53:08] <piasdom_> well, i appreciate all ya'll hard work.keep up the great job!
[14:53:18] <SWPadnos> oh, I don't know. I didn't download or install it
[14:53:27] <cradek> piasdom_: what parts interest you? what are your skills? that's a very open question, but with more details we can help find a part for you to work on.
[14:53:30] <cradek> dangit
[14:53:33] <SWPadnos> I actualy have a graphing calculator sitting on my (physical) desktop
[14:54:00] <SWPadnos> oh bummer - I missed his question
[14:57:37] <cradek> I recall seeing piasdom around before, but I don't know if we could figure out an email address or something. it's a shame if someone wants to help and is ignored.
[14:59:39] <SWPadnos> yeah, he's certainly been around a bit
[15:09:18] <JT-Work> he will be back :)
[15:12:30] <JT-Work> and there he is
[15:13:01] <JT-Work> piasdom_: cradek was typing to you but you had left
[15:13:04] <piasdom_> hi :)
[15:13:12] <piasdom_> he told me
[15:13:18] <JT-Work> ok
[15:13:42] <piasdom_> i was just wondering if i could help because ya'll help ME so much
[15:13:59] <cradek> here is what I typed earlier: piasdom_: what parts interest you? what are your skills? that's a very open question, but with more details we can help find a part for you to work on.
[15:14:21] <piasdom_> well...
[15:15:01] <piasdom_> i'm learning to write code, can do math calulation programs...
[15:15:17] <piasdom_> can write gcode
[15:15:28] <piasdom_> don't really know what ya'll do :)
[15:16:15] <piasdom_> today i'm going to finiosh a pcb for skunkwork and mark
[15:16:34] <piasdom_> *finishing
[15:17:23] <piasdom_> been a machinist for 19 years
[15:18:07] <piasdom_> i like to learn more code writing or test software or hardware
[15:19:40] <cradek> I think it's my nature to only see that a part of emc needs improvement when I specifically use it and also I am able to improve it. so I may not see things that people with other skills could do.
[15:20:22] <piasdom_> the question was meant to be open because i didn't know what to ask to do as i don't know exactly what ya'll do :)
[15:20:26] <cradek> for instance we get a lot of questions on irc and the mailing list that are general machining questions. an experienced cnc (or manual!) machinist can answer these well
[15:20:54] <piasdom_> i can do that
[15:21:35] <SWPadnos> if it interests you, you could do something like a standalone feed/speed calculator
[15:21:49] <cradek> it's possible that those kinds of questions might belong on the web bbs in a "machining" section because they aren't specifically about emc - not sure
[15:22:03] <SWPadnos> that would let you learn some programming without having to understand the (large and sometimes confusing) EMC2 code
[15:22:09] <piasdom_> been a manual machinist for 19 years...cnc for about two years
[15:22:50] <SWPadnos> then, as a way of getting your feet wet with some of the EMC2 code, you could add a menu item to AXIS (and maybe some of hte other user interfaces) to run that program
[15:22:52] <piasdom_> i have a feed/speed calu
[15:23:07] <SWPadnos> well, if it doesn't interest you, then keep looking :)
[15:23:30] <piasdom_> that DOES interest me :)
[15:23:37] <piasdom_> ALL this does :) :)
[15:23:49] <SWPadnos> I was just thinking about a way of getting your machining expertise into a form that might be helpful to others
[15:23:57] <piasdom_> ok
[15:24:09] <SWPadnos> writing documentation, both for inclusion into the PDF docs and on the wiki, is also always appreciated
[15:24:21] <SWPadnos> (thank JT-Work)
[15:24:26] <SWPadnos> err, thanks
[15:24:54] <piasdom_> i'll work on adding menu item
[15:25:25] <piasdom_> writing is not one of my strong suit
[15:25:32] <SWPadnos> remember - you don't have to write something spectacular to be helpful - there are lots of details that are small but useful too
[15:25:59] <piasdom_> ok....ya'll can always edit it to sound sane
[15:26:06] <SWPadnos> heh
[15:26:18] <cradek> I see we do have "machining" forums on the web bbs
[15:26:31] <cradek> they are inactive
[15:27:02] <piasdom_> cradek: i can do that after work at home
[15:27:23] <cradek> wonder if you could drum up some interest there by posting about some projects you have done, and talking about the machining (speeds/feeds, fixturing, order of operations, etc) parts more than the CNC parts of the job
[15:27:53] <piasdom_> cradek: where is that site?
[15:28:09] <cradek> a lot of people come into it the opposite of you - they start with a cnc and don't know the first thing about machining - many need that kind of help.
[15:28:56] <cradek> linuxcnc.org, community, EMC support forum
[15:29:03] <piasdom_> k
[15:43:19] <Dave911> Thanks for the info on what is the most current docs (pdf vs http etc) guys, I knew the source code would be the most up to date info but looking up source code to find a pin description seems like a bit of overkill... ;-)
[15:43:33] <gtom_> interp_read -> read_one_item -> Bad Character using locale <> en_US ??? is there a way to change this???
[15:43:58] <cradek> gtom_: more details please
[15:44:18] <gtom_> as you know im working on a pascal gui
[15:44:41] <gtom_> everything works fine except the interpreter
[15:44:45] <jepler> Dave911: http://linuxcnc.org/docview/2.3 (stable version) http://linuxcnc.org/docview/devel (development 'master' version) are kept up to date with the latest changes
[15:45:32] <cradek> seb_kuzminsky: saw your commit, neat, I'll try it tonight or tomorrow.
[15:45:52] <gtom_> if i compile my program using locale the interpreter returns an error "bad character "." used
[15:46:16] <gtom_> this happens cause emc uses _gnu_source
[15:46:31] <gtom_> and pascal uses the locale...
[15:47:07] <gtom_> so the ordinal compare if (char < ' ') || (char > 'a') fails...
[15:47:20] <gtom_> in interp_read : read one item
[15:47:52] <gtom_> compiling without the locale the stuff works...
[15:47:59] <seb_kuzminsky> thanks cradek
[15:48:03] <jepler> Don't use setlocale(LC_ALL) or setlocale(LC_NUMERIC). These can change how floating-point numbers are written
[15:48:53] <jepler> rs274ngc defines floating point numbers with "." as the decimal point regardless of what the user's language dictates
[15:49:05] <gtom_> they also change the behaivour HOW a file is read???
[15:49:47] <jepler> It changes how strtod() called from read_real_number works
[15:50:55] <gtom_> but the error is raised in the CHKF(char < ' ' || char < 'z')
[15:55:14] <cradek> I see that same error can come from either of two tests. are you sure?
[15:57:07] <jepler> whatever the exact analysis is, it's due to setlocale(LC_ALL) or setlocale(LC_NUMERIC) and a locale that doesn't use "." for the decimal point character.
[15:57:30] <cradek> fair enough.
[15:57:33] <gtom_> so i should take the locale out of my project?
[15:58:08] <jepler> you can see this without your pascal program by making this change in sai: http://pastebin.ca/1670052
[15:58:33] <jepler> then running it with LANG=de_DE.UTF-8 rs274 -g
[15:58:37] <jepler> enter G0.0 and you'll get the error
[15:59:55] <jepler> this change to the interpreter at least puts the error message in the right place: http://pastebin.ca/1670056 (it's an error if not all the expected letters were consumed by strtod)
[16:01:55] <jepler> it's the LC_NUMERIC category that is the problem. It is possible to retrieve the current setting with one setlocale call, temporarily change it, and finally restore it to the original value. You could arrange to do this in your program anytime you are going to make a call to the interpreter
[16:02:28] <gtom_> Ok, thank you, now i understand what happened... caus ive tried it with the ',' also...
[16:02:38] <jepler> "," is rejected by the strspn call
[16:03:29] <gtom_> same error, but this one is raised in the read_one_item and the error with the '.' is raised in the STRTOD...
[16:03:34] <jepler> I'd also consider a patch that changes the interpreter to do that itself around the strtod call, or which temporarily changes "." to the locale's decimal point separator, or whatever
[16:04:09] <jepler> yeah, my patch doesn't fix anything (besides making the error happen "in the right spot")
[16:05:13] <gtom_> but why not declare a "own" decimalseperatorchar in emc???
[16:06:25] <gtom_> ill try to find a workaround in my pascal program... thank you for your help...
[16:06:38] <gtom_> regards, Thomas
[16:06:41] <gtom_> bye
[16:06:44] <jepler> because historically emc was not even translatable
[16:07:05] <jepler> like I said, I'd be happy to consider patches submitted to improve this.
[16:07:49] <gtom_> thank you for doing this, our new GUI is on the way... :-)
[16:07:57] <gtom_> Bye
[16:15:41] <seb_kuzminsky> hi PCW
[16:16:24] <PCW> Hi Sebastian!
[16:17:25] <PCW> Wouldnt normally be here at work this early but had the second 500G drive on our server fail in 2 months
[16:22:15] <PCW> bbl breakfast!
[16:51:16] <CIA-40> EMC: 03jepler 07master * r2135e4f8f4cc 10/src/emc/usr_intf/axis/Submakefile: Always append to PYI18NSRCS
[16:51:16] <CIA-40> EMC: 03jepler 07master * re966cd57d641 10/src/emc/usr_intf/stepconf/stepconf.py: cleanup
[16:51:17] <CIA-40> EMC: 03jepler 07master * ree6ed052fff0 10/src/emc/usr_intf/touchy/Submakefile: let strings in touchy be available for translation
[16:51:17] <CIA-40> EMC: 03jepler 07master * r0640fd600d3a 10/src/emc/usr_intf/touchy/touchy.py: translate touchy
[16:51:19] <CIA-40> EMC: 03jepler 07master * r8685d08226ad 10/src/emc/usr_intf/touchy/ (emc_interface.py mdi.py): these strings should be translatable
[16:51:21] <CIA-40> EMC: 03jepler 07master * r0fb682518fdd 10/src/emc/usr_intf/touchy/ (emc_interface.py touchy.py): decrease CPU usage
[16:51:24] <CIA-40> EMC: 03jepler 07master * rabee067ff808 10/src/emc/usr_intf/touchy/touchy.py: the set_active reformulation makes these ifs redundant
[16:51:29] <jepler> PCW: ugh, bad luck
[16:54:00] <mozmck_work> Hi seb, did you see the minor edits I made to hostmot2 for newer kernels? did it cause any problems?
[16:54:57] <seb_kuzminsky> hi mozmck_work, i saw it and tried it out at home and didnt notice any breakage
[16:55:00] <seb_kuzminsky> so thanks!!
[16:55:53] <mozmck_work> good! it wouldn't compile on karmic so I looked up the errors and found out what was going on.
[16:56:16] <seb_kuzminsky> gitk
[16:56:18] <seb_kuzminsky> oops
[16:58:14] <CIA-40> EMC: 03seb 07master * r529e0b871229 10/docs/src/common/User_Concepts.lyx: fix a typo
[17:00:53] <seb_kuzminsky> mozmck_work: the code changes in your commit f88ea0 look good, but there were also a bunch of whitespace changes which sort of buried the real code changes
[17:01:36] <seb_kuzminsky> thanks for cleaning up my whitespace sloppiness, but it might be easier to do that as a separate commit from the one that changes the behavior (just to make the diff easier to read)
[17:03:11] <mozmck_work> yeah, cradek told me about the whitespace stuff. I figured out eclipse did it.
[17:03:57] <mozmck_work> I should have looked at the diff before I pushed it.
[17:04:11] <seb_kuzminsky> yeah it looked like some helpful tool getting in the way ;-)
[17:04:25] <seb_kuzminsky> no problem, and thanks for the patch
[17:04:37] <mozmck_work> yep, I found and turned that setting off :)
[17:04:42] <seb_kuzminsky> heh
[21:47:35] <alex_joni> the mercurial webinterface is quite good: http://hg.openhex.org/hgwebdir.cgi/relatorio/graph/d5830c7ff9a7
[21:48:18] <Jymmm> ?
[21:48:39] <Jymmm> the tree?
[21:49:40] <alex_joni> Jymmm: all of it
[21:49:47] <alex_joni> but especially the tree
[21:50:00] <Jymmm> alex_joni: Ok, if you say so. But I don't see it.
[21:52:14] <Jymmm> alex_joni One example... I transversed your link to it's intitial version, but doesn't provide a path back it's the original - navigation wise.
[21:53:02] <Jymmm> alex_joni: anyhow =)
[21:56:11] <Jymmm> alex_joni: Ok, it's not bad. =)
[22:14:16] <micges> alex_joni: yes tree is cool