#linuxcnc-devel | Logs for 2016-08-03

[06:48:37] <skunkworks> I think andy can jump into any subject and hold his own...
[07:14:32] <jthornton> I think your correct
[09:41:32] <skunkworks> how come 2.7.5 isn't in (or .6 for that matter) isn't in git?
[09:42:25] <skunkworks> never mind - haven't 'git pull'ed in a while
[10:58:22] <mozmck> makefiles are annoying
[11:09:43] <skunkworks> wow - chrome keeps jessie from sleeping
[11:13:00] <archivist> has to talk to daddy
[11:48:19] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15gmoccapy opened issue #131: LCD crashes system calling a page > availible pages 02https://github.com/LinuxCNC/linuxcnc/issues/131
[12:08:35] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.6/issue-131-lcd 101d05a 06linuxcnc 10src/hal/components/lcd.c lcd: missing call to hal_ready * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=101d05a
[12:08:35] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.6/issue-131-lcd 0a06df4 06linuxcnc 10src/hal/components/lcd.c lcd: stop processing when page_num is too high * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0a06df4
[12:09:01] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.6/issue-131-lcd 3072970 06linuxcnc 10src/hal/components/lcd.c lcd: stop processing when page_num is too high * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3072970
[12:10:22] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler closed pull request #87: configure: revamp *mod detection (06master...06jepler/master/configure-foomod) 02https://github.com/LinuxCNC/linuxcnc/pull/87
[12:10:46] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #73: This needs a rebase onto our master branch before it can be merged. 02https://github.com/LinuxCNC/linuxcnc/pull/73#issuecomment-237293643
[12:45:07] <KGB-linuxcnc> 03Norbert Schechner 05master eec48e1 06linuxcnc 10(9 files in 2 dirs) gmoccapy_2_1_0 - new config for SCARA * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=eec48e1
[13:31:47] <linuxcnc-build> build #558 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/558 blamelist: Jeff Epler <jepler@unpythonic.net>
[13:50:37] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened pull request #132: Jepler/2.6/issue 131 lcd (062.6...06jepler/2.6/issue-131-lcd) 02https://github.com/LinuxCNC/linuxcnc/pull/132
[15:19:18] <linuxcnc-build> build #559 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/559 blamelist: dummy, Jeff Epler <jepler@unpythonic.net>
[16:37:12] <CaptHindsight> what is a good way to run a stepper motor that is not controlling an axis but will run for say 310 steps every few operations? And it should easily drop into G-code
[16:37:21] <CaptHindsight> custom M code?
[16:37:40] <jepler> ladder hooked to digital out from motion?
[16:42:37] <CaptHindsight> it doesn't have to sync to motion or be real time
[16:44:24] <cradek> scale a stepgen so 310 steps is 1 "position" unit and feed that from a motion output
[16:44:41] <cradek> or a ladder output or whatever
[16:49:26] <jepler> yes, I agree, set 1 position-unit = 310 steps
[16:54:53] <CaptHindsight> have to tie it to a custom M-code so it can be dropped in wherever they decide
[17:40:45] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15pkmcnc opened pull request #133: genhexkins: add new functionality (06master...06master) 02https://github.com/LinuxCNC/linuxcnc/pull/133
[19:36:43] <CaptHindsight> can you define M-codes over M199? Is there some hard limit in Linuxcnc?
[19:38:36] <andypugh> jepler: Thanks for fixing LCD. I would have got round to it eventually, but faster is better.
[19:47:13] <CaptHindsight> but 100 M-codes should be enough for anyone
[20:33:22] <jepler> CaptHindsight: I think there's an array somewhere with static size, probably a modest development effort to make it unlimited.
[20:41:50] <CaptHindsight> jepler: I think I have enough but I have noticed some 3D printer CAM that goes up at least until the M-300's
[20:43:58] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #133: I can't follow the math and don't have relevant hardware to test, but the code looks fine to me. 02https://github.com/LinuxCNC/linuxcnc/pull/133#issuecomment-237423147
[21:42:36] <skunkworks_> first mach support forum is down since this morning - now forum.linuxcnc.org is down. Coincidence? Hmmm
[21:43:59] <cradek> working for me...?
[21:44:07] <skunkworks_> maybe just really slow. or it is just me..
[21:44:12] <cradek> yeah it's slooooow
[21:44:31] <cradek> at about 16:30 today jepler installed some updates. I wonder if something's bogus now
[21:45:10] <skunkworks_> yeck
[21:45:41] <cradek> jepler: beep boop
[21:49:45] <jepler> umm I updated php on the forum a bit ago and then didn't check all was well
[21:49:54] <jepler> but it WFM
[21:50:49] <jepler> not at 16:30, though
[21:51:13] <jepler> 2016-08-03 21:49:22 but I think that's US eastern time or something
[21:51:50] <skunkworks_> seems to be working better now
[21:51:58] <jepler> cradek: what kinds of changes did you see at 16:30 ?
[21:54:00] <jepler> hm there's a joomla update today too
[21:54:26] <cradek> Source: isc-dhcp
[21:54:30] <cradek> -Version: 4.2.4-7ubuntu12.4
[21:54:34] <cradek> +Version: 4.2.4-7ubuntu12.5
[21:54:50] <cradek> libdrm, dhcp stuff, language-pack stuff
[21:55:10] <cradek> also kernel I think
[21:55:16] <cradek> a bit hard to read the diff
[21:55:39] <cradek> oh I'm only syncing once a day, ignore my time
[21:55:58] <jepler> OK
[21:56:22] <jepler> yes I did some updates yesterday as well, at 8:30 eastern time if anybody's keeping track
[21:59:05] <jepler> hmph and uh oh, the joomla 3.6.0 -> 3.6.1 update is broken even though I did the "update the updater" step first like I'm supposed to
[22:23:15] <jepler> [pid 1157] stat("/tmp/Joomla_3.6.x_to_3.6.1-Stable-Patch_Package.zip", 0x7ffe83a46480) = -1 ENOENT (No such file or directory)
[22:23:24] <jepler> I should *NOT* have strace'd the update process