Back
[09:08:09] <Roguish> morning jthornton
[09:08:22] <jthornton> morning
[09:56:06] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #219: > - <requires lib="gtk+" version="2.16"/>
[13:32:39] <andypugh> I wonder how to tell when a userspace component has seen a valid resolver position from a 7i49?
[13:33:41] <andypugh> I am currently trying the approach of setting the pin to -1e99 and checking if it has changed. But this feels a bit flaky.
[15:49:11] <andypugh> Well, I appear to have my lathe doing abolute-homing with single-turn encoders.
[15:53:08] <JT-Shop2> cool
[15:54:05] <andypugh> It feels like I should be able to just use the position.txt file, but that has extra behaviour that I think gets in the way
[15:55:11] <andypugh> I have writen a Python component that writes the joint positions to disk in exactly the same way as position.txt, but it does something a little different with it.
[15:56:35] <andypugh> On startup it checks to see what combination of full-turns + the current encoder single-turn position is closest to the old position, and then applies that many turns as an offset added to the position feedback.
[15:57:17] <andypugh> Then the new HOME_ABSOLUTE_ENCODER option is used to home where it is.
[15:57:34] <andypugh> _should_ be more accurate than position.txt I think.
[16:23:33] <BeachBumPete> whats a single turn encoder?\
[16:24:15] <andypugh> Well, in this case, it’s a resolver
[16:24:27] <andypugh> It’s single-turn absolute.
[16:29:20] <BeachBumPete> ah OK
[16:30:11] <andypugh> So, coarse position from a file exuivalent to position.txt and then fine position from the resolver itself.
[16:30:28] <BeachBumPete> http://i.imgur.com/rsw3eEH.jpg :)
[16:33:04] <andypugh> Surely you can force BP to buy you a clean one?
[16:34:28] <BeachBumPete> huh?
[16:44:27] <BeachBumPete> sorry I am in the wrong forum LOL
[20:15:46] <kwallace> Hello, I'm working on a g-code program that runs a loop. The loop has a test in it in which I need to record variables. The number of loops vary and the loops that need to record variables varies, so I would like to dynamically create and name these variables. The only similar g-code feature I can think of is the probing log, but that creates a file, I think I need local variables. Does anyone have advise?
[20:17:18] <cradek> you'll have to use numbered variables. #[#100] = [value to save] then #100=[#100+1]
[20:17:29] <cradek> this gives you something like an array, the array index being #100
[20:18:08] <cradek> in this case you might want to start off with #100=111
[20:18:13] <cradek> er I mean 101
[20:18:25] <cradek> whatever - just start somewhere in variable space that makes sense
[20:18:37] <kwallace> I was thinking that would add 1 to the value of #100.
[20:18:55] <cradek> yes and then next time #[#100] is the next spot in the array
[20:20:39] <cradek> http://linuxcnc.org/docs/html/gcode/overview.html#sub:numbered-parameters
[20:20:46] <cradek> > The # character may be repeated; for example ##2 means the value of the parameter whose index is the (integer) value of parameter 2.
[20:20:46] <kwallace> Hmm, I'll need to study that, thank you. I hope you had a good holiday.
[20:21:00] <cradek> seems you can just spell it ##100
[20:21:12] <kwallace> Cool. I missed that.
[20:21:17] <cradek> > Of course, #[1+2] does mean the value found in parameter 3.
[20:21:20] <cradek> "of course" haha
[20:21:25] <cradek> snarky documentation
[20:21:36] <cradek> I did, hope you did too
[20:22:48] <cradek> I ate green bean casserole and also burnt some candles, so it was multidenominational as far as I can pull it off
[20:25:40] <kwallace> Well, not so good for me. The last few years I have been caring for my mother and she passed just before Christmas. I have to sell her home which means the end of the shop too. I have no idea what's ahead, but for some reason I'm confident I can sort it out.
[20:25:56] <cradek> oh no, I'm so sorry
[20:26:03] <cradek> what a lot of things to handle at once
[20:27:09] <kwallace> But I figure I've nothing to loose, which is strangely liberating.
[20:28:01] <skunkworks> I have decided live can be hard some times
[20:28:06] <skunkworks> life
[20:28:13] <cradek> well I'm hoping for the best outcome, whatever that is for you
[20:29:00] <KGB-linuxcnc> 03Dewey Garrett 05master 4a01c6f 06linuxcnc 10(11 files in 7 dirs) Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4a01c6f
[20:29:01] <KGB-linuxcnc> 03Dewey Garrett 05master 6d1ff81 06linuxcnc 10docs/src/gui/gmoccapy-hu.txt gmoccapy-hu.txt:delete references to removed files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6d1ff81
[20:32:31] <kwallace> Thank you. I mentioned it, in case I disappear for a while or I need to unload my machines.
[20:32:55] <cradek> where do you live?
[20:33:58] <kwallace> California, next to Yosemite
[20:38:09] <linuxcnc-build> build #142 of 1540.rip-jessie-armhf is complete: Failure [4failed configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1540.rip-jessie-armhf/builds/142 blamelist: Norbert Schechner <nieson@web.de>, Sebastian Kuzminsky <seb@highlab.com>, Dewey Garrett <dgarrett@panix.com>, John Thornton <bjt128@gmail.com>
[20:51:30] <linuxcnc-build> build #2825 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/2825 blamelist: Norbert Schechner <nieson@web.de>, Sebastian Kuzminsky <seb@highlab.com>, Dewey Garrett <dgarrett@panix.com>, John Thornton <bjt128@gmail.com>
[20:52:45] <linuxcnc-build> build #3025 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/3025 blamelist: Norbert Schechner <nieson@web.de>, Sebastian Kuzminsky <seb@highlab.com>, Dewey Garrett <dgarrett@panix.com>, John Thornton
[20:52:45] <linuxcnc-build> <bjt128@gmail.com>
[20:53:48] <linuxcnc-build> build #2825 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/2825 blamelist: Norbert Schechner <nieson@web.de>, Sebastian Kuzminsky <seb@highlab.com>, Dewey Garrett <dgarrett@panix.com>, John Thornton <bjt128@gmail.com>
