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

[10:09:16] <skunkworks> jmk is trying to do some stuff with machine kit (he has an application that the bbb fits - mostly a hal device). He (in jmk fashion) is not sugar coating the issues he is running into and how things are done in machine kit. surprisingly mah hasn't weighed in..
[10:11:13] <cradek> I wonder if he needs mk-specific things, or if he could just use a linuxcnc-style-hal build on it
[10:11:33] <cradek> I suppose he might want their hardware stepgen or some bit like that
[10:14:46] <skunkworks> right - I think this is to run his grinder or such
[10:15:47] <skunkworks> he made a comment that he would have switched back to linuxcnc if it wasn't for the size
[10:17:32] <skunkworks> I think there is still wonkyness with the fixture offsets and 2.7.6. Maybe he never noticed it before as it happens in 2.7.1. I have not tried 2.6
[10:19:46] <skunkworks> the second you hit cycle start - the 'active gcodes' switch back to g54 even though you have set a different offset in mdi and it is set in the program.
[10:29:18] <skunkworks> if that makes sense
[11:10:52] <skunkworks> duh. I know what is happening.. we normally use m30 for program end.
[11:11:17] <skunkworks> I bet switching to % probably fixes the fixture issue
[11:19:40] <cradek> hmm yeah, is the motion right or wrong? after m2/m30 it will switch back to g54. if your program is straight gcode it'll run through it in no time and then the active codes will show the after-m2 state I think.
[11:20:07] <skunkworks> sure
[11:20:29] <skunkworks> motion does the right thing - but it gets confusing because mdi input is in g54 after program run.
[11:20:49] <skunkworks> which isn't a bug I guess because it is what m30 is supposed to do
[11:26:00] <cradek> http://www.linuxcnc.org/docs/html/gcode/m-code.html#mcode:m2-m30
[11:26:28] <cradek> yes I agree
[13:57:41] <KGB-linuxcnc> 03John Morris 05zultron/m30-remap-interaction-lcnc26 3721ee6 06linuxcnc 10(6 files) Unit test for M30 and remapped command interaction * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3721ee6
[13:59:32] <KGB-linuxcnc> 03John Morris 05zultron/m30-remap-interaction-lcnc26 9e716be 06linuxcnc 10src/emc/rs274ngc/rs274ngc_pre.cc interp: don't drop remap level at prog exit * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9e716be
[13:59:48] <cradek> ooo
[14:22:12] <linuxcnc-build> build #2591 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/2591 blamelist: John Morris <john@zultron.com>
[14:23:04] <linuxcnc-build> build #2591 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/2591 blamelist: John Morris <john@zultron.com>
[14:23:26] <skunkworks> So I threw one of the startech pci printer port cards into the the xp machine with mach and it doesn't magically force it into totem pole epp mode.
[14:23:59] <cradek> I forgot about this
[14:24:08] <skunkworks> heh
[14:24:12] <cradek> did you ever find a situation where the linuxcnc change worked?
[14:24:26] <jepler> we're all doing our best to forget about parallel port interfaced hardware
[14:24:34] <skunkworks> not yet - other than I could (on a working epp printer port) turn it off...
[14:25:20] <skunkworks> yes - but I think there is still a substantial amount of users that still lpt
[14:25:41] <linuxcnc-build> build #1059 of 1500.rip-jessie-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1500.rip-jessie-i386/builds/1059 blamelist: John Morris <john@zultron.com>
[14:25:52] <linuxcnc-build> build #4432 of 1200.rip-lucid-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/4432 blamelist: John Morris <john@zultron.com>
[14:25:55] <linuxcnc-build> build #1059 of 1520.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1520.rip-jessie-amd64/builds/1059 blamelist: John Morris <john@zultron.com>
[14:26:13] <jepler> hm I wonder if it's expected for the new test to fail. whoops.
[14:27:05] <jepler> BUG: remap_level < 0 : -1
[14:27:27] <linuxcnc-build> build #4432 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/4432 blamelist: John Morris <john@zultron.com>
[14:27:41] <linuxcnc-build> build #4430 of 1300.rip-precise-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/4430 blamelist: John Morris <john@zultron.com>
[14:29:41] <linuxcnc-build> build #2257 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/2257 blamelist: John Morris <john@zultron.com>
[14:29:43] <linuxcnc-build> build #4432 of 1306.rip-precise-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/4432 blamelist: John Morris <john@zultron.com>
[14:31:03] <linuxcnc-build> build #3642 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/3642 blamelist: John Morris <john@zultron.com>
[14:37:37] <jepler> >>>
[14:37:39] <jepler> True story: My former employer had a 40 deg C burn-in oven
[14:37:39] <jepler> for testing small VFDs. Over a weekend, the solid-state relay
[14:37:39] <jepler> used to control the heating element failed shorted. On Monday
[14:37:39] <jepler> we found 6 drives whose plastic covers looked like something
[14:37:41] <jepler> out of a Salvador Dali painting.
[14:37:44] <jepler> <<<
[14:37:46] <jepler> pics or it didn't happen
[14:42:08] <jepler> Subject: [PATCH 0918/1285] Replace numeric parameter like 0444 with macro
[14:42:11] <jepler> wow that's a big thread
[14:42:54] <mozmck> they were discussing on #linux-rt and said it's from intel
[14:43:06] <mozmck> a patch flood!
[14:43:17] <linuxcnc-build> build #4442 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/4442 blamelist: John Morris <john@zultron.com>
[14:43:17] <linuxcnc-build> build #4447 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4447 blamelist: John Morris <john@zultron.com>
[14:43:23] <jepler> yes the submitter is @intel.com
[14:45:20] <jepler> .. I forget I should lurk on #linux-rt (oftc.net, not freenode)
[14:47:39] <mozmck> yeah
[14:48:42] <jepler> It's unfortunate that, upon ariving at https://groups.google.com/forum/#!forum/machinekit it says "Topics which relate to both LinuxCNC and Machinekit right now, like usage and configuration will likely find a better audience at emc-developers and emc-users"
[14:49:06] <jepler> I am not sure if that is the initial message, or some descriptive text about the group
[14:50:15] <cradek> jeez I wish I could get an effing mbox out of this
[14:50:37] <cradek> I just want to do ~f jmk
[14:51:21] <jepler> https://github.com/icy/google-group-crawler
[14:51:44] <jepler> oh dear god, it's a shell script that generates a shell script for you to run
[15:09:03] <cradek> well the thread ends with him hoping to change and compile the corresponding source
[15:16:02] <skunkworks> it is pretty active - probably happen tonight ;)
[15:27:16] <jepler> <snark> if he starts compiling tonight, he'll be ready to post about the results on thursday</snark>
[15:54:04] <linuxcnc-build> build #557 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/557 blamelist: John Morris <john@zultron.com>
[17:21:20] <jepler> ah no I guess zultron intended a push to fail building, based on his ML post
[18:50:51] <andypugh> Is the reset-to-G65-on-abort behaviour fixed?
[19:13:40] <jepler> andypugh: I think this is one of the things fixed in 2.7.6. I am not sure about the state of master at this point.
[19:17:08] <andypugh> OK, great. Just checking before a forum reply.