#emc | Logs for 2009-07-16

[01:39:43] <Jymmm> http://www.cnn.com/2009/US/07/15/quadrillion.dollar.glitch/index.html
[01:40:56] <Jymmm> I was playing around with that 15" touch screen eee pc. Not bad at all. very responsive, I was even able to move the cursor using a piece of paper instead of my finger.
[01:41:54] <Jymmm> I placed a card on the sceen and was able to move the cursor too, so it could be covered n a thin layer for shop use.
[01:41:58] <sed_> we got the limit switch prblem solved, we had to isolate the limit switches with relays in order to get them to work with our stg card
[01:42:12] <sed_> no explination why it worked in emc1
[01:42:29] <sed_> now we want to get the index bit working with our encoders
[01:44:03] <sed_> what do we look for in hal scope or whatever, to see the index bit as the encoder goes by it?
[01:45:11] <SWPadnos> you can't directly see it under normal circumstances
[01:45:30] <SWPadnos> in fact, I think with the STG card, you can't directly see it at all
[01:46:15] <SWPadnos> what you can do to test it is to disconnect the encoder "index-enable" pin from the motion controller and manually set that pin to 1
[01:47:31] <SWPadnos> if you then move the motor (by hand or via a slow MDI/jog move), you should see the position output slowly ramp up (or down), and then it will suddenly jump to zero, in the same serov period as the index-enable gets set to 0
[01:47:59] <SWPadnos> the index-enable getting set to 0 is the indication that the hardware saw the index pulse and that the driver noticed it
[01:50:10] <sed_> we are not seeing the index pulse, across the entire scale (they are every 2 inches across the 18" scale)
[01:50:20] <sed_> we are not sure what the index pin is on the stg
[01:50:35] <SWPadnos> can you see it with a physical meter/scope?
[01:50:43] <SWPadnos> I don't know where to connect it either
[01:51:14] <sed_> we will check with our o scope..
[01:51:52] <sed_> still unsure how the stg gets the info
[01:52:16] <SWPadnos> there's got to be an index input pin on the card, probably somewhere close to the A and B encoder inputs
[01:52:27] <SWPadnos> probably called C, Z, or I
[01:52:45] <tomp> tomp is now known as tom3p
[01:53:35] <sed_> hang on let me get the stg manual..
[01:53:54] <Jymmm> SWPadnos: You forgot abc..xyz =)
[01:54:03] <SWPadnos> UVW
[01:54:49] <Jymmm> SWPadnos: I picked up one of each 8gig + 24 10/100
[01:54:56] <SWPadnos> cool
[01:55:39] <Jymmm> but can't find any rack mont screws, it 2 stores too
[01:55:42] <Jymmm> mount
[01:55:54] <SWPadnos> they've got to be some standard thread
[01:56:05] <SWPadnos> I don't know which one, but I'm sure it's standard
[01:56:05] <Jymmm> thread yes, head no
[01:56:19] <Jymmm> 1-/32 3/4"long WIDE head
[01:56:23] <SWPadnos> they're just wide pan-head screws
[01:56:25] <Jymmm> 10-32
[01:56:41] <Jymmm> well hd/lowes dont carry them
[01:56:53] <SWPadnos> they don't carry a lot of fasteners
[01:57:39] <Jymmm> and forget about metric
[01:57:50] <Jymmm> have to hit MR Metric for those
[01:59:00] <SWPadnos> philips, slotted, or tamper-resistant?
[01:59:16] <SWPadnos> and would you prefer stainless or is zinc or oxide-coated OK?
[01:59:32] <Jymmm> MrMetric has EVERYTHING metric
[01:59:41] <SWPadnos> 10-32 isn't metric
[01:59:50] <Jymmm> anything that doesn't strip the head
[01:59:54] <SWPadnos> let me know if they have a 19x1.0mm tap next time you're there :)
[02:00:08] <SWPadnos> (don't buy it though, I finally found one online)
[02:00:33] <Jymmm> http://www.mrmetric.com/
[02:00:44] <SWPadnos> http://www.mcmaster.com/#91770a831/
[02:01:29] <Jymmm> $12 + $50 shipping =)
[02:01:40] <SWPadnos> shipping will be $3 or so, max
[02:01:48] <Jymmm> really????
[02:01:52] <SWPadnos> there may be a minimum order fee though, so get me a J445 while you're at it ;)
[02:02:04] <SWPadnos> yeah, they're quite reasonable
[02:02:27] <SWPadnos> and they have several warehouses and ship from the closest that has the item in stock
[02:03:03] <Jymmm> J445??
[02:03:28] <SWPadnos> oh right. they don't carry it
[02:03:46] <SWPadnos> the flex collet I was talking about earlier ($65)
[02:03:56] <Jymmm> ah
[02:06:04] <SWPadnos> sed_, it looks like index 1 is P3-20 (+ side) and P3-30 (- side)
[02:06:39] <SWPadnos> with similar markings for the others (I#- and I#+, where # is the encoder number from 0 to 7)
[02:11:00] <sed_> yes they are hooked up to those pins, we were reading the the stg manual there is some bit that needs to be set to turn index on
[02:11:25] <SWPadnos> that should be done by the driver
[02:11:50] <SWPadnos> if you use halcmd show, you should see encoder index-enable pins
[02:12:09] <SWPadnos> (like stg.0.encoder.00-index-enable or similar)
[02:13:08] <SWPadnos> oh hmm. those are listed as "todo" in the comments
[02:13:42] <sed_> that would explain much, thanks
[02:14:14] <SWPadnos> ah. luckily the comment is wrong
[02:14:19] <SWPadnos> the pin does exist in the code :)
[02:14:46] <cradek> some of SWPadnos's advice was wrong. Do NOT poke index-enable while EMC is running and controlling the index. A position reset when EMC isn't expecting it will cause a serious runaway.
[02:15:11] <SWPadnos> oh - good point
[02:15:29] <SWPadnos> manually turning the motor while EMC is in machine off would still work though
[02:15:33] <cradek> when the homing process asks for index, it expects the reset and does the right thing
[02:15:45] <cradek> yes that is exactly what you want to do
[02:16:08] <sed_> we just killed the machine we have to figure out what file we fubard..
[02:16:38] <SWPadnos> may I suggest cvs or git for keeping track of changes you make to config files? :)
[02:16:57] <cradek> er, "while EMC is running and controlling the _axis_" is what I meant above
[02:18:37] <SWPadnos> hmm. the STG sample config should probably use -1 on line 11 (where it adds the write function)
[02:20:24] <tom3p> will an accelerometer tell me usefull info when the velocity change is from 1"/min to 2"/min in 200mS? (i'm not sure that such devices work at such low values)
[02:20:55] <SWPadnos> with loads of filtering, maybe
[02:21:12] <tom3p> iffy huh?  I'm trying to detect when an edm breaks thru one surface, to stop it before it hits a rear wall only .087" away (all blind )
[02:21:51] <SWPadnos> and there's actually back pressure before the break-through?
[02:22:20] <tom3p> yes but the volume is miniscule with a .009 dia hole and <100 psi
[02:22:49] <SWPadnos> a strain gauge may be just about as useful as an accelerometer
[02:23:00] <tom3p> so, the pressure diff is... negligible, the central hole in the tube electrode governs the pressure
[02:23:14] <SWPadnos> why the accel then?
[02:24:24] <tom3p> accells because it begins cutting air till the back wall is hit & buyer doesnt like back wall strike on their turbines
[02:24:46] <tom3p> there's a burst of speed just before the crash ;)
[02:25:05] <SWPadnos> ok - that's why I asked about back pressure - I figured there was some resistance to motion, and for EDM that didn't make much sense :)
[02:25:39] <tom3p> how might a strain gauge work here?
[02:25:40] <SWPadnos> look at the PID output - if it drops (relatively) sharply, you've just broken through
[02:26:00] <SWPadnos> measuring applied force to the cutting "head"
[02:27:23] <SWPadnos> if you're actually using EMC on this, you can also be tricky and look at the difference between commanded and actual position, and see if the delta position from last cycle to this cycle is much greater than that
[02:27:41] <SWPadnos> you just need to be clever about where you put the difference calcs in the thread execution order
[02:28:07] <tom3p> yeah, i began divying the user's command into .005" chucks & watching how long each took
[02:29:02] <tom3p> using a fiinite step size allowed the time calc to be fast
[02:29:07] <SWPadnos> oh - I'd just look at actual_pos-last_pos relative to cmd-pos-actual_pos
[02:29:28] <SWPadnos> after the motion controller has run, so cmd-pos is the expected "next_pos"
[02:31:30] <SWPadnos> oh, and maybe gate the result with an aux output (set with M6x or M5x or something) - a "be careful" output
[02:32:20] <tom3p> haha, yes, the operators now stare at a dro, with a finger over a 'stop' button. i want to automate it.
[02:32:53] <SWPadnos> I'd assume that motion is quite smooth for a while before the break-through?
[02:33:26] <renesis> guys if it shows up in halscope did it come from emc?
[02:33:31] <tom3p> i just opened the head covers and showed them the leadscrew coupling... watch that, when it spins, hit the button, while it creeps, dont worry
[02:33:36] <renesis> or does it track the hardware that emc2 is controlling
[02:33:40] <SWPadnos> renesis, that depends on what "it" is
[02:33:49] <renesis> step/dir
[02:33:54] <renesis> on parport
[02:34:23] <SWPadnos> still depends on what you're looking at
[02:34:25] <renesis> well anyway, that weirsd oscillation shows up in halscope
[02:34:39] <SWPadnos> I must have missed something
[02:35:05] <renesis> *weird
[02:35:29] <renesis> ive been getting these weird stepper oscillations
[02:35:37] <tom3p> step & dir are outputs, i'd guess they came from emc. if 'it' was an input, emc isnt the cause, only an observer
[02:36:38] <renesis> well it came from emc or halscope reads hardware registers and theres some like catostrophic emi on my mobo
[02:36:38] <tom3p> if you've hooked up inputs on the parport to some signal you've called step & dir, then emc is again an observer
[02:37:01] <renesis> no these are outputs for stepgen
[02:37:24] <SWPadnos> ok. if you're looking at step and dir from stepgen, then that is from emc
[02:37:46] <SWPadnos> you should also look at the position input, to be sure that the position command isn't wobbling
[02:37:47] <renesis> like, my steppers will oscillate typewriter style, hopping forward a couple steps at a time, maybe 8-10 total steps
[02:38:52] <renesis> always regular intervals like chirping, then itll return to original position every step all at once
[02:39:20] <SWPadnos> look at the position command into stepgen
[02:40:27] <renesis> it did it for 10min while i was paused during a test cycle, and the negative signs flashed in axis coordinate display while X and Y were zero'd
[02:41:11] <renesis> like it was hopping from -0.0000 to 0.0000
[02:41:37] <renesis> swpadnos: k next time it happens
[02:41:52] <SWPadnos> that could be, but I'd be surprised if stepgen would ever move more than one step back and forth
[02:42:43] <tom3p> does this stepper setup have any position feedback?
[02:43:01] <renesis> yeah the bug in changelog i read is just one step
[02:43:07] <renesis> no its open loop
[02:43:15] <SWPadnos> what version of EMC2?
[02:43:22] <renesis> and i dont think i have any feedback config stuff
[02:43:31] <renesis> 2.2.8
[02:44:06] <renesis> i went to the website (maybe the wiki?) to download the new script for ubuntu
[02:44:22] <renesis> i ran it and it looked like it checked a bunch of stuff online and told me i was up to date
[02:44:26] <SWPadnos> it won't work if you already have emc2 repositories in your sources.list
[02:44:41] <renesis> hmm
[02:44:47] <SWPadnos> you need to follow the other instructions to change the repos to point to 2.3 instead of 2.2
[02:44:59] <renesis> thats in /etc, i should remove emc servers?
[02:45:18] <SWPadnos> no. change the two locations where it says "emc2.2" to say "emc2.3"
[02:45:43] <SWPadnos> there will be a few other changes you need to make in your ini files, detailed on the wiki
[02:45:45] <renesis> k, ty
[02:46:09] <SWPadnos> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?UpdatingTo2.3
[02:46:25] <SWPadnos> then follow these: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?UPDATING
[02:48:22] <renesis> hey can halscope do analog stuff?
[02:48:36] <SWPadnos> if you have hardware with analog inputs, yes
[02:48:47] <renesis> neat
[02:49:22] <SWPadnos> but it can only sample at the fastest thread rate - it won't download a buffer fron a high speed capture card and show it to you
[02:49:56] <renesis> the only immediate application im thinking of is temp related
[02:50:36] <renesis> prob dont need more than 100Hz
[02:50:43] <SWPadnos> oh sure. if you have a card that can read the sensor, and there's a HAL driver for it (not too likely - there aren't many supported options for analog input), then you can look at it with halscope
[02:54:59] <tom3p> i think jepler? did some analog with an arduino
[02:55:18] <SWPadnos> yep. and STG has analog input as well
[02:55:34] <SWPadnos> plus my exceedingly expensive add-ons for the Mesa cards :)
[02:57:03] <tom3p> http://axis.unpy.net/01198594294 its user space but that may be ok
[02:59:00] <sed_> got emc working, but both our o-scopes are dead.....
[02:59:06] <SWPadnos> heh
[02:59:15] <SWPadnos> emc, scope, scoep - pick any two :)
[02:59:21] <SWPadnos> err, scope
[02:59:30] <SWPadnos> or pick any one, as the case may be
[02:59:51] <renesis> sed_: whats wrong with your scopes?
[03:00:06] <renesis> i have a tek 2230 its like, old =(
[03:00:10] <sed_> one turned on, then display went black
[03:00:12] <renesis> misbehaver
[03:00:13] <tom3p> europeans would say 'ko' , i never understood that one
[03:00:43] <sed_> the other one has display but probe wont work...
[03:10:52] <Valen1> Heh went to the drag strip last night
[03:11:08] <Valen1> somebody had a van with a supercharged V8 in it
[03:11:21] <Valen1> must have been his first night with it
[03:11:36] <Valen1> by his last run he was laying down a 10.5
[03:19:31] <Jymmm> jepler: do you have enlarged photos of that spindle you got? I'm iterested in seeing how it locks the tooling in.
[03:22:23] <Jymmm> http://sfbay.craigslist.org/sby/sys/1272247599.html lol
[03:33:47] <sed_> how come in the stg.ini we can use ROTORY for our rotory 4th axis???
[03:34:08] <sed_> can=cant
[03:34:30] <sed_> for type of axis
[03:35:07] <mozmck> Maybe it should be ROTARY?
[03:35:45] <Valen3> my puter is not happy with me :-< there be something hinkey with the disk system
[03:36:06] <Valen3> I'm getting "interface errors", and it can't write to disk any more
[03:36:15] <Valen3> oh well its rebooted see if that fixes it
[03:36:33] <SkinnYPuPp> e2fsck ?
[03:36:46] <Valen3> not yet lol too busy
[03:37:09] <Valen3> its not a file system problem, something in the hardware is stuffing up
[03:37:12] <SkinnYPuPp> hear ya, recently had to replace a mb that rebooted whenever the hell it felt like it
[03:37:23] <Valen3> sucky, probably the caps on it
[03:37:31] <SkinnYPuPp> yeah ..
[03:37:48] <sed_> its spelled correctly in the ini file.. it was a comment out example... heh
[03:38:15] <mozmck> huh, don't know then...
[04:42:36] <renesis> okay i put 2.3.2 i think the problem is gone
[09:20:32] <piasdom> g'mornin all
[09:21:36] <alex_joni> hi
[10:42:28] <piasdom> can someone tell me if status,Err is something i need to fix ? http://pastebin.com/d4533b020
[10:49:39] <alex_joni> piasdom: status=Err is something you need to fix
[10:49:46] <alex_joni> but in this case there is no status=Err
[10:49:52] <alex_joni> status is 'ii' which means installed
[10:50:35] <piasdom> so status,Err is not the same as status=err ?
[10:50:39] <alex_joni> the first 3 lines in your pastebin are simply for reference, what status a package could have
[10:51:11] <alex_joni> where did you see "status,Err" ?
[10:51:18] <piasdom> cool,thanks alex_joni
[10:51:35] <piasdom> third line at end
[10:59:45] <alex_joni> piasdom: that's only reference
[11:42:16] <piasdom> alex_joni;i answered before i saw your reply about the first three lines....thanks again
[11:48:37] <alex_joni> np ;)
[16:14:49] <NewType> Hi all, good news. I have started testing the 5 axis machine with and without kinematics. I think I can get both to work now. At least it looks right on the screen and when cutting in air.
[16:15:53] <NewType> The bad news is that when I am cutting for real, twice already, the machine will turn itself off in the middle of the cut.
[16:17:29] <NewType> I don't know what trips it off. The software start button is in the off position, and it stops in the middle of the GCode. And both times it stops around the same time. I didn't see at which line it stop the first time. I watched it stop the second time.
[16:17:41] <archivist> electrical noise
[16:17:52] <NewType> on the estop switch?
[16:18:01] <archivist> could be
[16:18:25] <NewType> humm.
[16:18:39] <NewType> more shielding of the wire then.
[16:18:44] <archivist> normally open or closed? and if open what size pull up
[16:18:45] <SWPadnos> or less
[16:19:04] <SWPadnos> make sure the shield is only connected at one end of the cable (the "source" end)
[16:19:13] <NewType> I think it is normally open, and with a 10K pull up.
[16:19:26] <SWPadnos> NO is bad for estop
[16:19:37] <archivist> gound loops being another problem SWPadnos is mentioning
[16:19:46] <SWPadnos> it should be NC, so that a broken wire will estop the machine
[16:20:09] <archivist> and a 300 ohms to pull it up
[16:20:17] <SWPadnos> are any mesasges shown when the machine stops?
[16:20:24] <NewType> I will double check it then. because another person is wired that for me.
[16:20:39] <SWPadnos> limit switches will also stop the program, but should show a message (I don't think that estop shows a message)
[16:21:12] <NewType> there is no estop message on the screen. so I was puzzled.
[16:21:33] <SWPadnos> I don't think estop prints a message, so unfortunately that doesn't tell us much
[16:21:50] <NewType> limit switch trip will produce a message. but that wasn't the case.
[16:22:03] <SWPadnos> ok
[16:22:03] <NewType> right, estop doesn't produce a message on the screen.
[16:22:21] <NewType> let's go with the electrical noise... and NC for estop.
[16:22:30] <NewType> let me attack that first.
[16:22:42] <NewType> because I do suspect it is the estop switch
[16:22:51] <SWPadnos> when you're cutting air, do you run the spindle?
[16:23:10] <NewType> ah. when I cut in air, it was fine. when I cut for real, it stops
[16:23:19] <NewType> and I suspect that's where the noise comes from.
[16:23:27] <frallzor> is there some nice visualsetup for emc thats optimal for touchscreens?
[16:24:04] <SWPadnos> I'm trying to confirm that the only difference between cuttin air and not cutting air is that the workpiece is in the vise (or whatever) - so spindle and servo loads are the only difference
[16:24:12] <SWPadnos> frallzor, no, not really
[16:24:32] <SWPadnos> a touchscreen-friendly UI has been discussed a bit, but never actually made AFAIK
[16:24:36] <NewType> I just wanted to get a 2nd opinion on this. because I replaced the older Dual PIII machien with this new single CPU P4. and it is my first time cutting for real... I just hope it wasn't somethign like the screensaver or something.
[16:24:43] <SWPadnos> oh crap. I have to leave. bbl
[16:25:01] <NewType> right, and when I have the spindle on, it seems to trip.
[16:25:19] <archivist> vfd electrical noise
[16:25:25] <NewType> right.
[16:25:26] <NewType> will do.
[16:25:33] <NewType> I am so very very very close. :)
[16:26:21] <NewType> thanks. back later tomorrow.
[16:26:29] <archivist> frallzor, I heard the tk version of the control has been used with a touch screen
[16:26:56] <frallzor> what is the tk version?
[16:28:13] <archivist> tkemc
[16:28:37] <archivist> I have the modded version somewhere
[16:29:25] <frallzor> nice
[16:32:18] <archivist_emc> frallzor, http://pastebin.ca/1497217
[16:33:47] <frallzor> nice thnx, care to tell what to do with it too? :)
[16:35:02] <archivist> no, I have not had time to play
[16:35:41] <archivist> as tkemc but upped to 5 axis and is used on a touch screen if Im correct
[16:36:54] <frallzor> I dont even know how to get the tkemc =)
[16:37:26] <frallzor> edit some ini I guess but I dont know squat about linux and finding =)
[17:46:45] <mozmck_work> can you connect a pin from a realtime component to a pin from a userspace component?
[17:49:01] <piasdom> frallor: still there ?
[17:50:32] <cradek> mozmck_work: yes definitely. consider halui's outputs (userspace) hooked to a mesa card's pins to control some indicator lights
[17:52:10] <mozmck_work> ok. I figured but thought I'd ask. A guy on the linuxcnc forum needs a component to switch relays via serial port.
[17:52:30] <cradek> yep if it's not timing-critical that can be done entirely in userspace
[17:52:37] <mozmck_work> I think I can write him one pretty quickly.
[17:52:40] <cradek> there is a nice python serial library
[17:52:57] <cradek> and there is a nice python hal interface!
[17:53:57] <mozmck_work> yes, I've seen that! the serial interface is just called serial right?
[17:54:46] <cradek> guess so
[17:54:48] <cradek> import serial
[17:54:49] <cradek> s = serial.Serial("/dev/ttyUSB0", 9600, rtscts=0)
[17:55:01] <cradek> ^ from a little program I use
[17:55:44] <mozmck_work> yeah, I saw something like that in another file
[17:56:22] <cradek> in ubuntu the package is python-serial
[17:57:03] <mozmck_work> ok. if I can get a little time I'll try and write it.
[17:57:20] <mozmck_work> thanks!
[17:57:25] <cradek> welcome
[18:09:18] <frallzor> piasdom im here now =)
[18:10:22] <piasdom> frallzor:do you know where your emc2 directory is located ? (mine is in my home dir)
[18:10:45] <frallzor> i know where 2 are
[18:11:11] <frallzor> one is just setting and one is something more it seems
[18:11:26] <frallzor> what about it?
[18:11:31] <piasdom> frallzor:does one have config folder ?
[18:11:42] <frallzor> hold 1 sec, logging in =)
[18:13:02] <frallzor> yes
[18:13:17] <frallzor> configs folder with setups in
[18:13:20] <piasdom> look for the ini file
[18:13:40] <frallzor> hmm not the right one then
[18:13:44] <frallzor> no inis, just stepconfs
[18:13:53] <frallzor> or its right?
[18:14:11] <frallzor> ah nm, found it
[18:14:19] <piasdom> think it needs to be ini file
[18:14:43] <frallzor> display changed to tkemc?
[18:14:54] <piasdom> in there is a list (axis,mini,tkemc)
[18:15:10] <piasdom> take the # off the one you want
[18:15:29] <piasdom> and add it to the one that didn't have one
[18:15:40] <frallzor> no commented things like that
[18:15:54] <frallzor> just a Dispelay = axis that is the closest
[18:16:06] <frallzor> change that to tkemc?
[18:16:27] <piasdom> under that type display = tkemc
[18:16:55] <piasdom> or you can change the one you have
[18:17:13] <frallzor> did it your way
[18:17:16] <frallzor> then what
[18:17:54] <piasdom> start emc...if that is the correct file then tkemc will start
[18:18:04] <frallzor> axis still
[18:18:13] <frallzor> but i left axis in the ini
[18:18:14] <mozmck_work> comment out the first display line
[18:18:21] <mozmck_work> with #
[18:18:31] <piasdom> can you use stepconf and select the file ?
[18:18:40] <frallzor> commented out
[18:18:43] <frallzor> works now
[18:19:00] <piasdom> cool
[18:19:09] <frallzor> http://pastebin.ca/1497217
[18:19:12] <frallzor> what about this
[18:19:47] <frallzor> supposedly modded for this purpose
[18:22:24] <piasdom> does tk work ?
[18:22:25] <frallzor> I assume its some file I need to paste it into
[18:22:27] <frallzor> yup
[18:22:32] <frallzor> seems to be working
[18:22:36] <piasdom> correctly ? :):)
[18:22:44] <frallzor> how to tell? :P
[18:23:10] <piasdom> run your machine and measure distances
[18:23:27] <frallzor> not up and running yet =)
[18:23:31] <piasdom> see if all axis work
[18:23:35] <piasdom> oooooooooooooooooo ok
[18:23:38] <frallzor> just doing what I can electronicswise
[18:23:42] <piasdom> well you got tk
[18:23:45] <frallzor> and softwarewise
[18:24:04] <mozmck_work> It looks like that pastebin is tkemc. Is it one someone modified and pasted for you?
[18:24:37] <frallzor> yes archivist
[18:24:37] <piasdom> that ini file is not the one i'm use to
[18:25:19] <frallzor> axis seems to be working properly
[18:25:49] <mozmck_work> frallzor: select the whole thing from the box at the bottom that says "Update Paste Below"
[18:26:21] <mozmck_work> then copy it to your text editor and save it as "tkemc"
[18:26:31] <piasdom> do you have an ini file that looks like this ? http://pastebin.ca/1497329
[18:27:13] <mozmck_work> I'm not sure offhand where this file should go, but you'll need to make it executable and replace your current tkemc with this one.
[18:28:09] <piasdom> frallzor;can you use stepconf ?
[18:28:14] <frallzor> yes
[18:28:31] <piasdom> in stepconf select that file
[18:29:03] <frallzor> im getting overwhelmed now :P
[18:29:06] <mozmck_work> piasdom: you can select any file for the display?
[18:29:30] <frallzor> I dont know what to do now :P which file
[18:29:52] <piasdom> mozmck: the file i want him to select is an ini file...not for display
[18:30:05] <frallzor> stepconffile for my stuff?
[18:30:13] <piasdom> do you remember the file name ?
[18:30:33] <frallzor> you are talking about the stepconf right?
[18:30:45] <frallzor> its open now
[18:31:10] <piasdom> in stepconf you get a choice of files that are in the emc dir
[18:31:41] <frallzor> i opened the stepconf for my stuff
[18:32:01] <piasdom> do you see the file ?
[18:32:04] <frallzor> yes
[18:32:34] <piasdom> select it
[18:32:59] <piasdom> then go thru stepconf
[18:32:59] <frallzor> I have a stepconf configured =)
[18:33:33] <piasdom> you'll have to select "edit existing file"
[18:33:44] <frallzor> ah the advanced configuration components options
[18:33:53] <frallzor> what to select? =)
[18:34:16] <piasdom> that's up to you and the machine ya'll get
[18:34:30] <frallzor> I know how to setup those things
[18:34:44] <piasdom> cool
[18:34:54] <piasdom> have fun
[18:36:39] <frallzor> where did you find the ini in the pastebin you linked?
[18:36:58] <frallzor> doing stepconf killed tk in my file
[18:38:37] <piasdom> then you selected a different file then you edited
[18:38:59] <frallzor> same file
[18:39:11] <piasdom> stepconf will overwrite any ini file you edit
[18:39:24] <frallzor> yes so I have to redo it again then
[18:39:30] <frallzor> add the tkemc
[18:39:30] <piasdom> go see if tk is still
[18:39:32] <piasdom> there
[18:39:35] <frallzor> it wasnt
[18:39:52] <piasdom> k
[18:40:18] <piasdom> as they say in here...if it works-don't fix it :)
[18:40:45] <piasdom> you'll just have to wait for the machine
[18:42:03] <frallzor> are you the swede btw? =P
[18:42:45] <piasdom> U.S.A.
[18:44:11] <frallzor> nah i think this tkemc look will work ok on touchscreen as it is =)
[18:47:44] <piasdom> what version of emc do you have?
[18:47:59] <frallzor> latest
[18:48:04] <frallzor> 2.3.2
[18:48:23] <piasdom> i don't use tk so i'm not familar /w it
[18:48:35] <piasdom> let me look at mine brb
[18:50:13] <piasdom> oh ya, didn't like it because i have to have too many win opened :)
[18:50:44] <piasdom> do you NEED to use tk for the touchscreen ?
[18:52:52] <frallzor> ppl seem to prefer tk for that use
[18:53:02] <frallzor> so ill try this =)
[18:54:28] <piasdom> k
[18:54:59] <piasdom> you'll need to run stepconf again to match your machine
[18:55:12] <piasdom> just remember to change ini
[19:06:19] <frallzor> =) yup
[19:06:39] <frallzor> ah will finally get a nice housing for my electronics tomorrow, great
[20:38:44] <Spida_> Spida_ is now known as Spida
[21:45:32] <frallzor> anyone know a nice site with some nice info about how to choose the best spindle speed and match a nice feed
[21:46:42] <archivist> frallzor, sandvik docs (pdfs)
[21:47:17] <frallzor> ahh good old sandvik
[21:47:45] <cradek> what kind of tooling?
[21:48:14] <frallzor> milling
[21:48:24] <cradek> hss? carbide?
[21:48:33] <frallzor> think its all carbide
[21:48:53] <cradek> it's important to know for sure
[21:48:57] <frallzor> ah both
[21:49:01] <toastydeath> modern tooling has speed and feed data in the catalog
[21:49:02] <cradek> many end mills are not carbide
[21:49:02] <frallzor> 4 hss 4 carbide it seems
[21:49:13] <cradek> cutting what material?
[21:49:28] <frallzor> cibatool and aluminium
[21:49:46] <frallzor> and acrylic
[21:50:07] <cradek> you can cut aluminum with HSS up to about 300 sfm with coolant
[21:50:22] <frallzor> sfm?
[21:50:25] <cradek> 200 is more common
[21:50:30] <cradek> surface feet/minute
[21:50:40] <frallzor> im swedish :P
[21:50:44] <cradek> with carbide, double or triple the speed
[21:50:46] <toastydeath> i don't want to be a big stick in the mud, but you can go way faster than that in aluminum
[21:50:50] <toastydeath> with hss
[21:51:19] <cradek> frallzor: the answers vary :-)
[21:51:24] <toastydeath> with carbide, in aluminum, the speed is only limited by the machine
[21:51:30] <cradek> you should experiment
[21:52:02] <cradek> yeah with carbide, most machines just run out of spindle speed unless the tool is very big
[21:52:07] <frallzor> mostly so it doesnt break my mills
[21:52:09] <toastydeath> i usually keep things at 600-700 sfm in aluminum with HSS
[21:52:19] <toastydeath> and for carbide, i top the machine out no matter what the tool is
[21:52:23] <cradek> what size of tools?
[21:52:27] <frallzor> 2-6mm
[21:52:44] <cradek> frallzor: what's your max spindle speed?
[21:52:50] <frallzor> 6000rpm
[21:53:49] <toastydeath> you'll be fine at 6000 rpm.
[21:53:54] <cradek> those tools are tiny. crank it all the way up and don't worry
[21:54:05] <cradek> you have flood coolant I hope
[21:54:07] <Jymmm> ... be happy
[21:54:22] <cradek> and 2 flute end mills I hope
[21:54:32] <frallzor> when I do cut I have bottle ready for it =)
[21:54:45] <frallzor> no fancy auto-coolant =)
[21:54:50] <frallzor> yup 2 flute
[21:55:10] <cradek> I bet you need more than an occasional squirt if you're doing 400 sfm (6mm cutter at 6000 rpm)
[21:56:05] <toastydeath> dry is fine
[21:56:06] <frallzor> I dont think so, I played around with it manually when I got it, nothing odd when I cut 5mm except that I milled too much at a time
[21:56:58] <frallzor> no issues that had to do with the lack of coolant afaik
[21:57:00] <toastydeath> coolant in aluminum comes into play when you're slotting, for chip clearance, and for things like spinning a 5" facemill at 8000 rpm
[21:57:16] <toastydeath> the boiling coolant keeps the chip from welding up
[21:57:35] <toastydeath> but you can do it dry with a zrn coating, or with a polished insert/endmill
[22:01:13] <anonimasu> hm, I'd defentively use air..
[22:01:55] <anonimasu> frallzor: btw, dormer had nice cutting data in their "selector" program
[22:02:05] <anonimasu> err has..
[22:03:21] <frallzor> dormer is nice, some of my mills are dormer =)
[22:03:49] <anonimasu> im not so extremely happy with their hss endmills, they dont seem to last for me long enonugh
[22:04:53] <anonimasu> though, im still trying to work out if I should get rid of coolant and use air instead..
[22:05:09] <frallzor> why?
[22:05:39] <bill2or3> hilsch vortex tube!
[22:05:42] <bill2or3> dooo eeeet.
[22:05:55] <anonimasu> bill2or3: I have a cad drawing of the orfice and stuff.. somewhere :)
[22:05:56] <toastydeath> i wouldn't get rid of coolant, just add air
[22:05:56] <archivist> you can get micro cracks if the coolant misses
[22:06:18] <anonimasu> my machine isnt enclosed and it's a huge f-mess
[22:06:30] <toastydeath> oh
[22:06:34] <toastydeath> then yeah, air i guess.
[22:06:42] <anonimasu> hilsch vortex tube would be even better..
[22:06:51] <anonimasu> I think that I re-cut chips and that breaks my edges
[22:07:19] <anonimasu> I end up with spraying like 3 meters from the machine with flood coolant on, if I want to get rid of chips
[22:07:55] <toastydeath> yeah, you need a coolant deluge if you're trying to clear chips on a vertical mill
[22:08:36] <anonimasu> maybe I should flip the head around and flip the axes around :]
[22:09:08] <anonimasu> just kidding though, a hilsch vortex tube would be optimal
[22:09:32] <toastydeath> you wouldn't have a chip problem if you did that!
[22:10:57] <anonimasu> * anonimasu draws up a hilsch vortex tube
[22:11:02] <anonimasu> again :]
[22:11:25] <anonimasu> http://www.visi.com/~darus/hilsch/
[22:27:00] <tom1> tom1 is now known as tom3p
[22:42:27] <DaViruz> anonimasu: whats the benefit of using a vortex tube (cool device, btw)? getting more cooling capacity due to colder air?
[22:42:53] <toastydeath> blowing the chips out and keeping part temp down
[22:43:07] <toastydeath> while not providing the same brutal thermal shock coolant does
[22:43:53] <toastydeath> it does not, however, change the temperature of the cut at the tool tip
[22:44:14] <DaViruz> so why not just have an air nozzle?
[22:44:40] <DaViruz> oh, keeping part temperature down
[22:45:37] <toastydeath> just plain air blast will cover 85% of what a vortex tube does
[22:46:21] <toastydeath> the problem with removing coolant entirely is that heavy roughing tools tend to be made of tough, but heat sensitive materials
[22:46:34] <toastydeath> so coolant is necssary for those
[22:46:49] <toastydeath> unless the machine is too light, in which case who cares, i suppose
[23:43:36] <tom3p> the air based coolers are cool ;) did you ever notice you can blow hot or cold air at will? the air at hi prsr thru pursed lips is cooller than the air with your mouth open. its the pressure drop (robert palmer)
[23:44:50] <tom3p> even cooler http://www.youtube.com/watch?v=bUxWmDgSXP4 pressure drop by the specials