#linuxcnc-devel | Logs for 2016-09-07

Back
[00:09:35] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15c-morley commented on issue #159: I will try to look at it this weekend
[05:45:31] <Patang> After upgrading from 2.7.3 to 2.7.6 my DRO's (gmoccapy) shows something completely wrong. Can't really say what they show, but I guess this might be enough info for someone to tell me if they have heard of anything similar?
[07:25:22] <jepler> Patang: issues can be filed at https://github.com/LinuxCNC/linuxcnc/issues - -I am not a gmoccapy user so I don't have any knowledge of this problem, but a quick search there didn't find a filed issue yet.
[07:34:13] <jepler> yay, gmane will survive under new leadership. http://lwn.net/Articles/699704/
[07:43:18] <cradek> Patang: I think this might be the known/fixed bug https://github.com/LinuxCNC/linuxcnc/issues/157
[07:44:01] <cradek> Patang: unfortunately that bug report involved a lot of mistakes, so be careful to read the whole thing
[07:45:09] <cradek> Patang: I'm not at a real computer to check, but I don't think the fix is released yet, so your choices are move back a version or use a buildbot prerelease package
[07:46:10] <Patang> cradek: Thanks, I'll have a closer look at it after work.
[08:07:46] <skunkworks> zlog,
[08:21:42] <jepler> cradek: thank you for finding that information.
[09:15:17] <seb_kuzm1nsky> i'll try to release 2.7.7 with the fix tonight
[09:18:34] <skunkworks> I Am pretty sure the speed coincidence is the problem with no motion. It also doesn't come on when you stop the spindle. (causing feed moves without the spindle on to not motion)
[09:18:56] <skunkworks> so we will move that logic into hal with a window comparator..
[10:14:43] <cradek> skunkworks: check out the near component
[10:15:14] <cradek> seb_kuzm1nsky: thank you, that would be great
[10:15:24] <skunkworks> hmm - wonder what I used on the K&T
[12:44:15] <mozmck> I've seen several people mention that the program line shown does not follow the actual line being executed. Is there a way to get the program line from task instead of motion?
[12:44:41] <mozmck> Here is one such question: https://forum.linuxcnc.org/forum/38-general-linuxcnc-questions/31547-motion-program-line-issue#80136
[19:20:54] <jepler> yay! I just got rid of that broken 3d printer I probably would never get around to fixing.
[19:21:06] <jepler> now I can buy another piece of junk to put in the vacated spot.
[20:40:38] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 e2c70c4 06linuxcnc 10VERSION 10debian/changelog LinuxCNC 2.7.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e2c70c4
[20:40:38] <KGB-linuxcnc> 03Sebastian Kuzminsky 05signed tags ffa8577 06linuxcnc 03v2.7.7 LinuxCNC v2.7.7 (tagged commit: e2c70c4) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ffa8577
[20:41:53] <jepler> hmph, spi didn't work first time
[20:42:20] <jepler> mesaflash sends 0100a840 00000000 00000000 00000000 00000000 (intent is to read cookie)
[20:42:31] <jepler> and reads back aaaaaaaa 00000000 00000000 00000000 00000000
[20:42:37] <jepler> before announcing that the cookie is not right
[20:46:04] <jepler> reading back aaaaaaaa seems to indicate that the basic SPI transaction is working
[20:46:34] <jepler> CS, clock, and MISO pins are right
[20:46:38] <jepler> I guess it doesn't prove MOSI is right
[20:47:04] <jepler> though I o-scoped it, and data seemed to be there
[20:51:51] <jepler> same behavior from linuxcnc, fails to read cookie (I didn't hex dump the read back transaction though)
[20:53:14] <jepler> unsurprisingly if I tie MISO to +5V or GND I read back all 00 or FF
[20:53:34] <jepler> so the problem must be MOSI, or the 7i90
[20:53:47] <jepler> tomorrow I'll dig out the odroid u3 that worked right last time I tested it...
[20:55:34] <jepler> seb_kuzminsky: thank you for your work towards 2.7.7.
[20:56:08] <jepler> cradek said he thought there was a gmoccapy fix in there (#157) but I don't see it in your changelog .. was he mistaken?
[20:56:11] <jepler> oh was it
[20:56:11] <jepler> + * Interp: fix startup regression regarding coordinate systems and more
[21:17:39] <cradek> yeah, it affected all guis
[21:18:22] <cradek> jepler: what did you do with the broken 3d printer?
[21:19:25] <cradek> yay for 2.7!
[21:45:47] <jepler> cradek: gave it away to Koji
[21:48:40] <cradek> yay!
[22:23:21] <seb_kuzminsky> ironically i found another bug in 2.7.6-26 just now :-(
[22:23:31] <seb_kuzminsky> a pretty bad one - surprise motion
[22:25:25] <skunkworks> zlog
[22:33:52] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky opened issue #160: Surprise motion when exiting cutter comp after no move 02https://github.com/LinuxCNC/linuxcnc/issues/160
[22:35:16] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #160: If there's a move between the g41.1 and the g40 (a cutter-comp entry move), then Z does not glitch on the move following the g40. 02https://github.com/LinuxCNC/linuxcnc/issues/160#issuecomment-245481400
[22:37:55] <seb_kuzminsky> i get nostalgic now when i configure --enable-simulator
[22:38:12] <seb_kuzminsky> we were so young back then
[22:38:15] <seb_kuzminsky> life was so simple
[22:40:34] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #160: Also affects v2.6.12-82-g4c613c1 and v2.6.12, so it's not because of my recent Task fiasco, for once. 02https://github.com/LinuxCNC/linuxcnc/issues/160#issuecomment-245482040
[23:07:28] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6-issue-160 bbf1259 06linuxcnc 10(6 files) add a test of early exit from cutter comp * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bbf1259
[23:09:02] <cradek> well that's odd
[23:09:23] <cradek> that may go back to the beginning of time
[23:09:40] <cradek> at least to the beginning of new-cutter-comp
[23:15:06] <seb_kuzminsky> good thing i had max speed turned down to something even my dull reaction time could deal with
[23:25:43] <cradek> comp_set_programmed() doesn't get called until a move issues, but convert_cutter_compensation_off() expects it to be valid
[23:28:03] <cradek> you may always get zero, not necessarily the zero from line 1 in your test program
[23:29:11] <linuxcnc-build> build #2662 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/2662 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:29:13] <cradek> heh I think we had good test coverage for every kind of entry move, except for the one that isn't there
[23:29:28] <cradek> you people write some weird gcode :-)
[23:30:59] <cradek> g'night
[23:34:11] <linuxcnc-build> build #4501 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/4501 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:35:26] <linuxcnc-build> build #2327 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/2327 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:35:27] <linuxcnc-build> build #4502 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/4502 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:35:39] <linuxcnc-build> build #2662 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/2662 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:37:37] <linuxcnc-build> build #4502 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/4502 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:38:33] <linuxcnc-build> build #4503 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/4503 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:40:10] <linuxcnc-build> build #3712 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/3712 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:43:37] <linuxcnc-build> build #1130 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/1130 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:47:52] <linuxcnc-build> build #1130 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/1130 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:55:42] <linuxcnc-build> build #4513 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/4513 blamelist: Sebastian Kuzminsky <seb@highlab.com>