Back
[00:26:13] <skunkworks> logger_dev: bookmark
[00:26:13] <skunkworks> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2010-04-09.txt
[02:47:22] <CIA-2> EMC: 03cradek 07master * r0074a4789679 10/docs/src/gcode/ (4 files in 2 dirs): add a bit more to the g76 section and markup fixes
[02:47:23] <CIA-2> EMC: 03cradek 07master * rb8eb1be3d826 10/src/emc/kinematics/tc.c: Approximately fix overblending of arcs.
[02:47:23] <CIA-2> EMC: 03cradek 07master * r10990ad37af9 10/configs/common/configurable_options/pyvcp/ (m5i20panel.xml parportpanel.xml): Fix panels to use correct disable pin spelling
[02:47:24] <CIA-2> EMC: 03cradek 07master * r4018a76cd3c5 10/lib/python/pyvcp_widgets.py: Fix inconsistance spelling of disable pin option
[02:47:25] <CIA-2> EMC: 03cradek 07master * r4ca13e5d0674 10/src/emc/rs274ngc/rs274ngc_return.hh: Remove unused string after merge of tlo_all_axes
[02:47:26] <CIA-2> EMC: 03cradek 07master * r15b145450f4d 10/src/po/pl.po: Updated Polish translations
[02:47:27] <CIA-2> EMC: 03cradek 07master * ree4f691d383f 10/docs/src/hal/pyvcp.lyx: added some missing info on disable pins
[02:47:27] <CIA-2> EMC: 03cradek 07master * rd12728e00d40 10/docs/src/common/User_Concepts.lyx: Fix wrong discription for G61
[02:47:28] <CIA-2> EMC: 03cradek 07master * rf642d5da3f57 10/docs/src/Master_User.lyx: Change order of chapters
[02:47:31] <CIA-2> EMC: 03cradek 07master * r2662f56a49ec 10/ (13 files in 10 dirs): Merge branch 'v2.4_branch'
[14:39:13] <cradek> http://timeguy.com/cradek-files/emc/0001-Export-motor-offset-to-HAL.patch
[14:39:38] <SWPadnos> cool. I had thought about that
[14:39:58] <cradek> I wonder if this is sufficient to satisfy those needs being discussed on the list
[14:40:08] <SWPadnos> but the latest mail by dave has a point - you can probably do this in HAL, if you're clever about thread ordering
[14:40:31] <SWPadnos> I thought there was already an offset pin
[14:40:33] <SWPadnos> or param
[14:40:34] <cradek> I've only tried it on sim, and oddly the offset switches between two close values when I home repeatedly
[14:41:20] <SWPadnos> isn't the difference between joint_pos_cmd and motor_pos_cmd the offset?
[14:41:53] <cradek> not quite, because I think screw comp and backlash comp cause more offset
[14:42:07] <SWPadnos> ah
[14:42:21] <cradek> but that's one of the reasons I'm reluctant to push this - I don't understand all of it
[14:43:27] <cradek> I should at least try it on a machine with index homing first
[14:43:36] <SWPadnos> yeah
[14:43:43] <cradek> I probably won't have time for a while though
[14:44:26] <SWPadnos> It seems like a misplaced request anyway
[14:44:42] <cradek> well, I definitely see the value for an index homed machine
[14:44:45] <SWPadnos> I can't tell if the machine in question gets turned off
[14:44:47] <SWPadnos> sure
[14:44:55] <SWPadnos> wait, why?
[14:45:11] <cradek> it would be great if you could detect 'it occasionally loses 4 encoder counts'
[14:45:15] <SWPadnos> it could be of interest on any machine that has real homing
[14:45:28] <SWPadnos> sure, but you can only detect that when you re-home
[14:45:34] <SWPadnos> usually after noticing that something doesn't look right
[14:45:48] <SWPadnos> and you can't home in G-code, it's a manual process
[14:45:55] <SWPadnos> so the machine can't check itself
[14:45:56] <cradek> if the problem is minor you might never notice. it'd be nice to be able to test it.
[14:46:20] <cradek> well, fwiw, an machine with index encoders CAN monitor itself, but that's another issue
[14:46:27] <SWPadnos> yeah. I'm just not sure how useful it really is
[14:46:51] <SWPadnos> yes, the machine can check its position whenever an index arrives - that's useful
[14:47:14] <SWPadnos> eh, anyway
[14:47:24] <cradek> yeah except our encoder interface sure doesn't support it
[14:47:53] <SWPadnos> the encoder interface doesn't have to
[14:48:08] <SWPadnos> hmmm. well actually I guess it does
[14:48:49] <SWPadnos> no, actually the index input (with parport and Mesa) is available to HAL, which is all that's needed
[14:48:57] <SWPadnos> pico, STG, etc. wouldn't work
[14:49:11] <cradek> at the end of being on all day, it'd be very nice to be able to verify that no encoder counts have been lost... On my machine a count is a micron. It would take a pretty huge number of them lost for me to notice.
[14:49:25] <cradek> what do you mean index input is available to hal?
[14:49:41] <SWPadnos> move very slowly, look for index in software, check encoder counts when encoder is seen
[14:50:00] <SWPadnos> with hostmot2, aren't all the I/O pins readable in HAL, even if they're attached to an advanced function?
[14:50:18] <cradek> IMO that's so limited and inadequate it's not worth doing
[14:50:44] <cradek> you'd want to use the capture-count-on-index in the fpga
[14:50:59] <SWPadnos> sure, that's a better idea
[14:51:12] <SWPadnos> might be available only to Mesa though
[14:51:15] <SWPadnos> and software
[14:52:46] <cradek> bbl
[14:53:46] <SWPadnos> see ya
[17:39:45] <SWPadnos> huh. why isn't that file in the nc_files dir?
[17:52:08] <alex_joni> it's somewhere in AXIS lib
[17:52:48] <cradek> file/save-gcode-as
[22:15:32] <ries_> ries_ is now known as ries