#linuxcnc-devel Logs

Feb 14 2018

04:17 AM jthornton- is now known as jthornton
10:13 AM seb_kuzminsky: https://www.youtube.com/watch?v=xYOXimZemeI
10:13 AM seb_kuzminsky: no word on which machine controller was used
12:33 PM pcw_mesa: Looked like a commercial router
12:33 PM pcw_mesa: I liked those no fasterner wood pieces
12:34 PM pcw_mesa: fastener even
01:08 PM KimK: Maybe they used LinuxCNC, he mentions LinuxCNC around 39:30 to 40:15 or so. (I didn't watch the whole thing, I just skipped thru it and and accidentally stumbled across that part.)
01:28 PM pcw_mesa: I must have missed that ( just noticed that the router did not look home built )
02:16 PM seb_kuzminsky: we have a router very similar to that one at the boulder hackspace, it's running linuxcnc of course
02:35 PM Chris_Morley: skunkworks: What boot settings etc did you set for your laptop? I have a t520 that works with the 7i92 for about a minute then kills the connection...
03:21 PM sliptonic: Hi all. I've been kind of leading the development of a CAM workbench for FreeCAD. FreeCAD is participating under the BRL-CAD umbrella for Google Summer of Code again this year.
03:21 PM sliptonic: I started chatting with one of the brlcad guys and it led to an idea. He suggested I chat with you guys as well.
03:22 PM sliptonic: We need a better tool library for the CAM workbench. We were thinking of proposing a GSoC project to create a standalone library that could be used by many projects. Something permissively licensed and perhaps ISO13399 compliant
03:23 PM sliptonic: I'm curious what your plans are around tool import/export management and what you think about joining forces to possibly mentor someone.
03:26 PM seb_kuzminsky: sliptonic! nice to see you here :-)
03:27 PM sliptonic: Hi seb_kuzminsky!
03:27 PM seb_kuzminsky: as you may know, the tool management in linuxcnc is pretty primitive
03:28 PM seb_kuzminsky: we store our tool table in a text file, which can be edited manually by the user (possibly via a custom format-imposing editor we have), or it can be modified via g-code at run-time
03:29 PM seb_kuzminsky: the tool file format closely matches our internal tool representation
03:29 PM seb_kuzminsky: brb
03:32 PM pcw_mesa: Chris_Morley: I know my cheapo ebay Dell E6420 works pretty wel with our Ethernet cards (I've had it up for a week or so)
03:33 PM pcw_mesa: just cant change the backlight brightness or change from wall to battery or vice-versa while running LinuxCNC
03:36 PM seb_kuzminsky: sliptonic: tool handling (both the tool file and our in-memory management) is an oft-maligned area of our software...
03:38 PM seb_kuzminsky: if we had a library to access tool information (from a file or a database or something), and a translator to convert to/from our internal tool representation, that might be workable
03:40 PM seb_kuzminsky: i think the grumpy old-timers machinists might be unhappy if we give up text-editor-accessible tool files
03:41 PM sliptonic: That's what I was thinking about too. I'd like something that could parse through manufacturer supplied tool data and extract what I need for building a visual representation and driving toolpath calculation.
03:41 PM sliptonic: The GOTM's might be happy if they could import the tool data directly from the manufacturers site
03:41 PM sliptonic: (though an internal editor will always be needed, I think)
03:42 PM seb_kuzminsky: yeah, a manual editor will probably be how 98+ % of our users edit the tool information
03:42 PM seb_kuzminsky: here's our current "friendly" tool editor gui: http://linuxcnc.org/docs/devel/html/gui/tooledit.html
03:43 PM seb_kuzminsky: (though I always use a text editor, because that's what i'm used to)
03:43 PM seb_kuzminsky: here's our current tool table format, which also represents what tool information linuxcnc cares about: http://linuxcnc.org/docs/devel/html/gcode/tool-compensation.html#sec:tool-table
03:43 PM sliptonic: Looks familiar. I wrote a basic importer from LinuxCNC to heekscad back in the day and again to FreeCAD Path.
03:43 PM seb_kuzminsky: cool
03:44 PM seb_kuzminsky: i've been daydreaming for a long time about having a feed & speed calculator integrated in the linuxcnc guis (like Axis)
03:45 PM sliptonic: I'd like to build one into Path as well.
03:45 PM seb_kuzminsky: do you see that kind of information as in-scope for this tool management library? or maybe the tool management library would just be an enabler for developing that kind of stuff
03:46 PM seb_kuzminsky: hmm, when i opened http://sliptonic.com/, chrome started running all my CPUs at 100%
03:47 PM sliptonic: I'm not sure. I've tried to get my head around ISO 13399 and failed (so far). My thought was to start with something that could read compliant data and then export it into other formats.
03:47 PM sliptonic: Hmm. Let me see if there's something going on there.
03:51 PM seb_kuzminsky: it worries me a bit that there's no link to the text of ISO 13399 on the wikipedia page (or at least i couldn't find it)
03:51 PM seb_kuzminsky: is it one of those standards that you have to have your employer pay hundreds of dollars to be allowed to read?
03:52 PM sliptonic: Nothing strange on the server. I'll look into it though. Doesn't affect any of the other sites.
03:52 PM sliptonic: Yes, it's an expensive standard.
03:52 PM sliptonic: sucks. But tool manufacturers seem to be adopting it.
03:56 PM seb_kuzminsky: bummer :-/
03:56 PM seb_kuzminsky: closed stuff like that is a step in the wrong direction, in my mind :-(
03:59 PM seb_kuzminsky: how do you intend to access the spec? gsoc won't pay for it, will they? and even if they did, it would not be licensed in a way where it could be shared, right?
04:03 PM sliptonic: I don't have those answers yet. My goal was to find out if there was enough interest to inquire further.
04:05 PM sliptonic: I know MT-Connect has done at least a little work here https://github.com/mtconnect/iso_133399 released under their own license. I was going to talk with them to figure out whether they're open to FOSS development and participation as well
04:07 PM seb_kuzminsky: hmm, they made up their own license, rather than use one of the standard open-source ones
04:07 PM * seb_kuzminsky tries to read LICENSE.TXT
04:08 PM seb_kuzminsky: "The term "you" and "your" as used in this Agreement includes you and any
04:08 PM seb_kuzminsky: other person or entity you that employs you"
04:10 PM Tom_L: the txt is $19
04:10 PM * sliptonic shudders
04:10 PM sliptonic: Tom_L: text of the standard? link?
04:10 PM Tom_L: https://webstore.ansi.org/FindStandards.aspx?SearchString=ISO+13399-1%2fAmd1%3a2010&SearchOption=0&PageNum=0&SearchTermsArray=null%7cISO+13399-1%2fAmd1%3a2010%7cnull
04:11 PM Tom_L: may not be the full thing
04:11 PM Tom_L: that may just be an amendment
04:13 PM seb_kuzminsky: ianal, but my read of the license on the MT Connect git repo tells me it's not open-source compatible
04:14 PM Tom_L: aparently the original done in 2006 is $232
04:15 PM seb_kuzminsky: specifically section 2.4 means we can't incorporate their work in ours
04:15 PM Tom_L: 2 corrections and 1 amendment since
04:18 PM sliptonic: As long as something truly open and permissive can developed around the standard, I'm willing to pursue collaboration and try to find a few bucks to get the standard if necessary. But I don't want to spend that effort on something closed or license incompatible with FreeCAD.
04:19 PM seb_kuzminsky: yeah, same here
04:20 PM seb_kuzminsky: in the end, it's about making useful open source software, if the standard helps with that then that's great, if it doesn't help then i don't have much interest in it
04:21 PM seb_kuzminsky: i'm open to collaboration with freecad and with the rest of the (loosely-connected) foss CAx community, independent of iso13399
04:22 PM sliptonic: Cool. I'll do a little more chatting around and try to get smarter. I might ping you back to help write up a GSoC proposal and/or help mentor if a student picks it up.
04:24 PM seb_kuzminsky: sounds good
04:25 PM seb_kuzminsky: and while i have your ear, thanks for your work on freecad, it's super exciting :-)
04:27 PM sliptonic: Thanks. 0.17 is coming out very soon, theoretically this month. I really want to start looking at lathe and 4th axis operations next.
04:28 PM seb_kuzminsky: groovy
04:28 PM seb_kuzminsky: some of the folks over in #debian-science are working on packaging 0.17 for sid
04:29 PM sliptonic: There will still be plenty broken. Assembly is still quite weak, but there's a lot of good stuff in 17.
04:30 PM seb_kuzminsky: i'm looking forward to it :-)
04:30 PM Tom_L: is this the same IchGucksLive is working on?
04:30 PM sliptonic: If you don't mind, try loading my site again. It never happened on firefox. I disabled a plugin and it's running normally for me in chrome now.
04:31 PM sliptonic: Tom_L: Yes. He's helped out some.
04:31 PM Tom_L: ok
05:07 PM Chris_Morley: pcw_mesa: in my case, the watch dog bites because ss0 doIt was not set - I paraphrase
05:08 PM KimK: seb_kuzminsky, sliptonic, Tom_L: (Hi, sliptonic, good to see you here.) The last time I was at my local library business/science/technology desk, I was asking about getting a look at one of those "fee" reports. They said there are some of them that they can get for "free", as part of some library group that they pay a fee to be in, or something. Next time I'm there, I'll ask them about getting a look at ISO13399 and see what they
05:08 PM KimK: say.
05:13 PM pcw_mesa: Chris_Morley: watchdog bites usually mean the latency has gotten to the 50 ms region
07:13 PM sliptonic: KimK: Awesome! Thanks.
09:02 PM Chris_Morley: pcw_mesa: ill run the latency test again and see what it shows - thanks
09:13 PM pcw_home: More valuable than a latency test is the read.tmax (since Ethernet latency is usually the culprit )
09:14 PM pcw_home: also if you have a Intel MAC on the host you need to turn off IRQ coalescing in the driver
09:15 PM pcw_home: ( this is easily verified by ping times )