Back
[03:20:51] <CIA-8> 03jmkasunich 07TRUNK * 10emc2/src/emc/motion/ (control.c motion.h): convert homing from edge to level triggered
[04:44:26] <Skullworks-PGAB> " (control.c motion.h): convert homing from edge to level triggered" - any reason why?
[04:45:54] <cradek> to detect errors on machines that have a particular problem - where the home switch is not at the end of travel, so you can get on the wrong side of it
[04:46:36] <Skullworks-PGAB> Kinda like that over ride switch?
[05:00:21] <tomp> jmkasunich: i think i once asked the estimated refresh rate for a servo system under emc.
[05:00:29] <tomp> I'm sure it's a function of cpu speed and thread speed, but iirc, it was a guestimated 5ms ? ( 200 hz ?) Sound reasonable?
[05:00:29] <tomp> (I'm looking at how fast i need to sample the edm gap to develop a new velocity , so nyquist strikes again ;)
[05:01:00] <tomp> servo update rate
[05:01:28] <cradek> even with an ISA servo controller emc can do 1kHz servo cycle
[05:01:45] <cradek> 2-8? kHz is possible with various hardware
[05:01:49] <jmkasunich> the default is 1KHz
[05:02:03] <tomp> guesses on the mesa?
[05:02:23] <cradek> >2
[05:02:26] <jmkasunich> at least
[05:02:49] <tomp> thanks, so i need 2x+ sampling rate, more if i average
[05:02:58] <jmkasunich> not sure I follow
[05:03:17] <jmkasunich> oh, you want to sample the gap volts at 2x EMC's servo rate
[05:03:23] <tomp> yes
[05:03:56] <tomp> i think i need to sample the process faster than i calculate the new velocity
[05:52:59] <CIA-8> 03jmkasunich 07TRUNK * 10emc2/src/emc/motion/ (command.c control.c motion.c motion.h usrmotintf.cc): fix override-limits so it only overrides the limits that have been hit, and prevents further movement in the wrong direction
[05:52:59] <CIA-8> 03jmkasunich 07TRUNK * 10emc2/src/emc/task/taskintf.cc: fix override-limits so it only overrides the limits that have been hit, and prevents further movement in the wrong direction
[06:23:38] <CIA-8> 03cradek 07TRUNK * 10emc2/src/emc/task/taskintf.cc: fix override limits readout on the guis
[07:36:56] <anonimasu> hi
[11:37:47] <a-l-p-h-a2> a-l-p-h-a2 is now known as a-l-p-h-a
[12:41:52] <alex_joni789> logger_emc: bookmark
[12:41:53] <alex_joni789> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emc/2007-06-15.txt
[13:00:13] <alex_joni_> alex_joni_ is now known as alex_joni
[13:22:52] <maddash> level triggering. finally.
[13:29:21] <hcseb> Hi there. My machine has a Y-LOCK actuator, which should be engaged when the Y position has been attained. A good case for synchronised digital output?
[13:29:51] <hcseb> It does this because the Y axis is a big heavy drill assembly which runs on a sloping track.
[13:30:49] <The_Ball_> hcseb, do you know the locking/unlocking times?
[13:31:13] <hcseb> No, I don't
[13:31:49] <alex_joni> hcseb: I suspect you need to make sure emc waits till it is unlocked
[13:31:55] <alex_joni> before it commands motion again
[13:32:04] <hcseb> Ok.
[13:32:13] <alex_joni> hcseb: I would set up a simple ladder
[13:32:17] <hcseb> Ok
[13:32:20] <alex_joni> which sets motion.feedhold
[13:32:28] <alex_joni> then emc2 can't move..
[13:32:40] <hcseb> Ah ha, that's the information I'm after.
[13:33:04] <alex_joni> use y-velocity as an input, if it starts to increase, set the feedhold
[13:33:07] <alex_joni> command the unlock
[13:33:17] <alex_joni> and wait a certain time before letting motion go
[13:33:30] <alex_joni> (at least the theory sounds easy/simple)
[13:33:40] <hcseb> :)
[13:34:00] <alex_joni> hcseb: familiar with HAL?
[13:34:17] <hcseb> motion.feedhold - is that an output from the motion controller? And I'm fairly familiar with the HAL now
[13:34:26] <alex_joni> input to the motion controller
[13:34:48] <alex_joni> motion.in-position (or something like that) is the output
[13:34:55] <hcseb> Ok, So I set motion.feedhold when I have engaged the lock.
[13:35:06] <hcseb> Ah, yes.
[13:35:17] <alex_joni> motion.in-position commands the lock
[13:35:24] <hcseb> *nod*
[13:35:31] <alex_joni> but you need to make sure emc2 doesn't run off while the lock disengages
[13:35:47] <alex_joni> when it needs to move motion.in-position will become false
[13:35:53] <alex_joni> and the lock will start to disengage
[13:35:56] <hcseb> Yes
[13:36:06] <alex_joni> but if in the mean time the Y axis starts to move, it might result in bad things
[13:36:12] <hcseb> Ok
[13:36:28] <alex_joni> so .. you need to prevent emc2 from moving until the lock is disengaged
[13:37:09] <alex_joni> * alex_joni loves his new monitor
[13:37:12] <hcseb> Disengage lock, wait for any motion in the axis, then as soon as some is detected, engage emc motion control?
[13:37:25] <alex_joni> lets say your axis is locked
[13:37:33] <alex_joni> you want to move now (in the program)
[13:37:45] <alex_joni> first detect the movement (YVel != 0)
[13:37:59] <alex_joni> then set motion.feedhold true (prevents emc from any further moves)
[13:38:06] <alex_joni> command disengage lock
[13:38:20] <alex_joni> when disengage lock is finished, program motion.feedhold false
[13:38:26] <alex_joni> then emc2 will start to move
[13:38:36] <hcseb> Ok
[13:38:58] <alex_joni> the only problem is the tiny movement when it detects that Y wants to move
[13:39:08] <hcseb> I feel like I'm going to need to sit down to work this one out
[13:39:08] <alex_joni> just before it blocks with motion.feedhold
[13:39:12] <alex_joni> indeed
[13:39:21] <alex_joni> and sleep on it a couple nights :P
[13:39:56] <hcseb> <- is standing next to the monitor which is awkwardly just to low to view while standing straight up...
[13:41:12] <alex_joni> I got me one of these:
http://www.trustedreviews.com/displays/review/2006/08/03/Samsung-SyncMaster-205BW-Widescreen-Monitor/p1
[13:46:14] <hcseb> Very posh
[13:48:38] <hcseb> Of course, before I get the Y Lock stuff sorted out, I have to work out why it is that I am getting no input signal for the Y axis..
[13:49:15] <alex_joni> from the encoder?
[14:31:08] <alex_joni> bbl
[14:43:38] <lerman_> lerman_ is now known as lerman
[15:56:33] <FanBoyUK> Aww.
[15:56:43] <FanBoyUK> Was hoping this was the channel of the IT company EMC :)
[16:55:22] <x3rox> Hello! Can EMC do an automatic measurement of the tool after a tool change? Would like that after every tool change it automatically moves to a sensor and measures the tool before proceeding with work.
[16:56:06] <jepler> x3rox: with g38.2 (probe) you can measure the length of a tool
[16:56:48] <jepler> x3rox: in emc 2.1 (the latest released version) you can't directly use this length with G43 tool length offsets. You can use G10 L2 ... or G93 ... to change the coordinate system offsets instead of using tool length offsets
[16:57:17] <x3rox> jepler: ?
[16:57:28] <x3rox> Newbee is asking... ;-D
[16:57:35] <jepler> x3rox: in emc 2.2 (the version under development) you will be able to simply give the tool length to G43.1 (transient tool length offset)
[16:59:13] <x3rox> So I initially set the working zero point once and from there all moves are relative, and then I can change tools as often as required without again setting the zero point?
[16:59:40] <x3rox> Sorry for asking possibly stupid, but I habe never used EMC.
[16:59:52] <jepler> x3rox: here's how it works in the development version: you put a switch that can be pressed from above by each tool in the corner of the table
[17:00:09] <x3rox> This is what I want to do.
[17:00:15] <jepler> x3rox: you load the first tool into the spindle and "touch off" to the top of material or otherwise set the Z=0 of the workpiece
[17:00:40] <x3rox> Ok
[17:00:39] <jepler> x3rox: then you use a sequence of moves to go above the switch and then down until the switch trips. This move until the switch closes is a G38.2 "probe" gcode
[17:01:10] <jepler> x3rox: later you put the second tool in the spindle -- it may be a different length
[17:01:29] <jepler> you do the "probe" sequence again, and the difference of those two numbers is the difference in the length of the two tools
[17:02:03] <x3rox> Ok. is then Z=0 again in exactly the same height to me?
[17:02:09] <jepler> you give that number to G43.1 (transient tool length offset) and now when you command Z=0 the tool tip goes to the same place the old tool tip did b efore the change
[17:02:45] <x3rox> All this can be done by a "macro" inside tool-change?
[17:02:57] <jepler> x3rox: in emc 2.1 the G43.1 code doesn't exist yet, so you have to hack around it by modifying a coordinate system offset.
[17:03:28] <x3rox> Well, I will get my mill not before 1-2 months. Is then v2.2 out?
[17:05:05] <jepler> x3rox: you have to explicitly call this code separate from the tool change. You command T1M6 to load tool 1, then the code to find the reference tool length. Later after you load the second tool with T2M6 you include the code to find the difference between the reference tool length and the new tool length
[17:05:53] <jepler> this is done best in an "O-word subroutine", and I think that emc 2.2 will include some feature that makes it fairly simple -- just something like "O1001 call" for the first tool and "O1002 call" for the subsequent tools
[17:06:18] <jepler> x3rox: We haven't chosen a date for emc 2.2, but I hope it will be released this summer. In any case, the upgrade from emc 2.1 to emc 2.2 will be fairly easy for most users.
[17:06:59] <x3rox> Would be great to make a tool change with one command. ;-D
[17:08:34] <jepler> I agree, but realistically emc 2.2 is not going to have such a feature
[17:08:55] <x3rox> Well, I surely will need some time to get the mill working again (must build new electronics,...), then I can play around with it in spolystyrole foam with version 2.1, so I assume I will not be ready before August.
[17:09:23] <jepler> in emc 2.3 I hope someone will choose to work on advanced tool changing stuff -- automatic length detection and tool-pockets-on-table are the two items that seem to be coming up most frequently
[17:09:46] <jepler> right now both can be done through gcode "Onnnn call" but not through a simple "Tn M6"
[17:10:44] <x3rox> jepler: as long as "O1001" is the only thing I have to enter, it is one command to me.
[17:11:09] <x3rox> Am I wrong?
[17:11:16] <archivist> * archivist can think of a really evil tool measuring problem
[17:13:07] <jepler> x3rox: depends if your CAM or whatever is generating gcode will be able to write the required Onnn call line
[17:13:59] <jepler> does anyone here know the status of the "O- call from file" feature in trunk? I hope I'm not mistaken about it
[17:19:04] <cradek> duck!
[17:22:15] <JymmmmEMC> QUACK!
[17:24:07] <JymmmmEMC> Is there a way to add a REVERSE switch to common household fans by chance?
[17:25:15] <JymmmmEMC> I'm thinking about getting this breakout board, can anyone see any pros/cons with it?
http://www.cnc4pc.com/Store/osc/product_info.php?cPath=33&products_id=48
[17:31:05] <JymmmmEMC> jmkasunich: are you doing live testing on the mazak machine, then coding to suit?
[17:33:35] <jepler> JymmmmEMC: I notice the silkscreen of the board says "pins 2, 4, 6, and 8 are for high-speed frequency signals"; if your step signal is on odd pins it sounds like they've engineered the board not to work
[17:34:23] <x3rox> jepler: Sorry, had a visitor... If all I have to do is "search & replace" normal tool-select-calls by "O100x", this is easy...
[17:37:04] <JymmmmEMC> jepler: Sorry, I dont quite understand what you mean by "sounds like they've engineered the board not to work" ?
[17:38:54] <archivist> cradek
http://www.archivist.info/search/index.php/Gear_miller started writing up what I think needs probing for a clock gear miller
[17:39:29] <jepler> JymmmmEMC: if you want a high frequency signal on pins other than 2, 4, 6, or 8 it sounds like it may not work, based on that text
[17:39:34] <jepler> (if these are for high frequency, the others must not be)
[17:39:37] <x3rox> Has somebody a really easy tutorial on G-Codes? Would like to lean that when I have time.... PDF preferred.
[17:40:15] <JymmmmEMC> jepler: I know that STEP woulg be hi-freq, but DIRECTION be considered that as well?
[17:40:25] <JymmmmEMC> s/but/would/
[17:41:06] <jepler> x3rox: our gcode manual is
http://linuxcnc.org/docs/2.1/html/gcode/main/index.html with a quick reference
http://linuxcnc.org/docs/2.1/html/gcode.html but neither is really a very good introduction
[17:42:34] <JymmmmEMC> jepler: Thanks, I'll email the guy after I've had a chance to RTFM some more.
[17:42:57] <jepler> JymmmmEMC: I don't see this mentioned in the pdf manual, all I have to go on is the silkscreen
[17:43:18] <jepler> http://www.cnc4pc.com/Store/osc/images/c11r3_1.jpg near the lower right
[17:44:28] <JymmmmEMC> jepler: You make a good point, I did find a couple things lacking in the docs myself. Thus my inquiry. (Yeah, got it open right now =) I already asked him if the SSR can be changed from 10A to 15A too, my spindle takes 12A.
[17:44:33] <jepler> it's also on the board picture in the last page of the pdf manual
[17:45:01] <JymmmmEMC> I do like the fact that almost all IC's are socketed though.
[17:46:22] <x3rox> jepler: Has nobody thought about making a pretty PDF book instead of this very thin appearing HTML "manual" about gcodes?
[17:46:29] <JymmmmEMC> jepler: Silly Question... do YOU see the SCR in that pic (is it the heatsinked left of the fuse?)
[17:46:52] <JymmmmEMC> x3rox: contributions are always welcome =)
[17:46:56] <JymmmmEMC> s/SCR/SSR/
[17:48:50] <x3rox> Is the whole "manual" of g-codes this one HTML file?
[17:53:07] <JymmmmEMC> jepler: On this page
http://cnc4pc.com/Multifunction_CNC_Board.htm at the bottom it says "Check out the scope images at 93.9khz on pins 2-9."
http://cnc4pc.com/C1_Performance.htm
[17:54:25] <JymmmmEMC> I guess s/he doens't love us anymore.
[18:17:06] <JymmmmEMC> Hmmm.... From the manual... Output pins 1,2,3,4,5,6,7,8,9,14,16,17.
[18:17:06] <JymmmmEMC> • Input pins 10,11,12,13,15.
[18:47:14] <CIA-8> 03cradek 07TRUNK * 10emc2/src/emc/kinematics/tp.c: second half of fix for rigid tap being position mode
[19:01:45] <jepler> ^^ we think rigid tapping works, and we're looking for the right tools to actually try it on the mazak
[19:05:28] <skunkworks> I witnessed it. :)
[19:10:15] <archivist> oo cant see it on the web cam
[19:12:28] <skunkworks> I am the guy on the right :) (your right)
[20:07:38] <Roguish> hey there. got a link to the webcam?
[20:08:14] <archivist> http://linuxcnc.org/compile_farm/festcam.shtml
[20:08:32] <Roguish> thanks, got it.
[20:09:33] <Roguish> hey, that mazak? a buddy of mine has 2 of those, running on original controls.
[20:31:25] <skunkworks> whoo hoo -- Rigid tapping works :)
[20:32:01] <archivist> prove it
[20:33:17] <archivist> show us out in the world
[20:34:26] <skunkworks> they are going to take pictures
[20:39:13] <JymmmmEMC> Hey guys, if you have a PayPal or Ebay account, you REALLY should order one of these tokens. They say $5, but when we ordered them, it was free.
https://www.paypal.com/securitykey
[20:39:49] <jmkasunich> 3/8-16, tapped on the mazak, and the bolt fits!
[20:39:54] <JymmmmEMC> My gf got her ebay account hijacked last month, this would have prevented it.
[20:40:06] <JymmmmEMC> http://www.theregister.co.uk/2007/03/21/ebay_hijack_plea/
[20:40:39] <JymmmmEMC> They're in the testing phase, so might limited on the wty they issue out.
[20:41:21] <JymmmmEMC> qty
[20:42:21] <JymmmmEMC> jmkasunich: cool beans!!!
[20:42:44] <JymmmmEMC> Now, if I only knew what RIGID tapping meant =)
[20:43:41] <archivist> head rotating and feeding at the tap screw pitch tap tight in the spindle
[20:44:32] <archivist> add a comma after pitch
[20:50:05] <jmkasunich> just did one in 1/2" thick aluminum plate (the first few were in plastic)
[20:53:19] <archivist> machine taps (spiral)?
[21:00:09] <jepler> emc has done rigid tapping on the mazak -- code is in cvs.
[21:29:14] <alex_joni> jepler: yay
[21:35:48] <skunkworks> alex_joni: hi
[21:40:35] <alex_joni> hey skunkworks
[21:52:01] <jepler> rigid tapping photos:
http://axis.unpy.net/index.cgi/01181942178
[21:53:33] <archivist> just seem em nice, try with a spiral tap in steel next
[21:54:05] <archivist> better at swarf clearing at speed
[21:54:49] <JymmmmEMC> Ok, i'm ignorant here... rigid tapping -vs- what tapping?
[21:56:01] <archivist> loose eg tap in a sliding sleeve
[21:56:34] <jepler> JymmmmEMC: at the bottom the spindle reverses and the tap comes out backwrads
[21:56:37] <jepler> backwards
[22:00:18] <jepler> (beats me; I'm no machinist)
[22:00:55] <jepler> http://www.mmsonline.com/articles/0703rt1.html
[22:02:57] <alex_joni> jepler: does g96/97 show now?
[22:04:51] <robin_sz> jepler, in rigid tapping the controller knows the tap is say, 1.2mm pitch. as the spindle turns, it moves Z down by 1.2mm for every rev, it has to keep it sync'd as it slows at the bottom and then revereses etc
[22:06:54] <jepler> alex_joni: I'll check
[22:07:19] <robin_sz> jepler, basically the Z axis becomes slaved to the spindle
[22:07:19] <alex_joni> I only looked for it to show in the gui
[22:07:27] <alex_joni> didn't check if it really works
[22:07:32] <jepler> robin_sz: yes sounds about right
[22:07:44] <jepler> alex_joni: g96/g97 work mostly
[22:07:56] <alex_joni> you should know :P
[22:08:02] <jepler> we tested it on chris's lathe
[22:08:09] <archivist> next add power sensing on the spindle and then tap wear can be noted
[22:08:31] <robin_sz> and sister tooling would be nice too
[22:08:39] <alex_joni> archivist: there is an input called adaptive feed override
[22:08:54] <alex_joni> basicly you feed an analog input (0..1) to select real time FO
[22:09:10] <robin_sz> alex_joni, no, thats not what he means
[22:09:18] <alex_joni> so you can check for wear, compare with a preset value and use that
[22:09:24] <robin_sz> not control, sensing
[22:09:36] <archivist> its the error signal from the servo drive
[22:10:07] <robin_sz> ?
[22:10:12] <alex_joni> robin_sz: you can probably check speed vs. programmed speed?
[22:10:19] <robin_sz> spindle speed?
[22:10:24] <alex_joni> yeah
[22:10:29] <archivist> a worn tap needs more power
[22:10:34] <robin_sz> its the spindle load that matters
[22:10:44] <archivist> and too much power breaks it
[22:11:59] <robin_sz> alex_joni, most modern CNCs read the actual power (watts) in the spindle ... you set a limit on the tool, and if the spindle exceeds that in a cut, then the tool is declared worn out, it then either:
[22:12:05] <robin_sz> a) stops
[22:12:44] <robin_sz> or b) swaps to a sister tool (if available) .. you can declare certain tool stations to be sisters of other tools, with maybe a differetn tool length offset
[22:13:30] <jepler> alex_joni: yeah it looks like the display is right
[22:13:33] <alex_joni> have you guys ever had issues with dvi monitors?
[22:13:41] <robin_sz> sister tooling is fairly common on machines these days
[22:13:50] <robin_sz> alex_joni, only the price
[22:13:52] <alex_joni> * alex_joni just got a new one, and it turns off from time to time
[22:14:08] <alex_joni> might be the graphics adapter though
[22:14:31] <alex_joni> it just goes blank, and restarts in ~ 1 second
[22:14:34] <robin_sz> or a mobo that can;t really supply enough amps?
[22:14:53] <alex_joni> robin_sz: wouldn't that lock up the machine?
[22:15:16] <robin_sz> probably
[22:15:23] <alex_joni> it is resolution-dependent
[22:15:29] <alex_joni> lower res doesn't do it
[22:15:35] <robin_sz> the AGP and PCIX slots often have a separte on board regulator on the mobo
[22:15:47] <alex_joni> this is agp 8x
[22:16:14] <alex_joni> older dual DVI card
[22:17:05] <alex_joni> anyways.. off to bed now
[22:17:08] <alex_joni> good night all
[22:17:23] <alex_joni> jepler: I didn't manage to make it say G96..
[22:18:41] <jepler> alex_joni: really? the startup should be g96 (spindle in RPM mode)
[22:19:00] <jepler> the alternative is g97 s- d- (spindle in CSS mode, S FPM, maximum D RPM)
[22:19:30] <tomp> fwiw if monitor makes 'clunk' sound, it can be the +12V is overloaded ( similar to de-gauss sound )
[22:19:32] <alex_joni> hmm.. let me check
[22:19:39] <tomp> Rugludallur: I've been studying the NewPlasmaDesign.odg, there's a few connections missing. would your .hal files fill in the missing bits ( eg Position Sel B's select line, AdjustHeight's in0 ...) ?
[22:19:45] <alex_joni> tomp: it's a tft.. no sound from it
[22:19:54] <tomp> k
[22:21:42] <lerman> alex_joni: My tft monitor goes blank if it is too cold in the shop.
[22:21:57] <lerman> It then stays blank until it warms up.
[22:22:21] <lerman> (It's a Xerox LCD display.)
[22:22:32] <alex_joni> lerman: it might be too warm now.. definately not too cold
[22:22:53] <cradek> hi alex
[22:23:03] <alex_joni> hey chris
[22:23:21] <jepler> http://icanhascheezburger.com/2007/06/09/halp-8/
[22:23:47] <cradek> did you see the rigid tapping photos?
[22:24:18] <jepler> alex_joni: er, I guess I had it the wrong way around
[22:24:22] <alex_joni> yup, very nice
[22:24:28] <jepler> g96 s- d- is CSS mode -- e.g., g96 s50 d1200
[22:24:30] <jepler> m3
[22:25:45] <alex_joni> well, if you say it's working .. I'll take your word
[22:25:57] <alex_joni> from the code I looked at it should work :)
[22:36:05] <ds2> more lathe progress?
[22:40:10] <alex_joni> good night all
[22:44:05] <jepler> ds2: not since earlier this week -- we added CSS and FPR
[22:44:27] <jepler> if you're watching the camera, everyone's clustered around it because we're trying to make a tool holder for the mazak -- there aren't any holders for smallish imperial tools
[23:07:31] <lerneaen_hydra> ooh CSS :D
[23:07:38] <lerneaen_hydra> sweet!
[23:39:47] <ds2> camera?
[23:40:03] <ds2> jepler: when are the stock removal canned cycles going in? ;)
[23:40:28] <jepler> ds2: not this fest
[23:40:37] <jepler> ds2: the camera is
http://linuxcnc.org/compile_farm/festcam.shtml
[23:40:39] <ds2> oh :(
[23:41:22] <ds2> where is the fest? looks like someone's shop
[23:41:44] <jepler> http://cnc-workshop.com/
[23:41:57] <jepler> it's a place called Cardinal Engineering in Galesburg, IL, USA
[23:42:02] <ds2> ah
[23:42:03] <Ziegler> ahh... is the galesburg thing going on today?
[23:42:14] <Ziegler> forgot all about it
[23:42:20] <jepler> Ziegler: we've been here all week (some of us since last saturday) but yeah today and tomorrow are the biggest days
[23:42:29] <Ziegler> im only about 20 minutes away
[23:42:31] <ds2> wish the cam put names on everyone ;)
[23:42:35] <jepler> Ziegler: come on down
[23:42:50] <jepler> ds2: you probably saw me, jmkasunich and cradek in the last frame
[23:43:20] <Ziegler> I might manage to come down tomarrow
[23:43:28] <Ziegler> I actually just finished up my machine last night
[23:43:34] <Ziegler> well... 98% finn
[23:43:39] <jepler> Ziegler: what machine is ever 100% finished?
[23:43:56] <Ziegler> http://images.myonlinesite.com/cnc/construct/20070614
[23:43:58] <Ziegler> lol
[23:44:01] <Ziegler> good point
[23:44:13] <jepler> Ziegler: just look for the big blue maxnc, and you'll find the emc folks nearby
[23:44:20] <jepler> if you go elsewhere you'll be invited to do crazy things like buy mach3 :-P
[23:44:34] <jepler> bbl
[23:44:50] <ds2> jepler: the one that is in the crusher or remelt furnance is 100% finished!
[23:46:15] <Ziegler> Jelper disappeared!
[23:46:18] <Ziegler> ;-P
[23:47:32] <jepler> ds2: yep that's true
[23:54:40] <CIA-8> 03jepler 07TRUNK * 10emc2/docs/html/gcode.html: document new gcodes added at fest: rigid tapping, constant surface speed, feed per revolution
[23:59:46] <ds2> need higher rez so I can read your screen }:-)
