Back
[07:13:19] <KGB-linuxcnc> 03John Thornton 052.7 ae20daa 06linuxcnc 10docs/src/gui/pyvcp.txt Docs: fix markup * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ae20daa
[07:13:19] <KGB-linuxcnc> 03John Thornton 052.7 65d8981 06linuxcnc 10docs/src/gui/pyvcp.txt Docs: expand the descriptions * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=65d8981
[07:13:19] <KGB-linuxcnc> 03John Thornton 052.7 3e9f464 06linuxcnc 10docs/src/gui/pyvcp.txt Docs: disable does not work on a label * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3e9f464
[07:31:33] <jepler> seb_kuzminsky: I wonder what happens to the comments when I rewind the branch, are they lost from github's web ui forever?
[07:37:04] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults f20f8cc 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.h 10src/hal/drivers/mesa-hostmot2/sserial.c 10src/hal/drivers/mesa-hostmot2/sserial.h hostmot2: sserial: split error checking into local, remote * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f20f8cc
[07:50:23] <KGB-linuxcnc> 03John Thornton 052.7 59889fc 06linuxcnc 10docs/src/gui/pyvcp.txt Docs: more info on labels * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=59889fc
[10:26:40] <CaptHindsight> how is RTAI-5 with Linuxcnc, somebody mentioned issues in the other channel but no details?
[10:29:03] <jepler> I think the buildbot slaves have been somewhat crashy with seb's kernel. the 64-bit one particularly.
[11:49:42] <JT-Shop> I just homed the BP with the latest jepler/sserial branch and everything works... I still get a sserial error but I can run
[12:12:12] <jepler> I'll try to get that fixed before I merge this into 2.7 for real
[12:12:40] <jepler> I think it'll mean a slightly worse diagnosis of the misconfiguration where you add the .write function but not the .read function of the mesa card to the servo thread
[12:15:37] <JT-Shop> thanks
[12:59:46] <maxcnc> Question on behavior of the task to my problem on global variables the min manuell move updates the parameter but not at MDI or g-code move the interpreter cc are not pased on task where do i update this
[13:01:58] <maxcnc> there iso nly a rs274pre so this is also not pased at ttask end
[13:02:52] <maxcnc> the devolopers docu gives no clue to the runtime filepasess in non realtime
[13:03:18] <maxcnc> nml seams to be the transicions
[13:46:51] <skunkworks> when I was a kid....
[14:34:04] <JT-Shop> that was a long time ago for me
[14:56:44] <jepler> cradek: I see there's a block of code that looks like it's intended to prevent reading #5420 et al while in cutter comp mode
[14:56:47] <jepler> CHKS(((index >= 5420) && (index <= 5428) && (_setup.cutter_comp_side)),
[14:56:50] <jepler> _("Cannot read current position with cutter radius compensation on"));
[14:57:07] <jepler> ... but the test doesn't seem to work
[14:57:08] <jepler> [8$READ => g42.1 d1
[14:57:08] <jepler> 21 N..... COMMENT("interpreter: cutter radius compensation on right")
[14:57:08] <jepler> READ => (debug,#5420)
[14:57:08] <jepler> 22 N..... MESSAGE("2.000000")
[14:58:21] <jepler> oh argh , that bit of code *IS* hit if you G0X#5420
[14:58:30] <jepler> READ => g0x#5420
[14:58:30] <jepler> Cannot read current position with cutter radius compensation on
[15:01:02] <cradek> oh weird
[15:03:02] <cradek> I suppose debug doesn't use the normal readers
[15:03:07] <jepler> right
[15:06:35] <jepler> READ => g42.1d1
[15:06:38] <jepler> READ => (debug,#5420)
[15:06:39] <jepler> 10 N..... MESSAGE("######")
[15:06:57] <jepler> that's better, I think
[15:07:50] <jepler> READ => g0x#<_x>
[15:07:50] <jepler> Length of cutter compensation entry move is not greater than the tool radius
[15:08:04] <jepler> second problem: #<_x>, an alias for #5420, doesn't have this check
[15:08:36] <cradek> ick
[15:14:51] <jepler> READ => g42.1d1
[15:14:53] <jepler> READ => (debug,#<_x> #<_y> #<_z>)
[15:14:53] <jepler> 9 N..... MESSAGE("###### ###### ######")
[15:14:55] <jepler> much better
[15:14:59] <jepler> READ => g0x#<_x>
[15:15:00] <jepler> Cannot read current position with cutter radius compensation on
[15:47:38] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 465d571 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: work around sticky error reporting * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=465d571
[15:47:39] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 7d596fd 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: add notes about interpreting fault bits * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7d596fd
[15:47:39] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults a6489e0 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: fix off-by-one error in error reporting * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a6489e0
[15:47:42] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults d7a558f 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.h 10src/hal/drivers/mesa-hostmot2/sserial.c 10src/hal/drivers/mesa-hostmot2/sserial.h hostmot2: sserial: split error checking into local, remote * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d7a558f
[15:47:47] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 31b5ca1 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c 10src/hal/drivers/mesa-hostmot2/sserial.h hostmot2: sserial: actually check if read function added * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=31b5ca1
[15:48:21] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults d0921e2 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: work around sticky error reporting * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d0921e2
[15:48:22] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 9bae85e 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: add notes about interpreting fault bits * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9bae85e
[15:48:22] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults a9a9f11 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c hostmot2: sserial: fix off-by-one error in error reporting * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a9a9f11
[15:48:25] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 0880065 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.h 10src/hal/drivers/mesa-hostmot2/sserial.c 10src/hal/drivers/mesa-hostmot2/sserial.h hostmot2: sserial: split error checking into local, remote * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0880065
[15:48:30] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/hm2-sserial-faults 301005a 06linuxcnc 10src/hal/drivers/mesa-hostmot2/sserial.c 10src/hal/drivers/mesa-hostmot2/sserial.h hostmot2: sserial: actually check if read function added * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=301005a
[15:49:31] <KGB-linuxcnc> 03Jeff Epler 05jepler/master/interp-vars-ccomp e834546 06linuxcnc 10src/emc/rs274ngc/interp_convert.cc interp: deduplicate variable search code * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e834546
[15:49:31] <KGB-linuxcnc> 03Jeff Epler 05jepler/master/interp-vars-ccomp 3dfad7b 06linuxcnc 10src/emc/rs274ngc/interp_namedparams.cc interp: consolidate code for #<_x> .. #<_w> * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3dfad7b
[15:49:31] <KGB-linuxcnc> 03Jeff Epler 05jepler/master/interp-vars-ccomp 92b0562 06linuxcnc 10src/emc/rs274ngc/interp_namedparams.cc interp: Like #5420, #<_x> is an error with cutter comp on * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=92b0562
[15:52:00] <jepler> JT-Shop: the newest version of that branch should avoid that one error message soon after startup
[16:06:25] <JT-Shop> I'll test it in a bit
[16:06:50] <JT-Shop> painting
[16:14:35] <KGB-linuxcnc> 03Jeff Epler 05jepler/interp-machine-coord 9c4b3ff 06linuxcnc 10src/emc/rs274ngc/interp_find.cc interp: allow conversion to "G53" coordinate system * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9c4b3ff
[16:14:35] <KGB-linuxcnc> 03Jeff Epler 05jepler/interp-machine-coord e031ecb 06linuxcnc 10src/emc/rs274ngc/interp_namedparams.cc 10src/emc/rs274ngc/interp_read.cc 10src/emc/rs274ngc/rs274ngc_pre.cc interp: add "machine position" parameters * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e031ecb
[16:14:36] <KGB-linuxcnc> 03Jeff Epler 05jepler/interp-machine-coord 527bea7 06linuxcnc 10docs/src/gcode/overview.txt docs: document machine coordinate parameters * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=527bea7
[16:14:38] <KGB-linuxcnc> 03Jeff Epler 05jepler/interp-machine-coord fa30301 06linuxcnc 03tests/interp/5440/expected 03tests/interp/5440/test.ngc 03tests/interp/5440/test.sh 03tests/interp/5440/test.tbl tests: test "machine position" parameters" * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fa30301
[16:52:51] <cradek> cool
[16:52:52] <cradek> !
[17:15:44] <JT-Shop> jepler: I just homed the BP about 25 times with NO sserial errors on your latest
[18:05:39] <jepler> JT-Shop: awesome
[18:08:49] <JT-Shop> jepler: awesome for sure
[18:09:05] <JT-Shop> as in YIPPIE!
[20:01:10] <KGB-linuxcnc> 03Jeff Epler 05jepler/2.7/read-request-crash 7e28bf8 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.c hostmot2: don't crash with bad thread configuration * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7e28bf8
[20:04:07] <jepler> I think that finishes off the errors I bumped into while working on this sserial thing
[20:05:40] <jepler> I *thought* that there was a sticky error that would persist after one session stopped sserial due to excess errors into the next session, but now I believe that was only due to my glitch-inducing still being active the next time I started realtime.
[20:09:00] <jepler> hm2/hm2_7i92.0: hm2_sserial_waitfor: Timeout (24mS) waiting for addr 5d1c &mask ff00 val 2000
[20:09:25] <jepler> this occurs >1 in 10 when I don't turn off the glitch before exiting halrun, and <1 in 20 when I do turn it off, so I think it's glitch-induced
[20:10:22] <jepler> ditto occasional non-detection when glitch is still enabled
[20:19:59] <PCW> I think a stop and start of sserial clears all memory so there should not be anything that's persistant
[20:20:51] <jepler> right, it was my left over 10kHz or whatever glitch train that was causing the problems
[20:21:36] <PCW> though if there is something that can cause a hang it would be good to know ( some of the previously fixed hangs were caused by errors during startup )
[20:21:40] <jepler> PCW: did you get a chance to try my branch / do you want to try it before it goes into the 2.7 branch
[20:21:47] <jepler> ?
[20:22:04] <PCW> I can try tommorow, pretty beat today
[20:22:16] <jepler> OK, that's fine by me
[20:22:29] <jepler> everything relevant is in branch jepler/2.7/hm2-sserial-faults
[20:23:00] <jepler> seb gave me a positive review, though I put a few more changes on top of that to fix the last error message that jt mentioned earlier
[20:23:14] <PCW> i have a physical error inducer ( Ethernet transformer in series with TX and RX with function gen )
[20:24:06] <PCW> i need to rebuild all bitfiles with the filtered UART also, need a faster machine
[20:24:09] <jepler> if you can trigger a remote fault in your testing, that would cover something I haven't been able to do
[20:24:47] <PCW> yeah is easy on 7I76.77,71,71,84
[20:24:59] <PCW> (just short an output to GND)
[20:25:58] <jepler> Ok, I'll look forward to hearing the result of your tests
[20:26:19] <PCW> you could trigger a remote WD error by running your thread realllly slow
[20:27:10] <PCW> you would need to bump up the FPGA WD time
[20:27:56] <PCW> ( default remote WD time is 50 ms )
[20:28:15] <jepler> OK
[20:28:17] <jepler> hm2/hm2_7i92.0: Smart serial card hm2_7i92.0.7i69.0.7 error = (24) Watchdog Fault
[20:28:27] <jepler> yeah that works to trigger, but the message continually re-triggers
[20:28:34] <jepler> but now I can test it, so that's good!
[20:28:48] <PCW> forgot about the WD
[20:29:44] <jepler> oh wait I wasn't on the right branch
[20:29:57] <jepler> changing branches back to mine I get
[20:29:57] <jepler> hm2/hm2_7i92.0: Smart serial card hm2_7i92.0.7i69.0.7 error = (24) Watchdog Fault
[20:30:00] <jepler> hm2/hm2_7i92.0: Smart serial card hm2_7i92.0.7i69.0.7 error = (8) Remote fault
[20:30:03] <jepler> just once
[20:31:24] <PCW> Ahh thats good ( wonder if a per channel hal flag would be the right thing for this)
[20:31:51] <jepler> I *think* the way I've coded it, it is one per channel
[20:31:59] <jepler> let me scare up another cat5 cable and see
[20:34:26] <jepler> yep it prints fault (24) and (8) for each of two channels
[20:37:01] <PCW> a remote WD fault is pretty serious (no outputs can be enabled without a restart )
[20:49:02] <linuxcnc-build> build #2085 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/2085 blamelist: Dewey Garrett <dgarrett@panix.com>
[20:51:14] <jepler> In file included from emc/nml_intf/emc.cc:24:0:
[20:51:15] <jepler> emc/nml_intf/canon.hh:131:39: sorry, unimplemented: non-static data member initializers
[20:51:17] <jepler> emc/nml_intf/canon.hh:131:39: error: ISO C++ forbids in-class initialization of non-const static member ‘rotary_unlock_for_traverse’
[20:51:32] <cradek> "sorry"?
[20:51:35] <jepler> "sorry".
[20:51:50] <jepler> but maybe it was forbidden anyway?
[20:52:43] <cradek> don't ask me, I'm barely a C programmer
[20:54:45] <jepler> I wonder what version of gcc that is; I don't see it on my odroid but that's ubuntu/linaro, not debian
[20:54:57] <linuxcnc-build> build #3892 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/3892 blamelist: Dewey Garrett <dgarrett@panix.com>
[20:55:20] <jepler> oh "good" -- it fails on more than one platform
[20:56:01] <cradek> but I bet the change fixed the bug on dewey's platform; he doesn't push random untested stuff...
[20:56:50] <jepler> it builds on my jessie laptop
[20:57:16] <cradek> how do you even c++
[20:58:29] <jepler> $ g++-4.6 -std=c++0x -c fudge.cc
[20:58:29] <jepler> fudge.cc:2:14: sorry, unimplemented: non-static data member initializers
[20:58:30] <jepler> fudge.cc:2:14: error: ISO C++ forbids in-class initialization of non-const static member ‘i’
[20:58:39] <jepler> I do reproduce it with g++-4.6 on debian wheezy
[20:59:38] <jepler> checking whether g++ supports C++11 features with -std=c++11... no
[20:59:39] <jepler> checking whether g++ supports C++11 features with -std=c++0x... yes
[20:59:52] <jepler> this pair of configure lines is enough to tell me it's g++-4.6 and not -4.7 there, so mystery solved
[21:00:04] <jepler> it's a legitimate feature of C++11 not supported by old g++, so we'll have to work around it...
[21:02:25] <jepler> objects/emc/task/taskclass.o:taskclass.cc:function non-virtual thunk to boost::exception_detail::error_info_injector<boost::bad_lexical_cast>::~error_info_injector(): warning: relocation refers to discarded section
[21:02:59] <cradek> that's just making up words
[21:03:01] <KGB-linuxcnc> 03Jeff Epler 05jepler/for-dewey/gcc46-workaround 009cfd3 06linuxcnc 10src/emc/nml_intf/canon.hh nml_intf: Work around poor c++11 support in g++4.6 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=009cfd3
[21:03:01] <jepler> wonder what that one is
[21:03:25] <jepler> I hope dgarr sees that. I wonder if I should drop him an e-mail
[21:13:24] <linuxcnc-build> build #3894 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/3894 blamelist: Dewey Garrett <dgarrett@panix.com>
[21:19:36] <linuxcnc-build> build #3103 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/3103 blamelist: Dewey Garrett <dgarrett@panix.com>
[22:31:35] <linuxcnc-build> build #3906 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3906 blamelist: Dewey Garrett <dgarrett@panix.com>
[22:31:44] <trentster> Hey guys - I was wondering if this is a known bug. If you look at my video at around 18:55 - you can see the Linuxcnc not showing cone or tool
https://www.youtube.com/watch?v=swa-eX0irPg I Would love some help with this as it really bothers me! It does this regardless of gcode complexity - yet it does show the cone innitially when starting up and using the default linuxcnc gcode sample file. The display options of course have been set to alway
[23:01:34] <seb_kuzminsky> jepler: you can see what version of gcc it's using by looking at the environment-report step or the configure step
[23:18:29] <seb_kuzminsky> trentster: i see you're using a big machine and a small tool
[23:18:54] <seb_kuzminsky> are you sure you're not just so far zoomed out that your .125 inch diameter cutter becomes too small to see easily?
[23:19:31] <seb_kuzminsky> oh wait, you're in metric
[23:19:53] <seb_kuzminsky> so your tool diameter is .125 mm, that's a pretty small cylinder in the backplot...
[23:20:06] <seb_kuzminsky> do this experiment:
[23:20:37] <seb_kuzminsky> after your program is done, jog up so the tool is above the clutter of the tool path, and zoom in
[23:20:56] <seb_kuzminsky> might help to drive it to some easy-to-find location first, like the active coordinate system's origin
[23:22:25] <trentster> seb_kuzminsky: in this particular video its a big part, but it does not even show it when I cut smaller parts e.g. 60mm x 80mm in dimention
[23:22:40] <seb_kuzminsky> it looks like the tool diameter in your tool table does not match the tool in the spindle, so i'm going to assume you're not using cutter compensation in your program
[23:22:54] <seb_kuzminsky> thus the tool diameter is not used, and you could set it to something bigger, easier to see
[23:23:15] <seb_kuzminsky> 60x80 mm is still 600 times bigger than your programmed tool diameter
[23:24:57] <trentster> seb_kuzminsky: in that particular video it was default gcode output for linuxcnc postprocessor from Vectric aspire
[23:25:21] <trentster> As far as I know they dont use smoothing or cutter compensation
[23:25:38] <trentster> and in Linuxcnc the lookahead smoothing is active by default afaik
[23:25:48] <seb_kuzminsky> yep
[23:25:58] <seb_kuzminsky> i bet your tool diameter is just too small to see
[23:26:04] <trentster> it also does not show for me when I use gcode output from autodesk fusion 360 using smoothing and compensation
[23:26:36] <seb_kuzminsky> it's a feature of the tool table, not of your cam
[23:26:58] <seb_kuzminsky> try "g10 l10 p1 r50"
[23:27:27] <seb_kuzminsky> that says, "set tool diameter" (g10 l10) of tool 1 (p1) to 50mm (r50)
[23:28:27] <seb_kuzminsky> http://linuxcnc.org/docs/2.7/html/gcode/g-code.html#gcode:g10-l10
[23:28:34] <seb_kuzminsky> ah, sorry, it's tool radius, not tool diameter
[23:30:41] <trentster> ok - let me go out to the garage and check up
[23:30:54] <trentster> I know I have put the radius in the tool table
[23:31:08] <trentster> I am using metric and have used 6 for 6mm etc
[23:31:53] <seb_kuzminsky> the video shows 0.125 for the radius
[23:31:58] <seb_kuzminsky> mm
[23:34:08] <trentster> yeah thats in that video, like I said the same thing happens every time regardless of tool used or part size
[23:34:26] <trentster> but I understand the video is your only reference source
[23:34:28] <seb_kuzminsky> .1mm is about the width of two human hairs side by side
[23:34:56] <trentster> lol - yes I know
[23:34:59] <seb_kuzminsky> heh
[23:35:05] <seb_kuzminsky> i dont know what your other tools are like
[23:35:11] <trentster> perhaps it been put into tool table incorrectly. I will check and revert
[23:35:20] <trentster> thanks a ton for your help btw :-)
[23:35:35] <seb_kuzminsky> but i have a suspicion you're using a tool table that was preloaded with imperial tools
[23:35:46] <seb_kuzminsky> in fact the tlo of 0.511 looks familiar
[23:36:29] <seb_kuzminsky> sim/axis/sim.tbl:T1 P1 Z0.511 D0.125 ;1/8 end mill
[23:36:46] <seb_kuzminsky> it's the example tool table we ship with just about all our example configs
[23:37:00] <seb_kuzminsky> it's intended for imperial machines
[23:37:11] <trentster> seb_kuzminsky: yes that sounds like a plausible explanation.
[23:37:17] <trentster> How do I remedy that?
[23:37:38] <trentster> delete tool table and start with a clean one?
[23:38:35] <trentster> it would also explain why I see the cone for default linuxcnc gcode file that loads when gui opens as its in inches right
[23:38:53] <seb_kuzminsky> i'd recommend instead, in Axis, go to the File menu, select Edit Tool Table
[23:39:45] <trentster> ok going out be back in 5 or 10 minutes
[23:39:47] <seb_kuzminsky> the splash code runs without a tool
[23:39:54] <seb_kuzminsky> aka, with tool T0
[23:40:00] <trentster> yup
[23:40:05] <seb_kuzminsky> which shows up as a cone, because of reasons
[23:40:28] <seb_kuzminsky> ok
[23:40:37] <seb_kuzminsky> if i'm not still here in 5 or 10 minutes, i'll read back in the morning
[23:48:19] <trentster> seb_kuzminsky: ok you were right!
[23:48:53] <trentster> there were still default imperial tools in half of the tool table. duh! I feel so stupid
[23:48:59] <trentster> thanks for your help
[23:50:19] <seb_kuzminsky> welcome! i'm glad it's working right for you now :-)
[23:50:48] <seb_kuzminsky> that's a nice tutorial, it covers a lot of important stuff
[23:51:10] <trentster> ah thanks - its my first cnc one
[23:51:38] <trentster> I plan to do a couple more LinuxCNC related ones, I think there is a need for some newbie style videos
[23:52:19] <seb_kuzminsky> yeah there sure is
[23:52:26] <trentster> at least now I will have cones in the videos ;-)
[23:52:35] <seb_kuzminsky> :-)