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

[07:03:27] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features 730d1f0 06linuxcnc 10(279 files in 23 dirs) bringin_features: import to share/features * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=730d1f0
[07:03:27] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features 967acc2 06linuxcnc 10(36 files in 3 dirs) bringin_features: relocate sim demo files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=967acc2
[07:03:27] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features 64da59e 06linuxcnc 10lib/python/gladevcp/hal_python.xml 10lib/python/gladevcp/hal_pythonplugin.py bringin_features: fernV edits * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=64da59e
[07:03:28] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features d0e67e3 06linuxcnc 03lib/python/gladevcp/features.py 04share/features/features.py bringin_features: relocate features.py * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d0e67e3
[07:03:33] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features 457f422 06linuxcnc 10(7 files in 4 dirs) bringin_features: adapt to LinuxCNC git tree * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=457f422
[07:03:36] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features c800ffb 06linuxcnc 10(31 files in 6 dirs) bringin_features: place demo configs in tree * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c800ffb
[07:03:41] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features ee87e72 06linuxcnc 10debian/linuxcnc.files.in 10src/Makefile bringin_features: support deb package * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ee87e72
[07:03:44] <KGB-linuxcnc> 03Dewey Garrett 05bringin_features 20ba56d 06linuxcnc 10(13 files in 7 dirs) bringin_features: new README, minor updates * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=20ba56d
[07:06:40] <dgarr> http://www.panix.com/~dgarrett/stuff/bringin_features.txt
[08:02:41] <jepler> dgarr: will look at that branch in the next few days, please ping if you don't hear from me
[08:03:24] <jepler> so I moved from 7i90 connector P1 to P2 and now the motors turn both ways. I think the drivers on connector P1 were damaged last year at TXRX labs when we blew the 7i30
[08:03:29] <jepler> .. yay ?
[08:03:41] <jepler> afk to work
[09:22:41] <cradek> yay?
[10:12:27] <cradek> ooh I love how you edit things and the preview updates
[10:16:26] <cradek> I'm getting a few "image file not found" errors, like: Image file not found : /home/cradek/emc/share/features/graphics/images/square.png
[10:20:26] <cradek> this looks like a huge step, thanks dgarr
[10:36:06] <skunkworks> That is neat!
[10:38:38] <skunkworks> taper hole is pretty cool :)
[10:45:31] <mozmck> good article on mailing lists vs forums: http://www.freelock.com/blog/john-locke/2010-03/mailing-list-or-forum-theory
[11:02:22] <JT-Shop> one thing for sure everyone has an opinion on that subject lol
[11:08:48] <cradek> > Harder to find answers, archives are generally organized by date not topic
[11:08:59] <cradek> this is sure true (although I have terrible luck with forum searches too)
[11:09:37] <cradek> just because I have an email folder with all the emc-users messages, and can search it easily and quickly, that doesn't mean others can do that
[11:12:38] <jepler> forum searches tend to be poor quality (pre-google web search quality) are often rate limited and sometimes require forum sign-ins
[11:13:16] <jepler> but yeah, clearly part of what makes the mailing list useful for me is that I have my own local full text search of 10+ years
[11:15:31] <JT-Shop> use a site search to search a forum like servo site:linuxcnc.org
[11:16:02] <jepler> ditto once you know the location of a high-quality archive of a mailing list
[11:22:27] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 a6bda7b 06linuxcnc 10docs/man/man9/hm2_7i90.9 hm2_7i90 manpage: remove incorrect EPP info * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a6bda7b
[11:22:27] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 2485089 06linuxcnc 10docs/man/man9/hm2_7i90.9 hm2_7i90 manpage: clarify firmware management * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2485089
[11:24:16] <mozmck> I thought he laid out the pros and cons of both pretty well, and explained why lots of people find mailing lists more useful. I have often said I don't have time to look at forums.
[11:25:25] <mozmck> I can look at all the posts on 30 or 40 ml faster than I can go to one forum and browse a few posts.
[11:26:18] <skunkworks> brian.. 'CV settings are getting worked on now and I hope to have that done next week. I am redoing all the code from what it was in Mach3'
[11:26:20] <skunkworks> impressive
[11:27:43] <cradek> I don't see how any one guy can understand and rewrite (!) all the parts of a nontrivial program
[11:28:56] <archivist> I think that is why it relies on external motion planners more and more
[11:32:21] <seb_kuzminsky> yay, features! thanks dgarr!
[11:33:06] <seb_kuzminsky> each time i update a feature, i get a message saying "Message from defaults.ngc: stop and check 'Skip lines starting with /'"
[11:33:18] <cradek> yeah I didn't understand that either
[11:33:32] <cradek> if you don't have block delete on, it makes 100 rapid squares for some reason
[11:33:45] <cradek> it's supposed to be a safety thing? I don't understand it.
[11:34:06] <seb_kuzminsky> oh weird
[11:34:28] <seb_kuzminsky> o<safety-999>
[11:35:19] <seb_kuzminsky> i think i'm going to like conversational machining in some situations
[11:35:22] <cradek> I poked block delete and moved on
[11:35:29] <cradek> yeah, it looks really useful
[11:35:44] <cradek> I got some mill stuff to work, but couldn't figure out facing on the lathe
[11:35:45] <seb_kuzminsky> a lot of the things i do are on-offs where i dont care about being able to go back to my exact gcode months later
[11:36:07] <cradek> yeah and who enjoys writing gcode for facing?
[11:36:22] <cradek> pretty much all lathe stuff is trivial but tedious to write
[11:36:26] <seb_kuzminsky> i've never written any gcode for lathes...
[11:36:50] * seb_kuzminsky looks guiltily at the little servos he bought for the little lathe, collecting dust under a bench
[11:37:42] <cradek> I sometimes MDI repeating drill cycles for basic turning/facing type stuff (not ideal because it drags the tool on the way back out)
[11:37:46] <cradek> it's a silly hack
[11:38:09] <seb_kuzminsky> hmm, there's a surprising thing about the default Features circle
[11:38:43] <archivist> I mdi a bout 3 lines and try to be consistent going back a few, edit, next nest
[11:39:46] <seb_kuzminsky> the thing that surprised me was my own misunderstanding of how to specify the circle
[11:40:37] <seb_kuzminsky> you give two points on the circumference, that's weird to me. there are an infinite number of circles containing any two points
[11:41:15] <seb_kuzminsky> are they assumed to be 180 degrees apart?
[11:41:28] <cradek> maybe so
[11:41:41] <cradek> center and radius or diameter would be less surprising to me
[11:41:54] <seb_kuzminsky> same
[11:42:03] <cradek> dewey's work sure got more eyes on this already
[11:42:38] <seb_kuzminsky> ooh, it works with cutter comp
[11:42:41] <seb_kuzminsky> <3
[11:43:22] <seb_kuzminsky> cool, the circle Feature can make circular pockets, that's super useful
[11:43:48] <seb_kuzminsky> i'm getting dizzy looking at all these spirals
[11:44:30] <KGB-linuxcnc> 03John Morris 05zultron/g52 79bf330 06linuxcnc 10src/emc/rs274ngc/interp_convert.cc interp_convert.cc: noop: wrap ridiculously long lines * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=79bf330
[11:44:30] <KGB-linuxcnc> 03John Morris 05zultron/g52 51b80d5 06linuxcnc 10src/emc/rs274ngc/interp_convert.cc interp_convert.cc: use readable symbols for `switch(g_code)` * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=51b80d5
[11:44:30] <KGB-linuxcnc> 03John Morris 05zultron/g52 a219c2d 06linuxcnc 10(27 files in 9 dirs) Implement G52 offsets * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a219c2d
[11:44:51] <cradek> boom!
[11:45:30] <seb_kuzminsky> oh yeah, i owe zultron another look at that remap/subroutine/start-from-line thing
[11:45:51] <seb_kuzminsky> and a first look at the other things he's pushed
[11:46:10] <cradek> so many things! it's great!
[11:47:41] <seb_kuzminsky> the Features/Circle/Create-a-pocket fails silently(?) if there's no tool loaded
[11:47:54] <seb_kuzminsky> which makes sense, because how would it know how wide to make the passes?
[11:53:09] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 21ae480 06linuxcnc 10docs/man/man9/hm2_7i90.9 10src/emc/motion-logger/motion-logger.c Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=21ae480
[11:53:40] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master e2b0651 06linuxcnc Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e2b0651
[11:54:10] <seb_kuzminsky> if i had remembered to do the merge earlier, zultron wouldn't have had to cherry-pick the motion-logger fix that his test needs
[11:54:14] <seb_kuzminsky> better late than never i guess
[11:54:41] <jepler> if it's still just in his personal branch he can rebase if he prefers
[11:57:07] <seb_kuzminsky> yeah
[11:58:44] <seb_kuzminsky> ooh, rtai 5.0 is being readied for release
[11:59:11] <seb_kuzminsky> using some crazy "copy files between CVS repositories" technique
[12:01:16] <KGB-linuxcnc> 03John Morris 05zultron/g52 89bec83 06linuxcnc 10(27 files in 9 dirs) Implement G52 offsets * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=89bec83
[12:01:59] <jepler> I'm pleased to see zultron contributing
[12:03:12] <seb_kuzminsky> me too
[12:08:08] <seb_kuzminsky> oops, bringin_features brought in the github.com/cnc-club/linuxcnc-features master branch, but nick told me in private email that fern's repo is the one to use
[12:08:42] <seb_kuzminsky> it should be easy to apply the updates from ferns repo to the bringin_features import
[12:09:04] <seb_kuzminsky> or i could redo the first commit in that branch, the one that imports it
[12:09:14] <seb_kuzminsky> dgarr: do you have a preference between these two?
[12:29:44] <linuxcnc-build> build #206 of 1503.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1503.rip-jessie-rtpreempt-amd64/builds/206 blamelist: John Morris <john@zultron.com>, dummy
[12:30:10] <linuxcnc-build> build #206 of 1501.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1501.rip-jessie-rtpreempt-i386/builds/206 blamelist: John Morris <john@zultron.com>, dummy
[12:30:41] <seb_kuzminsky> yay, the buildbot actually did something useful for once
[12:30:44] <cradek> yay!
[12:30:50] <seb_kuzminsky> found a tiny bug in the new docs
[12:31:17] <cradek> however, I am appalled that it uses *** in places that aren't failures
[12:31:27] <cradek> *** this is fine!
[12:31:44] <cradek> *** http://i1.kym-cdn.com/photos/images/newsfeed/000/234/765/b7e.jpg
[12:31:52] <cradek> sorry
[12:32:18] <seb_kuzminsky> i wanted something eye catching, but i can understand that "***" looks scary
[12:32:38] <seb_kuzminsky> probably silence on success would be better
[12:32:50] <seb_kuzminsky> feel free to change it if you like :-P
[12:33:22] <seb_kuzminsky> nice, the zultron/g52 branch has tests and docs and everything
[12:35:27] <seb_kuzminsky> zultron: if you apt-get install w3c-linkchecker, then building the docs will check all the links
[12:35:42] <seb_kuzminsky> the reason we don't build-depend on it is that it's not available in lucid
[12:35:52] <seb_kuzminsky> so that's one more good thing we can do if we drop lucid support...
[12:52:15] <linuxcnc-build> build #3578 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/3578 blamelist: John Morris <john@zultron.com>, dummy
[12:53:48] <KGB-linuxcnc> 03Sebastian Kuzminsky 05jepler/for-master/drop-lucid 2e94777 06linuxcnc 10debian/control.in 10docs/src/checkref 10src/configure.in build-depend on w3c-linkchecker * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2e94777
[12:53:57] <linuxcnc-build> build #3580 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/3580 blamelist: John Morris <john@zultron.com>, dummy
[12:56:28] <andypugh> seb_kuzminsky: Reading back in the logs, it may be that even “Features” is overkill for one-off lathe work. I use a set of turn/bore/face tabs where you just fill in the numbers (which persist through a restart) and press “go”. It covers approximately 97.6% of my lathe stuff: http://www.linuxcnc.org/index.php/english/forum/41-guis/26550-lathe-macros
[13:17:05] <linuxcnc-build> build #206 of 1502.rip-jessie-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1502.rip-jessie-amd64/builds/206 blamelist: John Morris <john@zultron.com>, dummy
[13:18:43] <linuxcnc-build> build #206 of 1500.rip-jessie-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1500.rip-jessie-i386/builds/206 blamelist: John Morris <john@zultron.com>, dummy
[13:33:55] <cradek> seb_kuzminsky: oops, it was you who picked that? :-)
[13:34:15] <cradek> ... make has printed *** on errors forever so that's what I always try searching for
[13:37:06] <linuxcnc-build> build #3591 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3591 blamelist: John Morris <john@zultron.com>, dummy
[13:42:57] <seb_kuzminsky> huh, we dont have continuous jogging input pins in Motion, i thought we did
[13:43:22] <seb_kuzminsky> just wheel jogging in motion, or SHM commands from Task i guess
[13:43:38] <cradek> right
[13:43:45] <cradek> halui has it though
[13:44:41] <seb_kuzminsky> yeah, but that's lame because halui and task are not realtime
[13:44:54] <seb_kuzminsky> i bet that's the problem stuart's having
[13:54:44] <andypugh> One might argue that the Cinci was just big enough that you should deprecate non-realtime jogging
[13:56:06] <cradek> that machine is verrrrry slow. if he doubles the servo cycle I bet the problem goes away
[13:56:22] <andypugh> Isn’t continous jog just a straight-traverse to the axis limit, and an abort on release?
[13:56:28] <cradek> he's got very complex kins running on it and I bet he used one of those shitty atom boards
[13:56:59] <cradek> sort of - they're planned in joint space, but yes abort on release
[13:57:00] <andypugh> Is the machine slow, or just moving a long way?
[13:57:46] <cradek> I don't know the numbers but I think it's slow and the accel is slower
[13:58:02] <cradek> and surely velocity mode servos so you don't need a fast update
[13:58:04] <archivist> on my machine you stop pressing the keyboard and it continues a bit
[13:58:48] <cradek> I wonder if changing the servo cycle would detune his pids. sadly, probably yes
[13:59:01] <archivist> mine is stepper
[14:00:06] <Tom_itx> so you don't care for the atom boards?
[14:00:12] <Tom_itx> 525 etc
[14:00:28] <archivist> any thing a bit slow or low ram
[14:01:27] <Tom_itx> so the Q1900 would be a better choice?
[14:32:52] <seb_kuzminsky> dgarr's email about features is right on point
[14:33:55] <seb_kuzminsky> i haven't looked at the bringin_features branch closely, but if it's as non-invasive as it sounds, it could sure go in 2.7
[14:47:31] <seb_kuzminsky> i just found a bug in linuxcnc. sometimes when you type "make" it crashes your laptop
[14:54:01] <cradek> hmm, I wonder when stuart's machine last rebooted
[15:14:49] <seb_kuzminsky> tell him to run make
[16:28:07] <cradek> http://linuxcnc.org/index.php/english/forum/38-general-linuxcnc-questions/29848-old-install-having-new-issues#64472
[16:28:13] <cradek> I hate when people start two threads
[16:28:36] <cradek> > If you press the arrow key multiple times it will speed up.
[16:28:38] <cradek> uhh
[16:31:32] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 d2e8f94 06linuxcnc 10(28 files in 2 dirs) tests: move the basic motion-logger tests * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d2e8f94
[16:32:02] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6-mountaindew e9e5bcc 06linuxcnc 10(10 files in 2 dirs) tests: add a motion-logger test of the mountaindew bug * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e9e5bcc
[16:43:01] <seb_kuzminsky> cradek: it might be good to talk directly to the guy at the machine, instead of going through Stuart
[16:43:24] <seb_kuzminsky> and he (i'm guessing) might feel more at home talking to us through a webpage instead of joining our mailing list
[16:43:38] <andypugh> Tell them they are out of service contract on 2.4-pre
[16:43:52] <andypugh> (they should at least use a released version)
[16:43:58] <seb_kuzminsky> heh
[16:44:32] <seb_kuzminsky> there have been some juicy jogging fixes in Axis in the, uh, 5.5 years since 2.4.0
[16:44:33] <andypugh> I didn’t know that tjamscad was at MPM. He’s posted a lot to the forum
[16:44:49] <seb_kuzminsky> andypugh: i think that's conjecture at the moment
[16:45:03] <seb_kuzminsky> just since he described a similar issue as what stuart said on the mailing list
[16:45:59] <andypugh> Well, his forum profile says that he lives in Wichita and that his web page is www.mpm1.com
[16:46:08] <seb_kuzminsky> ah, heh
[16:48:19] <andypugh> I wonder what I did today to get 4 new YouTube subscribers?
[16:48:34] <cradek> andypugh: did you figure out your spark problem?
[16:48:58] <andypugh> I haven’t looked at the Ner-a-Car since. Too busy with pattern making
[16:56:57] <JT-Shop> we need a NO_ARE_YOU_SURE entry in the ini
[17:32:30] <andypugh> Has anyone else had the situation where Touchy jumps to 15,000% feed over-ride?
[17:32:50] <andypugh> (It takes a long, long, time to wind it back at 25% per turn)
[17:33:03] <dgarr> seb_kuzminsky: "do you have a preference ...", http://www.panix.com/~dgarrett/stuff/longanswer.txt
[17:41:51] <KGB-linuxcnc> 03John Morris 05zultron/g52 eba2b3c 06linuxcnc 10(27 files in 9 dirs) Implement G52 offsets * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=eba2b3c
[17:42:32] <mozmck> dgarr: I wonder if fernv might help with some of that if you mentioned it to him?
[17:44:30] <seb_kuzminsky> dgarr: reading it now
[17:45:47] <seb_kuzminsky> ok, sounds good.
[17:46:11] <seb_kuzminsky> you know features better than any of us, so your guidance on this is very valuable
[17:46:44] <seb_kuzminsky> i wish nick had sent his reply to the list instead of just back to me, i asked him to keep emc-developers on the To: line for future emails
[17:48:10] <seb_kuzminsky> i agree with mozmck that bringing fern and nick into this would be good - they should have some knowledge of why that change was made, and will maybe/hopefully be willing to do some of the integration work that you've been doing
[17:54:37] <seb_kuzminsky> dgarr: looking at your bringin_features branch, i see no reason why it couldnt go into a future 2.7 release
[17:54:59] <seb_kuzminsky> it looks like it's not making any changes to any existing APIs, and no scary changes to build infrastructure etc
[18:03:47] <cradek> andypugh: no I haven't seen that...
[18:04:37] <andypugh> Do you know where it stores the FO value? It would be less trouble to shut down, edit something, and re-start
[18:05:20] <cradek> ~/.touchy_preferences
[18:05:30] <andypugh> It might be a bazillion false counts on the 7i73.
[18:05:50] <cradek> yeah it seems like it must have been a jump in input counts
[18:06:23] <seb_kuzminsky> andypugh: did it jump in the middle of running touchy, or was it jumped when you started touchy?
[18:06:25] <cradek> kinda forgot it saves those. a feature I guess...?
[18:06:34] <cradek> good question
[18:06:47] <andypugh> It was like that when I started Touchy
[18:07:02] <andypugh> And FO is not in the prefes file
[18:07:50] <andypugh> (i do see “toolsetting_fixture” which is something I think I will change. That’s the L11 / L1 setting I guess?
[18:08:22] <cradek> yeah but it's on the prefs screen
[18:08:43] <andypugh> I just hadn’t spotted it :-)
[18:08:51] <cradek> wait you're right - FO isn't in here
[18:09:06] <cradek> it must be doing that wrong thing at every restart then?
[18:09:12] <andypugh> But it _is_ sticky, as far as I can tell.
[18:09:40] <cradek> one of us is going to have to look at the code, I can just tell
[18:09:49] <andypugh> And no, it isn’t always 15,000. It happens under unusual circumstances that I have not identified. a total of 4 times, ever.
[18:10:48] <andypugh> So, it’s not a huge issue, except that it does lead to tool/work damage as feeds become a bit quick
[18:11:33] <cradek> what's peculiar about your setup?
[18:13:38] <andypugh> Everything
[18:14:15] <andypugh> The mpg is connected through a 7i73 to smart-serial, for a start.
[18:14:59] <andypugh> Otherwise it is one of only two known resolver / 8i20 setups
[18:15:51] <cradek> hmm
[18:15:56] <andypugh> Though that shouldn’t matter, except that false counts could be actually semi-real. Perhaps it’s a bug in the sserial mpg encoder handling
[18:16:03] <cradek> next time it happens, check to see if the counts are unreasonable?
[18:16:18] <andypugh> I should have thought of that
[18:17:20] <andypugh> Having wound it all the way back… 11 s32 OUT -2401 hm2_5i23.0.7i73.0.5.enc0.rawcounts
[18:17:59] <andypugh> So, it’s at -2401 counts after being wound back 600 full turns. It looks like it was at lots more before I wound it back. SO I blame me.
[18:22:48] <cradek> howso?
[18:23:34] <cradek> hm, an unwanted index reset would sure make a jump. any chance of index confusion?
[18:29:41] <andypugh> It’s an mpg, no index
[18:30:04] <andypugh> I am wondering about a bug in my bit-extension code
[18:32:14] <andypugh> The smart-serial encoders can have any bit-length. I extend them to 64 bits here: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=src/hal/drivers/mesa-hostmot2/sserial.c;h=c4ac675498548ea22e79035fa0b1a3f5b1a69044;hb=e2b065110dd5f17fbd5101ba7d0908c8f5b7e9d1#l1421
[18:33:18] <andypugh> Code so clever that I can’t believe that I ever understood it…
[18:52:05] <andypugh> I do like taking a silly idea seriously. Vacuum drawbar, I ask you!
[18:52:26] <andypugh> (I am hoping he is going to ask about a “really high vacuum” :-)
[18:57:19] <cradek> seems like it could work with enough area, which there is not
[19:44:23] <andypugh> cradek: I just found one surprising thing. The 7i73 MPG counter still counts if LinuxCNC is not loaded.
[19:45:11] <andypugh> I can exit Linuxcnc, rotate the encoder, and re-start linuxcnc to see different counts on the 7i73 (accurately different)
[19:45:38] <micges> maybe 7i73's wd is disabled?
[19:45:46] <andypugh> So, tomorrow I might try exiting linuxcnc, turning the knob backwards, re-starting and seeing what happens.
[19:46:27] <andypugh> It isn’t _wrong_ that it should count when it is powered but not being talked to. Just surprising.
[19:46:42] <micges> ok
[19:50:50] <andypugh> I think my code assumes that the last value seen was zero, I will have a look to see if that is a dangerous assumption. I think all sserial encoder counters are mpg without index, so unlikely to be connected to an axis, where this would be a bit seriously bad.
[19:52:49] <micges> worth checking
[19:55:08] <PCW> The sserial watchdogs normally only affect outputs
[21:30:05] <linuxcnc-build> build #3584 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/3584 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:32:08] <seb_kuzminsky> what now
[21:32:16] <seb_kuzminsky> oh, that one's supposed to fail, good!
[21:36:38] <linuxcnc-build> build #3583 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/3583 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:37:01] <linuxcnc-build> build #3585 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/3585 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:40:52] <linuxcnc-build> build #1744 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/1744 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:42:25] <linuxcnc-build> build #1743 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/1743 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:43:54] <linuxcnc-build> build #2792 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/2792 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:51:24] <linuxcnc-build> build #1408 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/1408 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:51:32] <linuxcnc-build> build #211 of 1502.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1502.rip-jessie-amd64/builds/211 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:51:56] <linuxcnc-build> build #3584 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/3584 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[21:53:42] <linuxcnc-build> build #211 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/211 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[22:05:03] <linuxcnc-build> build #3587 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/3587 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[22:05:03] <linuxcnc-build> build #3596 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3596 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>
[22:45:39] <KGB-linuxcnc> 03John Morris 05zulton/g52 fb3c944 06linuxcnc 10(24 files in 6 dirs) Implement G52 offsets * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fb3c944
[22:46:43] <KGB-linuxcnc> 05zulton/g52 fb3c944 06linuxcnc 04. branch deleted * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fb3c944
[22:46:51] <KGB-linuxcnc> 03John Morris 05zultron/g52 fb3c944 06linuxcnc 10(24 files in 6 dirs) Implement G52 offsets * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fb3c944
[22:54:38] <linuxcnc-build> build #3598 of 0000.checkin is complete: Failure [4failed fetch branch to local git repo] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3598 blamelist: John Morris <john@zultron.com>