#linuxcnc-devel | Logs for 2015-12-10

[07:01:20] <skunkworks> zlog
[07:37:29] <jepler> just happened to encounter this http://blog.linuxmint.com/?p=2955 and now I wonder how it is that Linux Mint defines update levels. It seems like an interesting concept.
[07:39:37] <jepler> so far I've found that a description may be shown in the UI and might be in a big documentation PDF. boo.
[07:40:30] <jepler> the 5 levels are "Certified", "Recommended", "Safe", "Unsafe", and "Dangerous"
[07:56:36] <cncbasher> i gather we live in the Dangerous catagory
[08:05:23] <jepler> we're not even on their list
[08:22:40] <jepler> but it does make me wonder if we did have official packages, how do we make our stable versions appear at a low level number and our unstable versions appear at higher level numbers
[08:32:02] <cncbasher> jepler:did you get any further with the pathpilot ?
[08:32:30] <cncbasher> i'm see in a few changes mostly with the tooltable
[08:33:30] <cncbasher> and a few changes to motion & nml
[08:38:33] <cradek> jepler said tormach put all the offsets in the stat buffer, and that sounds like a nice change to me
[08:38:39] <cncbasher> but the interesting one is canterp i think , from my little understanding
[08:38:51] <cradek> oh?
[08:38:59] <cncbasher> yes thats what i'm looking at now
[08:39:33] <cncbasher> also they added fsync to iocontrol for the tool table
[08:41:16] <cncbasher> theirs quite a few interesting snips
[08:41:38] <cncbasher> if i could only get it to compile ! haha
[08:41:56] <cncbasher> iv'e slipped up somewhere
[08:42:27] <cncbasher> i'm currently updating 2.7 with pathpilot
[08:42:54] <cncbasher> or more or less merging some aspects
[08:45:07] <cradek> sweet!
[08:45:53] <cradek> it would be so awesome if you could separate the changes, in different branches, so we can evaluate which ones to merge
[08:46:02] <cradek> are you working from their git, or just a snapshot?
[08:46:15] <jepler> cncbasher: no, I haven't touched it
[08:46:46] <jepler> cradek: to my knowledge they have not announced a url for a public git repository.
[08:47:15] <cradek> argh, that sounds like terrible work then. sorry, cncbasher
[08:47:34] <cradek> (I didn't know what they send when you request the source)
[08:48:47] <jepler> cradek: I did some sleuthing and found a ref which I believe is not far from their branch point. https://forum.linuxcnc.org/forum/pathpilot/29983-notes-on-path-pilot-1-8-2-source-code
[08:52:25] <cncbasher> it's in my dropbox if you want it
[08:53:04] <cncbasher> https://www.dropbox.com/s/dyt30zowmfbptqq/pathpilot_source.tar?dl=0
[08:54:08] <cncbasher> they change the button images in the source as they treat them as copyright , but no big deal
[08:54:50] <cncbasher> but if you want them , then email me
[08:55:11] <jepler> there's also a link in that forum post to the source tar
[08:55:24] <jepler> images used for user interface elements are the very least interesting part of it for me
[08:56:15] <jepler> improvements to the core of linuxcnc are more so, but trying to ferret some of them out and get them ready to go into our master branch is not something that's risen to the top of my todo lists
[08:57:39] <cncbasher> i'm working through them, so see how it goes and whats worth implementing , after iv'e tested it
[08:59:02] <jepler> that's good. are you familiar with git already?
[08:59:41] <cncbasher> i'd class my self as intermediate in that , but getting there
[09:01:46] <jepler> the main items I'd emphasize are to avoid putting unrelated things in the same commit and learning to use git gui or other interactive tools to double check each thing you are adding to a commit.
[09:01:53] <jepler> afk
[09:02:14] <cncbasher> yes i understand
[09:02:48] <cncbasher> makes it easier to track and revert etc
[09:03:32] <cncbasher> ok i'm out for a few hrs back in about 2 or so
[09:51:46] <jepler> anyway with my pull request to seb's rtai repo, I get a full testsuite pass on Linux r64 3.16.0-9-rtai-amd64 #1 SMP PREEMPT Debian 3.16.7-6linuxcnc (2015-11-30) x86_64 GNU/Linux
[09:51:50] <jepler> Runtest: 172 tests run, 172 successful, 0 failed + 0 expected
[09:52:10] <jepler> .. going to delete that VM now, it's on a pay by the hour service (dang they're convenient)
[09:53:55] <cradek> cncbasher: thank you for digging through it - I appreciate your work
[10:23:21] <mozmck> http://www.ncgeeks.org/wp-content/uploads/2014/09/images.jpg
[10:23:48] <jepler> I'm more like the guy in the middle even on my linux machines
[10:24:54] <mozmck> Yeah, I have gotten more that way. You mentioned the linux mint update levels - it seems like a good idea. They don't automatically push out updates that could break things without testing them first.
[10:25:48] <mozmck> I ran Debian unstable for years, and while it wasn't too bad, my wife would groan every time I did a system update :-) Sometimes it took a while to get it running again.
[11:07:29] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/ja10v2 c2cd226 06linuxcnc 10src/emc/motion/command.c command.c: error message on one line (joints_axes) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c2cd226
[11:39:30] <cncbasher> i,m back
[11:51:59] <skunkworks> jepler: cool! I can test it tomorrow.
[11:53:42] <seb_kuzminsky> jepler: i've been busy with non-linuxcnc stuff but i'll try to incorporate your fix tonight, thanks very much
[12:35:29] <jepler> seb_kuzminsky: np
[12:35:50] <jepler> skunkworks: let us know how it goes
[14:37:35] <cradek> https://forum.linuxcnc.org/forum/38-general-linuxcnc-questions/30055-x-y-and-z-a
[14:37:38] <cradek> xes-are-reversed/66761
[14:37:41] <cradek> can't wait to hear the answer to this
[14:43:20] <cncbasher> probably needs to turn the monitor round ...
[14:43:54] <cncbasher> got to have done somthing he's not saying
[14:45:30] <cradek> well if he didn't change his software config, it IS hardware ... but not sure what exactly
[14:46:21] <seb_kuzminsky> shop gremlins reversed his encoder cables
[14:58:10] <cncbasher> i could't resist
[14:58:22] <cncbasher> i had to answer it
[15:01:07] <seb_kuzminsky> cncbasher: your questions sure point at the likely culprits
[15:05:48] <cncbasher> lets see
[15:14:43] <skunkworks> cncbasher: thank you for everthing you do on the forums!
[15:22:07] <cncbasher> thanks