#linuxcnc-devel | Logs for 2018-09-20

Back
[00:05:10] -!- Tom_itx has joined #linuxcnc-devel
[00:14:24] -!- Tom_itx has quit [Quit: Leaving]
[01:58:17] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #246: Thanks, @KurtJacobson, I was able to reproduce in master (commit 02ba5a1f).... 02https://github.com/LinuxCNC/linuxcnc/issues/246#issuecomment-423049528
[02:37:07] -!- abrotman14 has joined #linuxcnc-devel
[02:39:33] -!- abrotman14 has quit [K-Lined]
[02:47:58] -!- meka2 has joined #linuxcnc-devel
[02:51:16] -!- meka2 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
[02:54:22] -!- c-log has quit [Ping timeout: 272 seconds]
[02:55:54] -!- c-log has joined #linuxcnc-devel
[03:16:20] -!- rektide_ has joined #linuxcnc-devel
[03:20:28] -!- rektide_ has quit [Remote host closed the connection]
[03:30:08] -!- chibill0 has joined #linuxcnc-devel
[03:34:15] -!- chibill0 has quit [Remote host closed the connection]
[04:06:00] -!- rob_h has joined #linuxcnc-devel
[04:08:14] -!- fide has joined #linuxcnc-devel
[04:09:56] -!- fide has quit [Killed (Sigyn (Spam is off topic on freenode.))]
[04:11:13] -!- voyageur5 has joined #linuxcnc-devel
[04:11:52] -!- voyageur5 has quit [Remote host closed the connection]
[04:36:32] -!- podjackel has joined #linuxcnc-devel
[04:40:40] -!- podjackel has quit [Remote host closed the connection]
[05:03:13] -!- tgm488311 has joined #linuxcnc-devel
[05:06:39] -!- tgm488311 has quit [Remote host closed the connection]
[05:18:36] -!- Arrfab8 has joined #linuxcnc-devel
[05:20:17] -!- Arrfab8 has quit [Remote host closed the connection]
[05:42:06] -!- rob_h has quit [Ping timeout: 260 seconds]
[05:48:58] -!- Guest68402 has joined #linuxcnc-devel
[05:50:42] -!- Guest68402 has quit [Remote host closed the connection]
[05:52:39] -!- samathy20 has joined #linuxcnc-devel
[05:53:25] -!- hero100_ has joined #linuxcnc-devel
[05:54:09] -!- samathy20 has quit [Remote host closed the connection]
[05:55:22] -!- kusuriya19 has joined #linuxcnc-devel
[05:56:20] -!- kusuriya19 has quit [Remote host closed the connection]
[05:56:51] -!- hero100_ has quit [Remote host closed the connection]
[06:19:58] -!- insanitea has joined #linuxcnc-devel
[06:21:11] -!- insanitea has quit [Remote host closed the connection]
[07:15:03] -!- Hexafox[I] has joined #linuxcnc-devel
[07:18:23] -!- Hexafox[I] has quit [Remote host closed the connection]
[07:53:10] -!- spoonm23 has joined #linuxcnc-devel
[07:54:04] -!- spoonm23 has quit [Remote host closed the connection]
[07:57:37] -!- paolof20 has joined #linuxcnc-devel
[08:01:41] -!- paolof20 has quit [Remote host closed the connection]
[08:04:58] -!- rob_h has joined #linuxcnc-devel
[09:14:39] Jin|away is now known as Jin^eLD
[09:22:02] -!- Lorkki3 has joined #linuxcnc-devel
[09:24:20] -!- rob_h has quit [Ping timeout: 252 seconds]
[09:25:20] -!- Lorkki3 has quit [Remote host closed the connection]
[09:45:08] -!- TGCFabian has joined #linuxcnc-devel
[09:45:15] -!- TGCFabian has quit [Remote host closed the connection]
[10:35:22] -!- mpr21 has joined #linuxcnc-devel
[10:37:58] -!- mpr21 has quit [Remote host closed the connection]
[10:45:47] -!- pcw_home has quit [Remote host closed the connection]
[11:16:13] -!- xacktm7 has joined #linuxcnc-devel
[11:20:22] -!- xacktm7 has quit [Remote host closed the connection]
[11:41:13] -!- nsh15 has joined #linuxcnc-devel
[11:43:39] -!- jemurray has joined #linuxcnc-devel
[11:45:20] -!- nsh15 has quit [Remote host closed the connection]
[11:52:40] -!- jemurray has quit [Ping timeout: 246 seconds]
[11:55:14] -!- apmorton- has joined #linuxcnc-devel
[11:55:28] -!- apmorton- has quit [Remote host closed the connection]
[12:03:53] -!- RenatoCRON13 has joined #linuxcnc-devel
[12:04:39] -!- Roguish has joined #linuxcnc-devel
[12:04:54] -!- RenatoCRON13 has quit [Remote host closed the connection]
[12:18:20] -!- dngor11 has joined #linuxcnc-devel
[12:19:19] -!- dngor11 has quit [Remote host closed the connection]
[12:49:17] -!- pcw_home has joined #linuxcnc-devel
[13:04:00] -!- hustl4 has joined #linuxcnc-devel
[13:04:05] -!- hustl4 has quit [Remote host closed the connection]
[13:26:00] -!- wbs4 has joined #linuxcnc-devel
[13:29:23] -!- wbs4 has quit [Remote host closed the connection]
[13:30:55] -!- rob_h has joined #linuxcnc-devel
[13:32:22] <rene_dev_> andypugh how is multi spindle getting along?
[14:09:20] <andypugh> I haven’t really touched it since my email to the dev list
[14:09:52] <andypugh> Needs docs and shanges to runtests.
[14:09:56] <andypugh> (changes)
[14:10:35] <andypugh> And for a decision about whether 2.8 goes out soon, then I merge, or I merge now.
[14:13:12] <mozmck> andypugh: is it likely to break something else?
[14:13:25] <andypugh> Well, it shouldn’t.
[14:13:27] <mozmck> If not, I would say merge it now.
[14:13:33] -!- rmu has quit [Ping timeout: 252 seconds]
[14:14:02] <andypugh> It fails a lot of “runtests” now, but that is because of an an added index to the spindle commands.
[14:15:39] -!- rmu has joined #linuxcnc-devel
[14:16:04] <andypugh> I am busy tonight, but will look to get it merged by sunday evening.
[14:16:11] <mozmck> I see. is that index required?
[14:16:37] <mozmck> Or are the tests not expecting it and failing because it is there?
[14:16:39] <andypugh> Yes, it indicates in the commands which spindle is being used
[14:16:47] <andypugh> Yes, that.
[14:17:09] <mozmck> Ok, so if you only have one spindle you don't need the spindle index then.
[14:18:40] <andypugh> The falures are purely with the comparison between actual and predicted canon logs.
[14:19:34] <andypugh> Oh, I also need to modify the update-ini script and run the sample configs through it.
[14:21:27] <hazzy-m> andypugh: Does it add/change any of the python interface attributes? (I would assume some things need to be changed to tuples etc. to support values from multiple spindles)
[14:21:57] <andypugh> I confess that I have forgotten.
[14:22:08] <andypugh> I would expect so.
[14:22:25] <hazzy-m> ok 🙂
[14:22:27] <mozmck> I kind of hate to push off state-tags, external-offsets, and reverse-run, but perhaps we can release and then merge those right away and work on a new release with those features.
[14:23:13] <mozmck> (as well as others I didn't mention...)
[14:25:53] -!- rmu has quit [Ping timeout: 245 seconds]
[14:27:48] -!- ve7it has joined #linuxcnc-devel
[14:28:01] <rene_dev_> none of those features should break anything, so might as well be merged ;D
[14:28:11] <rene_dev_> unless they are used, that is.
[14:28:16] <mozmck> ya think? ;-)
[14:28:42] <hazzy-m> state-tags being a possible exception to that
[14:28:48] <mozmck> That's like saying, "that food is non-fattening if you don't eat it"
[14:28:49] <rene_dev_> who is in charge of releasing 2.8?
[14:28:56] <rene_dev_> yeah^^
[14:29:16] <mozmck> technically myself, but I have been very busy and slow about doing anything about it.
[14:29:29] <rene_dev_> Honestly I dont really care, as I use master anyway. but would be nice to have, for normal users
[14:29:46] <rene_dev_> none of my machines work with 2.7
[14:29:50] <hazzy-m> I suspect releasing 2.8 will bring some life and interest back to the project, its been kinda stagnant for a while, without any significant improvements being released
[14:30:25] <mozmck> Probably true.
[14:30:42] <rene_dev_> agree
[14:30:56] <rene_dev_> and it is really stable as it is right now
[14:31:49] <hazzy-m> I think it is more stable than 2.7, lol
[14:32:10] <mozmck> So I think if we merge andy's spindle stuff, and any other bug fixes like you suggested rene-dev, then we should release as soon as possible now.
[14:32:16] <pcw_mesa> Ive had 2.8 and Preempt-RT up for months with Axis
[14:32:49] <pcw_mesa> not running a wide range of gcode however
[14:32:55] <hazzy-m> and when we do release 2.8 we will have a dev branch again 😃
[14:33:13] <pcw_mesa> and > 1 month on a RPI3
[14:34:40] <mozmck> So far I have not had time to actually run 2.8 on a machine myself, but 2.7 works well for me :-)
[14:35:15] <andypugh> <shuffles feet>
[14:35:37] <andypugh> I might have forgotten to convert the Python interface to multispindle
[14:35:43] * hazzy-m has never run 2.7 on a real machine
[14:36:14] <andypugh> But then the Python interface isn’t very good for spindles. I can’t actually see how you set a spindle speed….
[14:36:37] <andypugh> I think you just have to send SPINDLE_INCREASE rpm / 100 times...
[14:36:55] <hazzy-m> You can't :(
[14:37:07] <hazzy-m> it is even hard to get the commanded spindle speed
[14:37:21] <hazzy-m> have to do stat.settings[1] * stat.spindlerate
[14:37:33] <andypugh> c.MDI(“M3 S1000 $2”) ought to work
[14:37:48] <hazzy-m> which is not intuitive
[14:38:41] <hazzy-m> sure, but there are commands to turn the spindle on and off in manual mode
[14:39:16] <andypugh> Yes, I need to add the Python interface to the list. Looks like I have a busy Sunday ahead :-)
[14:39:29] <hazzy-m> you can do cmd.spindle(linuxcnc.SPINDLE_FORWARD, speed)
[14:39:52] <hazzy-m> (I just added that to the docs, took me for ever to figure that out, lol)
[14:41:08] <hazzy-m> So I would assume with multi spindle you would so something like spindle(spindle_num, linuxcnc.SPINDLE_FORWARD, speed)
[14:41:46] <mozmck> forever? it was about 3 minutes 33 seconds between your "You can't" and telling us how!
[14:42:18] <mozmck> 2:33
[14:42:36] <mozmck> :-)
[14:48:18] -!- rob_h has quit [Quit: Leaving]
[14:48:33] <andypugh> Yes, looks like a simple fix in emcmodule.cc
[14:48:45] <andypugh> (the other end already knows what to do)
[14:50:09] <hazzy-m> mozmck: What I meant is you can't set the requested spindle speed without actually starting the spindle, (no equivalent to the S word). The `speed` argument is optional in cmd.spindle, so it would make since if there was a way to set it, in stead it seems to always default to 1rpm
[14:51:42] <hazzy-m> It took me about 12 hr to even figure out that I could pass a speed argument to cmd.spindle, as it was not mentioned in the docs anywhere
[14:52:36] <hazzy-m> probably the best thing to do there is make the speed parameter required ...
[14:54:57] <seb_kuzminsky> i'm not a very active developer in the linuxcnc world these days, and I sure appreciate you all picking up the gauntlet
[14:55:34] <seb_kuzminsky> i will be happy to help with release mechanics, git stuff, and buildbot stuff, in a supporting role, while y'all take the lead
[14:56:09] <seb_kuzminsky> i specifically want to comment on hazzy-m's statement that "when we do release 2.8 we will have a dev branch again":
[14:57:15] <seb_kuzminsky> i recommend making the 'stable/2.8' branch or 'stable/3' or whatever you want to call it early in the release process, as it signals the user base that the stable release is nearing, and encourages everyone to increase the dilligence of our collective testing and bug reporting
[14:57:34] <seb_kuzminsky> as soon as the stable release branch is created, master becomes the "dev" branch again
[14:58:20] <seb_kuzminsky> *however* i know that lots of folks run master rather than the stable branches, so I encourage you to not break master; do scary development work in feature branches and merge them into master when they're ready
[15:05:16] <rene_dev_> hazzy-m what UI stuff are you working on at the moment?
[15:06:29] <mozmck> seb_kuzminsky: yeah, good idea. I think it is kinda working like that anyhow with people using feature branches.
[15:07:36] <rene_dev_> what then usually happens, is that once it works it stays there forever....
[15:07:42] <hazzy-m> seb_kuzminsky: I completely concur with that. I think we should feel a little more relaxed about merging not quite polished features into master than we have been (to expose them to a wider range of testers), but also strive to keep master as reliable as possible. After all, this is a machine control, and bad things can happen
[15:07:56] <seb_kuzminsky> mozmck: i agree, i just want to re-state my support for that development model
[15:08:07] <seb_kuzminsky> hazzy-m: +1
[15:08:23] <mozmck> +2
[15:08:45] <hazzy-m> rene_dev_: QtPyVCP, a branch of CMorley's QtVCP: https://gitlab.com
[15:09:15] <rene_dev_> so you will make a new hazzy version based on that?
[15:09:30] <rene_dev_> how is that getting along? especially the backplot...
[15:10:03] <seb_kuzminsky> there was been a general lack of energy/attention from the "old boys club" (jepler, cradek, and me, pretty much), so stuff has been languishing in feature branches for a long time, from lack of volunteer time to test and integrate stuff
[15:10:48] <seb_kuzminsky> so again, i'm pleased and hopeful that a new generation of energetic & motivated developers will step up to carry the torch for a while as us old-timers drift away
[15:12:32] <hazzy-m> rene_dev_: Yes, hazzy3 🙂 It is coming very well, home to be able to run a machine with it very soon. I haven't done any more on the backplot, but plan to once some of the other things are out of the way
[15:12:58] <rene_dev_> cool :)
[15:13:25] <rene_dev_> seb_kuzminsky yeah, I know what its like when you work on a project for too long :D
[15:14:11] <rene_dev_> do you know who keeps track of the pathpilot changes, and puts them back into linuxcnc? do you know if they have a public git repo of their changes?
[15:14:14] <seb_kuzminsky> for me, it's more that i want to get deeper into *using* linuxcnc for other projects, rather than having linuxcnc *be* my project all the time
[15:14:36] <rene_dev_> haha, I feel the same with stmbl sometimes :D
[15:14:59] <seb_kuzminsky> rene_dev_: pathpilot does not have a public git repo, as of last time i checked, but they're legally and morally obligated to provide the source code to their fork of linuxcnc when asked
[15:15:01] <hazzy-m> rene_dev_: Lcvette is working on a pathpilotish interface built with QtPyVCP: https://forum.linuxcnc.org
[15:15:26] <seb_kuzminsky> so you can email them and they *should* send you a CD with their code, possibly charging you for shipping
[15:15:30] <rene_dev_> none of my machines have a real clean cabinet, with a stmbl with case
[15:16:00] <rene_dev_> not like this: https://imgur.com
[15:16:15] <seb_kuzminsky> i think zultron and rob ellenberg have occasionally tried to offer PRs of some of pathpilot's changes, and received little or no feedback from the linuxcnc dev community
[15:16:48] <rene_dev_> Im not even talking about the gui, but from the linuxcnc. apparently they fixed some things.
[15:16:58] <rene_dev_> and their stuff should run stable...
[15:20:28] -!- syme8 has joined #linuxcnc-devel
[15:20:57] -!- syme8 has quit [Remote host closed the connection]
[15:29:52] -!- rmu has joined #linuxcnc-devel
[16:14:09] -!- Guest40424 has joined #linuxcnc-devel
[16:16:00] -!- SergeyLukjanov28 has joined #linuxcnc-devel
[16:17:35] -!- Guest40424 has quit [Remote host closed the connection]
[16:18:36] -!- SergeyLukjanov28 has quit [Remote host closed the connection]
[16:53:54] -!- rmu has quit [Ping timeout: 252 seconds]
[17:10:59] -!- rmu has joined #linuxcnc-devel
[17:19:13] -!- rmu has quit [Ping timeout: 245 seconds]
[17:42:00] -!- rmu has joined #linuxcnc-devel
[17:42:43] -!- uncleowen23 has joined #linuxcnc-devel
[17:43:38] -!- uncleowen23 has quit [Remote host closed the connection]
[17:44:43] -!- hazzy has quit [Remote host closed the connection]
[17:45:03] -!- hazzy has joined #linuxcnc-devel
[18:10:17] -!- andypugh has quit [Quit: andypugh]
[18:38:27] Jin^eLD is now known as Jin|away
[19:04:25] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[19:17:01] -!- rmu has quit [Ping timeout: 260 seconds]
[19:18:14] -!- rmu has joined #linuxcnc-devel
[19:33:21] -!- njh has quit [Ping timeout: 260 seconds]
[19:38:31] -!- njh has joined #linuxcnc-devel
[19:57:57] -!- otti4 has joined #linuxcnc-devel
[19:59:32] -!- otti4 has quit [Remote host closed the connection]
[20:03:27] -!- njh has quit [Ping timeout: 252 seconds]
[20:06:45] -!- rmu has quit [Ping timeout: 252 seconds]
[20:10:42] -!- njh has joined #linuxcnc-devel
[20:23:51] -!- rmu has joined #linuxcnc-devel
[21:07:07] -!- gworku6 has joined #linuxcnc-devel
[21:10:22] -!- gworku6 has quit [Remote host closed the connection]
[21:26:22] -!- jcallen9 has joined #linuxcnc-devel
[21:27:16] -!- jcallen9 has quit [Remote host closed the connection]
[21:41:33] -!- memfrob has joined #linuxcnc-devel
[21:42:47] <memfrob> Hi all, scripts/rtapi.conf.in says "DO NOT EDIT THIS FILE" but RTAI 4 is missing from there
[21:43:49] <memfrob> I believe I tried this though and it didn't work: http://dpaste.com
[21:45:09] <memfrob> It's a very fragile file and was looking for suggestions.
[21:46:46] -!- Tom_itx has joined #linuxcnc-devel
[21:46:53] -!- Lindrian15 has joined #linuxcnc-devel
[21:46:59] -!- Lindrian15 has quit [Remote host closed the connection]
[21:53:05] -!- Tom_itx has quit [Quit: Leaving]
[22:14:51] <jepler> looks like the comment in that file is a lie
[22:50:18] <memfrob> I'll ignore it then, thanks! Also it seems that || doesn't work with that.
[22:50:23] <memfrob> 6+.0+6
[23:12:04] -!- andyrtr6 has joined #linuxcnc-devel
[23:14:39] -!- andyrtr6 has quit [Remote host closed the connection]
[23:20:03] -!- grossing6 has joined #linuxcnc-devel
[23:22:34] -!- grossing6 has quit [Remote host closed the connection]