Back
[05:39:14] <jthornton> I think it would be easier to have the download link just go to
http://linuxcnc.org/iso/ instead of the 2.7 manual otherwise I have to update all the manuals done in lyx
[05:39:50] <jthornton> going to the manual page is confusing for people with legacy systems
[05:41:53] <jthornton> there have been several posts recently where people needed a legacy disk but could not find it on their own
[07:37:47] <jthornton> I expected 2.6 on ubuntu-10.04-linuxcnc3-i386.iso but it is 2.5.0 as is ubuntu-10.04-linuxcnc2-i386.iso
[08:51:14] <jthornton> something like this might be good
http://gnipsel.com/linuxcnc/files.html
[08:51:40] <jthornton> as a download page
[11:04:45] <KGB-linuxcnc> 03Dewey Garrett 05master c43b6dd 06linuxcnc 10src/hal/components/lowpass.comp lowpass.comp: add man page note section * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c43b6dd
[14:28:30] <KGB-linuxcnc> 03Dewey Garrett 05master 1b0a034 06linuxcnc 10src/hal/components/lowpass.comp Revert "lowpass.comp: add man page note section" * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1b0a034
[14:44:15] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes13 138af2f 06linuxcnc 10docs/man/man9/kins.9 kins.9 fix editing errors JA * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=138af2f
[14:44:15] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes13 ffeada0 06linuxcnc 10configs/sim/axis/vismach/5axis/table-rotary-tilting/examples/test-xyzac.ngc 10configs/sim/axis/vismach/5axis/table-rotary-tilting/examples/test-xyzbc.ngc test-xy[ab]c.ngc fix cut/paste errs JA * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ffeada0
[14:44:16] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes13 65def92 06linuxcnc 10lib/hallib/basic_sim.tcl basic_sim.tcl: provide disabling options * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=65def92
[14:44:18] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes13 142228f 06linuxcnc 10src/hal/user_comps/vismach/xyzac-trt-gui.py xyzac-trt-gui.py: fix table item vismach model JA * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=142228f
[15:22:42] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15sleepybishop opened pull request #55: add bitbang spi driver for the max31855 thermocouple to digital conve… (06master...06max31855) 02
https://github.com/LinuxCNC/linuxcnc/pull/55
[17:35:15] <JT-Shop> hmmm
[17:36:42] <Tom_itx> hmmm?
[17:42:09] <JT-Shop> made a suggestion this morning
http://gnipsel.com/linuxcnc/files.html
[17:47:30] <Tom_itx> handy
[17:57:50] <seb_kuzminsky> JT-Shop: looks like a big improvement
[17:59:15] <seb_kuzminsky> i suggest only showing the most recent revision of each install cd, so for example just ubuntu-10.04-linuxcnc3-i386.iso, not ubuntu-10.04-linuxcnc (2 or 1) .iso
[17:59:52] <seb_kuzminsky> i also think we shouldn't show install isos for versions we no longer support, so 2.4 and older
[18:00:11] <JT-Shop> 1 is 2.4 and 2-3 is 2.5
[18:00:17] <JT-Shop> so where is 2.6?
[18:00:20] <seb_kuzminsky> also it's LinuxCNC now, not EMC2 ;-)
[18:00:41] <JT-Shop> but yes 3 is all we need for 2.5
[18:00:48] <seb_kuzminsky> first in the list it says 2.5.0, #2 says 2.5.0 also, and #3 says 2.4.3
[18:01:16] <seb_kuzminsky> cut-n-paste bug maybe
[18:01:23] <JT-Shop> oh #3 is linuxcnc1
[18:01:34] <JT-Shop> #1 is linuxcnc3
[18:01:40] <seb_kuzminsky> do you know how to work with the new jekyll website? it's all git and markdown
[18:01:41] <JT-Shop> #2 is linuxcnc2
[18:01:53] <JT-Shop> not yet
[18:02:01] <JT-Shop> need a secret key?
[18:02:03] <seb_kuzminsky> but #2's EMC2 Version says 2.5.0, just like #1's
[18:02:43] <seb_kuzminsky> JT-Shop: you clone the wlo repo:
https://github.com/LinuxCNC/wlo
[18:02:51] <JT-Shop> right, I was expecting 2.6 on linuxcnc3 then we left for St Louis
[18:02:56] <JT-Shop> just got back
[18:03:38] <JT-Shop> ok, I'll do that in the morning
[18:03:47] <JT-Shop> trying to get the BP pc back running
[18:04:10] <seb_kuzminsky> i see that you don't have push access to that repo, you can either set up a github account with an ssh key and i'll give you access to wlo, or you can send me patches or pointers to some other public repo
[18:04:33] <andypugh> It looks like the cable in my limit-home prox has died again. The sensor works in some Z positions but not others.
[18:04:35] <seb_kuzminsky> there's a README that says how to build the website locally, for testing purposes
[18:04:55] <seb_kuzminsky> JT-Shop: and i'm always happy to help if you have any questions about it
[18:05:39] <JT-Shop> I have a github account
[18:06:28] <JT-Shop> I'll have to find that info
[18:18:43] <andypugh> Does anyone object to me hitting the button on the thermocouple SPI driver thing?
[18:21:19] <JT-Shop> insert both keys at the same time and press the big red button
[18:21:49] <seb_kuzminsky> andypugh: i trust your review, if you like it it's fine by me
[18:22:18] <seb_kuzminsky> have you merged PRs from github before? it's not the obvious "click the merge button"
[18:23:09] <andypugh> Well, it probably isn’t how I would have written it, but it’s a HAL component so can’t do any harm. The guy says it works for him. It is a useful skeleton for future bitbanged SPI drivers too.
[18:23:14] <seb_kuzminsky> andypugh: and since it just adds a comp, without touching anything else, it's fine for 2.6 or 2.7 (or master), whatever you think is right
[18:23:23] <seb_kuzminsky> exactly
[18:23:28] <seb_kuzminsky> thanks for dealing with it
[18:23:50] <andypugh> seb_kuzminsky: In that case I won’t press the obvious button. Perhaps someone else ought to do it if there are hidden complexities.
[19:28:35] <seb_kuzminsky> andypugh: i'd be happy to teach you the process, it's not hard
[19:29:09] <seb_kuzminsky> the key insight is that our linuxcnc repo on github is a mirror of the real repo at git.linuxcnc.org
[19:29:29] <seb_kuzminsky> so you can't make changes directly to the repo at github, because they'll be overwritten next time we sync from git.linuxcnc.org
[19:30:21] <seb_kuzminsky> so you have to fetch the PR into a local repo on your development machine, merge it into the right branch from glo, and push the result to glo (the push is just like what you do with your own commits)
[19:30:38] <seb_kuzminsky> after a while, glo will sync to github, and then you can close the PR
[19:32:39] <andypugh> Right, OK.
[19:32:57] <andypugh> At the moment I don’t have a dev machine, it became the lathe controller.
[19:34:03] <andypugh> I have a VM on the Mac, but I don’t know, at the moment, if I can push from there.
[19:34:43] <andypugh> I have a list of projects to get on with in the code, but at the moment I am 100% hardware on the lathe.
[19:35:11] <andypugh> So, right now, I probably can’t merge the new comp without a fair bit of work setting up a new dev system.
[19:45:12] <andypugh> Actually, this might be OK, the Mac uses git too.
[19:45:51] <andypugh> The puzzle is how to get the PR into my local git
[19:51:58] <seb_kuzminsky> i thought jepler wrote up some docs on this a while back
[19:52:24] <andypugh> Maybe he did, I haven’t been paying much attention
[19:53:29] <seb_kuzminsky> and i can't find it, so maybe i'm hallucinating again
[19:53:32] <andypugh> The “command ine instructions” link is actually pretty clear.
[19:54:45] <seb_kuzminsky> there's this:
https://help.github.com/articles/checking-out-pull-requests-locally/
[19:54:56] <seb_kuzminsky> heh, which say to do what you just said
[19:55:50] <seb_kuzminsky> yep, those instructions seem spot on
[19:56:12] <seb_kuzminsky> what do you know, the github folks know git
[19:58:19] <andypugh> Well, except that the merge command asked me to write a commit message, and put me in vi to do it. And I have never used vi…
[20:00:15] <andypugh> How do you get out of vi?
[20:01:33] <Tom_itx> :x
[20:02:00] <Tom_itx> http://www.lagmonster.org/docs/vi.html
[20:02:55] <Tom_itx> i use pico
[20:03:24] <andypugh> Tom_itx: So do I. Or nano. When it is my choice.
[20:08:38] <andypugh> Looks like I don’t have the ssh keys etc set up on this machine.
[20:09:00] <andypugh> I tried pushing with dry-run and it wasn’t having it.
[20:14:34] <seb_kuzminsky> ok, i'll do it, i have github access here
[20:16:07] <andypugh> Thanks.
[20:18:45] <seb_kuzminsky> did you build it?
[20:23:31] <seb_kuzminsky> it doesnt build on my uspace machine
[20:23:52] <seb_kuzminsky> the build system for our .comp files is really lame and broken
[20:29:44] <andypugh> Ah, well spotted.
[20:30:16] <andypugh> I didn’t try to build it. It shouldn’t need to be in the makefile should it?
[20:30:28] <andypugh> Should just be picked up as a comp.
[20:31:16] <andypugh> As I mentioned, I was in OSX Git, no point trying to build there.
[20:35:42] <andypugh> He has put it in src/hal/drivers That is probably the wrong place.
[20:43:31] <seb_kuzminsky> it might work on rtai and not on uspace
[20:43:39] <seb_kuzminsky> do you know what his development environment is?
[20:49:20] <KGB-linuxcnc> 03Sebastian Kuzminsky 05sleepybishop-max31855 c0f7aae 06linuxcnc Merge branch 'max31855' of
https://github.com/sleepybishop/linuxcnc-mirror into sleepybishop-max31855 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c0f7aae
[20:49:20] <KGB-linuxcnc> 03Sebastian Kuzminsky 05sleepybishop-max31855 1cab897 06linuxcnc 03src/hal/components/max31855.comp 04src/hal/drivers/max31855.comp move the new max31855 comp to hal/components * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1cab897
[20:54:16] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #55: Unfortunately an annoying wrinkle in our .comp build system prevents the component from building on uspace configurations. I'm guessing you're developing on an RTAI machine?... 02
https://github.com/LinuxCNC/linuxcnc/pull/55#issuecomment-210934628
[21:01:52] <linuxcnc-build> build #3258 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/3258 blamelist: Sebastian Kuzminsky <seb@highlab.com>, joseph calderon <calderon.joe@gmail.com>
[21:06:03] <linuxcnc-build> build #1873 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/1873 blamelist: Sebastian Kuzminsky <seb@highlab.com>, joseph calderon <calderon.joe@gmail.com>
[21:10:15] <seb_kuzminsky> sigh
[21:10:26] <linuxcnc-build> build #1201 of 1902.clang-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1902.clang-wheezy-rtai-i386/builds/1201 blamelist: Sebastian Kuzminsky <seb@highlab.com>, joseph calderon <calderon.joe@gmail.com>
[21:21:21] <skunkworks> zlog
[21:22:54] <linuxcnc-build> build #4061 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4061 blamelist: Sebastian Kuzminsky <seb@highlab.com>, joseph calderon <calderon.joe@gmail.com>
[21:45:16] <andypugh> I wonder what the problem is?
[21:45:40] <seb_kuzminsky> NAN not defined
[21:46:25] <andypugh> Oh
[21:47:07] <andypugh> That’s something the chiip itself does a lot (we use them at work)
[21:47:47] <andypugh> As in, the chip sends a float, and it uses NaN as an error