Back
[00:00:17] <cradek> open a file, write one byte, seek forward a gigabyte, write another byte, close the file
[00:00:30] <cradek> in unix, this file won't take up a gigabyte on disk
[00:00:40] <cradek> databases are often like this
[01:33:49] <alex_> is that little dc motor really 8KW?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=160128276964&ssPageName=ADME:B:WNA:US:12
[01:34:11] <alex_> alex_ is now known as The_Ball_
[01:35:25] <The_Ball_> and does "Tach: 9.5 V/Krmp" mean that you get 1000rpm per 9.5volts applied?
[01:35:28] <skunkworks> for about a second
[01:35:34] <skunkworks> peak amperage
[01:35:52] <The_Ball_> ah
[01:36:12] <jepler> skunkworks: do you interpret it to say that the continuous is 140V * 10.2A = 1.4kW?
[01:36:26] <skunkworks> yes
[01:36:31] <skunkworks> but that is my opinion
[01:37:19] <jepler> The_Ball_: "tach" is an analog speed output -- it reads 9.5V per 1000 RPM
[01:37:53] <The_Ball_> i just picked up two alu plates 320x220x32 and 320x220x10 of 5083. They will become a vacuum table for pcb milling
[01:38:09] <The_Ball_> jepler, ah, of course a tachometer
[01:39:36] <jepler> so they'd need encoders before they could be used as axes
[01:40:10] <skunkworks> 30,000 rpm. cool
[01:40:57] <The_Ball_> jepler, centaur seems quite knowledgeable about filters, we might put some filters on the inputs designed for the pwm frequency of the pluto
[01:41:52] <skunkworks> hmm - maybe 10A stall is what ever voltage that would be.. Maybe less than 140v. still- pretty scary servos
[01:42:35] <The_Ball_> skunkworks, buld me one of your pwm boards for 1.4kW thanks
[01:43:11] <jepler> The_Ball_: that would be great. is there anything about the pluto's pwm output I should clarify for him?
[01:43:57] <The_Ball_> not really, the pwm frequency is 19.5kHZ right?
[01:44:13] <The_Ball_> does it do 100% duty cycle or 99%?
[01:44:50] <jepler> it can do 100% duty cycle
[01:45:11] <The_Ball_> problem with 100% duty cycle is that the frequency dissaperes
[01:45:31] <The_Ball_> same for 0% of course but that is desirable
[01:45:43] <jepler> if you don't want 100% then set the max-dc parameter.
[01:46:33] <jepler> since the duty cycles (after scaling to internal units) go from -2047 to 2047, you would want to set max-dc to (2046/2047) = .9995...
[01:46:54] <jepler> and adjust gain by the same fraction
[01:47:10] <jepler> that is, if you want "the largest duty cycle less than 100%"
[01:47:10] <The_Ball_> yes, that
[01:47:38] <The_Ball_> yes, that's perfect, then a narrow filter at 19.5kHZ would reject noise very effectively
[01:48:13] <jepler> the pluto has another option, at least for now: interleaved PWM
[01:48:42] <The_Ball_> is that the PDM? I don't know how that signal looks
[01:48:50] <jepler> yes
[01:49:58] <jepler> for "interleaved pwm" the upper bits in the pwm counter are rearranged before they are compared to the pwm duty cycle
[01:51:51] <jepler> for duty cycles less than 50%, the "on" times are 4 cycles of the 40MHz clock (so 10MHz/10ns) (except for at most one "runt" on time per 19.5kHz) and the "off" times are a variable number of cycles. For duty cycles above 50%, it is the opposite with off times being 4 cycles.
[01:53:00] <jepler> I was originally told a mode like this was useful for conversion to analog, but I don't know if my implementation choices (such as the number of bits to interleave, which determine the length of the mini cycles) were appropriate
[01:53:05] <The_Ball_> on thing, is the pwm signal hardware generated or by the firmware. down the line if the firmware is updated will the pwm frequency change?
[01:53:58] <The_Ball_> jepler, i am totally unfamiliar with this PDM mode
[01:54:00] <jepler> the signal is generated by the fpga firmware, so within the constraints of the chip resources it can be changed
[01:54:14] <jepler> do you have a machine that can run emc?
[01:54:19] <jepler> in simulator mode, even
[01:54:22] <jepler> handy
[01:54:42] <The_Ball_> not right now, im at work
[01:54:51] <jepler> OK let me see if I can make you a screenshot
[01:55:08] <jepler> emc's "pwmgen" in PDM mode is similar (but not exactly the same as) what pluto does in this mode
[02:00:03] <The_Ball_> i have been meaning to do a 2.2 checkout, it might be time
[02:01:05] <skunkworks> I would thing the h-bridge should do 1.5kw.... 150v and 10a
[02:01:30] <skunkworks> think
[02:01:36] <The_Ball_> yes, i guess with the proper fet's, what is the rating of yours?
[02:01:53] <skunkworks> 500v 44a. but that is not really possible.
[02:02:19] <skunkworks> I am hoping for around 150v 20a with some peak power,
[02:02:23] <The_Ball_> sure it is, and you get a nice pyrotechnics show
[02:03:17] <jepler> The_Ball_:
http://emergent.unpy.net/index.cgi-files/sandbox/pwm-pdm-analog.png -- from top to bottom, pwm; pdm; produced from analog input
[02:03:29] <Jymmm> jepler:
[02:03:32] <toastydeath> fancy!
[02:03:52] <Jymmm> jepler: I found those motors you used for the etch a sketch..... $3/ea and ~50 available
[02:04:00] <Jymmm> new old stock
[02:04:19] <The_Ball_> jepler, thanks, studying it now
[02:04:28] <jepler> Jymmm: don't buy too many before making sure they're adequate for even the toy needs
[02:04:32] <jepler> Jymmm: but, cool
[02:04:56] <skunkworks> backlash is a problem with those motors - isn't it?
[02:05:02] <jepler> skunkworks: not the servos, the "pancake steppers"
[02:05:07] <skunkworks> ah
[02:05:16] <jepler> if Jymmm had found those servos for $3 I'd be first in line to buy more
[02:05:23] <skunkworks> ;)
[02:06:03] <Jymmm> heh
[02:06:39] <jepler> The_Ball_: in pwm, you have to wait on average 50% of the pwm cycle (e.g., ~50uS) before the output goes the opposite way; over a full period, the average output is the desired value
[02:06:46] <Jymmm> Yeah, sorry... no such luck there. Though I did find some VERY nice enclosures for the new controller, bought the last two they had.
[02:07:17] <jepler> The_Ball_: in pdm, you wait a much smaller amount of time, except when the desired value is most extreme (close to 0% or 100%)
[02:07:38] <The_Ball_> jepler, yes, the pdm signal appears as a pwm signal at a much higher frequency
[02:07:48] <jepler> http://en.wikipedia.org/wiki/Pulse-density_modulation
[02:08:18] <Jymmm> hey, are GE faunic programmable controllers any good?
[02:08:18] <The_Ball_> which is a good thing in analog conversion, less ripples
[02:08:25] <Jymmm> if so, what are they?
[02:08:41] <The_Ball_> Jymmm, which series of controllers?
[02:08:57] <Jymmm> The_Ball_: sorry, no clue... black
[02:09:00] <jepler> Jymmm: beats me whether they're any good, but they are CNC controllers -- the same thing emc does
[02:09:07] <Jymmm> jepler: Ah
[02:09:27] <Jymmm> These were about 5" tall 4" wide and 6" long
[02:09:36] <skunkworks> we have a ge fanuc controller at work running the laser
[02:10:01] <toastydeath> pew pew pew
[02:10:02] <Jymmm> skunkworks: how do you program it?
[02:10:13] <Jymmm> or it is like a one time thing.
[02:10:24] <toastydeath> fanuc is uh
[02:10:31] <toastydeath> an amazing controller
[02:10:41] <toastydeath> in general
[02:10:41] <skunkworks> It has ladder logic in it - but it is a machine controller.
[02:10:45] <Jymmm> The_Ball_: what series should I be looking for?
[02:10:55] <skunkworks> takes gcode and runs axiss
[02:11:06] <Jymmm> oh takes gcode directly????
[02:11:09] <skunkworks> yes
[02:11:11] <toastydeath> yes
[02:11:27] <toastydeath> they're what you see on the front of a lot of commercial cnc machines
[02:11:28] <Jymmm> well, shit.... maybe I need to head back and take a closer look
[02:11:43] <jepler> they're not compatible with emc gcode though
[02:11:52] <jepler> dunno why you'd want something that isn't compatible with rs274ngc
[02:11:51] <toastydeath> there's a reason fanuc g-code is like, an industry standard
[02:12:02] <The_Ball_> Jymmm, i have some s2k controllers, they are fully programmable motion controllers, over kill for running something with emc, but very happy with them
[02:12:03] <jepler> (I'm trolling just a bit when I say that)
[02:12:40] <toastydeath> most controllers have a fanuc g-code compatability mode
[02:12:44] <Jymmm> The_Ball_: silly question, but why would you run them with emc?
[02:13:05] <The_Ball_> they are motion controllers, they do not accept gcode
[02:13:23] <Jymmm> * Jymmm scratchs head
[02:13:30] <skunkworks> ?
[02:13:37] <toastydeath> motion control and machine control are different
[02:13:59] <Jymmm> 19:11:08) Jymmm: oh takes gcode directly????
[02:13:59] <Jymmm> (19:11:11) skunkworks: yes
[02:13:59] <Jymmm> (19:11:13) toastydeath: yes
[02:14:05] <The_Ball_> so you program it to control a servo motor to do a specific task depending on the logical inputs, then leave it
[02:14:07] <toastydeath> his s2k controllers
[02:14:12] <toastydeath> are motion controllers
[02:14:13] <jepler> s2k != fanuc ?
[02:14:44] <toastydeath> we were talking about fanuc machine controllers and switched to motion control, i thought
[02:14:50] <toastydeath> or am i high
[02:14:53] <jepler> beats me
[02:15:14] <toastydeath> Fanuc's crap is usually labeled like "18T"
[02:15:14] <jepler> if you told me your bridgeport was made by chevrolet I wouldn't know if you were telling the truth or pulling my leg
[02:15:19] <Jymmm> ok, so motion control is what?
[02:15:21] <The_Ball_> s2k != machine controller, yes
[02:15:46] <toastydeath> i don't know anything about motion controllers, just machine controls
[02:15:58] <The_Ball_> Jymmm, a fancy PLC with a servo attached
[02:16:21] <Jymmm> The_Ball_: no drive in between?
[02:17:34] <The_Ball_> the motion controller is the drive and a fully programmable PLC running some realtime os
[02:18:09] <Jymmm> ah, ok. making more sense now.
[02:18:24] <toastydeath> a programmable machine control is a g-code thingy that allows you to customize what it does
[02:18:32] <toastydeath> versus a dedicated mill or turn unit
[02:18:53] <The_Ball_> Jymmm, here is a picture
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=180119980489&fromMakeTrack=true&ssPageName=VIP:watchlink:middle:us
[02:19:38] <toastydeath> could I use a motion controller between EMC and a servo
[02:19:46] <toastydeath> to preform additional error correction on an axis?
[02:20:17] <The_Ball_> these support a secondary encoder yes, so you get servo stability and correct possitioning
[02:20:43] <toastydeath> hot
[02:21:00] <The_Ball_> have a look in the manual, it's on page 500 or something ;)
[02:21:04] <jepler> toastydeath: in principle, emc can use anything that can take a position command at the servo rate, and return a position feedback at the same rate -- but you have to write the driver if it's something exotic and new
[02:21:20] <toastydeath> jepler: i'm talking about multiple sources
[02:21:57] <Jymmm> The_Ball_: yeah, those ar enothing like these at all
[02:22:25] <The_Ball_> yes, but it seems you guys were talking about machine controllers which is different
[02:22:38] <The_Ball_> g-code accepting devices
[02:22:48] <toastydeath> a big ass control panel with wires hanging out the back
[02:23:00] <toastydeath> bunch of switches, etc
[02:23:38] <The_Ball_> jepler, PDM seems to be the way to go for faster response in the PDM-analog conversion'
[02:23:53] <The_Ball_> jepler, allows for a smaller RC delay
[02:24:09] <jepler> The_Ball_: I guess maybe I should talk to centar about how to make the PDM mode most useful for a digital-to-analog converter. However, the PDM mode might not be useful to you personally, because it has to be enabled for all PWM outputs or for none, and I seem to recall that one of your motors was PWM input and the others were analog input...
[02:24:18] <jepler> er, centaur
[02:25:08] <The_Ball_> jepler, I am building a H-Bridge for the Z axis yes. The PDM mode switches to quickly for the FET's I guess
[02:26:16] <jepler> right now it is effectively 10MHz, way too fast for FETs
[02:26:54] <jepler> if centaur thinks a different rate (I could easily choose any 40MHz / 2^n) would be a better compromise for filters, I'll change to his suggestion
[02:27:03] <The_Ball_> what's the --enable-run-in-place .configure parameter do exactly?
[02:27:18] <jepler> do you mean, what's the use? or how does it work?
[02:27:41] <The_Ball_> what behaviour does it change?
[02:27:51] <jepler> with --enable-run-in-place, you don't "make install". instead you ". scripts/emc-environment" in each terminal window before running emc, halrun, etc
[02:28:11] <The_Ball_> ah, i see
[02:28:13] <jepler> it means that you don't need to install any files outside the emc2 tree you got from the cvs checkout
[02:28:43] <jepler> it's very useful to developers because we often have several source trees on a single system
[02:29:14] <jepler> it's also a good idea for anyone who wants to install a .deb package of emc and also compile another version, for whatever reason
[02:29:29] <The_Ball_> yes, very nice indeed
[02:29:44] <jepler> (otherwise, "make install" will overwrite some files from the package [files in /etc] even though the package has prefix=/usr and the other version probably has prefix=/usr/local)
[02:37:18] <The_Ball_> jepler, just to state the obvious, in pdm mode there is still one up and one down channel, right
[02:38:50] <jepler> The_Ball_: yes
[02:39:58] <jepler> if you wanted, you could set scale and offset with knowledge of the input range so that an output signal only appeared on one channel
[02:40:17] <jepler> you can also set the "pwm+direction" mode for pdm
[02:41:22] <The_Ball_> ok
[02:41:41] <The_Ball_> i have never run emc on a quick machine, this is nice, time to upgrade the hardware i think
[02:43:15] <The_Ball_> the limits bounding box in 2.2 looks very nice
[02:43:32] <jepler> I agree
[02:51:16] <CIA-8> 03jmkasunich 07v2_1_branch * 10emc2/docs/src/hal/drivers.lyx: document revisions to the 5i20 driver (index fixes)
[02:52:28] <jepler> 'night all
[02:53:10] <skunkworks> jepler: night
[02:56:38] <The_Ball_> night
[02:57:37] <toastydeath> fff.
[02:59:35] <Skullworks-PGAB> here is an off beat question
[02:59:46] <toastydeath> there might be an off beat answer!
[03:00:12] <The_Ball_> ok, that's enough beating off
[03:01:25] <toastydeath> agreed
[03:01:27] <CIA-8> 03jmkasunich 07TRUNK * 10emc2/docs/src/hal/drivers.lyx: document changes to 5i20 driver to make indexing work
[03:02:00] <Skullworks-PGAB> can i have EMC move to a location X-Y-Z then call a user defined M function that takes over Z axis movement externally but watches the encoder count until a specified target value is reached - then EMC takes over again.
[03:02:17] <toastydeath> oooooh
[03:02:20] <toastydeath> tracer?
[03:02:25] <Skullworks-PGAB> EMD
[03:02:27] <Skullworks-PGAB> EDM
[03:02:30] <toastydeath> o
[03:03:17] <Skullworks-PGAB> use EMC for positioning
[03:03:40] <Skullworks-PGAB> including a G43 offset for electrode
[03:04:20] <Skullworks-PGAB> then let the EDM handle spark control / flushing infeed
[03:06:10] <Skullworks-PGAB> until Z axis has done the programed amount - then rapid out and prep for M6 of next electrode (assumes a multi burn to compensate for erosion.)
[03:07:28] <cradek> the only move emc can make that ends up in an undetermined place, and then recover from, is a probe move G38.2
[03:07:48] <Skullworks-PGAB> maybe a do / while loop?
[03:08:08] <cradek> if you could issue a probe move, and then use adaptive feed to control the speed, and then hit the probe button when done, ...
[03:08:08] <jmkasunich_> jmkasunich_ is now known as jmkasunich
[03:10:30] <toastydeath> beep
[03:12:00] <Skullworks-PGAB> cradek: this would leave the encoder feedback live - just routing the motor control to the voltage sense circuit.
[03:12:47] <Skullworks-PGAB> then once the Z target is attained the motor control switches back to EMC
[03:14:44] <Skullworks-PGAB> the chosen GUI would show the Z axis movement.
[03:15:54] <Skullworks-PGAB> kind like when the servos are in e-stop but encoders are powered and you manually crank a table - encoders continue to act as a DRO
[03:16:46] <cradek> yeah the only time emc will follow the encoders and not give a following error is when in "machine off" state
[03:17:25] <Skullworks-PGAB> and I guess there isn't a way to isolate a single axis
[03:17:26] <cradek> I don't see an easy way to do what you want - if you aren't using emc's commanded position, you'll get a following error
[03:17:59] <The_Ball_> is there no way a hal command can specify a position of a axis?
[03:18:35] <cradek> people have done this kind of thing in HAL but they have to "lie" to emc to pretend the axis hasn't moved
[03:18:44] <Skullworks-PGAB> OK - just have to run dual Z axis
[03:18:46] <cradek> the DRO behavior on one axis is not possible
[03:19:14] <Skullworks-PGAB> EMC would not be aware of the second slide
[03:19:24] <cradek> well, anything's possible, the program is yours :-)
[03:19:32] <cradek> but not everything is simple
[03:19:43] <skunkworks> in my mind - I was thinking of a loop that would check a bit. 0 would be go further in - 1 runs it out. The bit would be controlled by the setpoint of the arc voltage. each time tthru the loop - emc would advance or retract by an amount like .0001
[03:20:06] <skunkworks> but that might be too simple.
[03:20:22] <cradek> do you mean a gcode loop?
[03:20:25] <skunkworks> yes
[03:20:35] <Skullworks-PGAB> thats not a problem - the EDM has its own internal voltage comparator to handle infeed
[03:20:39] <cradek> gcode can't check inputs like that
[03:20:45] <skunkworks> damn
[03:21:18] <cradek> this is sinker?
[03:21:19] <skunkworks> I thought you could set or check I/o
[03:21:28] <cradek> set, yes - check, no
[03:21:34] <skunkworks> hmm
[03:21:41] <skunkworks> well then - never mind :)
[03:21:53] <Skullworks-PGAB> the hope was that I could use a single servo and read the encoder to know how far from the first "short" the infeed had gone
[03:21:59] <Skullworks-PGAB> sinker
[03:23:27] <Skullworks-PGAB> then at the defined depth the feedback loop for the edm is switched off and the servo retracted by EMC
[03:31:24] <The_Ball_> where on the scale is 20LPM of vacuum? It's for a vacuum table to hold pcb's, but 20LPM doesn't mean anything to me
[03:32:18] <Skullworks-PGAB> 20 liter per min?
[03:32:32] <The_Ball_> must be
[03:32:32] <Skullworks-PGAB> flow rate?
[03:32:37] <The_Ball_> free flow rate
[03:32:54] <The_Ball_> oh, per head, so it's 40 in parallel
[03:33:00] <The_Ball_> http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&item=190126336923&fromMakeTrack=true&ssPageName=VIP:watchlink:middle:au
[03:36:08] <skunkworks> we are using a 1hp vane pump... To much? ;)
[03:36:23] <skunkworks> no clue on the specs
[03:36:32] <skunkworks> some millitary surplus
[03:37:08] <The_Ball_> hehe, that should do the job
[03:38:27] <skunkworks> oh well - bed time. :)
[03:38:32] <The_Ball_> night
[03:38:32] <skunkworks> night
[03:39:03] <Skullworks-PGAB> hmmm
[03:39:40] <Skullworks-PGAB> what about some crazy Osub to handle the servo movement
[03:39:54] <Skullworks-PGAB> a do /while loop
[03:40:36] <Skullworks-PGAB> and a check of an input pin
[03:41:15] <Skullworks-PGAB> incrament a G91 z#1
[03:41:54] <Skullworks-PGAB> +/- .0001" per check, then reloop
[03:43:34] <Skullworks-PGAB> neat part is you could actually improve retrack flushing
[03:44:59] <Skullworks-PGAB> I think I'll write this up as a NGC file in proper syntax then post it for feedback
[03:52:01] <cradek> we went over that - read above :-)
[03:52:39] <cradek> (summary: you can't read hal inputs in gcode)
[03:52:56] <cradek> goodnight all
[03:53:51] <The_Ball_> night
[03:53:54] <Skullworks-PGAB> right - but this takes the output signal the would normally control the feed by the EDM and uses it to report a T|F condition to EMC, which in the do loop
[03:54:15] <Skullworks-PGAB> will handle the movement
[03:54:38] <Skullworks-PGAB> SO EMC is now doing all the servo movement
[07:00:09] <alex_joni> Skullworks-PGAB: EMC can't read the T/F condition
[07:16:43] <Jymmm> Uh huh
[08:26:41] <anonimasu> 0hi
[08:26:58] <Jymmm> vey
[08:30:14] <anonimasu> what's up+
[08:30:15] <anonimasu> ?
[08:30:56] <Jymmm> nada at the moment. Got some enclosures today though, so I'm jazzed =)
[08:31:37] <Jymmm> They're even rack mountable too
[08:32:08] <anonimasu> ok
[08:32:10] <anonimasu> :)
[08:32:20] <anonimasu> I'm trying to get around to machining a fibreglass mold..
[08:32:39] <Jymmm> I hope the material you're maching isn't fiberglass
[08:33:11] <anonimasu> why not?
[08:33:20] <anonimasu> *grin*
[08:33:22] <anonimasu> just kidding..
[08:33:24] <Jymmm> obvious reasons
[08:33:46] <Jymmm> unless of course your masicistic, then GO FOR IT!!!
[08:33:55] <Jymmm> BREATH DEEPLY
[08:34:10] <Jymmm> take all your clothes off and rub your body againest it!
[08:35:04] <anonimasu> yep
[08:37:31] <anonimasu> I'm going to machine that blue foam stuff..
[08:38:01] <Jymmm> I hope you have a GREAT vac system
[08:38:10] <Jymmm> and HUGE tank =)
[08:42:54] <anonimasu> nope...
[08:43:22] <Jymmm> you'll need it =)
[08:43:45] <anonimasu> ffs..
[08:43:58] <anonimasu> just a vaccum cleanre..
[08:44:01] <anonimasu> cleaner..
[08:44:01] <Jymmm> I'm not kidding.... the stuff goes everywhere.
[08:44:06] <anonimasu> why do you make everything so damn hard?
[08:44:21] <Jymmm> Hey, it's your crap, what do I care =)
[08:44:48] <Jymmm> I only make and sell foam cutters =)
[08:45:20] <anonimasu> and?
[08:45:24] <anonimasu> I build machines and program plc
[08:45:25] <anonimasu> 's
[08:45:28] <anonimasu> for a living..
[08:45:38] <Jymmm> and your point is?
[08:46:01] <anonimasu> none whatsoever..
[08:46:22] <Jymmm> Okey then, gawd damnit! LOL
[08:46:31] <anonimasu> and that was the whole point of it ;)
[08:46:40] <anonimasu> now to get this stupid device to sync
[08:46:49] <Jymmm> you just said you dont have a point, make up your dman mind already!
[08:47:07] <Jymmm> Eeeeeesh, kids these days
[08:50:04] <Jymmm> what device?
[08:52:00] <anonimasu> a windows ce computer..
[08:52:05] <Jymmm> ah
[08:55:38] <anonimasu> http://www.cc-systems.com/en/onboard-pc/images/stories/CCPXLII.jpg
[09:29:36] <Jymmm> anonimasu: what is it, an lcd?
[10:07:20] <anonimasu> it's a computer..
[10:11:00] <anonimasu> hey The_Ball
[10:19:26] <alex_joni> hi guys
[10:19:42] <alex_joni> anders, how is it up there? nice & cool?
[10:23:17] <The_Ball> hey anonimasu
[10:39:03] <anonimasu> yeah
[10:39:06] <anonimasu> today it's very cold :/
[10:44:25] <alex_joni> we're struggling with 36+ here :((
[10:44:36] <alex_joni> wanna change?
[10:47:16] <anonimasu> sure
[10:47:24] <anonimasu> my body hurts like hell from this weather
[10:47:37] <anonimasu> it's been around 20 - 30c other days
[10:57:48] <anonimasu> :)
[10:57:55] <anonimasu> alex_joni: done anything cool lately?
[11:15:53] <alex_joni> not much
[13:35:30] <danielbr> hello, Alexjoni: It seems there isn't a halui.program.stop, any chance for create a new one?
[14:19:27] <The_Ball> did I hear that EMC2 is known to run better on "older" hardware like P4's or is there no truth in that?
[14:20:38] <anonimasu> it all depends on how rt-friendly your chipset is..
[14:20:43] <jepler> The_Ball: P4 is now "older hardware"? That's news to me
[14:20:43] <cradek> my experience is that P3 machines are very good for realtime performance
[14:21:02] <cradek> good morning
[14:21:08] <jepler> hi cradek
[14:22:12] <The_Ball> jepler, sure isn't new ;)
[14:22:41] <cradek> oh, I assumed that was a typo
[14:23:31] <The_Ball> cradek, when you say "good for realtime performance", are you referring to the lowest guarantied latency?
[14:23:44] <jepler> or having acceptable max latency at all
[14:23:50] <cradek> yes both
[14:24:26] <cradek> some machines don't work with realtime at all like jepler says - that doesn't seem to happen with P3 machines
[14:24:31] <The_Ball> so newer hardware, even though it has more throughput, sometimes have higer latency?
[14:24:36] <cradek> yes
[14:24:39] <The_Ball> I see
[14:24:40] <anonimasu> The_Ball: yes
[14:25:58] <jepler> Pentium 4 and newer offerings from Intel frequently use something called "SMI" for power and thermal management, which can cause long interruptions at regular intervals (e.g., 2ms every 64s on one developer's board)
[14:26:13] <jepler> there are chipset-specific ways to disable this, a collection of them is in the module rtai_smi.ko
[14:26:24] <The_Ball> auch
[14:27:05] <archivist> bring back the 6502
[14:27:18] <cradek> my dual P3 system has a max latency of about 10us, or 5us if one cpu is isolated
[14:27:31] <The_Ball> 6510 for me thanks
[14:29:14] <cradek> it's a great realtime system and cost me about $150
[14:29:32] <The_Ball> very nice, but is axis very slow with larger jobs?
[14:30:08] <cradek> it's acceptable for whatever I have done, but I suppose there is always a job large enough to make it slow
[14:30:41] <The_Ball> i was thinking of pcb's, they can have lot's of code
[14:30:46] <anonimasu> heh..
[14:30:50] <anonimasu> now try 3d contouring.
[14:31:01] <anonimasu> ^_^
[14:31:11] <The_Ball> oh, yeah i guess, haven't gotten to that stage yet ;)
[14:32:01] <The_Ball> i picked up the alu for my vacuum table, 320x220x42mm... i think i went and did a overkill again
[14:32:07] <jepler> there are two tricks to know if you have large gcode files: First, put a comment (AXIS,stop) to make the automatic preview only display up to that point in the file. Second, hit the "clear backplot" button from time to time, and/or change MAX_POINTS in emcmodule.cc and recompile to have the backplot automatically trim itself more frequently
[14:32:51] <The_Ball> ah, very handy, i knew about clearing the backplot
[14:33:24] <cradek> 42mm seems like a lot
[14:33:59] <anonimasu> yeah
[14:34:00] <anonimasu> :)
[14:34:02] <The_Ball> yes, two plates, one 32mm and one 10mm, that way i can machine the insides of the table... but it's going to be a big lump
[14:34:06] <anonimasu> it'll take forever to machine ;)
[14:35:01] <The_Ball> i will complete the machine enclosure before i start machining that for sure
[14:35:30] <jepler> oh, I forgot this great intel thermal management feature: if the CPU is heating up, the clock is turned off for up to 3.0 microseconds at a time. (
http://download.intel.com/design/Pentium4/datashts/30235104.pdf page 79)
[14:35:48] <cradek> arg
[14:36:08] <anonimasu> jepler: atleast it dosent fry your cpu as much as the athlon thermal management ;)
[14:36:33] <jepler> ah but the AMD CPU will keep position right up until it fires the heatsink through the hard drive and sets off an atomic bomb explosion
[14:36:39] <The_Ball> wow, i assumed it reduced the clock frequency. i remember when the feature was introduced, they played quake at tomshardware and removed the cpu cooler while playing the game
[14:36:43] <jepler> now which is better, I ask you?
[14:37:28] <anonimasu> I perfer my meat hot but not fried.
[14:38:32] <anonimasu> just kidding
[14:39:04] <anonimasu> brb
[14:39:05] <anonimasu> going home
[14:41:51] <bill2or3> Mmmmhome
[17:38:02] <toastydeath> beep
[17:38:28] <archivist> finished bleeding yet?
[17:40:28] <toastydeath> yes!
[17:40:30] <toastydeath> it is healing well
[17:40:38] <toastydeath> i crashed a machine AGAIN at work
[17:40:39] <toastydeath> i really hate this control
[17:40:47] <toastydeath> it is too user-friendly
[17:40:51] <toastydeath> it throws me off
[17:41:23] <bill2or3> quit clicking the button labled "Crash"
[17:46:39] <toastydeath> i would prefer to stare at a cold, green CRT
[17:46:45] <toastydeath> with cryptic letters on them
[17:46:53] <toastydeath> not "mill line"
[17:47:18] <toastydeath> staring at 10 lines, with the exact same text on them
[17:47:23] <toastydeath> does not differentiate what you are about to do
[18:49:10] <CIA-8> 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: fix mouse jogging, maybe without breaking anything
[18:49:38] <cradek> crap
[18:50:11] <ds2> this is one up on a hamster wheel huh? ;)
[18:50:16] <jepler> cradek: commit, then test?
[18:50:34] <cradek> :-P
[18:50:52] <cradek> how many ways do we need to jog anyway
[18:51:24] <ds2> just one more ;)
[18:51:55] <ds2> * ds2 waits for the "hamster barbell weights" commit
[18:53:07] <JymmmmEMC> Mouse jogging? Sounds icky for some reason
[18:53:09] <archivist> hmm where do I fit the hamster to my hobbymat lathe?
[18:53:26] <JymmmmEMC> archivist: You dont' want to know
[18:54:17] <archivist> it may improve said lathe enough to make it useable
[18:59:55] <JymmmmEMC> archivist: NSFW
http://www.realhamster.com/
[19:01:00] <archivist> hehe
[19:01:33] <JymmmmEMC> archivist: When I say you don't want to know, I mean you REALLY DONT WANT TO KNOW! =)
[19:07:43] <CIA-8> 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: -/= jogging doesn't work for now
[19:10:08] <archivist> why hobbymat is crap, cross slide hand wheel calibrated 0-9, screw is 1.25mm pitch
[19:10:47] <cradek> ouch
[19:11:16] <archivist> was just taking it to bits as a cnc donor
[19:11:40] <archivist> I have hated it for a while
[19:11:58] <JymmmmEMC> This?
http://www.mike-willis.com/hobbymat.html
[19:13:08] <archivist> yes thats the ugly b.....
[19:13:29] <archivist> I have a long list of faults
[19:13:50] <JymmmmEMC> So, you cna't print out a label and attache it to the wheels?
[19:14:30] <JymmmmEMC> I actually have a program for printing rulers like that btw
[19:14:38] <archivist> heh that poor bloke thinks its good
[19:15:56] <archivist> I suppose he has never used a schaublin or southbend etc
[19:16:45] <JymmmmEMC> archivist: And like you have </troll>
[19:17:33] <anonimasu> lol
[19:18:23] <anonimasu> toastydeath: well, run TKEMC instead :)
[19:18:45] <JymmmmEMC> Man I hit the jackpot yesterday, and all the odd ball stuff I've been looking for that (for some reason) is been hard to find; Enclosures, 15A IEA 15A filtered socket, 2.5" cap clamps
[19:18:56] <anonimasu> toastydeath: oh didnt read sorry
[19:26:51] <CIA-8> 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: back to v2.1's operation which worked best so far. too many ways to jog.
[19:48:23] <JymmmmEMC> archivist: I was just playin, no need to take your ball and run home ;)
[19:48:49] <archivist> still attacking crap hobbymat
[19:48:58] <JymmmmEMC> oh, lol
[19:49:08] <ds2> hobbymat is a fine lathe =)
[19:49:26] <archivist> contemplating is it worth doing anything with
[19:49:37] <archivist> its rubbish
[19:49:54] <JymmmmEMC> do you have to re do the ways on it?
[19:50:09] <anonimasu> ds2: schaublin is a fine lathe..
[19:50:10] <anonimasu> ;)
[19:50:24] <archivist> "ways" its a flatted round bed
[19:50:35] <ds2> anonimasu: the hobbymat is better then the 7x10's out of thebox
[19:51:05] <JymmmmEMC> archivist: then take it to the scrap yard for $5 (you pay them), then get on with life!
[19:51:33] <archivist> anonimasu, we have a few schaublins here but too good to attack
[19:51:43] <anonimasu> archivist: ;)
[19:51:52] <JymmmmEMC> archivist: do you have the mill attachment for it?
[19:51:57] <archivist> no
[19:52:13] <JymmmmEMC> might have been nice for a 4th axis
[19:52:14] <anonimasu> archivist: taking them apart is amazing :)
[19:52:37] <archivist> the hobbymat its no way sturdy enough to use for milling
[19:52:57] <anonimasu> archivist: it's made by retired watchmakers.. :)(must be)
[19:53:03] <ds2> sure it is... mill foam for lost foam casting
[19:53:14] <anonimasu> heh
[19:53:29] <archivist> I like my swarf to fly over the tailstock
[19:53:43] <JymmmmEMC> archivist: Ah, so you're just in a rant and rave mode, gotcha! (Must be PMS - Pre Machinable Status)... Carry On!
[19:53:56] <anonimasu> hehe
[19:56:09] <Unit41> tee hee heheh
http://rapidshare.com/files/39514465/Building_The_TESLA_Turbine_LQRS.pdf.html
[20:21:15] <CIA-8> 03alex_joni 07TRUNK * 10emc2/src/emc/usr_intf/halui.cc: add halui.program.stop (it does the same thing as halui.abort, and helps only for consistency in naming)
[20:22:58] <JymmmmEMC> has anyone machined HDPE?
[20:23:19] <CIA-8> 03alex_joni 07TRUNK * 10emc2/docs/man/man1/halui.1: update manpage with halui.program.stop
[20:23:19] <toastydeath> test a peice with kerosene
[20:23:26] <JymmmmEMC> ?
[20:23:27] <toastydeath> if it doesn't mess the surface up, use kerosene.
[20:23:32] <toastydeath> as a lubricant
[20:23:35] <toastydeath> it will cut fine.
[20:23:58] <JymmmmEMC> toastydeath: you and your kerosene
[20:24:04] <toastydeath> i'm not kidding dude
[20:24:06] <archivist> it works
[20:24:39] <toastydeath> if you don't have a specific lubricant for plastics, kerosene works amazing for aluminum and plastics
[20:24:52] <JymmmmEMC> so does diesel fuel
[20:24:59] <toastydeath> uh
[20:25:04] <toastydeath> i've never heard that
[20:25:05] <skunkworks> pretty close to the same thing
[20:25:32] <toastydeath> but what are your questions about hdpe
[20:25:54] <JymmmmEMC> Yeah, when you can't get a car on the towtruck, pour diesel fuel on the ramp, real slick then =)
[20:26:27] <JymmmmEMC> does HDPE hold it's shape, or sorta kind "warps" distorts?
[20:26:33] <JymmmmEMC> when machined
[20:26:35] <toastydeath> don't know
[20:26:58] <toastydeath> it also depends on how you want to define "warping"
[20:27:10] <JymmmmEMC> distort is a better word
[20:27:20] <toastydeath> it will be very suceptible to thermal effects and workholding
[20:27:29] <toastydeath> i don't know if there's an internal creep effect to hdpe, but i have not heard of anyone mention it
[20:28:03] <JymmmmEMC> Hmmm, maybe I'll grab a piece of ABS instead
[20:28:14] <toastydeath> you're going to need to worry about those things with any plastic
[20:28:27] <toastydeath> especially if you are milling it
[20:28:30] <JymmmmEMC> I have tooling made for plastics.
[20:28:52] <toastydeath> that doesn't affect your thermal load or workholding
[20:29:10] <toastydeath> well, i guess it does, but not in a substantial way
[20:29:23] <toastydeath> what size cutters
[20:29:25] <toastydeath> and how fast is your machine
[20:29:51] <JymmmmEMC> they're designed to prevent melt back. 150MPH in 2.4s
[20:30:06] <toastydeath> uh, what tool is measured in mph
[20:30:19] <JymmmmEMC> you asked how fast the machine is
[20:30:23] <toastydeath> spindle speed, duh
[20:30:31] <JymmmmEMC> you want rpms, ips,
[20:31:13] <JymmmmEMC> 8k-25K RPM, and I can do 60IPM (for now)
[20:31:26] <toastydeath> cool, so you won't have any problem
[20:31:26] <JymmmmEMC> technically 90IPM (under TCNC)
[20:31:39] <toastydeath> that 90 ipm might come in handy
[20:31:46] <anonimasu> JymmmmEMC: I thought you were going way faster..
[20:32:00] <JymmmmEMC> anonimasu: not under EMC
[20:32:17] <anonimasu> JymmmmEMC: like 200ipm :/
[20:32:28] <toastydeath> zip zip zip
[20:33:06] <JymmmmEMC> anonimasu: oh no, more like 120IPM but not stable under the current (xylotex) controller. I'm hoping that the new controller will take care of that issue though.
[20:33:16] <anonimasu> my mill is around 150 ipm.. though it'll be down to a bit..
[20:33:25] <anonimasu> around there after gearing too
[20:33:33] <anonimasu> I need more accel.. :)
[20:33:38] <JymmmmEMC> anonimasu: how bif is yours?
[20:33:41] <anonimasu> small
[20:33:47] <JymmmmEMC> in inches?
[20:34:18] <anonimasu> 600x210mm
[20:34:20] <anonimasu> just a sec..
[20:34:36] <anonimasu> 23"x8"
[20:34:51] <anonimasu> err wrong..
[20:35:07] <JymmmmEMC> This is a 3" round acrylic disc (Photo out of focus, poor lighting at the time) I carved
http://farm1.static.flickr.com/84/206158222_cb5c34978c_m.jpg
[20:35:29] <anonimasu> it's 260 x 150 and 310 Z
[20:35:41] <Unit41> where is the best place to get rack bar for pinion
[20:35:49] <anonimasu> 10" x 6" x 12.2"
[20:35:52] <anonimasu> xyz
[20:36:24] <JymmmmEMC> anonimasu: Ah, gotcha. Mine is 24" x 24" x 6"
[20:36:33] <archivist> Unit41, HPC in the uk can supply
[20:36:36] <anonimasu> it's a mill.. :)
[20:36:57] <JymmmmEMC> anonimasu: ah
[20:37:40] <archivist> Unit41,
http://www.hpcgears.com/
[20:37:56] <anonimasu> though I need the accels twice as fast..
[20:38:06] <anonimasu> need/want
[20:38:13] <anonimasu> it's what makes it zip zip zip when contouring
[20:38:14] <anonimasu> :)
[20:38:20] <JymmmmEMC> anonimasu: YOU GET NU_TING! lol
[20:38:26] <toastydeath> hahaha
[20:38:28] <anonimasu> nu_thing?
[20:38:30] <toastydeath> guys
[20:38:34] <toastydeath> how do you balance a servo?
[20:38:41] <anonimasu> balance?
[20:38:43] <toastydeath> yeah
[20:38:44] <JymmmmEMC> anonimasu: Schultz, from Hogans Heros'
[20:38:47] <Guest374> Does anyone know of a free CAM program that can import DXF, DWG, 3DS, and other formats?
[20:38:53] <anonimasu> never read/seen it
[20:38:53] <toastydeath> apparently servos, maybe analog servos only?
[20:39:01] <anonimasu> toastydeath: oh you mean offset adjustment?
[20:39:02] <toastydeath> have pots on them for something called "balance"
[20:39:07] <toastydeath> maybe?
[20:39:08] <JymmmmEMC> anonimasu: TV show from the 60's/70's
[20:39:30] <anonimasu> toastydeath: I guess you monitor the position of them and tweak it until your machine stops to creep
[20:39:44] <toastydeath> well, i mean, what does the setting do
[20:39:49] <toastydeath> on the motor itself
[20:39:51] <JymmmmEMC> sounds like s/balance/tune/
[20:39:54] <anonimasu> toastydeath: offset 0-10v..
[20:40:04] <anonimasu> to make the servo stop moving around with no power...
[20:40:12] <toastydeath> hmm
[20:40:54] <toastydeath> like, the setting i am blindly referring to
[20:41:03] <toastydeath> which is probably what you are talking about!
[20:41:11] <toastydeath> affects how accurately a servo can do countouring?
[20:41:19] <JymmmmEMC> jepler: Do you have any mroe of those etch-a-sketch PCB's by chance?
[20:41:23] <anonimasu> toastydeath: no
[20:41:35] <anonimasu> toastydeath: that would be the PID parameters..
[20:41:56] <toastydeath> this is something on the motor itself
[20:42:04] <anonimasu> toastydeath: toastydeath not on the drive?
[20:42:09] <toastydeath> maybe?
[20:42:11] <JymmmmEMC> toastydeath: He means so the motor won't keep turning do to the shaft being unbalanced (like an egg)
[20:42:31] <toastydeath> no, the shaft balance isn't it, it's not literal balance
[20:42:38] <toastydeath> i don't know why this guy called it balance
[20:42:48] <JymmmmEMC> Then RTFM the spec for the motors =)
[20:42:51] <anonimasu> JymmmmEMC: I mean the electric balance..
[20:43:01] <anonimasu> offset..
[20:43:08] <toastydeath> that might be it?
[20:43:11] <JymmmmEMC> anonimasu: shush, I'm trying to confuse him with my ignorance =)
[20:43:26] <anonimasu> toastydeath: that's off, it's usually on the drivers..
[20:43:29] <toastydeath> jymmmmemc: it was too obvious to work
[20:43:29] <anonimasu> odd..
[20:43:41] <anonimasu> atleast for everything I've seen but I havent seen mich
[20:43:40] <anonimasu> much
[20:43:43] <toastydeath> hurr
[20:43:46] <JymmmmEMC> toastydeath: Ya never know =)
[20:43:47] <anonimasu> YARR!
[20:43:49] <toastydeath> i wish i had a set of motors to mess with
[20:43:50] <toastydeath> and look at
[20:43:51] <toastydeath> oh well
[20:44:51] <toastydeath> the test for this particular setting on the drive/motor/whatever
[20:45:02] <toastydeath> was a ground disk, of an arbitrary diameter
[20:45:11] <toastydeath> in the spindle of a mill, or parallel to the ways of a lathe
[20:45:33] <toastydeath> and one takes a high accuracy measurement device at 45 degrees, and you command the machine to move in an arc
[20:45:42] <toastydeath> then, you kill it with feed hold when it is about at 45 degrees
[20:45:52] <toastydeath> and measure where the tool is versus where it should be
[20:46:06] <toastydeath> and this adjustment on the drive or motor or something will bring that number very close to what it should be
[20:46:43] <toastydeath> and maybe he was talking about on ancient equipment from the 60's
[20:46:58] <anonimasu> it sounds just like PID settings
[20:46:59] <toastydeath> and now, you guys do this inside emc or in some controller rather than on the physical equipment
[20:47:18] <anonimasu> yes.. that's right
[20:47:32] <anonimasu> still it depends on your drives..
[20:48:17] <toastydeath> hmm
[20:48:30] <anonimasu> some drives might have that and some dont..
[20:48:37] <toastydeath> regarding motion controllers
[20:48:52] <toastydeath> is there an advantage to having a motion controller between the servo drive/motor and emc?
[20:49:01] <toastydeath> or am i making new devices up
[20:49:04] <anonimasu> motion controller?
[20:49:21] <toastydeath> yes, yesterday some of the guys in here were talking about a distinct unit for motion control
[20:49:29] <JymmmmEMC> fanuc
[20:49:31] <bill2or3> you mean a motor driver?
[20:49:33] <toastydeath> yes, jymmmmemc has it
[20:49:38] <toastydeath> the fanuc uh, s2k?
[20:49:52] <anonimasu> toastydeath: *slaps youÄ
[20:49:52] <anonimasu> *
[20:49:55] <toastydeath> what
[20:49:59] <toastydeath> i don't know about this stuff, man
[20:50:03] <anonimasu> that's a cnc controller.. :)
[20:50:05] <toastydeath> no, dude
[20:50:06] <anonimasu> nothing to do with emc..
[20:50:14] <toastydeath> fanuc makes motion controllers and machine controllers
[20:50:24] <toastydeath> all fanuc's machine controls are labeled ##A
[20:50:35] <toastydeath> like, 18T or 20M
[20:50:34] <anonimasu> or are you talking about motion control cards?
[20:50:34] <JymmmmEMC> that was (and still is) my confusion.
[20:50:46] <toastydeath> they're standalone units of some sort
[20:50:57] <toastydeath> that control the servo drives?
[20:51:02] <anonimasu> yeah..
[20:51:05] <JymmmmEMC> anonimasu: a black box about 4" x6" x 4"
[20:51:23] <toastydeath> it piqued my interest because they can take multiple encoders
[20:51:24] <anonimasu> well, there are programable controllers for use in the industry I for machines..
[20:51:25] <JymmmmEMC> DIN rail mounted
[20:51:33] <toastydeath> hmm
[20:51:48] <toastydeath> jymmmmemc:
[20:51:51] <toastydeath> who was talking about them
[20:51:53] <JymmmmEMC> me
[20:52:01] <toastydeath> no, but who had the s2k's
[20:52:09] <anonimasu> that's as far as I know about them..
[20:52:14] <toastydeath> hurr
[20:52:15] <anonimasu> and that you can program them to do stuff ;)
[20:52:32] <toastydeath> hahah.
[20:52:36] <toastydeath> INCREDIBLE
[20:52:40] <anonimasu> yeah..
[20:53:01] <anonimasu> there are programable motion controllers(cards) too..
[20:53:15] <JymmmmEMC> no, these were not cards.
[20:53:17] <toastydeath> and those are what emc uses?
[20:53:21] <anonimasu> no
[20:53:29] <anonimasu> though you could ;)
[20:53:34] <anonimasu> but thats another story
[20:53:41] <toastydeath> well, that would be benificial
[20:53:47] <anonimasu> http://www.galilmc.com/products/accelera/dmc18x6.html
[20:53:59] <toastydeath> because as i understand, emc doesn't do the whole "bajillion encoders" thing
[20:54:05] <toastydeath> while these mysterious motion controls DO
[20:54:15] <anonimasu> toastydeath: theres a misnormer with that..
[20:54:19] <toastydeath> ?
[20:54:32] <anonimasu> toastydeath: emc dosent do multiple encoders because nobody has cared about doing it.
[20:54:34] <toastydeath> ah
[20:54:52] <anonimasu> toastydeath: it's not a limitation.. it's just not implemented because nobody has had a need for it..
[20:54:52] <toastydeath> well i can't program
[20:54:57] <toastydeath> =(
[20:55:02] <toastydeath> yeah
[20:55:20] <toastydeath> but like, if these motion controls can do it out of the box, and return a pre-corrected location to emc
[20:55:23] <toastydeath> that would work brilliantly
[20:55:24] <cradek> you can read many encoders into HAL and do whatever you want with them
[20:55:48] <anonimasu> toastydeath: I think you are fooling yourself if you think it'll be better..
[20:55:51] <toastydeath> and pipe the output into emc?
[20:55:54] <cradek> you could nest pid loops or whatever
[20:56:01] <anonimasu> toastydeath: you would still need to have the controller do what you want..
[20:56:01] <cradek> sure, whatever the "output" is
[20:56:22] <anonimasu> toastydeath: better idea would be to learn about hal.. :)
[20:56:24] <toastydeath> anonimasu: yeah, but what i'm saying is that these controls seem to do exactly what i want
[20:56:31] <toastydeath> but if hal can handle it, that's brilliant
[20:56:32] <anonimasu> toastydeath: you have no idea what they do really :)
[20:56:37] <anonimasu> didnt you say so ;)
[20:56:38] <toastydeath> i have a vauge idea, and hopes
[20:56:46] <lerneaen_hydra> random musing: would it be possible to have a gcode section that probes the current tool, and when an input is received it uses the Z distance for a tool offset? (auto tool measurement)
[20:57:10] <cradek> lerneaen_hydra: yes, I did that already, didn't you see it on the list?
[20:57:26] <lerneaen_hydra> cradek: you did?
[20:57:30] <anonimasu> toastydeath: better would be to learn hal and implement it yourself ;)
[20:57:30] <lerneaen_hydra> must have missed that
[20:57:33] <toastydeath> anonimasu: i'm basically trying to stumble my way from what i know about kinematic accuracy
[20:57:35] <lerneaen_hydra> cradek: difficult?
[20:57:39] <anonimasu> *hint hint*
[20:57:42] <toastydeath> into actually producing an accurate positioning stage
[20:57:58] <alex_joni> lerneaen_hydra: he meant he implemented it..
[20:58:06] <alex_joni> it's easy for users now :P
[20:58:09] <lerneaen_hydra> oh, right :p
[20:58:19] <cradek> yeah it works fine
[20:58:34] <cradek> it's just one of the many things you can do with probing
[20:58:35] <anonimasu> toastydeath: im not sure it's all that well, since you end up with dual pid loops..
[20:58:49] <lerneaen_hydra> it would seem to be quite simple to implement with hardware (just get electrical contact)
[20:58:53] <toastydeath> i don't want to use two encoders to try and drive the same axis
[20:59:01] <toastydeath> i want to use multiple encoders to correct a master encoder
[20:59:01] <lerneaen_hydra> cradek: got a page describing it?
[20:59:27] <anonimasu> toastydeath: well, you really need to get specs for thoose little black boxes..
[20:59:34] <toastydeath> yar =(
[20:59:38] <anonimasu> toastydeath: or just figure out how to do the correction..
[20:59:43] <toastydeath> the correction is easy
[20:59:52] <toastydeath> subtract the value from encoder 2 from encoder 1
[20:59:56] <toastydeath> then give the result to emc
[21:00:03] <cradek> lerneaen_hydra: you use probing (G38.2) to get the length, then set a transient tool offset G43.1
[21:00:40] <lerneaen_hydra> cradek: got a gcode + hal file sample?
[21:01:00] <cradek> lerneaen_hydra:
http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/nc_files/tool-length-probe.ngc?rev=1.4
[21:01:07] <lerneaen_hydra> ah perfect
[21:01:28] <cradek> hal file = hook the button to the probe input
[21:01:36] <anonimasu> sweet :9
[21:01:47] <anonimasu> can you stuff that into a macro?
[21:01:50] <lerneaen_hydra> oh the standard probe input?
[21:02:07] <cradek> yes the probe input, it uses the probe gcode
[21:02:25] <cradek> sure you could put it in a subroutine
[21:02:28] <cradek> it's very simple
[21:02:41] <lerneaen_hydra> nice
[21:02:49] <lerneaen_hydra> oh I would put it in my CAM app ;)
[21:03:04] <anonimasu> toastydeath: I'd suggest playing with hal.. :)
[21:03:12] <anonimasu> toastydeath: or well, call GE about thoose things
[21:03:15] <toastydeath> yeah man, it seems that way
[21:03:19] <toastydeath> re: hal
[21:03:26] <anonimasu> but im more into beliving in emc ;)
[21:03:44] <toastydeath> haha, i thought hal would do it but someone told me earlier it wouldn't
[21:03:54] <anonimasu> *comes from the guy that havent looked at hal*
[21:04:00] <cradek> would do what?
[21:04:06] <toastydeath> hey, i did look at hal
[21:04:15] <toastydeath> i looked over the docs for it and whatnot
[21:04:15] <anonimasu> cradek: correct encoders against eachother
[21:04:24] <anonimasu> cradek: or position that really is..
[21:04:27] <lerneaen_hydra> cradek: I assume using touch-off to get the work material with the right coordinates wouldn't break anything?
[21:04:42] <cradek> if the problem statement is "use many encoders to do ... something" then HAL can certainly do it
[21:05:06] <toastydeath> rock!
[21:05:06] <cradek> lerneaen_hydra: I don't understand the question
[21:05:20] <anonimasu> lerneaen_hydra: yes it'll still work..
[21:05:38] <anonimasu> cradek: setting your workpiece height
[21:05:39] <anonimasu> :)
[21:05:42] <lerneaen_hydra> um, a coordinate offset done manually beforehand via touch off for instance wont mess up when using the autoprobe
[21:05:48] <cradek> right
[21:06:01] <cradek> I think the comments in the gcode explain that
[21:06:05] <lerneaen_hydra> so no nasties like reverting to the base coordinates
[21:06:15] <cradek> you touch off the first tool, and then the program measures it and remembers the length
[21:06:23] <anonimasu> lerneaen_hydra: I think we got away from that with emc1..
[21:06:24] <lerneaen_hydra> ah ok
[21:06:24] <cradek> THEN it uses that to find the offsets for any subsequent tools
[21:06:34] <lerneaen_hydra> sweet :)
[21:06:40] <lerneaen_hydra> touch off uses g54, right?
[21:06:41] <toastydeath> also it's better if you can to set tool 1 to 0,0,0
[21:06:55] <cradek> also, you can touch off with a tool offset in effect, and get the right results
[21:06:56] <toastydeath> and have all your tools go off that
[21:07:07] <toastydeath> so they work across multiple work offets
[21:07:24] <cradek> yes ideally you have SOME kind of repeatable depth, but even if not, this scheme will work, since it measures and remembers the first tool (the one you used to touch off)
[21:08:27] <toastydeath> remembers it outside the work/tool offets?
[21:08:31] <toastydeath> *offsets
[21:08:33] <ds2> does subroutines work in emc?
[21:08:43] <cradek> sure
[21:08:45] <lerneaen_hydra> is it hard to make a sensor thats got repeatability to say 1/100th mm? (3 thou)
[21:08:52] <ds2> 'k
[21:08:58] <cradek> lerneaen_hydra: I got that with a regular old microswitch
[21:09:02] <anonimasu> http://www.gefanuc.com/za/ProductServices/MotionControl/Standalone/index.html
[21:09:03] <lerneaen_hydra> oh sweet
[21:09:10] <toastydeath> lerneaen_hydra: i have a sensor that will do that
[21:09:17] <toastydeath> paper from my notebook =)
[21:09:20] <cradek> .01mm is not 3 thou, it's .4 thou
[21:09:44] <lerneaen_hydra> oh, right
[21:09:46] <anonimasu> toastydeath: looks like you need to program them manually still.
[21:09:45] <toastydeath> just about anything you use will trigger that repeatably
[21:09:48] <lerneaen_hydra> inches are not my thing :p
[21:10:06] <toastydeath> anonimasu: is this re - motion controllers?
[21:10:09] <anonimasu> yeah
[21:10:12] <anonimasu> http://www.gefanuc.com/Downloads/en/flexiblemotionsolutions_cutsheet_gfa611.pdf
[21:10:25] <toastydeath> so they're kind of hal in a box?
[21:11:04] <anonimasu> I guess control in a box for like machine tasks..
[21:11:14] <anonimasu> think production lines..
[21:11:23] <toastydeath> yar
[21:11:27] <toastydeath> but from what i understand re: hal
[21:11:36] <toastydeath> you could implement a production line with that, correct?
[21:11:47] <anonimasu> this is more like PLC motion controllers..
[21:11:49] <toastydeath> or is my preception of what hal is so far out of whack that i should never talk again
[21:12:15] <anonimasu> cradek: help!
[21:12:15] <anonimasu> :D
[21:12:30] <toastydeath> does that mean never talk again =(
[21:12:35] <anonimasu> look at the application for thoose things
[21:12:37] <ds2> btw, any one of a utility (perferably command line and runs in Linux) that will take a STL file in and a series of DXF files describing slices of the STL object?
[21:12:43] <ds2> any one know of...
[21:12:54] <ds2> and generate
[21:12:58] <anonimasu> toastydeath: I guess you could..
[21:14:43] <toastydeath> emc sewing machine!
[21:14:48] <anonimasu> toastydeath: thoose motion controllers have their own OS..
[21:15:47] <toastydeath> haha, epic
[21:16:05] <anonimasu> http://application.gefanuc.com/infolink/manuals/gfk1848a.pdf
[21:16:06] <anonimasu> I rock.
[21:16:17] <toastydeath> i am noticing that
[21:16:25] <anonimasu> ^_^
[21:16:45] <anonimasu> that should help
[21:16:54] <toastydeath> that is a gigantic manual
[21:17:09] <anonimasu> * anonimasu waves a HAL flag
[21:17:23] <anonimasu> just hope it dosent set anything dangerous.
[21:17:30] <alex_joni> * alex_joni brings out the NML gun
[21:18:21] <toastydeath> i have EVEN MORE QUESTIONS, except these are unrelated to the other annoying questions i have been asking
[21:18:24] <archivist> * archivist avoids downloading manual and gettin distracted
[21:18:43] <toastydeath> does EMC have an MDI mode?
[21:18:47] <alex_joni> sure
[21:18:55] <alex_joni> it's called ...
[21:18:54] <alex_joni> MDI
[21:19:00] <anonimasu> tea time.
[21:19:11] <toastydeath> when i installed the emc environment thing
[21:19:12] <toastydeath> that was just emc
[21:19:14] <toastydeath> i didn't see one
[21:19:28] <toastydeath> which is why i ask
[21:19:53] <alex_joni> toastydeath: what are you talking about?
[21:19:57] <jepler> perhaps we don't know what you mean by "MDI mode"
[21:20:10] <toastydeath> manual data input?
[21:20:18] <jepler> all the GUIs offer an MDI mode or tab
[21:20:23] <alex_joni> toastydeath: each of the GUIs have a MDI mode
[21:20:26] <toastydeath> interesting
[21:20:31] <toastydeath> this means only one thing
[21:20:32] <jepler> in axis, press F5 then type in your gcode
[21:20:37] <toastydeath> i am far, far more retarded than i once believed
[21:20:42] <alex_joni> but there is also a standalong mdi program
[21:20:47] <toastydeath> ah, that would explain it
[21:20:49] <toastydeath> the f5
[21:21:02] <skunkworks> well - in axis it is also a tab..
[21:21:09] <alex_joni> yeah, activated by F5
[21:21:14] <toastydeath> hmm!
[21:21:16] <alex_joni> but also labeled MDI
[21:21:30] <ds2> now if there was only an offset editor....
[21:21:35] <toastydeath> clearly, actualy looking at the gui is for sissies
[21:22:26] <skunkworks> http://www.electronicsam.com/images/KandT/Dapper.png
[21:22:32] <alex_joni> http://linuxwiki.de/EMC/EMC2_GUI
[21:22:34] <skunkworks> older - but similar
[21:22:44] <toastydeath> snap
[21:23:07] <jepler> bbl
[21:36:15] <alex_joni> good night al
[21:36:18] <alex_joni> all
[21:36:56] <lerneaen_hydra> 'night
[22:08:01] <JymmmmEMC> alex_joni: see ya soon =)
[22:37:27] <Ziegler> hey... is there a way to pic up were you left off in the middle of some g-code
[22:37:41] <Ziegler> or pick a specific point to continue from?
[22:47:07] <Ziegler> anyone around?
[22:56:19] <JymmmmEMC> Just us chickens
[22:57:42] <Ziegler> is there any way to easily pick up in the middle of some g-code after an e-stop?
[22:58:23] <anonimasu> Ziegler: Yes, click on the line.. and press set Next line..
[22:58:32] <anonimasu> err the line where you want to resume at..
[22:58:41] <Ziegler> set next line?
[22:58:49] <Ziegler> where is that in axis?
[22:58:58] <anonimasu> I cant remeber on the same menu as run is..
[22:59:45] <Ziegler> ahh I see it cool
[22:59:47] <Ziegler> then just run?
[23:00:08] <anonimasu> yeah
[23:00:20] <anonimasu> but make sure you are at the right place before if it's a arc or such :)
[23:00:21] <Ziegler> thanks!
[23:00:28] <Ziegler> right right!
[23:00:43] <anonimasu> and be careful if you have tool offsets and stuff..
[23:01:01] <anonimasu> you should ask someone that knows better then me..
[23:01:18] <anonimasu> about how that works with estop, but I think they are modal so it shouldnt matter..
[23:02:45] <anonimasu> good luck
[23:03:08] <Ziegler> I have been doing it the hard way... ie.. starting over
[23:03:15] <Ziegler> this isnt long code
[23:03:32] <anonimasu> :)
[23:03:37] <Ziegler> but I have 10 of these signs to make, and they take about 8 minutes a piece
[23:03:37] <anonimasu> it should help you out lots
[23:04:36] <Ziegler> for sure
