Back
[01:08:08] <linuxcnc-build> build #1305 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/1305 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:09:00] <linuxcnc-build> build #1303 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/1303 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:09:44] <linuxcnc-build> build #725 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/725 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:10:17] <linuxcnc-build> build #686 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/686 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:13:36] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/debs_wodocs 060d64b 06linuxcnc 10(7 files) debian: support deb build without doc packages * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=060d64b
[01:17:34] <linuxcnc-build> build #3391 of 1200.rip-lucid-i386 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/3391 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:41:50] <linuxcnc-build> build #3394 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3394 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:45:31] <linuxcnc-build> build #3391 of 1202.rip-lucid-amd64 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3391 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[01:57:13] <linuxcnc-build> build #3401 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3401 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[08:48:42] <seb_kuzminsky> when we were first starting on liblinuxcncui ("lui") at the hackspace in texas, i thought of proposing we name it instead the "LinuxCNC Meta-Controller", LMC, after this:
http://apod.nasa.gov/apod/ap150827.html
[09:36:05] <jepler> nice
[09:36:11] <jepler> maybe this winter I'll get back to that
[10:43:40] <seb_kuzminsky> jepler: yeah me too - it's one of the 2.8 projects i'm pretty excited about
[12:11:32] <JT-Shop> skunkworks, doesn't seem to be as much chatter on this channel
[12:12:07] <JT-Shop> I changed the after move to .5 and the output only cycled on twice out of the 8 times I coded
[12:14:17] <JT-Shop> the test G code
http://pastebin.com/EZV2vveK
[12:25:32] <mozmck1> need a #linuxcnc-ot channel for the chatter
[12:25:48] <pcw_home> sure seems like that would toggle every time
[12:33:05] <JT-Shop> maybe I need to watch it in halscope instead of show hal configuration
[12:43:04] <pcw_home> yeah the screen update rate will mask/alias short changes
[12:46:39] <skunkworks> yes - watclscope
[12:46:44] <skunkworks> wow
[12:46:46] <skunkworks> watch halscope
[12:51:34] <JT-Shop> can't seem to get halscope setup to show the on state or what to trigger on lol
[12:56:18] <skunkworks_> http://i.imgur.com/VI2HaPu.png
[12:58:41] <skunkworks_> JT-Shop: with velocit
[12:58:44] <skunkworks_> velocity
[12:58:46] <skunkworks_> http://i.imgur.com/UuPg5uR.png
[12:59:33] <skunkworks> pretty darn cool
[12:59:39] <JT-Shop> yea
[12:59:45] <skunkworks> did you get it?
[13:00:00] <JT-Shop> I was on the phone, going to try now
[13:20:42] <jepler> yes, I would expect/hope that the m62/m63 codes work consistently like it shows in skunkworks second imgur
[13:29:54] <JT-Shop> yes, I finally got halscope to trigger... copying skunkworks too close and left it in stop mode
[13:30:50] <JT-Shop> I did notice that I get a more even on time if the last move is G1 not G0, G0 causes a delay in M63 turning off
[13:49:51] <skunkworks> how much longer?
[13:55:28] <JT-Shop> http://imgur.com/i7V28s1,em5a5nV
[13:55:37] <JT-Shop> about twice as long
[13:56:11] <JT-Shop> first image is a G1 after and second is a G0 after the last M63
[13:56:27] <skunkworks> it looks like the actual program line takes twice as long too
[13:57:08] <skunkworks> might be a blend thing.. - G1 - g0 are exact stops
[13:57:31] <skunkworks> yes - that is why
[13:57:54] <skunkworks> deaccelleration adds time
[15:36:20] <jthornton> that makes sense
[16:49:17] <seb_kuzminsky> linuxcnc-build: force build --branch=2.7 0000.checkin
[16:49:18] <linuxcnc-build> build #3402 forced
[16:49:18] <linuxcnc-build> I'll give a shout when the build finishes
[16:49:22] <seb_kuzminsky> jessie debs?
[17:07:38] <jepler> wow, I just learned about Intel Quark that all revisions have a silicon bug that makes the LOCK prefix sometimes corrupt processor state. They note it as a fixed issue, because their Linux distribution (yocto) has a patched as which always strips the "lock" prefix from software it assembles.
[17:09:00] <seb_kuzminsky> "fixed"
[17:09:17] <jepler> (quark is intel's 2013 low power offering)
[17:09:35] <seb_kuzminsky> that's the processor on their edison?
[17:10:26] <jepler> I initially thought that, but this page says it Edison is "powered by the Intel® Atom™ SoC dual-core CPU"
[17:11:59] <seb_kuzminsky> ok
[17:12:21] <jepler> wikipedia says "dual-core Intel Quark x86 CPU" though
[17:12:27] <jepler> Intel doesn't seem to say..
[17:13:27] * seb_kuzminsky shrugs
[17:20:29] <jepler> oh and I didn't even read wikipedia. the next sentence was: A later announcement changed the CPU to a 22 nm Silvermont dual-core Intel Atom CPU,[5]
[17:21:00] <jepler> so my two sources agree it's z34xx for which intel hasn't published much documentation
[17:29:35] <jepler> silvermont also includes z36xx/z37xx, which *do* have euphemistically-named "specification update" documents. no real howlers except a memory-ordering bug ("MOVNTDQA may pass earlier locked instructions").
[17:29:39] <jepler> lots of peripheral bugs, though
[17:29:54] <jepler> "doesn't even boot sometimes because of smi"
[17:31:49] <linuxcnc-build> build #0 of 3004.dsc-jessie is complete: Failure [4failed shell] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/3004.dsc-jessie/builds/0
[17:31:52] <linuxcnc-build> build #0 of 3302.dsc-jessie-rtpreempt is complete: Failure [4failed shell] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/3302.dsc-jessie-rtpreempt/builds/0
[17:31:58] <seb_kuzminsky> or not...
[17:33:52] <seb_kuzminsky> because of lintian errors
[17:33:57] <seb_kuzminsky> that's something you dont see every day
[17:34:37] <jepler> I have had DEBUILD_LINTIAN="no" for a very long time
[17:35:02] <seb_kuzminsky> i explicitly run lintian on our dscs and debs after producing them
[17:35:17] <seb_kuzminsky> fixed several issues they found, down to just warnings now
[17:35:23] <seb_kuzminsky> ... until jessie
[17:37:00] <jepler> E: linuxcnc source: license-problem-gfdl-invariants docs/src/common/gpld-copyright.txt invariant part is: with no invariant sections, no front-cover texts, and one back-cover text: this linuxcnc handbook is the product of several authors writing for linuxcnc.org. as you find it to be of value in your work, we invite you to contribute to its revision and growth
[17:37:05] <jepler> E: linuxcnc source: license-problem-gfdl-invariants docs/src/common/GPLD_Copyright_fr.txt invariant part is: with no invariant sections, no front-cover texts, and one back-cover text: this linuxcnc handbook is the product of several authors writing for linuxcnc.org. as you find it to be of value in your work, we invite you to contribute to its revision and growth
[17:37:10] <jepler> these two files can be fixed by taking a clean upstream version
[17:39:33] <jepler> KimK: do we have your permission to remove the back-cover text from the file "overleaf.txt"? DFSG "back-cover texts" are considered a license problem by Debian -- I can provide more information about that if you care.
[17:41:05] <jepler> debian's viewpoint about this:
https://www.debian.org/vote/2006/vote_001
[17:42:38] <linuxcnc-build> build #3402 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3402
[22:31:42] <cradek> With the part zeroed at the center, everything has polar coordinates. The bolt holes are #10 on a 50 mm BCD, which is G0 @25^[45+90*i].
[22:31:50] <cradek> yay ed mentions polar coordinates
[22:31:53] <cradek> that's 3 users :-)
[22:34:55] <cradek> wow, that poor sherline cutting steel plate
[23:15:29] <KimK> jepler: Yes, everyone certainly has my permission (and encouragement!) to delete or change anything I did if it helps LinuxCNC (or the developers). And if I inadvertently specified a license that later proved to be troublesome, my apologies, please change it.
[23:15:39] * KimK steps up to the microphone...
[23:15:55] <KimK> *tap* *tap* Is this on? (cough)
[23:16:03] <KimK> I hereby grant to the LinuxCNC developers my permission to delete or change anything I did if it will help LinuxCNC (or the developers). Thank you.
[23:16:16] * KimK steps away from the microphone...
[23:16:29] <KimK> OK, is that good? Do I need to do anything more than that? Let me know, and thanks for working on this.
[23:19:08] <KimK> jepler: Or would you like it to look better if *I* change it? I'm happy to change it if you'll specify what you want done or send me a patch to push or something.
[23:20:07] <KimK> I'm happy to help by either method.
[23:21:53] <KimK> s/either/any/
[23:38:59] <seb_kuzminsky> thanks KimK
[23:39:44] <KimK> Hi Seb, how are things?
