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

Back
[00:41:47] <CMorley> Andypugh: pncconf used spindle_9 because it used an axis variable (for PID info) 0 -8 were axes, 9 ended up being the spindle. It was a programming short cut that never got cleaned up
[01:06:56] -!- c-log has quit [Ping timeout: 272 seconds]
[01:09:07] -!- c-log has joined #linuxcnc-devel
[01:22:27] -!- c-log has quit [Ping timeout: 240 seconds]
[01:23:56] -!- c-log has joined #linuxcnc-devel
[02:16:39] -!- Kris14 has joined #linuxcnc-devel
[02:23:34] -!- Kris14 has quit [Ping timeout: 240 seconds]
[03:21:47] -!- selroc has joined #linuxcnc-devel
[03:45:12] -!- selroc has quit [Quit: Leaving]
[03:49:22] -!- rob_h has joined #linuxcnc-devel
[04:54:08] -!- When has joined #linuxcnc-devel
[04:57:29] -!- When has quit [Read error: Connection reset by peer]
[05:23:40] -!- rob_h has quit [Ping timeout: 246 seconds]
[06:04:21] Jin|away is now known as Jin^eLD
[07:19:28] -!- selroc has joined #linuxcnc-devel
[07:21:55] -!- selroc has quit [Client Quit]
[08:26:46] -!- rob_h has joined #linuxcnc-devel
[08:38:08] -!- Jusii has joined #linuxcnc-devel
[08:38:52] -!- Jusii has quit [Remote host closed the connection]
[09:13:32] -!- grinsekatze22 has joined #linuxcnc-devel
[09:13:44] -!- tmesis17 has joined #linuxcnc-devel
[09:14:14] -!- grinsekatze22 has quit [Remote host closed the connection]
[09:16:38] -!- tmesis17 has quit [Remote host closed the connection]
[09:29:08] -!- choco20 has joined #linuxcnc-devel
[09:30:31] -!- Pinchiukas14 has joined #linuxcnc-devel
[09:32:01] -!- choco20 has quit [Remote host closed the connection]
[09:35:26] -!- plunden5 has joined #linuxcnc-devel
[09:36:08] -!- plunden5 has quit [Remote host closed the connection]
[09:38:23] -!- Pinchiukas14 has quit [Ping timeout: 245 seconds]
[09:46:00] -!- rob_h has quit [Ping timeout: 252 seconds]
[10:37:27] <hazzy-m> CMorley: Ah, that makes sense!
[10:38:10] -!- feliks5 has joined #linuxcnc-devel
[10:41:00] -!- feliks5 has quit [Remote host closed the connection]
[10:47:31] <hazzy-m> andypugh: statetags also seems like something that might should be added to the list of things to discuss merging ...
[11:00:49] -!- Roguish has joined #linuxcnc-devel
[11:08:53] <cradek> last I knew, zultron had some statetags fixes he was intending to share
[11:16:29] <hazzy-m> yes, he said the new fixes are in PP, but doesn't look like he has added them to the statetags branch
[11:17:12] <cradek> I think our statetags branch is currently fairly broken
[11:17:21] <hazzy-m> there are multiple statetags branches, but they all seem pretty stale, are there any more recent ones?
[11:17:44] <hazzy-m> Yes, I tried building it a few month ago, it did not go well :)
[11:17:46] <cradek> I don't think so. it's been waiting for attention for a long time.
[11:18:01] <cradek> well as I remember, it builds and runs, but it's got problems
[11:18:13] <cradek> he and I worked on it together at ... somewhere we were, it's been years
[11:19:05] <pcw_home> I think PP has also got some TP patches from Rob that fix some uncommon arc/line transition pauses
[11:19:44] <seb_kuzm1nsky> https://github.com
[11:21:01] <pcw_home> Oh ok so its fixed?
[11:21:51] <hazzy-m> Excellent!!
[11:22:01] <seb_kuzm1nsky> it's not fixed
[11:22:05] seb_kuzm1nsky is now known as seb_kuzminsky
[11:22:45] <seb_kuzminsky> rob told me off-list this summer that it needs work and that he would ping me when he fixed it, but i haven't heard from him since
[11:30:05] <jepler> php update and forum reboot coming up
[13:22:42] <hazzy-m> thank you jepler
[13:24:01] <hazzy-m> what does `linuxcnc.command.set_feed_hold` do? It does not seems to do anything, and the docs aren't very enlightening as to what it is supposed to do
[13:25:33] <seb_kuzminsky> hazzy-m: i see in emcmodule.cc that it sends the EMC_TRAJ_SET_FH_ENABLE command to Task
[13:33:31] <hazzy-m> seb_kuzminsky: ah, so it set a flag to enable feedhold
[13:33:31] <hazzy-m> How would one send the feedhold command, and is it different than EMC_TASK_PLAN_PAUSE?
[13:38:03] <Jin^eLD> what is the policy on supporting new machines? should I try to clean up and submit my gearshifting comp for the mh400e mill? or should I just leave it in my github and be done with it? both is OK to me, just want to know what is preferrable to you guys :)
[13:38:05] <seb_kuzminsky> good question! I don't know off the top of my head, i'd have to trace both commands through Task to see how they differ
[13:38:57] <seb_kuzminsky> Jin^eLD: if you've written a generic component that would be useful to other people, i'd like to include that in linuxcnc
[13:39:49] <Jin^eLD> seb_kuzminsky: well thats the question.. it would only be useful to people who own this specific model...
[13:40:23] <hazzy-m> seb_kuzminsky: Thank you! I was just curious. I have been trying to trace them, but unfortunately don't know enough about what I am looking at :(
[13:40:32] <Jin^eLD> I had a brief talk with miss0r who has an MH500 and already there the gearbox seems to be different
[13:40:43] <Jin^eLD> so its probably really just MH400E specific
[13:41:03] <Jin^eLD> "probably really" lol :)
[13:41:37] <seb_kuzminsky> hazzy-m: the structure is this: UIs send NML commands to Task (which includes the Interpreter), Task handles some of them and sends some of them to Motion (which is the realtime motion controller) and sends some of them to IO (which is the non-realtime IO handler)
[13:42:05] <seb_kuzminsky> this diagram tries to capture & convey this information: http://linuxcnc.org
[13:42:30] <seb_kuzminsky> that diagram predates HAL, but is otherwise accurate
[13:43:12] <seb_kuzminsky> so you'd look in Task to see what it does with those commands, and for stuff that goes to Motion, look there to see what *it* does
[13:43:41] <hazzy-m> Fantastic! I'll study it, having an idea what it does should make the code make more sense
[13:43:49] <seb_kuzminsky> :-)
[13:45:16] <seb_kuzminsky> Task is pretty complicated on the inside, so maybe get a cup of coffee and put on your seatbelt before looking in there
[13:45:43] <JT-Shop> hazzy-m: if you figure something out that is not clear in the documents let me know what you figure out.
[13:46:20] <hazzy-m> I did not realize everything from the GUI went thru task
[13:46:23] <JT-Shop> I've already updated the set_feed_hold to add the work enable...
[13:46:55] <hazzy-m> JT-Shop: Thank you! I was just getting ready to update that myself
[13:47:01] <hazzy-m> will do
[13:47:11] <seb_kuzminsky> hazzy-m: Task is very much in control of Motion. the GUIs just ask it nicely
[13:47:22] <seb_kuzminsky> except for HAL, which bypasses Task
[13:47:28] <seb_kuzminsky> bbl
[13:47:45] -!- alex_joni has joined #linuxcnc-devel
[13:47:52] -!- alex_joni has quit [Changing host]
[13:47:52] -!- alex_joni has joined #linuxcnc-devel
[13:47:52] -!- mode/#linuxcnc-devel [+v alex_joni] by ChanServ
[13:49:09] <pcw_home> Any ideas on the "right way" to include data for motion synchronized "painting" applications? (laser,inkjet etc)
[13:49:53] <alex_joni> with stock code?
[13:51:34] <JT-Shop> hi alex_joni
[13:52:11] <alex_joni> hey JT
[13:54:57] <pcw_home> I guess halstreamer lots of hal magic and gcode would work but I just wondered if there was any kind of standard way to do this
[14:01:13] <alex_joni> there was a fork a while ago
[14:01:32] <alex_joni> but I have no idea where or in what state it is now..
[14:01:55] <alex_joni> it was for laser etching/marking
[14:02:46] <alex_joni> pcw_home: maybe this helps? http://wiki.linuxcnc.org
[14:04:12] <alex_joni> this does XY for motion, W for table height, and laser on/off using Z
[14:06:49] <hazzy-m> pcw_home: This is interesting, but probably not what you are looking for: https://github.com
[14:20:13] -!- ve7it has joined #linuxcnc-devel
[14:25:29] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jethornton pushed 1 new commit to 062.7: 02https://github.com/LinuxCNC/linuxcnc/commit/382e52ba882ffe6269383ff8fe012a9310e3f436
[14:25:29] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/062.7 14382e52b 15jethornton: Docs: update what set_feed_hold does...
[14:26:38] <pcw_home> Thanks, Ill take a look
[14:28:15] -!- micges has joined #linuxcnc-devel
[14:28:53] -!- micges has quit [Client Quit]
[14:29:54] -!- micges has joined #linuxcnc-devel
[14:46:04] -!- rob_h has joined #linuxcnc-devel
[16:32:27] -!- micges has quit [Quit: Leaving]
[16:39:14] -!- drobbins26 has joined #linuxcnc-devel
[16:44:05] -!- drobbins26 has quit [Remote host closed the connection]
[17:29:18] <jepler> with "even" the linux kernel adopting a Code of Conduct, I hope the LinuxCNC project will consider it. It is becoming a standard expectation of Free software projects.
[17:39:07] Jin^eLD is now known as Jin|away
[18:05:21] -!- DrRetro25 has joined #linuxcnc-devel
[18:10:05] -!- DrRetro25 has quit [Remote host closed the connection]
[18:19:29] -!- jakmodii3 has joined #linuxcnc-devel
[18:22:23] -!- jakmodii3 has quit [Remote host closed the connection]
[19:09:06] <seb_kuzminsky> a code of conduct might have avoided some historical unpleasantness
[19:09:55] <seb_kuzminsky> pcw_home: my naive first try would be a gcode file full of alternating m68 and g1
[19:35:57] -!- ve7it has quit [Remote host closed the connection]
[19:46:42] -!- ve7it has joined #linuxcnc-devel
[20:03:00] <hazzy> and on a somewhat similar note, editorconfig files seem to be becoming quite popular...
[20:03:02] <hazzy> https://editorconfig.org
[20:36:26] -!- Tom_shop has joined #linuxcnc-devel
[20:36:34] -!- Tom_shop has quit [Client Quit]
[20:43:23] -!- rob_h has quit [Ping timeout: 245 seconds]
[20:55:48] -!- Tom_shop has joined #linuxcnc-devel
[20:57:11] -!- Tom_itx has joined #linuxcnc-devel
[20:57:23] -!- Tom_itx has quit [Client Quit]
[20:57:42] -!- Tom_shop has quit [Client Quit]
[21:38:46] -!- Tom_shop has joined #linuxcnc-devel
[21:39:04] -!- Tom_shop has quit [Client Quit]
[23:22:15] -!- georgyo has joined #linuxcnc-devel
[23:22:39] georgyo is now known as Guest32480
[23:27:21] -!- Guest32480 has quit [Remote host closed the connection]
[23:48:47] -!- ve7it has quit [Remote host closed the connection]