#linuxcnc-devel | Logs for 2016-10-20

[06:23:55] <jthornton> I just downloaded the arduino software and noticed they had a download counter...
[10:13:11] <KGB-linuxcnc> 03Jeff Epler 05master fea7872 06linuxcnc 10COPYING 03COPYING.more De-confuse github about licenses * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fea7872
[10:16:06] <KGB-linuxcnc> 03Jeff Epler 05master a50c5c3 06linuxcnc 10docs/src/hal/comp.txt Merge remote-tracking branch 'gh-jepler/halcompile-rawstring' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a50c5c3
[10:16:27] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler closed pull request #168: Halcompile rawstring (06master...06halcompile-rawstring) 02https://github.com/LinuxCNC/linuxcnc/pull/168
[12:27:52] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened pull request #183: Refactor debian configure (06master...06refactor-debian-configure) 02https://github.com/LinuxCNC/linuxcnc/pull/183
[13:38:03] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #180: There are two bugs here. One is that the F-word changes surprisingly, and the other is that you have to issue an MDI command (after Aborting, or switching into and back out of Manual) before the wonky F-word is revealed. 02https://github.com/LinuxCNC/linuxcnc/issues/180#issuecomment-255183604
[13:46:12] <KGB-linuxcnc> 03Sebastian Kuzminsky 05issue-180 b58bd9f 06linuxcnc 10(8 files) tests: add an abort-vs-feed-rate test (skipped) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=b58bd9f
[13:46:12] <KGB-linuxcnc> 03Sebastian Kuzminsky 05issue-180 7941a6b 06linuxcnc 10src/emc/task/emccanon.cc canon: return correct feed rate in G95 mode * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7941a6b
[13:46:12] <KGB-linuxcnc> 03Sebastian Kuzminsky 05issue-180 e7960c0 06linuxcnc 10src/emc/rs274ngc/rs274ngc_pre.cc interp: after synching settings from canon, update all copies of the info * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e7960c0
[13:46:14] <KGB-linuxcnc> 03Sebastian Kuzminsky 05issue-180 c0bbe2a 06linuxcnc 04tests/abort/feed-rate/skip tests: enable the abort-vs-feed-rate test created a few commits ago * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c0bbe2a
[13:59:01] <andypugh> I wish I knew more about multi-axis stuffs;
[13:59:02] <andypugh> https://forum.linuxcnc.org/10-advanced-configuration/29276-xzc-lathe-rotational-feed-rate-kinematics?start=10#81896
[14:05:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 c4b6361 06linuxcnc 10src/emc/task/emccanon.cc canon: return correct feed rate in G95 mode * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c4b6361
[14:05:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 a7d52ea 06linuxcnc 10src/emc/rs274ngc/rs274ngc_pre.cc interp: after synching settings from canon, update all copies of the info * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a7d52ea
[14:05:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 b36c723 06linuxcnc 04tests/abort/feed-rate/skip tests: enable the abort-vs-feed-rate test created a few commits ago * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=b36c723
[14:15:15] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #179: I'd like to know what the previous version of 2.8.0 you had was, where things worked right. You can probably see the old version number by running this command:... 02https://github.com/LinuxCNC/linuxcnc/issues/179#issuecomment-255193618
[14:18:23] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 e3c6812 06linuxcnc 10src/emc/rs274ngc/rs274ngc_pre.cc 10src/emc/task/emccanon.cc Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e3c6812
[14:18:35] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #176: Your guess about the interpretation of "G1 F10000" is approximately on target; the preview and bounds calculations assume that the start of a program is a number of preparatory G0 moves, which fully establish the starting coordinates; otherwise, some arbitrary value (possibly the origin of the active coordinate system?) is used instead.... 02https://github.com/LinuxCNC/linuxcnc/issues/176
[14:43:05] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened pull request #184: pncconf: don't refer to kernel_version when not is_kernelspace (06master...06issue-159) 02https://github.com/LinuxCNC/linuxcnc/pull/184
[14:54:13] <linuxcnc-build> build #2213 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_1] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/2213 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[14:58:44] <mozmck> I'm having trouble with linuxcnc.stat()
[15:07:24] <jepler> mozmck: tell us more
[15:08:01] <mozmck> yeah, I'm still looking at it. I'm using a custom gscreen skin, and using GStat() which is in hal_glib()
[15:08:52] <mozmck> Trying to read line numbers and other vars in a 100ms periodic function, and it seems to not be updating properly.
[15:10:23] <mozmck> I call: self.gstat.stat.poll() and then print the line number, call_level, and file name, and it seems to only ever print my external touchoff subroutine file name and line number
[15:10:47] <cradek> pretty sure AXIS's Machine/Show LinuxCNC Status thingy updates faster than 100ms
[15:11:38] <mozmck> It may, but this does not seem right.
[15:11:54] <cradek> file and current_line do look right
[15:12:09] <cradek> (I wonder what they're doing differently)
[15:12:30] <jepler> mozmck: if you are seeing different info than emctop shows, then look at your program for the problem. If you're seeing the same data in both, but it's not the data you wish you would see, then it's probably task you get to blame next.
[15:12:50] <jepler> (emctop is a standalone program, though the easiest way to start it is from a pulldown in axis)
[15:12:54] <mozmck> What I'm ultimately trying to fix is the codeview jumps back to near the beginning when running a subroutine.
[15:13:04] <mozmck> Hmm, I'll have to look at emctop.
[15:13:18] <cradek> a subroutine in a different file?
[15:13:30] <mozmck> I at first tried making changes in hal_glib and it was doing the same thing.
[15:13:47] <jepler> er I guess it's linuxcnctop now of course
[15:13:48] <cradek> it's probably jumping to the line numbers in that other file - I have seen AXIS do that
[15:14:26] <mozmck> Yes, separate file. My thought was to look at the call level and not send a line number event from hal_glib if the call level is > 0
[15:15:13] <cradek> yeah I think this is a deep issue
[15:15:17] <mozmck> Yes, that is what it is doing, and in trying to fix it I can't get anything to work!
[15:15:29] <cradek> the call level can be >0 but the line numbers valid (if the sub is in your main program file)
[15:16:10] <mozmck> The problem is that stat() seems to not be updating properly from what it looks like.
[15:16:50] <mozmck> What I want is that only the line numbers from the file displayed are used.
[15:17:05] <jepler> that's not what task does right now.
[15:17:21] <mozmck> So when it goes into an external subroutine it just sits on that line until the sub is done.
[15:17:41] <mozmck> what is not what task does?
[15:17:53] <jepler> task doesn't put the values you want into the stat buffer, it puts other values
[15:18:34] <jepler> stat.file always reflects the file opened by the NML EMC_TASK_PLAN_OPEN
[15:18:59] <jepler> but the line numbers represent a line number in "some file"
[15:19:27] <mozmck> well, the file name it is giving me is my subroutine - not the main file.
[15:19:54] <mozmck> I think I've seen that in the past - the file name changes based on the actual file it is running.
[15:19:55] <jepler> OK, I am surprised by that but you tested it more recently than I did
[15:20:29] <mozmck> I'll have to dig deeper. Nothing simple is ever actually simple it seems.
[15:20:47] <jepler> (axis never or almost never cares what the value of file from the stat buffer is)
[15:21:39] <mozmck> Yeah, I was not going to use the file name - just the call level. But when that always came back "1", I started looking at other variables.
[15:46:20] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #184: @c-morley let me know if you have any concerns about merging this, otherwise I'll do it in the next week or so. 02https://github.com/LinuxCNC/linuxcnc/pull/184#issuecomment-255216070
[15:47:27] <andypugh> You know, I am not at all a fan of the Tcl HAL files in the current examples. Linuxcnc says that it is making a copy for you to edit, but you can’t. Because you don’t actually end up with a .HAL file.
[15:50:12] <mozmck> do you end up with the .tcl files?
[15:51:17] <andypugh> They live in a linked folder called hallib
[15:51:35] <andypugh> (in usr/share)
[15:51:35] <mozmck> oh I see.
[15:54:21] <jepler> configs/sim/touchy/ngcgui/pyngcgui_touchy.ini:HALFILE = LIB:basic_sim.tcl
[15:54:25] <jepler> you mean files that say things like this?
[15:54:34] <andypugh> Yes
[15:54:55] <jepler> which can be done with .tcl or .hal extensions I guess?
[15:54:55] <jepler> configs/sim/axis/simtcl/twopass_compat.ini:HALFILE = LIB:axis_manualtoolchange.hal
[15:55:21] <andypugh> Specifically I was wanting to open axis/sim_mm then fiddle about to make a quick XYZA simulator to tst some code
[15:56:14] <jepler> I guess I so seldom run installed packages that I wouldn't have hit this myself
[15:56:42] <jepler> I wonder if dgarr would have a suggestion about how to make this better, I think he added support for LIB:
[15:56:59] <andypugh> And for the TCL HAL files too, I guess
[15:57:24] <andypugh> My problem is that the TCL does not seem to be making a feedback loop for joint 3
[15:57:59] <andypugh> I can put it in postgui HAL, I suppose.
[16:24:24] <KGB-wlo> push to master branch: http://linuxcnc.org/
[16:24:26] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15SebKuzminsky pushed 1 new commit to 06master: 02https://github.com/LinuxCNC/wlo/commit/57f0b2633dd20f8b3d8adcadd03a6b41bef439d4
[16:24:27] -linuxcnc-github:#linuxcnc-devel- 13wlo/06master 1457f0b26 15Sebastian Kuzminsky: add copies of the two NIST papers...
[16:26:55] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 9fff492 06linuxcnc 10docs/src/common/emc-history.txt docs: add links to both NIST papers * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9fff492
[17:00:40] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened issue #185: axis: do better when preview programs which aren't "grounded" in space 02https://github.com/LinuxCNC/linuxcnc/issues/185
[18:02:48] <linuxcnc-build> build #4560 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/4560 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[18:23:38] <linuxcnc-build> build #4575 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4575 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:02:05] <skunkworks_> zlog
[22:04:13] <Tom_L> i just cleared out all but 2016 logs
[22:04:25] <Tom_L> if you want older ones they are in the _old directory