#emc | Logs for 2007-09-04

[00:03:23] <JymmmEMC> jepler: http://www.zshare.net/image/346256907852d9/
[01:05:38] <gene__> silly q:
[01:05:54] <JymmmEMC> a: putty
[01:06:31] <gene__> is there a way I can log into this box while emc is running, and query its positions?
[01:06:40] <JymmmEMC> keystick ?
[01:06:50] <JymmmEMC> I'm assuming shelling in
[01:06:55] <gene__> ssh
[01:06:59] <JymmmEMC> yeah
[01:07:22] <JymmmEMC> keystick is CLI interface, can run concurrent and even control it too.
[01:07:33] <JymmmEMC> scarry huh =)
[01:07:52] <gene__> where can i get that, and which machine does it run on?
[01:08:13] <JymmmEMC> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Keystick
[01:08:23] <JymmmEMC> gene__: it runs on the machien you connect to,
[01:08:38] <gene__> this one then.
[01:09:08] <JymmmEMC> does "THIS" machien have emc already on it?
[01:10:11] <gene__> yes, its running a program that won't be done till midnight or so, v2.1.7
[01:10:49] <JymmmEMC> I THINK it has to be configured in advance of starting a job, but best to ask the other guys to be sure
[01:11:06] <gene__> from the sounds of the link, yes,
[01:11:18] <gene__> I'd have to restart
[01:11:23] <JymmmEMC> that link also mentions emc1 too, so not sure.
[01:11:31] <JymmmEMC> you could use live cd I guess
[01:11:42] <gene__> I saw that also.
[01:12:08] <JymmmEMC> It worked great on BDI when I tried it a ways back...dual control
[01:12:22] <JymmmEMC> ok, back in 90
[01:12:44] <gene__> something to investigate later I guess
[01:12:58] <gene__> thanks for the link
[01:13:30] <fenn> try emcsh
[01:14:05] <gene__> I'm going too let this finish in the dark I guess, I'm bushed. I might check emcsh later also, thanks Fenn.
[01:14:31] <fenn> emc_rel_act_pos Returns double objs containing the XYZ-SXYZ actual pos in rel coords, including tool length offset
[01:16:17] <fenn> emc_rel_act_pos 0 returns X position
[01:16:52] <fenn> you have to run emcsh in the directory your .ini is in i think
[01:40:43] <cradek> you should be able to fire up keystick to talk to a running emc, but I wouldn't try it the first time when an important program is running
[01:52:34] <Fritz^2> On axis.unpy.net, I saw an entry about making a custom usb HID device...
[01:53:28] <Fritz^2> Here's what I'm getting and am going to play with: http://www.ultimarc.com/ipac1.html
[01:54:58] <cradek> that looks very interesting!
[02:01:30] <Fritz^2> ...and it's fully programmable by doing a pass-thru connection with a regular keyboard and a text editor :)
[03:52:00] <jmkasunich_> jmkasunich_ is now known as jmkasunich
[04:06:09] <fenn> jmkasunich: re your post on the mail list, did you think i was talking about stepping with the new doublestep driver? i thought it would have a 50% duty cycle normally
[04:06:54] <jmkasunich> stepgen always generates pulses
[04:07:15] <jmkasunich> normally they are one base period long, with doublestep they are whatever the programmed time is long
[04:07:39] <jmkasunich> the only time you get 50% is when you are at the maximum possible speed (one step every other interrupt)
[04:07:47] <fenn> oh
[04:09:18] <fenn> i guess i confused myself
[04:18:47] <fenn> oh man i hate opencascade.. sigh
[04:26:33] <fenn> #($*@% InstallShield wizard for linux..
[04:39:18] <fenn> his License does not grant any rights to use the trademarks, trade names and domain names "MATRA", "EADS Matra Datavision", "CAS.CADE", "Open CASCADE", "opencascade.com" and "opencascade.org" or any other trademarks, trade names or domain names used or owned by the Initial Developer.
[04:40:12] <fenn> i wish i knew what they were thinking
[04:40:30] <SWPadnos> s/what/that/
[04:40:56] <fenn> hey i got this neat new cad library, from SOMEWHERE
[04:41:25] <fenn> i'll give you a copy once sed finishes chugging through 70 THOUSAND FILES
[04:42:09] <SWPadnos> With technology provided by <name withheld by request>
[04:43:05] <fenn> perhaps we could call it IceweaselADE
[04:43:26] <fenn> or just weaselADE
[04:43:53] <SWPadnos> or <name withheld by request>
[04:52:02] <jmkasunich> would somebody do me a favor? can you see if this page loads reasonably fast: http://jmkasunich.dyndns.org/cgi-bin/blosxom
[04:52:25] <jmkasunich> (I had a problem with the thumbnails, which I think I've fixed, but it's always fast from here)
[04:53:05] <SWPadnos> yep. the thumbnails are popping up pretty quickly
[04:53:13] <jmkasunich> cool
[04:53:24] <SWPadnos> the two puma images are the slowest
[04:53:44] <jmkasunich> they're pretty big, and png instead of jpg
[04:53:53] <SWPadnos> yep
[04:54:04] <jmkasunich> I should figure out how to shrink them and do thumbnails like all the rest
[04:54:21] <jmkasunich> or make one more post so they fall of the bottom ;-)
[04:54:21] <SWPadnos> same way - using image magick convert
[05:33:49] <Jymmm> jmkasunich: slow man, slow
[05:35:22] <Jymmm> jmkasunich: If you like, I can "test" your connection for you =)
[05:42:59] <fenn> it loaded fine here
[05:43:14] <fenn> maybe a little slow
[05:43:39] <fenn> nothing compared to compiling opencascade though :)
[05:44:58] <Jymmm> fenn: Well, I have a tiny connection here, just ask SWPadnos
[10:40:43] <renesis> "In the absence of long setup or hold times, the absolute maximum step rate is one step per two BASE_PERIODs."
[10:41:14] <renesis> whats "long setup or hold time"
[12:09:46] <jepler> renesis: it is a characteristic of your stepper driver. However, I used different words there than in the rest of emc's documentation. The normal terms are "step length" and "step space".
[12:11:57] <renesis> ooo that makes alot more sense
[12:12:15] <renesis> microstepping is neat, very quiet
[12:12:17] <jepler> renesis: where did you read that text you quoted? I want to correct it..
[12:12:28] <renesis> sec
[12:13:04] <renesis> http://linuxcnc.org/docs/devel/html/config/ini_config/index.html
[12:13:46] <jepler> renesis: thanks
[12:13:56] <renesis> k ty too
[12:14:21] <jepler> hm maybe somebody besides me wrote that :-P
[12:15:45] <CIA-8> 03jepler 07TRUNK * 10emc2/docs/src/config/ini_config.lyx: improvement of wording about BASE_PERIOD suggested by renesis
[13:51:36] <cradek> jepler: I made some progress on the vacuum table yesterday
[13:52:04] <cradek> (between problems with the mill)
[13:52:16] <cradek> I also did a lot of troubleshooting and think I have a couple of its problems figured out
[13:52:39] <jepler> cradek: I barely touched my machine all weekend
[13:53:00] <jepler> I need a dial indicator or something to help me quantify the table slope
[13:53:40] <jepler> but after tightening the spindle holder the "dots appeared as small circles" problem seems to have gone away
[13:54:00] <cradek> that's good
[13:55:22] <jepler> oh, and the threaded inserts are 1/4-20 as you had thought
[13:55:38] <cradek> cool
[13:56:25] <jepler> did you run that small vacuum pump yet?
[13:57:01] <cradek> http://www.cdcotools.com/item.php?itemid=96
[13:57:09] <cradek> nope not yet
[13:57:27] <cradek> this is the most obvious kind of indicator to use, but the mountings are both too big for your spindle
[13:58:02] <jepler> there's also the extremely limited height available on Z
[13:58:58] <cradek> see right under the dial there is a dovetail that you can use for mounting
[13:59:13] <jepler> oh, I see
[13:59:18] <cradek> so, it takes very little height, the dial sticks out horizontally
[13:59:28] <jepler> well then, just stick the 3/8" clamp in a lathe and turn it down to 1/8
[14:00:41] <cradek> I think these probably have screws through them, so it's not that easy
[14:00:47] <cradek> I'm not familiar with that style of clamp
[14:01:02] <cradek> mine has a nut on the outside
[14:01:06] <jepler> oh, I can kinda see that
[14:01:20] <cradek> (I'm going to order some stuff from these guys today)
[14:12:46] <jepler> if I could see how to use it on my machine I'd sure have you order it
[14:20:43] <cradek> hmm, I blew right past $70
[14:21:46] <SWPadnos> is it possible to order from a machine/tool supplier and not spend $70?
[14:21:52] <cradek> need anything else from cdco?
[14:22:12] <cradek> SWPadnos: jepler and I joke that ordering one little thing from mouser etc. costs $70
[14:22:29] <SWPadnos> heh - so true
[14:23:03] <cradek> SWPadnos: this company has a lot of the cheap-but-seems-good chinese stuff that 800watt sells
[14:23:25] <SWPadnos> ah. I got a lot of that stuff from Machine Tools Direct (eBay)
[14:23:36] <SWPadnos> and another company I don't remember the name of
[14:54:22] <cradek> CDCO also takes payment by paypal, which I like, because they don't get my cc#
[16:31:58] <jmkasunich> jepler: regarding turning down the indicator mount - it's probably hardened
[17:07:59] <fenn> you dont need to mount it in the spindle to check for table flatness (parallelism)
[17:10:27] <archivist> spindle mount checks spindle squareness to table (can do if offset and rotated)
[17:22:36] <fenn> you dont even really need a DTI for checking spindle squareness
[17:41:22] <fenn> compiling opencascade only took 9 hours
[17:43:43] <SWPadnos> you need to try something other than those 200 MHz panel PCs :)
[17:43:55] <SWPadnos> and no, having 10 of them doesn't make it any faster
[17:44:19] <fenn> what if i make a cluster of 30 of them?
[17:44:32] <SWPadnos> that could be faster, unless they only have 10Base-T
[17:44:32] <archivist> upgrading from an 8080 is an option
[17:44:44] <SWPadnos> Z-80,000, baby!
[17:44:54] <SWPadnos> but I think they never released it
[17:45:02] <archivist> nah 6502 was faster
[17:45:12] <SWPadnos> hahahahaha
[17:45:23] <archivist> the original risc
[17:45:38] <SWPadnos> closer to 0isc
[17:47:36] <archivist> JymmmEMC, a troll in ##php to kickban Farzad
[17:50:22] <ds2> EMC/beowulf!
[18:08:24] <cncjunior> hello !
[18:08:59] <jepler> hello cncjunior
[18:10:24] <cncjunior> i want to test how trajectory planner influence the positioning accuracy
[18:11:00] <cncjunior> where is it implemented the trajectory planner ?
[18:13:42] <jepler> cncjunior: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Simple_Tp_Notes says "The source is documented and meant to be easy to read/understand. The files are in emc2/src/emc/kinematics"
[18:15:04] <cncjunior> ok, thank you
[18:17:04] <cncjunior> i found some topics on trajectory planner from march, 2006 wrote by cradek
[18:17:36] <jepler> there have not been any huge changes since that time.
[18:17:50] <jepler> mostly addition of small features such as spindle synchronized motion, as well as bug fixes
[18:18:22] <cncjunior> i want to compare the old trajectory planner with this one
[18:19:01] <cncjunior> on which version is the old one ?
[18:19:38] <cradek> I'm just curious - are you having a problem that you think is a bug?
[18:19:52] <jepler> all released versions of emc2 incorporate cradek's trajectory planner.
[18:20:05] <cncjunior> no
[18:20:47] <cncjunior> i use emc2 on a research regarding the optimization of cnc milling machines
[18:22:02] <cncjunior> with your help i understand how to implement feed rate override and spindle speed override almost in real time ( 0.2 seconds )
[18:24:44] <cncjunior> now i want to modify the source code of the trajectory planner and see the modifications
[18:27:33] <cncjunior> cradek : i want to try with the same file - narrow.ngc from your example but the link don't work
[18:29:05] <jepler> what example refers to "narrow.ngc"?
[18:30:16] <cncjunior> it was an example used by cradek with axis in march, 2006
[18:30:44] <cradek> sorry I don't remember what I had for lunch yesterday
[18:31:46] <cradek> if you have a screenshot of a test case you should be able to approximately rewrite the gcode
[18:32:40] <cncjunior> the files were on timeguy.com/cradek-files/emc/nasty-blend.png
[18:34:29] <cncjunior> at that moment i want to try that example and see what hapens
[18:40:32] <jepler> those very old screenshots are from just before or after the "simple_tp" planner was merged into the TRUNK; they probably refer to bugs that existed for a short time and were fixed..
[18:46:46] <cncjunior> i don't know if they were bugs, for me is useful to understand the old trajectory planner and the new one
[18:48:45] <cradek> http://timeguy.com/cradek-files/emc/.old/nasty-blend.png
[18:49:02] <cradek> this is one of the wrong behaviors of the old planner
[18:49:21] <cncjunior> cradek: thank you,
[18:49:22] <cradek> you can see enough gcode in the image to retest this case if you want
[18:49:34] <cradek> of course it will work today
[18:51:02] <cncjunior> cradek : i want to test it on YOZ plane
[18:52:08] <rap2> is there a way to import the emc.ini from EMC2 into EMC2?
[18:52:23] <rap2> er EMC1 to EMC2 that is
[18:52:42] <cradek> rap2: the numbers to copy down are your max velocity, max acceleration, and axis scales
[18:52:52] <cradek> other than that you should not keep your old ini file
[18:53:04] <cradek> just set those values in the new file
[18:53:33] <rap2> I use a stg card. would that be the stg.ini?
[18:53:54] <cradek> yes, when you start emc2, pick the stg sample configuration
[18:54:05] <cradek> it will copy it to your home directory, and there you can modify it with the values you need
[18:54:30] <rap2> so I have to set forth axis, sever versus stepper and all that?
[18:55:04] <rap2> is the stg.ini file the only one I need to edit?
[18:55:08] <cradek> yes you have a little work in front of you. So much is different there's not a straightforward conversion.
[18:55:35] <cradek> rap2: I can't say. It depends what all is on your mill.
[18:55:50] <rap2> cool thank you for the help at least I know (sorta) what I am up agenst.
[18:56:07] <cradek> good luck rap2, come back with specific questions if you get stuck
[19:06:03] <jepler> one characteristic of the current trajectory planner that I don't think has been extensively studied: does the commanded path actually remain within the tolerance specified G64 P- compared to the ideal path specified in the gcode?
[19:07:37] <jepler> (actually I am quite certain you can find conditions where the difference between commanded and ideal is 2*P, because the interpreter combines multiple "straight feed" moves that are all within tolerance P of a single straight feed; and then the trajectory planner can stray an additional P from that modified path ...)
[19:08:50] <jepler> the constraints test have also not been run for more than 4 axes (XYZA); the development version of emc now permits up to 9 axes (XYZABCUVW)
[19:09:57] <cncjunior> i have only a 3 axis cnc milling machine, only for research
[19:11:41] <cncjunior> i will put some optic sensors in well determined positions and check if the real path coresponds with ideal path
[19:11:57] <jepler> depending what you want to measure, you may not need to use a real physical machine. Most of the testing I refer to was done on a simulated machine, with xvel, xacc, yvel, and so on computed by hal 'ddt' blocks, and exceeded constraints being flagged by a 'wcomp' block for each constraint.
[19:12:26] <cradek> I think optical sensors will test your machine more than they will test the software
[19:12:35] <cradek> it sounds fun
[19:13:43] <cncjunior> here in Romania we have a few word: theory like theory but the practice killing us
[19:14:04] <jepler> In theory, theory in practice are the same.
[19:14:05] <jepler> er
[19:14:07] <jepler> In theory, theory and practice are the same.
[19:14:43] <cncjunior> i want to see not only on the screen but also on the machine
[19:17:28] <cncjunior> the emc2 is a very good platform for research
[19:18:30] <cncjunior> if you think that my experiment is interesting i can described it
[19:19:08] <cncjunior> thank you for your help
[21:40:50] <tomp> if i move really really slow (say 0.01mm/minute) and am moving a vector of 3um X and 1um Y, (G91 G01 X.003 Y0.001 F0.01)... will i observe something like steps, even though it's a servo system?
[21:41:35] <anonimasu> no
[21:42:00] <tomp> will it smoothly move thru the 3um?
[21:42:09] <anonimasu> yeah
[21:42:24] <anonimasu> tomp: given that you have small enough encoders to handle it..
[21:42:26] <tomp> how can it resolve less than the 1um on my scales?
[21:42:32] <tomp> i got 1um
[21:42:41] <tomp> heidenhain ls130
[21:43:18] <anonimasu> then I dont know
[21:43:24] <tomp> tat 1 um scale rez, and 1um smallest command unit, i think it will act like steps
[21:43:51] <anonimasu> tomp: yeah, you cant really move smaller then your motor can see..
[21:43:58] <anonimasu> motor/control
[21:44:55] <anonimasu> tomp: dont they usually say that you need 10 times better resolution then the minimum detail you want to be able to cut?
[21:45:01] <tomp> than the control can see from the feedback. it's just that the step-like quality 'scared' me.
[21:45:36] <anonimasu> tomp: well, add a tach/encoder/anything that tells your machine your motor is moving
[21:45:38] <anonimasu> :/
[21:46:03] <anonimasu> I dont know about your machine.. or how that works.. though your servo jitter should be around 1um too right?
[21:46:07] <tomp> yes, and i cant afford that, and if i use .001" scales, it'd be the same story for .001"x .003"y ( wether i interpret it correct or not, it'd be the same story, for me and all )
[21:46:33] <tomp> servo jitter is .001 ( dro and lag show 0 or .001 )
[21:46:47] <anonimasu> 0.001 = what?
[21:46:51] <tomp> mm
[21:46:57] <tomp> 1um
[21:47:49] <anonimasu> hm, I wonder if the motor will interpolate so you move 1um in 1 minute.. or whatever you specify..
[21:48:03] <anonimasu> dosent really seem plausible though as you have no feedback
[21:48:25] <tomp> i think i have to sub count like you said ( use 1/10 smallest command unit ) and display only 3 decimal places to >reduce< this steppiness
[21:48:33] <anonimasu> yeah
[21:48:54] <anonimasu> tomp: I think to do it you need to interpolate it somehow
[21:49:24] <anonimasu> im wondering what would happen as 1um is the space pid has to keep in position within
[21:49:30] <tomp> slow speed is a bitch, right, no feedback for long periods of time (many servo cycles)
[21:49:45] <anonimasu> tomp: I dont think that would work
[21:50:40] <anonimasu> tomp: though maybe you could write a tp that handles that
[21:50:45] <anonimasu> or modify it.
[21:50:51] <anonimasu> way ahead of me
[21:52:33] <tomp> well i begin by feeding analog voltages to an amp, and hope that the tp i use can make motion as nice as that. or consider that a goal to get closer to
[21:53:09] <anonimasu> tomp: well, you cant do pid that way..
[21:53:25] <tomp> no no no no not pid, just p
[21:53:39] <anonimasu> hm, well, that'd work
[21:53:50] <tomp> velocity is proportional to my control voltage
[21:54:15] <tomp> yeah, kinda off topic for here, thanks
[21:55:06] <anonimasu> :9
[21:55:08] <anonimasu> I dont mind
[21:55:14] <anonimasu> it's just that i dont understand how to do it
[21:57:11] <tomp> monitoring lag is interesting, today ( non-emc) i used it to find a bad ballnut. once at speed, a good system has a constant lag (+/- 1 unit jitter), and this one had up to 18.
[21:57:57] <tomp> i removed/replaced the thrust and tension bearing, but still had 12 units... removed the hi-win ballscrtew to feel a real click every rev :(
[21:58:32] <tomp> i bet hal can be used to help debug such problems
[22:01:37] <fenn> you can plot acceleration vs current
[22:02:08] <tomp> no current difference seen, lag is more 'fine'
[22:02:42] <fenn> if there's a dip in acceleration and the current stays the same, it means something is binding or not working right there
[22:02:51] <tomp> the amp's current output looked pretty steady ( copley 423 )
[22:03:21] <tomp> 500mV max output tho, so signal buried in noise
[22:04:45] <tomp> sorry current monitor, not output
[22:07:12] <fenn> well, just feed the amps a known signal
[22:07:25] <tomp> fenn: any ideas on very slow speed control? can you scroll back?
[22:07:30] <fenn> use sensitive tachos
[22:07:52] <tomp> fenn: yess, used a lab power supply eventually my brain kicked in.
[22:08:30] <tomp> tachos for slow speed or debugging stickies?? ( both i 'spose )
[22:08:49] <fenn> for slow speed
[22:09:13] <fenn> they're just motors with a high volts/rev ratio
[22:09:47] <fenn> if you spin them too fast i suppose the coil inductance kicks in to limit current
[22:09:55] <fenn> but i dont really know
[22:10:44] <fenn> hmm.. another option would be to use a sinusoidal encoder somehow
[22:10:52] <fenn> all encoders are sinusoidal at some point
[22:11:17] <tomp> yeh, but mine 'frets' ( jitters ) and the overall motion is slow velocity ( maybe several hundreds of +1/4um -1/8um a couple whole ums that cancel each other... meaning, well ... 0 )
[22:11:37] <tomp> all inside 1 servo cycle of 4mS
[22:12:18] <fenn> hm.. what's moving the motors if its within one servo cycle?
[22:12:30] <anonimasu> fenn: he's not running PID..
[22:12:34] <anonimasu> fenn: just P..
[22:12:45] <tomp> right, didnt point that out, its just P
[22:12:54] <anonimasu> tomp: resolvers might work for that
[22:12:55] <fenn> ok so why do you have a servo cycle at all?
[22:13:29] <tomp> just to check up on things ( out of bounds, off track, too big a signal swing since last )
[22:14:05] <tomp> and maybe... ooh we made progress, move over here now ( change the target )
[22:14:05] <fenn> so there is a PID with a wide deadband, and an analog P loop inside that?
[22:14:40] <fenn> or not analog?
[22:14:42] <tomp> no pid at all, no deadband desired ( theres always some ), only a p loop with a cyclical check
[22:15:59] <tomp> loop may be a bad word here, only a p control is better
[22:16:41] <fenn> i wonder if there is a such a thing as a resonant resolver
[22:16:52] <Ziegler> http://www.xkcd.com/309/
[22:17:10] <tomp> the loop that exists is rechecking and varying the P to get on track if necc, or to speed up if poss, or to abort becuz the position feedback says i fell off the edge of the map
[22:18:34] <fenn> i dont get how it can back up if P stays the same
[22:19:01] <tomp> P doesnt, p is created eaqch cycle from the process control
[22:19:17] <tomp> p doesnt care what it was last cycle
[22:19:19] <fenn> then how does it do "+1/4um -1/8um all inside 1 servo cycle of 4mS"
[22:20:10] <tomp> i'ts LIVE P, it's an initial value and live modified by the process. so it can change a bit
[22:20:40] <tomp> imagin connecting a pot to an analog amp, replace the pot by a process, limit the pot by a range
[22:21:09] <tomp> you got live dynamic fwd/bwd in a range, and you checdk it cyclicly
[22:24:52] <tomp> good q tho... i got n servo updates per evaluation in the system i'm modeling after...., i dont have this stuff in emc yet
[22:28:00] <anonimasu> tomp: I think you need to figure it out how to omit the normal servo driver(modify it) to just handle what you want
[22:29:08] <tomp> fenn: you right , what i observed can't be inside a servo cycle, it was inside many, i was reporting 'tracking'
[22:29:51] <tomp> doh, i cant see the dro that fast , and wasnt logging
[22:52:57] <anonimasu> *yawn*
[23:07:13] <fenn> aw crap. ran out of disk space while linking the opencascade files
[23:08:23] <fenn> 2.9G and counting
[23:21:53] <anonimasu> fenn: do you have any idea what changing the paper "thickness" for a laser printer does?
[23:24:23] <fenn> uh, makes the paper thicker? :)
[23:24:41] <anonimasu> heh, does it print with more toner..
[23:24:45] <anonimasu> more heat less heat?
[23:25:00] <fenn> i think the printer usually keeps the fuser a constant temperature
[23:25:17] <SWPadnos> changing thickness with a lever or in some config dialog?
[23:25:32] <anonimasu> in some config dialog
[23:25:47] <anonimasu> im doing toner transfer to a pcb.. and im wondering if changing it will give me more toner
[23:26:18] <SWPadnos> I don't think so, but I'm not sure what they're doing, to be honest
[23:26:17] <fenn> try it and see
[23:26:45] <anonimasu> or well, same amount of toner and faster/less heated paper
[23:27:00] <fenn> yeah maybe its the speed the paper goes through
[23:27:16] <fenn> in which case you'd probably want it set to "thinnest"
[23:27:33] <anonimasu> yep
[23:28:17] <anonimasu> that's what I'm thinking about
[23:28:25] <anonimasu> I want the toner to come off easily :9
[23:28:40] <fenn> what kind of paper are you using btw?
[23:29:00] <anonimasu> I found some glossy laser printer paper that works
[23:29:18] <anonimasu> http://imagebin.org/10243
[23:29:50] <fenn> anyone know why copying files takes up 100% cpu?
[23:30:07] <anonimasu> that's the first pcb I've ever made :)
[23:30:34] <anonimasu> it just took ~5 hours of messing about finding a paper that would transfer ok
[23:30:49] <fenn> heh 5 pins. i cant see much detail so i wont try to analyse anything
[23:31:04] <anonimasu> http://imagebin.org/10245
[23:31:06] <anonimasu> closeup :)
[23:31:35] <anonimasu> it's a smd opamp
[23:31:41] <anonimasu> err for
[23:32:01] <fenn> yep looks good enough. try lowering temperature and increasing iron pressure (use the edge of the iron)
[23:32:16] <anonimasu> hm, use a higher dpi printer..
[23:32:50] <fenn> the rounded corners and wobbliness are from too high a temperature
[23:33:25] <fenn> but it works eh?
[23:33:31] <anonimasu> yeah
[23:33:46] <anonimasu> now I have a stupid 5x5mm chip with 8 leads..
[23:34:04] <fenn> next time make more than one
[23:34:16] <fenn> unless pcb stock is expensive (i got it practically free on ebay)
[23:35:13] <anonimasu> it's expensive..
[23:35:18] <anonimasu> depends on where you buy it though :)
[23:36:57] <anonimasu> fenn: I think it's low dpi because everything came clean off the paper..
[23:37:07] <anonimasu> 600dpi..
[23:37:31] <anonimasu> 23points per square mm...
[23:37:47] <anonimasu> 0.04.. that's big :p
[23:39:53] <fenn> ah good old linux. re-mounting part of one (mounted) filesystem over another one would have been impossible in most operating systems
[23:40:04] <anonimasu> fenn: does that sound sane?
[23:40:17] <anonimasu> fenn: at 1200 dpi the dotsize of 0.02mm :)
[23:40:37] <fenn> look at the printout and see if it's satisfactory
[23:40:53] <anonimasu> it looks like that on the printour..
[23:40:53] <fenn> if you have wobblies and rounded corners on the printout, no amount of ironing is going to fix it :)
[23:40:57] <anonimasu> printout..
[23:40:58] <SWPadnos> 1200 DPI is only 1/8 the resolution of a real photoplotter
[23:40:59] <anonimasu> :)
[23:41:07] <anonimasu> photoplotter?
[23:41:19] <fenn> laser beam on x/y table, draws on photographic film
[23:41:21] <SWPadnos> what the professional PCB houses use to make gerber plots
[23:41:25] <anonimasu> ah
[23:41:50] <SWPadnos> at least, that's what the prototype house I just ordered from uses :)
[23:42:02] <jepler> Results 1 - 10 of about 2,610 for pentium "heat sync" </google>
[23:42:22] <anonimasu> SWPadnos: I'm happy if I can prototyep smd stuff in my kitchen :p
[23:42:26] <SWPadnos> well, you need synchronized heating or SMP performance is unpredictable
[23:42:42] <SWPadnos> anonimasu, mmmm - I love the smell of baking etchant
[23:42:49] <anonimasu> lol
[23:43:02] <SWPadnos> hmmm. I should go get some donuts with my cream. bbl
[23:43:07] <anonimasu> night :)