Back
[00:02:47] -!- [1]hdokes has quit [Read error: Connection reset by peer]
[00:04:05] <mhaberler> we need to factor the UI out and rewrite this as plain ngc calls; too many moving parts
[00:29:09] -!- syyl__ has quit [Quit: Leaving]
[00:44:34] -!- krusty_ar_ has quit [Ping timeout: 256 seconds]
[00:52:16] -!- PCW has quit [Remote host closed the connection]
[00:52:52] -!- GammaX-Shop has quit [Ping timeout: 252 seconds]
[00:57:54] -!- thesisb has quit [Quit: Leaving...]
[01:11:04] -!- cpresser has quit [Ping timeout: 276 seconds]
[01:15:02] -!- zlog has quit [Remote host closed the connection]
[01:15:04] -!- Tom_itx has quit []
[01:15:19] -!- henrikl has quit [Quit: henrikl]
[01:19:34] -!- sumpfralle1 has quit [Ping timeout: 246 seconds]
[01:19:44] -!- gmag has quit [Quit: Enough small talk...]
[01:33:36] -!- mhaberler has quit [Quit: mhaberler]
[01:35:36] -!- jfire1 has quit [Quit: Leaving.]
[01:41:14] -!- hashfail_ has quit [Ping timeout: 256 seconds]
[01:44:10] -!- tmcw has quit [Remote host closed the connection]
[02:06:43] <seb_kuzminsky> andypugh: that sounds like a bug that was reported on the forum a while back
[02:08:00] <seb_kuzminsky> http://www.linuxcnc.org/index.php/english/forum/40-subroutines-and-ngcgui/26290-subroutine-stops-without-warning
[02:09:50] <seb_kuzminsky> i tweaked the OP's config until it ran for me:
http://git.highlab.com/?p=emc2.git;a=log;h=refs/heads/2.5.1-halui-probe-mdi
[02:09:58] <seb_kuzminsky> but i couldn't repro the probelm
[02:13:32] -!- tandoori has quit [Read error: Connection reset by peer]
[02:31:02] -!- tandoori has quit [Read error: Connection reset by peer]
[02:32:03] -!- toxx has quit [Remote host closed the connection]
[02:32:34] -!- fiesh has quit [Ping timeout: 245 seconds]
[03:09:04] -!- jfire has quit [Quit: Leaving.]
[03:10:08] -!- FinboySlick has quit [Quit: Leaving.]
[03:13:27] -!- tandoori has quit [Read error: Connection reset by peer]
[03:14:23] -!- tjb1 has quit [Ping timeout: 252 seconds]
[03:14:26] tjb1_ is now known as tjb1
[03:18:08] -!- PetefromTn has quit [Ping timeout: 256 seconds]
[03:19:56] <KGB-linuxcnc> 03micges 05master 60ad92d 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.c * hostmot2: fix compilation warning
[03:19:56] <KGB-linuxcnc> 03chris 05master 1860a4f 06linuxcnc 10docs/ 10html/gcode.html 10src/gcode/o-code.txt * Document o-repeat in the quickref
[03:19:58] <KGB-linuxcnc> 03tissf 05master 3eb5f26 06linuxcnc 10docs/ 10html/gcode_fr.html 10src/gcode/o-code_fr.txt * French doc. update to follow Chris: Document o-repeat in the quickref
[03:20:06] <KGB-linuxcnc> 03chrisinnanaimo 05master b32d2ff 06linuxcnc 10src/emc/usr_intf/pncconf/pncconf.py * pncconf -fix default PDM rate to 6000000
[03:20:12] <KGB-linuxcnc> 03jthornton 05master 80e497d 06linuxcnc 10docs/src/lathe/lathe-user.txt * Docs: update spindle section to include feed per rev
[03:20:19] <KGB-linuxcnc> 03tissf 05master 123d91d 06linuxcnc 10docs/ 10html/gcode_fr.html 10src/gcode/gcode_fr.txt 10src/hal/pyvcp_examples_fr.txt 10src/lathe/lathe-user_fr.txt * French doc. update to follow John: update spindle section
[03:20:29] <KGB-linuxcnc> 03tissf 05master de3853e 06linuxcnc 10docs/ 10src/gcode/gcode_fr.txt 10src/lathe/lathe-user_fr.txt * French doc. update - Sentences more understandable.
[03:20:35] <KGB-linuxcnc> 03tissf 05master d71388c 06linuxcnc 10docs/src/hal/pyvcp_fr.txt * French doc. update - Consistency between image and code
[03:20:41] <KGB-linuxcnc> 03tissf 05master 63292dc 06linuxcnc 10docs/src/hal/pyvcp_fr.txt * French doc. update - fix missing example code
[03:20:48] <KGB-linuxcnc> 03tissf 05master a1baaaf 06linuxcnc 10docs/src/hal/pyvcp_fr.txt * French doc. update - fix typo
[03:20:53] <KGB-linuxcnc> 03seb 05master c75bd6a 06linuxcnc 10docs/src/hal/comp.txt * docs: clarify comp's 'option userinit yes'
[03:21:00] <KGB-linuxcnc> 03seb 05master c310c42 06linuxcnc 10src/hal/utils/comp.g * comp: warn if the user sets userinit but not userspace
[03:21:06] <KGB-linuxcnc> 03seb 05master 2edc654 06linuxcnc 10src/hal/utils/comp.g * comp: fix a couple of syntax errors when using userinit
[03:21:12] <KGB-linuxcnc> 03seb 05master 9e53f9f 06linuxcnc 10src/hal/components/bldc.comp * bldc: remove unused option userinit
[03:21:18] <KGB-linuxcnc> 03seb 05master 3758720 06linuxcnc 10(5 files in 5 dirs) * Merge branch 'v2.5_branch'
[03:21:24] <KGB-linuxcnc> 03seb 05v2.5_branch c75bd6a 06linuxcnc 10docs/src/hal/comp.txt * docs: clarify comp's 'option userinit yes'
[03:21:30] <KGB-linuxcnc> 03seb 05v2.5_branch c310c42 06linuxcnc 10src/hal/utils/comp.g * comp: warn if the user sets userinit but not userspace
[03:21:37] <KGB-linuxcnc> 03seb 05v2.5_branch 2edc654 06linuxcnc 10src/hal/utils/comp.g * comp: fix a couple of syntax errors when using userinit
[03:21:41] -!- tjb1 has quit [Ping timeout: 248 seconds]
[03:21:43] <KGB-linuxcnc> 03seb 05v2.5_branch 9e53f9f 06linuxcnc 10src/hal/components/bldc.comp * bldc: remove unused option userinit
[03:24:55] -!- tjb1_ has quit [Ping timeout: 256 seconds]
[03:26:01] -!- PetefromTn has quit [Client Quit]
[03:27:29] -!- PetefromTn_ has quit [Ping timeout: 248 seconds]
[03:32:19] -!- Felix29 [Felix29!Felix@c-71-193-105-131.hsd1.in.comcast.net] has joined #linuxcnc-devel
[03:38:49] -!- firephoto has quit [Ping timeout: 245 seconds]
[04:02:19] -!- PetefromTn has quit [Ping timeout: 246 seconds]
[04:08:33] -!- tjb1 has quit [Ping timeout: 256 seconds]
[04:14:39] -!- tjb1 has quit [Ping timeout: 245 seconds]
[04:25:09] -!- PetefromTn_ has quit [Ping timeout: 248 seconds]
[04:39:10] s1dev is now known as s1dev|away
[04:44:38] <KGB-linuxcnc> 03chrisinnanaimo 05master 0e02c01 06linuxcnc 10configs/sim/gmoccapy/gmoccapy_handler.py 10src/emc/usr_intf/gscreen/gscreen.py * gscreen -fix run away jogging with keyboard controls
[04:46:25] -!- Loetmichel has quit [Ping timeout: 246 seconds]
[04:52:01] -!- mrsun__ has quit [Ping timeout: 246 seconds]
[04:53:20] -!- mhaberler [mhaberler!~mhaberler@213-33-10-109.adsl.highway.telekom.at] has joined #linuxcnc-devel
[05:00:33] -!- fiesh has quit [*.net *.split]
[05:00:34] -!- JT-Shop has quit [*.net *.split]
[05:00:34] -!- skroon has quit [*.net *.split]
[05:00:34] -!- t12 has quit [*.net *.split]
[05:00:34] -!- Connor has quit [*.net *.split]
[05:00:34] -!- carper64_lb_ has quit [*.net *.split]
[05:00:34] -!- shurshur has quit [*.net *.split]
[05:00:35] -!- logger[mah] has quit [*.net *.split]
[05:00:35] -!- netxshare has quit [*.net *.split]
[05:00:35] -!- Celelibi has quit [*.net *.split]
[05:00:35] -!- nots_ has quit [*.net *.split]
[05:00:35] -!- jleh has quit [*.net *.split]
[05:00:52] -!- _Fox_Muldr has quit [Read error: Operation timed out]
[05:03:00] -!- PetefromTn has quit [Remote host closed the connection]
[05:03:27] -!- JT-Shop [JT-Shop!~John@99.198.67.11] has joined #linuxcnc-devel
[05:03:27] -!- carper64_lb_ [carper64_lb_!~quassel@94.15.49.82] has joined #linuxcnc-devel
[05:03:27] -!- logger[mah] [logger[mah]!~loggermah@mah2.mah.priv.at] has joined #linuxcnc-devel
[05:04:12] -!- Connor has quit [Read error: No route to host]
[05:07:14] -!- ve7it has quit [Remote host closed the connection]
[05:10:24] -!- PetefromTn has quit [Remote host closed the connection]
[05:14:05] -!- Felix29 has quit []
[05:17:28] Cylly is now known as Loetmichel
[05:33:40] Rob__ is now known as GammaX-laptop
[05:38:55] -!- maximilian_h has quit [Quit: Leaving.]
[05:39:01] -!- maximilian_h [maximilian_h!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[05:52:27] -!- mhaberler has quit [Quit: mhaberler]
[06:19:18] -!- Nick001 has quit [Ping timeout: 245 seconds]
[06:22:24] -!- GammaX has quit []
[06:24:12] -!- cmorley has quit [Quit: Leaving.]
[06:26:27] -!- cmorley [cmorley!~chris@S010600c09fc019c2.no.shawcable.net] has joined #linuxcnc-devel
[06:28:55] -!- steves_logging has quit [Ping timeout: 276 seconds]
[06:31:35] -!- jfire has quit [Quit: Leaving.]
[06:44:11] -!- stsydow has quit [Remote host closed the connection]
[07:27:10] -!- DJ9DJ has quit [Quit: bbl]
[07:42:20] -!- emel has quit [Excess Flood]
[07:42:49] -!- Andy1978 has quit [Read error: Connection reset by peer]
[07:47:49] -!- AndChat|159600 has quit [Read error: Connection reset by peer]
[07:51:16] -!- GammaX-laptop has quit [Ping timeout: 256 seconds]
[07:51:16] -!- gammax-Laptop1 has quit [Ping timeout: 256 seconds]
[07:52:18] -!- Andy1978 has quit [Client Quit]
[07:52:26] -!- rob_h [rob_h!~rob_h@94.4.80.67] has joined #linuxcnc-devel
[07:55:53] -!- maximilian_h has quit [Quit: Leaving.]
[07:55:58] -!- maximilian_h1 [maximilian_h1!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[07:58:15] -!- psha[work] [psha[work]!~psha@195.135.238.205] has joined #linuxcnc-devel
[08:01:42] -!- holst has quit [Quit: Leaving]
[08:10:28] -!- b_b has quit [Changing host]
[08:15:31] -!- skroon has quit [Ping timeout: 264 seconds]
[08:17:47] -!- vvompy has quit [Ping timeout: 252 seconds]
[08:29:04] emel is now known as mle
[09:12:21] -!- stsydow has quit [Remote host closed the connection]
[09:55:39] -!- adb [adb!~IonMoldom@178.211.237.94] has joined #linuxcnc-devel
[10:07:39] -!- lagmonster has quit [*.net *.split]
[10:07:39] -!- coco_ has quit [*.net *.split]
[10:24:50] -!- GammaX-laptop has quit [Ping timeout: 256 seconds]
[10:24:50] -!- gammax-Laptop1 has quit [Ping timeout: 256 seconds]
[10:25:58] -!- largecheesepuff has quit [Ping timeout: 256 seconds]
[10:28:08] -!- sumpfralle has quit [Ping timeout: 252 seconds]
[10:31:01] -!- mackerski has quit [Read error: Operation timed out]
[10:31:01] mackerski_ is now known as mackerski
[10:37:39] -!- lagmonster has quit [Ping timeout: 250 seconds]
[10:46:24] -!- skunkworks has quit [Remote host closed the connection]
[10:53:28] jthornton_ is now known as jthornton
[11:08:25] -!- coco_ has quit [Ping timeout: 250 seconds]
[11:14:22] -!- skunkworks [skunkworks!~skunkwork@68-115-41-210.static.eucl.wi.charter.com] has joined #linuxcnc-devel
[11:22:22] -!- toastyde2th has quit [Read error: Connection reset by peer]
[11:29:14] -!- carper64_lb [carper64_lb!~quassel@94.9.2.183] has joined #linuxcnc-devel
[11:29:58] -!- dhoovie has quit [Ping timeout: 246 seconds]
[11:30:31] -!- carper64_lb_ has quit [Ping timeout: 264 seconds]
[11:33:21] -!- b_b has quit [Changing host]
[11:41:52] geohacke1 is now known as geohacker
[12:05:45] -!- gommo has quit [Remote host closed the connection]
[12:06:58] -!- gommo has quit [Read error: Connection reset by peer]
[12:12:09] -!- gommo has quit [Ping timeout: 256 seconds]
[12:19:35] -!- carper64_lb_ [carper64_lb_!~quassel@94.9.2.183] has joined #linuxcnc-devel
[12:20:19] -!- carper64_lb has quit [Ping timeout: 264 seconds]
[12:34:01] -!- b_b has quit [Changing host]
[12:46:04] -!- holst has quit [Remote host closed the connection]
[12:53:47] -!- psha[work] has quit [Quit: Lost terminal]
[13:08:52] -!- bedah has quit [Quit: Ex-Chat]
[13:09:46] -!- stsydow has quit [Quit: Leaving]
[13:16:32] -!- skorasaurus has quit [Ping timeout: 256 seconds]
[14:13:46] -!- sumpfralle1 has quit [Read error: Connection reset by peer]
[14:16:03] -!- Valen has quit [Quit: Leaving.]
[14:27:55] -!- PetefromTn has quit [Ping timeout: 260 seconds]
[14:29:04] -!- maximilian_h1 has quit [Read error: Connection reset by peer]
[14:29:11] -!- maximilian_h [maximilian_h!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[14:46:38] -!- maximilian_h1 [maximilian_h1!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[14:46:38] -!- maximilian_h has quit [Read error: Connection reset by peer]
[14:54:45] -!- maximilian_h1 has quit [Quit: Leaving.]
[14:54:51] -!- maximilian_h [maximilian_h!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[14:59:42] -!- maximilian_h has quit [Read error: Connection reset by peer]
[14:59:48] -!- maximilian_h1 [maximilian_h1!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[15:12:10] -!- Bojangle1 has quit [Ping timeout: 276 seconds]
[15:31:41] -!- PetefromTn_ has quit [Ping timeout: 256 seconds]
[15:39:26] -!- PetefromTn has quit [Ping timeout: 252 seconds]
[15:41:17] -!- IchGuckLive has quit [Quit: ChatZilla 0.9.87 [Firefox 20.0/20130329043827]]
[15:42:55] -!- zzolo has quit [Quit: zzolo]
[15:45:00] -!- capricorn_1 has quit [Quit: Konversation terminated!]
[15:52:43] -!- PetefromTn_ has quit [Remote host closed the connection]
[15:57:37] -!- psha [psha!~psha@213.208.162.67] has joined #linuxcnc-devel
[16:01:29] -!- jfire has quit [Quit: Leaving.]
[16:11:17] -!- Kup has quit [Read error: Connection reset by peer]
[16:17:01] <cradek> after seb's fixes to comp, all the .comps are regenerated
[16:17:09] <cradek> our build system is awesome
[16:31:18] -!- mackerski has quit [Quit: mackerski]
[16:34:18] -!- skorasaurus has quit [Ping timeout: 256 seconds]
[16:41:05] -!- PetefromTn has quit [Ping timeout: 256 seconds]
[16:48:06] -!- PetefromTn has quit []
[16:48:07] -!- Wildhoney has quit [Ping timeout: 246 seconds]
[16:50:45] -!- GammaX-Extra1 has quit [Client Quit]
[16:50:45] -!- GammaX-Extra has quit [Client Quit]
[16:51:20] -!- pingufan has quit [Quit: Konversation terminated!]
[16:57:59] -!- andypugh [andypugh!~andy2@cpc16-basl9-2-0-cust685.20-1.cable.virginmedia.com] has joined #linuxcnc-devel
[16:59:47] <seb_kuzminsky> yeah i noticed that while i was testing the changes
[16:59:51] <seb_kuzminsky> it's pretty cool :-)
[17:01:50] <seb_kuzminsky> oh, but it's not really *my* fix to comp, it's Curtis Dutton's from the mailing list
[17:04:38] -!- stsydow has quit [Read error: Connection reset by peer]
[17:05:03] -!- kos_ has quit [Ping timeout: 250 seconds]
[17:05:42] -!- tmcw has quit [Remote host closed the connection]
[17:07:11] -!- ler_hydra has quit [Remote host closed the connection]
[17:08:35] -!- PetefromTn has quit []
[17:18:47] -!- Bojangles has quit [Ping timeout: 256 seconds]
[17:29:03] <cradek> those changes have you for the author...
[17:29:25] <seb_kuzminsky> yeah, Curtis did his changes to src/objects/hal/utils/comp.py by mistake
[17:29:59] <cradek> I've never been sure whether to set author for changes where the contributor doesn't give me a usable git patch (of course that's the best possible situation)
[17:30:04] <seb_kuzminsky> i wrote a new commit that did what he meant, not what he said, and tried to credit him in the commit message
[17:30:26] <cradek> I've probably done it some of the times and not others
[17:30:35] -!- stsydow has quit [Read error: Connection reset by peer]
[17:31:28] <seb_kuzminsky> i wouldnt feel comfortable impersonating someone in an Author: or Committer: line
[17:32:38] <cradek> I don't think git commit --author is impersonation
[17:32:54] <cradek> I agree you wouldn't want to change committer
[17:33:04] <seb_kuzminsky> ah, i see what you're saying
[17:33:54] <seb_kuzminsky> yeah ideally casual contributors would send us usable patches, with themselves as the author, and we'd become their committer
[17:37:06] -!- ve7it [ve7it!~LawrenceG@S01060014d19d0b68.pk.shawcable.net] has joined #linuxcnc-devel
[17:37:57] <skunkworks> we all should be committed...
[17:38:15] <seb_kuzminsky> heh
[17:47:00] <seb_kuzminsky> skunkworks:
http://stevelosh.com/blog/2013/04/git-koans/
[17:49:53] <cradek> those are meant to be funny, but mostly they make me sad
[17:50:18] <seb_kuzminsky> it's a valueable reminder of how awful git is
[17:50:29] <seb_kuzminsky> it's easy to forget, because git is so awesome
[17:50:43] -!- pingufan has quit [Quit: Konversation terminated!]
[17:50:46] <cradek> oh I never forget how bad the UI is. how could you?
[17:51:04] <seb_kuzminsky> i never think about the ui any more, my fingers do it for me now
[17:51:12] <seb_kuzminsky> oh btw! tig ftw!
[17:51:38] <cradek> ?
[17:51:38] <seb_kuzminsky> i use it for most everything i used to use gitk/git gui/git cli for now
[17:51:52] <seb_kuzminsky> tig is an ncurses interface to most git functionality
[17:51:56] <cradek> oh did someone slather a new layer over git?
[17:52:06] <seb_kuzminsky> no no, just a new ui ;-)
[17:52:29] <seb_kuzminsky> my favourite feature is that it lets you stage lines and hunks easily from the terminal
[17:53:37] -!- pjm has quit [Ping timeout: 248 seconds]
[17:54:55] -!- ghuz has quit [Read error: Connection reset by peer]
[18:03:19] -!- IchGuckLive has quit [Remote host closed the connection]
[18:14:20] -!- IchGuckLive has quit [Quit: ChatZilla 0.9.87 [Firefox 20.0/20130329043827]]
[18:16:32] <seb_kuzminsky> the tool number overloading in the lathe/fadal patch gives me the willies
[18:26:14] -!- Delysid has quit [Ping timeout: 276 seconds]
[18:28:50] -!- pjm has quit [Read error: Connection reset by peer]
[18:32:41] -!- ravenlock has quit [Ping timeout: 252 seconds]
[18:35:45] -!- wboykinm has quit [Remote host closed the connection]
[18:48:36] -!- krusty_ar has quit [Remote host closed the connection]
[18:51:24] -!- RagingComputer has quit [Ping timeout: 252 seconds]
[18:55:08] -!- gammax-Laptop1 has quit [Ping timeout: 245 seconds]
[19:11:22] -!- skorasaurus has quit [Ping timeout: 276 seconds]
[19:16:10] -!- motioncontrol has quit [Ping timeout: 246 seconds]
[19:44:08] -!- Simooon has quit [Ping timeout: 256 seconds]
[20:01:56] -!- adb has quit [Remote host closed the connection]
[20:03:47] -!- skunkworks has quit [Quit: Leaving]
[20:13:45] -!- iDGS has quit [Client Quit]
[20:17:28] simon_ is now known as Simooon_l
[20:23:12] -!- ReadError_ has quit [Read error: Connection reset by peer]
[20:27:25] -!- gommo_ has quit [Ping timeout: 256 seconds]
[20:34:28] -!- mhaberler [mhaberler!~mhaberler@extern-186.stiwoll.mah.priv.at] has joined #linuxcnc-devel
[20:39:01] -!- riz_ [riz_!62dd7d6e@gateway/web/freenode/ip.98.221.125.110] has joined #linuxcnc-devel
[20:39:47] <riz_> I am trying to figure out how to change the max accel/vel of a rapid traverse (G0). Where can I find that?
[20:41:30] <andypugh> I think it is the axis max velocity.
http://www.linuxcnc.org/docs/html/config/ini_config.html#sub:TRAJ-section
[20:43:58] <seb_kuzminsky> riz_: there may be other limits on rapid speed, in addition to the ones andypugh mentioned
[20:44:05] <seb_kuzminsky> max speed of your steppers, for example
[20:44:36] <seb_kuzminsky> and there's some suspicious config variables in the [DISPLAY] section:
http://linuxcnc.org/docs/2.5/html/config/ini_config.html#_display_section_a_id_sub_display_section_a
[20:44:47] <riz_> Oh, ok. I am actually trying to slow my rapid down haha
[20:44:59] <andypugh> press "5" :-)
[20:45:02] <riz_> I am getting a following error
[20:45:21] <seb_kuzminsky> does your machine have servos?
[20:46:21] <riz_> yes
[20:46:55] <riz_> Is there anything special I should do wen running servos?
[20:47:12] <seb_kuzminsky> in that case you should probably tune your servos rather than lower your [TRAJ]MAX_VELOCITY
[20:47:33] <seb_kuzminsky> ferror with servos almost always means bad tuning
[20:48:07] <riz_> Yeah, I kind fo assumed that
[20:48:15] <riz_> What is a typical max velocity and acc?
[20:48:47] <seb_kuzminsky> there is no typical value, it depends entirely on your machine
[20:49:04] <riz_> And should I tune the drive first, then tune linuxcnc PID?
[20:49:56] <seb_kuzminsky> http://linuxcnc.org/docs/2.5/html/common/Integrator_Concepts.html#_servo_systems
[20:50:09] <seb_kuzminsky> yes
[20:51:13] <riz_> There is no tool to tune linuxcnc is there?
[20:51:20] <riz_> Would I manually do it?
[20:52:39] <seb_kuzminsky> yes, pid tuning is a manual process, somewhat described by the link i just pasted
[20:53:57] <riz_> OK. Thanks for the help!
[20:54:05] <riz_> Ill play around with it
[20:55:26] <seb_kuzminsky> there's also this:
http://linuxcnc.org/docs/2.5/html/motion/pid_theory.html
[20:55:49] <seb_kuzminsky> sure thing! good luck!
[20:56:07] -!- FinboySlick has quit [Quit: Leaving.]
[20:56:34] <riz_> thanks
[20:56:38] -!- riz_ [riz_!62dd7d6e@gateway/web/freenode/ip.98.221.125.110] has parted #linuxcnc-devel
[20:58:56] -!- mhaberler has quit [Quit: mhaberler]
[21:07:25] -!- Tecan has quit [Remote host closed the connection]
[21:07:30] -!- frallzor has quit []
[21:10:10] -!- L84Supper has quit [Quit: gone (puff of smoke)]
[21:14:19] -!- DJ9DJ has quit [Quit: bye]
[21:25:23] -!- GammaX-Shop has quit [Ping timeout: 252 seconds]
[21:25:44] -!- psha has quit [Quit: Lost terminal]
[21:25:58] -!- maximilian_h1 has quit [Ping timeout: 245 seconds]
[21:31:18] -!- tmcw has quit [Remote host closed the connection]
[21:40:44] -!- maximilian_h [maximilian_h!~bonsai@h138-36-9-212.dsl.netz-quadrat.de] has joined #linuxcnc-devel
[21:42:42] <cradek> where is the latest version of this tool table patch everyone is talking about?
[21:46:15] <andypugh> Chris's hard-drive, I suspect. There is one version here:
http://www.linuxcnc.org/index.php/english/forum/20-g-code/24387-tool-offset-patch?start=30#33970
[21:46:53] <cradek> AttachmentThis attachment is hidden for guests. Please log in or register to see it.
[21:46:58] <cradek> that's so obnoxious
[21:47:28] <seb_kuzminsky> you misspelled secure
[21:48:01] <cradek> probably helps not get nailed by robots
[21:50:06] <cradek> after I log in, your link stops working
[21:50:15] <cradek> I don't see the attachments anymore
[21:50:58] <cradek> for some reason, when I log in, the threads all reverse, but it stays on the same "page", so I always lose my place
[21:53:19] -!- GammaX-Shop has quit [Read error: Connection reset by peer]
[21:56:39] <cradek> the first blob in the patch undoes bugfix 1288ae3c
[21:57:31] <andypugh> I think Chris is working on a clean patch, triggered by an INI option.
[21:59:40] <cradek> I wish I understood the problem we are trying to solve
[22:00:25] <andypugh> Lathe users apparently want to change tool with a "T"
[22:00:41] <andypugh> And they want separate offsets for tool geometry and wear.
[22:01:05] <andypugh> And they are too stupid to learn to use M6 and G43
[22:01:35] <andypugh> (I am mainly a lathe user, but I have never used anything except M6 and G43)
[22:01:39] <cradek> T1234 changes to tool 12 with offset 34, which consists of two separate offsets?
[22:01:45] <andypugh> Yes.
[22:02:16] <cradek> so this breaks tool numbers >99
[22:02:27] <andypugh> So, the 12 offset might be -7mm, +25mm, and the wear offset would be -0.1, +0.05
[22:02:29] <cradek> and is not a general solution that lets you apply more than one offset
[22:02:50] <andypugh> Yes.
[22:03:03] <cradek> fucking gcode
[22:03:07] <andypugh> Quite.
[22:03:43] <andypugh> It is worse than it seems, because you also need to remember to go into the tool table and create a tool 10012 to hold the geometry offset.
[22:03:44] <cradek> I don't care about compatibility, but I do care about the functionality, and the abilty to apply more than one tool offset sounds like the thing we are missing
[22:04:17] <cradek> well yeah this is really incomplete as it stands. I assume touch-off in an existing gui screws it all up too
[22:04:25] <andypugh> If you don't create the dummy tool to hold the geometry, then it all goes wrong.
[22:04:56] <andypugh> I am pretty sure that touch-off will just tweak the wear offset.
[22:05:00] -!- Simooon has quit [Quit: Leaving]
[22:05:53] <cradek> well what should it do?
[22:06:06] <andypugh> (I don't care, I have the spanners out and I am about to rip into interp:convert and completely remove the tool table from settings.)
[22:06:56] <andypugh> I think touch-off _should_ tweak the wear offsets.
[22:07:16] <cradek> well I think it should set whichever offset the user wants it to set
[22:07:31] <seb_kuzminsky> maybe sometimes it should, but touch-off should also be able to set coordinate systems & tlos
[22:08:10] <cradek> we already have a problem with touch off vs. t1m6g43h2 (it sets t1's offset)
[22:08:14] <cradek> so it's already ambiguous
[22:08:43] <cradek> if we have the equivalent of (imagine) t1m6g43h2h3h4 (load tool 1, apply the sum of offsets 2,3,4) it gets more ambiguous
[22:08:46] <seb_kuzminsky> g43h is just crazy to start with
[22:09:39] <cradek> explain
[22:10:07] <seb_kuzminsky> load tool X, but apply tool Y's offsets? it makes no sense
[22:10:49] <cradek> in that case Y wouldn't usually be an actual tool. it's just a way to get a different offset applied to tool X
[22:10:54] <andypugh> Did you see my email earlier?
[22:11:13] <andypugh> I want to have multiple extra offsets per tool.
[22:11:25] <andypugh> (but that breaks the conventional Fanuc way)
[22:11:27] <seb_kuzminsky> cradek: but, but... the docs says "H - tool number (optional)"
[22:11:28] <cradek> imagine tool X has two useful points on it - like a slitting saw with a top and bottom face, or a ball end mill with a tip and a ball-center
[22:11:43] <cradek> well we're slavishly copying someone else's old implementation
[22:11:57] <cradek> that's why I want to talk about functionality, not more slavish copying of someone's lathe this time
[22:12:17] <andypugh> Yes, we are, because someone at MPM has been insistent that is what we should be doing
[22:12:20] <cradek> if your tool table only has tools, and you want that functionality, they're sorta kinda tool numbers
[22:12:42] <cradek> andypugh: I think you mean tormach
[22:12:52] <andypugh> No, I mean MPM
[22:12:55] <seb_kuzminsky> the "tool" isn't the thing in the toolholder, it's the datum you care about on the thing in the toolholder?
[22:13:13] <cradek> andypugh: I didn't think they had cnc lathes at all
[22:13:16] <seb_kuzminsky> hrm, i guess i could see that
[22:13:21] <cradek> andypugh: shows how behind the times I am
[22:13:43] <seb_kuzminsky> i haven't heard any lathe feature requests from MPM either
[22:13:53] <andypugh> Tormach wanted the patch too, and wrote it. But I think Tormach would be relatively happy not to be quite so slavishly copying Fanuc
[22:13:54] <cradek> this is my puzzled look
[22:14:22] <andypugh> It is possible that I am getting confused, I am not good at keeping track of people
[22:14:53] <cradek> unless you're positive otherwise, I bet you mean tormach :-)
[22:15:05] -!- Simooon_l has quit [Quit: Leaving]
[22:15:14] <andypugh> Tormach is Daniel Rogge?
[22:15:17] <cradek> yes
[22:16:11] <seb_kuzminsky> MPM is stuart stevenson, who's hosting the hack fest again this year
[22:16:12] <andypugh> Rick Lair is who I am thinking of:
http://www.linuxcnc.org/index.php/english/my-profile-usermenu-17/userprofile/LAIR82
[22:16:22] <cradek> I don't know that name
[22:17:12] <seb_kuzminsky> according to his profile he does not live near MPM
[22:17:35] <cradek> I'm imagining another gcode that means "also add in tool offset #N"
[22:18:03] <cradek> if you've got more than one offset applied, touch off could just refuse to adjust the tool table
[22:18:05] <andypugh> Indeed. I now need to remember who it was who was pushing for an industrial version of Gscreen
[22:18:32] <seb_kuzminsky> g43 --add hxxx
[22:19:06] <cradek> whatever the syntax, would that give us all the needed functionality? it's at least coherent to me
[22:19:17] <seb_kuzminsky> i get the impression from drogge that the goal is gcode-level compatibility with fanuc
[22:19:37] <cradek> well I can see that is not the only goal
[22:20:11] <cradek> besides, that's trivial to do with a trivial filter (T1234 -> T12M6G43H34)
[22:20:52] <cradek> if you want it to use the sum of offsets 34 and 134 or whatever, it would surely be just as easy
[22:22:18] -!- maximilian_h has quit [Ping timeout: 264 seconds]
[22:22:29] <cradek> I'd be shocked to learn that that's the only significant thing in the way of fanuc compatibility
[22:23:45] <seb_kuzminsky> i think that filter is harder than that, T[#3*##4] may or may not expand to a second G43Hsomething depending on the values or 3 and whatever 4 points to
[22:24:16] <seb_kuzminsky> i think it needs support in interp to do it right
[22:24:23] <cradek> um does fanuc let you do that?
[22:25:06] <seb_kuzminsky> fiik
[22:25:12] <andypugh> The idea is to be able to hit two different tolerances with the same tool.
[22:25:34] <cradek> if the goal is to support existing fanuc gcode, I'd need to know what's allowed in fanuc to know how hard the filter would be
[22:25:37] <andypugh> (why not change the G-code diameter? Don't ask me)
[22:25:45] <cradek> and I don't know that and frankly I don't care
[22:26:32] <cradek> andypugh: my understanding is they want to adjust tool offset as the tool (probably insert) wears, and then put it back to nominal when replacing it
[22:26:39] <andypugh> I need to know how wedded to the idea of setting an offset with G10 P10044 the lathe guys are.
[22:27:10] -!- maximilian_h [maximilian_h!~bonsai@130.255.104.21] has joined #linuxcnc-devel
[22:27:24] <cradek> yeah that's all rolled up in the problem of how stuff gets set (from mdi and gui touch-off)
[22:27:24] <andypugh> The ability to use different wear offsets with the same tool number is supposedly to hit different tolerances though.
[22:27:54] <cradek> but T1234 doesn't allow that does it?
[22:28:08] <cradek> you get 34 and 134. no way to get 34 and 135
[22:28:40] <cradek> do you need a fake tool 35 with the same geometry offset as 34? that's stupid and now you're down to a max of 98 tools.
[22:28:44] <andypugh> Yes, you could turn one diameter with T1234 and another with T1256, same tool, but different secondary offset.
[22:29:11] <cradek> I think one of us isn't following
[22:29:41] <seb_kuzminsky> i think "T1234" should be parsed as "tool 12 with wear offset 34", is that right andypugh ?
[22:29:44] <cradek> in the T1234 scheme, how do you use a single geometry offset but your choice of among two wear offsets?
[22:30:03] <andypugh> You change the second two digits.
[22:30:18] <cradek> is the geometry offset 12 or 34?
[22:30:19] <seb_kuzminsky> cradek: i think "T1298" means "tool 12 and wear offset 98"
[22:30:40] <cradek> in T1234, which geometry offset and which wear offset do you get?
[22:30:59] <andypugh> And to use T1298 you need to have created a tool 10098 in an empty pocket.
[22:31:00] -!- stsydow has quit [Quit: Leaving]
[22:31:20] <cradek> in T1234, which geometry offset and which wear offset do you get?
[22:31:20] <andypugh> Sorry, that was backwards
[22:31:42] <cradek> I don't care about the current incomplete implementation
[22:31:51] <seb_kuzminsky> cradek: TLO 12 and wear offset 34
[22:31:56] <cradek> still trying to understand the problem
[22:31:57] <andypugh> Tool 12 geometry (from the pocket containing tool 10012) and Tool 34 offset (from the pocket comtaining tool 34)
[22:32:02] <cradek> oh ok ok
[22:32:14] <seb_kuzminsky> whoa, i had it backwards
[22:32:16] <seb_kuzminsky> :-(
[22:32:25] <cradek> so you can no longer apply a non-matching geometry offset either
[22:32:48] <seb_kuzminsky> what andypugh just said disagrees with what drogge said here:
http://thread.gmane.org/gmane.linux.distributions.emc.devel/9664/focus=9676
[22:33:00] <andypugh> Well, actually, you probably can. I haven't checked but G43 Hnn will almost certainly still work.
[22:33:12] <cradek> haha "work"
[22:33:24] <cradek> T1234 G43H56 => ??
[22:33:58] <seb_kuzminsky> from the email i just pasted: "G43 isn't an accepted Fanuc lathe code"
[22:34:04] <seb_kuzminsky> so we'll have to drop it ;-)
[22:34:19] <cradek> the comments in the patch agree with andypugh (I can't decipher the code with a lot more study)
[22:34:22] <cradek> without
[22:35:39] <andypugh> cradek: Well, that would load the tool from the pocket containing tool 12, it would apply the wear offsets from tool 34, and the geometry offsets from the pocket containing tool 56. It's all perfectly logical. :-)
[22:36:20] <andypugh> seb_kuzminsky: I am fairly sure that what I said the second time round agrees with Daniel.
[22:36:55] <cradek> I promise you it doesn't currently do that
[22:37:15] <cradek> (no I didn't try it)
[22:37:43] <seb_kuzminsky> andypugh: i dont understand why you said "Tool 12 geometry (from the pocket containing tool 10012)"
[22:37:50] <cradek> the fanuc 10 manual in front of me talks about tool life stuff too
[22:39:03] <andypugh> seb_kuzminsky: I may have tied myself in knots again. And I don't have the patch file open here.
[22:39:23] <seb_kuzminsky> me neither ;-)
[22:39:28] <cradek> T101; M6T102
[22:39:31] <andypugh> Are you saying that you think the wear offset comes from the pocket containing tool 10012?
[22:39:32] <cradek> surprise, guess which tool is loaded
[22:39:59] <cradek> sorry, how fanuc works is a sidetrack, forget it
[22:40:16] <andypugh> T102 I think, T having higher prioruty?
[22:40:20] <seb_kuzminsky> andypugh: no, i think for "T1234", the TLO comes from tool 12 and the wear offset comes from tool 34 (or maybe 10034, i'm not sure)
[22:40:52] <cradek> (if you can only have 99 tools, why are the offsets 10000 instead of 100?)
[22:41:05] <andypugh> I have no idea.
[22:41:32] <cradek> fanuc 10 also has "tool groups"
[22:41:34] <andypugh> If I was doing it, Tool 4400 would be the geometry for 44.
[22:41:48] <cradek> when one in a group wears out (it keeps track), it goes to the next one
[22:42:00] <cradek> we are NOT going to be compatible with fanuc gcode without a LOT of changes
[22:42:14] <andypugh> And I don't think we necessaily want to be.
[22:42:45] <andypugh> But I think what you described there is a use-case for having the same tool-number in more than one pocket-number.
[22:42:48] <seb_kuzminsky> i think drogge and cmorley are working towards fanuc compatibility with this project
[22:42:50] <cradek> this was 1984. I'm sure they have more features by now.
[22:42:55] -!- GammaX-Shop has quit [Ping timeout: 240 seconds]
[22:43:19] <andypugh> I think we should push Fanuc towards NIST compatibility.
[22:43:30] <seb_kuzminsky> heh
[22:43:51] <seb_kuzminsky> yeah, all we need is huge market share so that cam vendors & machinists will ask them for it
[22:44:04] <cradek> it's clear we want more flexibility from the tool table - but I think this patch's approach (slavishly copying a certain 1% of fanuc) is the wrong approach
[22:44:20] <seb_kuzminsky> *we* have deviated from nist a good ways, haven't we?
[22:44:44] <cradek> if you know you only use 1% of fanuc, you can write a filter for that 1% IFF we have a superset of the equivalent functionality
[22:44:55] <cradek> IMO that should be our goal
[22:45:37] <andypugh> cradek: Yes. I agree. But as long as it can be turned on and off with an INI switch, I am not too concerned. I did discuss options on the mailing list earlier.
[22:45:57] <seb_kuzminsky> i am concerned about ini switches, from a test matrix standpoint
[22:46:08] <cradek> well yeah, then it's only more stuff to keep working, as you try to do something better
[22:46:25] <andypugh> But my current thinking is that each tool can have as many wear offsets as it wants.
[22:46:47] <andypugh> Independent from those of any other tool.
[22:47:01] <andypugh> _OR_ we have an independent table of wear offsets.
[22:47:10] <cradek> we already have load tool N, apply offset M, we only need "also apply offset O"
[22:47:15] <andypugh> I prefer the first approach.
[22:47:57] <cradek> I don't want to give up arbitrarily large tool numbers, and I don't want to give up being able to load N with geometry offset M
[22:48:10] <andypugh> Load tool N, apply offset M can also be achiaved by having more than one tool in the same pocket.
[22:49:04] * cradek squints
[22:49:15] <cradek> I'm not following that
[22:49:21] <andypugh> T2 and T3 can both send the same pocket number to the toolchanger, but apply different length offsets.
[22:49:55] <andypugh> (gang tooling, for example)
[22:50:04] <seb_kuzminsky> implementing that right would be hairy with the random toolchanger
[22:50:40] <cradek> yeah I'm pretty sure those problems are incompatible
[22:50:42] <seb_kuzminsky> you'd have to go find all the pseudo-tools in the current tool's home pocket, and move them all
[22:50:46] -!- L84Supper [L84Supper!~TheLarch@unaffiliated/l84supper] has joined #linuxcnc-devel
[22:51:04] <seb_kuzminsky> i think it could be solved
[22:51:08] <andypugh> I would need to think about it. Perhaps RANDOM_TOOLCHANGER needs to exclude duplicate pocket numbers.
[22:51:46] -!- GammaX-Shop has quit [Read error: Connection reset by peer]
[22:51:57] <cradek> andypugh: am I right that if we always map T->P (find_tool_pocket()), what you want is no problem
[22:51:57] <seb_kuzminsky> i'm holding out hope for a solution that does not further fracture our behavior and feature set
[22:52:21] <seb_kuzminsky> ooh, time for dinner here!
[22:52:27] <cradek> lucky you
[22:52:32] <seb_kuzminsky> later!
[22:52:33] <cradek> bye
[22:52:54] <andypugh> cradek: If I read your psudocode correctly, then I think so.
[22:53:16] <cradek> sorry to be obscure: find_tool_pocket() is real code
[22:53:59] <andypugh> Yes, but at the moment it actually locates the index of the tool table array, rather than the actual pocket number.
[22:54:34] <cradek> yes that's an accident of the (C) implementation
[22:54:47] <andypugh> What I am proposing is that you always find a tool by tool number, and the pocket it is kept in is just another parameter of that tool.
[22:55:32] <cradek> "what the hell do we do about the tool table that covers all the interesting use cases" is a discussion we should have at fest. I'd hold off shoehorning another patch in, meanwhile
[22:56:22] <andypugh> I was hoping to be at least part-way there by the fest. If not in detailed implementation of "what" at least part-way through "how"
[22:56:50] -!- zzolo has quit [Quit: zzolo]
[22:57:20] <cradek> sorry, where is "there"? do you mean fanuc lathe compatibility, or something else?
[22:57:58] <andypugh> I don't care about fanuc lathe compatibility.
[22:58:39] <cradek> I don't either. I do care about the functionality of wear offsets though
[22:58:53] <cradek> tool life tracking would be nice too
[22:58:57] <andypugh> And those need to be baked-in to whatever replaces the tool table.,
[22:59:31] <andypugh> Well, if the tool-table is a key-value store (as has been suggested) then it is infinitely expandable.
[22:59:45] <cradek> if I do T[tap]M6 and that tap has already tapped 200" worth of hole, stop and prompt
[23:00:33] <cradek> well key-value is only adequate if you have the important mapping in one direction only
[23:00:35] <andypugh> search the database for tool.7.lifetime then...
[23:01:30] <cradek> you can't have both "what all tools are in P3 (for gang tooling)" and "what pockets make up T1 (for tool groups)"
[23:01:48] <cradek> we should not talk about an implementation until we know what functionality we want
[23:02:26] <andypugh> Indeed. And I have only got as far as looking at where the tool table data is used, so far.
[23:02:55] <andypugh> It actually seems to have a very ling journey through very many layers, to a very small amount of consuming code.
[23:03:22] <cradek> all I know is it's horrible AND currently working, bad combination
[23:04:06] <andypugh> It isn't currently working.
[23:04:07] -!- fiesh has quit [Ping timeout: 264 seconds]
[23:04:23] -!- ravenlock_ has quit [Ping timeout: 252 seconds]
[23:05:13] <andypugh> Skunkworks can't use all of his tool chain, this is a bug that must be fixed :-)
[23:06:37] <cradek> heh, well we disagree slightly on "working"
[23:07:41] -!- skunkworks [skunkworks!~chatzilla@str-broadband-ccmts-ws-26.dsl.airstreamcomm.net] has joined #linuxcnc-devel
[23:08:02] <andypugh> I don't see why we can't just move the tool table into the global variables :-)
[23:09:36] <andypugh> (I was extremely surprised when I found them, after all the gymnastics to create and use NML, it seems odd)
[23:09:44] -!- wd-40 has quit [Quit: Leaving]
[23:21:31] -!- ds3 has quit [Ping timeout: 246 seconds]
[23:28:47] -!- Nick001-Shop has quit [Read error: Connection reset by peer]
[23:37:18] -!- syyl has quit [Ping timeout: 264 seconds]
[23:50:52] -!- thesisb has quit [Ping timeout: 276 seconds]
[23:51:37] -!- asdfasd has quit [Ping timeout: 246 seconds]
[23:52:47] -!- ronson has quit [Remote host closed the connection]