Back
[00:18:11] <CIA-2> EMC: 03micges 07iotask_remove * r25b1c0c655c0 10/ (327 files in 96 dirs): Merge branch 'master' into iotask_remove
[01:13:49] <ries_> ries_ is now known as ries
[01:35:23] <mshaver> cradek: If you see this I wanted to let you know that I rebuilt usbtouchscreen.ko and got the touchscreen to respond after rmmodding usbhid and then hotplugging the USB cord. I think I can use usbhid quirks to get that driver to ignore the touchscreen and let it be controlled by usbtouchscreen instead. The _real_ problem stems from the fact that the touchscreen reports itself as an HID, but really isn't HID compatible.
[01:35:55] <cradek> spectacular - congrats
[01:36:33] <mshaver> It still doesn't work right, but once I get done I'll do a whole big writeup on the complete process.
[01:36:54] <cradek> but it moves the pointer?
[01:37:08] <cradek> (what a pain in the ass badly-behaved USB devices are)
[01:37:40] <mshaver> eh, it seems to register all touches in the lower right corner of the screen, repeatedly opening the trashcan
[01:37:50] <cradek> ugh
[01:38:00] <cradek> I guess that's something.
[01:38:35] <mshaver> I think that's related to another problem where the driver thinks there are two touchscreens instead of on (shown by xinput --list)
[01:38:59] <mshaver> It's a multi-problem type of situation...
[01:39:39] <cradek> swirly
[01:39:45] <mshaver> anyway, time to pass out for the day! Thanks for all the help!
[01:39:52] <cradek> welcome
[07:37:04] <morfic-> morfic- is now known as morfic
[13:13:04] <ries_> ries_ is now known as ries
[15:53:46] <JT-Work_> JT-Work_ is now known as JT-Work
[16:21:24] <skunkworks> does this make sense?
http://sherline.com/CNCmenu.htm
[16:24:07] <SWPadnos> what is an incremental mode preset?
[16:24:12] <cradek> you mean that they knew about a bug in february but didn't tell us? nope, doesn't make sense.
[16:24:41] <cradek> SWPadnos: they mean increment settings, I bet
[16:25:42] <SWPadnos> ok, jog increment settings
[16:25:45] <SWPadnos> ?
[16:25:50] <cradek> alex fixed it (??) in jan 2010
[16:25:55] <cradek> brb
[16:26:50] <skunkworks> heh
[16:26:58] <SWPadnos> I wonder if someone should email them
[16:28:24] <SWPadnos> "hey, this was fixed the month before you posted this message, so if you update (back-date?) your version of emc2, it'll be fixed" ...
[16:28:50] <SWPadnos> "unless of course it's not actually fixed for you, in which case it might be nice for you to tell someone"
[16:40:04] <cradek> hard to say whether alex's fix is what they report (but it sure seems likely)
[16:46:39] <cradek> knowing the interesting change is a5133a5231f7, how can I tell which tagged release versions that's in?
[16:48:27] <jepler> cradek: well there's probably a smart way
[16:48:33] <jepler> but the dumb way I do it is: gitk -1 a5133a
[16:48:35] <jepler> click the commit
[16:48:42] <jepler> look at the Follows: and Precedes: lines
[16:48:47] <jepler> Follows: cvs-import
[16:48:47] <jepler> Precedes: v2.4.0-pre1, v2.5.0-pre0
[16:49:04] <cradek> so all of 2.4, none of 2.3
[16:49:09] <cradek> ?
[16:49:12] <jepler> yes
[16:49:25] <cradek> thanks
[16:49:53] <psha> to see what was tag before commit you may use git describe
[16:50:01] <psha> $ git describe a5133a5231f7
[16:50:01] <psha> cvs-import-693-ga5133a5
[16:50:39] <cradek> psha: that's not really what I want - I wondered which releases follow (or which branches that change is merged into)
[16:50:52] <cradek> hm, I guess it also may have been cherry picked in some release branches
[16:51:18] <psha> i see :) so i've stated that it only shows tag _before_ :)
[16:51:38] <psha> cherry pick is impossible to track as i understand git
[16:51:49] <psha> since it's just reapplying of commit
[17:05:43] <mshaver> Is Ray still in contact with Sherline? If not, is anyone? I ask because it's probably a good idea if we make sure that they are shipping the latest & greatest EMC2, and that their users know how to get upgrades, fixes and support. I know it's not really our job, but Sherline is a significant portal through which many people get their first exposure to EMC. It would be "a good thing" if their experience was as positive as is possible.
[17:06:18] <mshaver> Does anyone from Sherline ever get on here and talk?
[17:08:20] <cradek> years ago there was a guy who was routinely in contact. he left sherline and I haven't seen anyone since.
[17:08:48] <mshaver> Was that Mike <something>?
[17:09:18] <mshaver> The guy who was out in Ann Arbor years ago? Dark hair, youngish?
[17:11:48] <cradek> yes mike something - I never met him in meatspace
[17:13:08] <mshaver> He was somewhat, ...volatile.
[17:13:35] <mshaver> completely disappeared
[17:14:32] <mshaver> no one else eh? Any word from Ray lately?
[17:17:35] <cradek> ray drops me an email once in a great while, but he hasn't been on irc for ages.
[17:33:28] <psha> buildbot is up?
[17:35:35] <jepler> I think seb is working on it at the moment..
[17:40:31] <psha> cool
[17:41:03] <psha> when new packages will be ready i'll report how new rendering in axis works in real environment
[19:17:03] <cradek> "With cutter compensation in effect, some dwell will occur for blocks that are executed in less than .25 seconds."
[19:18:05] <cradek> (boss 8)
[19:18:15] <skunkworks> heh
[19:18:38] <skunkworks> I thought block processesing was .25 seconds for all moves ;)
[19:18:52] <cradek> our cutter comp is now officially better than this control from 1983 had.
[19:19:07] <skunkworks> sweet :)
[19:19:19] <cradek> we get all the cases right that it does, plus two that I see that it gets wrong
[19:20:10] <cradek> and we probably only use 100x the ram and 1000x the cpu power to do it
[19:20:32] <skunkworks> exactly.. remember the good old days where the os fit on a floppy?
[19:23:32] <cradek> The part program storage area is equivalent to 100 feet of NC tape and is non-volatile.
[19:23:55] <cradek> by my experience that should be "and is sometimes non-volatile"
[19:24:44] <SWPadnos> "and is as non-volatile as NC tape stored in a warm, damp place"
[19:24:56] <cradek> ha
[19:27:08] <skunkworks> plastic tape!
[19:27:49] <SWPadnos> "... stored in direct sunlight"
[19:28:27] <skunkworks> actually - I think the test tapes we got with the K&T are metal
[19:30:02] <cradek> cool, it could do a grid ("frame"?) of holes with one block
[19:30:45] <cradek> G191 X Y Z X Y Z P P F
[19:33:36] <skunkworks> yikes
[19:36:06] <cradek> maximum control limit, coordinate words: +/- 838.8607
[19:36:16] <cradek> (?)
[19:37:52] <cradek> aha, that's sign plus 23 bits
[19:38:25] <cradek> 3 byte words!
[20:10:01] <mshaver> cradek: my connection is a little shaky today - do I understand that you've implemented all the Bridgeport mega-G-codes in the interp? :)
[20:10:42] <cradek> sorry to inform you, but your grasp on reality is apparently a little shaky too
[20:11:15] <skunkworks> G191!
[20:11:18] <cradek> (someone asked me about adding filleting - I remembered boss8 did it, so I looked it up)
[20:11:38] <mshaver> but you did say that our cutter comp handling is equivalent?
[20:11:49] <cradek> not equivalent to filleting
[20:12:10] <cradek> I was just commenting that our cutter comp is better than boss8's :-)
[20:12:22] <mshaver> but no gouging errors for too small inside radii?
[20:12:44] <cradek> I don't understand the question
[20:13:22] <mshaver> boss8 would not balk at a sharp inside corner with comp on
[20:13:37] <cradek> emc has handled that for some time now
[20:13:58] <skunkworks> *since cradek fixed it...
[20:14:04] <mshaver> really. I did not know that.
[20:14:09] <cradek> dude
[20:14:13] <cradek> where have you been?
[20:14:28] <mshaver> not in front of a machine obviously!
[20:14:58] <cradek> April 2009, EMC 2.3.0 release note: "new cutter compensation algorithm handles inside sharp corners and does not require complicated entry moves"
[20:15:21] <cradek> so saying "for years" would have been a bit hyperbolous...
[20:15:59] <mshaver> actually, I've been trying to get this touchscreen to work - which once i made some adjustments to xorg.conf.d/10-evtouch.conf and blacklisted usbhid is now almost sort of working
[20:16:10] <cradek> cool
[20:16:50] <mshaver> it's just a little off tracking a stylus - need to get the numbers right and I think it will work
[20:17:18] <cradek> awesome
[20:17:38] <mshaver> anyway, back to work on that...
[20:21:41] <micges> cradek: polar coordinates can be applied to G2/G3 ?
[20:24:46] <cradek> micges: yes you can specify the endpoint in polar
[20:25:21] <cradek> g0@1^0; g3i-1^90
[20:27:06] <micges> thanks
[21:22:28] <JT-Work_> JT-Work_ is now known as JT-Work