#linuxcnc | Logs for 2012-09-13

[01:09:42] <nathanstenzel> hi
[01:09:54] <nathanstenzel> so, anybody here?
[01:11:02] <nathanstenzel> I guess not
[01:16:13] <nathanstenzel> anyone have any experience with rotation nut designs for use with lead screws?
[01:16:52] <Jymmm> you mean an anti-backlash nut?
[01:16:59] <nathanstenzel> nope
[01:17:08] <Jymmm> then nope
[01:17:29] <nathanstenzel> I mean a stationary screw with a spinning nut/pulley
[01:17:48] <Jymmm> might try back in 6 hours
[01:18:36] <nathanstenzel> it is described here: http://www.cnczone.com/forums/diy-cnc_router_table_machines/127299-rotating_lead_nut_design.html
[01:20:01] <nathanstenzel> evdently some hoss machine and a 1970's bridgeport machine useed it
[01:21:16] <nathanstenzel> It is supposed to have no resonance problem and would be able to use an anti-backlash nut just like a setup with a spinning lead screw would
[01:24:14] <nathanstenzel> people tell me my long lead screw would do no good, but it sounds like it should probably be fine with the rotating nut design. I came up with the idea the other day and then found out tonight that it was used before
[01:25:17] <nathanstenzel> not sure if it was used exactly like I plan on using it, but oh well
[01:38:01] <nathanstenzel> good night
[01:42:25] <DJ9DJ> moin
[02:43:18] <V0idExp> hi all!
[02:44:33] <DJ9DJ> hi there
[02:44:50] <V0idExp> have a question... related to the same situation explained a week ago. I have a piston that feeds ink to a XYZ dyeing head. The piston is driven as spindle, and it's a step drive.
[02:46:28] <V0idExp> So, the question is... :) when my piston reaches the limit (the ink is finished) I want some GCode to be executed immediately, or at least, being notified on that, and interrupt any dyeing process... is that possible?
[02:49:26] <V0idExp> I'll explain better. My head goes here and there on XY plane, then, when there's something to paint, the Z stepper pushes the head down near the plane and it starts to paint by activating the piston spindle and moving on plane.
[02:50:59] <V0idExp> as soon as it has finished, the spindle stops (no ink is fed) and the Z motor raises the head up. Thats' all :)
[02:51:56] <V0idExp> but, obviously, there may be an exceptional situation, when the head is in painting mode (down to the plane) and the ink in the head is finished, which occurs when the piston reaches its lowest limit
[02:52:03] <V0idExp> I need a way to handle this situation
[02:52:35] <Jymmm> like a limit switch?
[02:52:38] <Valen> i don't think anything off the shelf will do that?
[02:52:43] <V0idExp> yes
[02:53:27] <Valen> limit switch would cause it to stop, i don't think you could then go and refill it or whatever
[02:53:38] <Valen> and then continur
[02:53:42] <Valen> continue
[02:54:12] <Valen> not without hooking into something lower level anyway
[02:55:02] <V0idExp> well, the idea is to have that switch stop everything, sure, but it should also notify my software (which is python based on linuxcnc API) about that, so it will automatically launch the "refill the head" procedure (GCode prgoram)
[02:55:31] <Valen> I'd be more inclined to approach the problem from the other end
[02:55:41] <V0idExp> :)
[02:55:42] <V0idExp> ?
[02:55:45] <Valen> make it so you dont run out of paint in the first place
[02:56:02] <Valen> if your stepping the paint out you should be able to know when your getting low
[02:56:05] <V0idExp> unfortunatelly, it's impossible by design :(
[02:56:36] <Valen> hook the thing up as an axis rather than the spindle
[02:57:22] <V0idExp> but if I set it up as an axis, I'd have to control it with positions, not rotate/stop commands
[02:57:59] <Valen> how are you making the gcode?
[02:58:14] <Valen> got a picture of your whole setup?
[02:58:33] <V0idExp> I mean, I'd have to control it with G01 command. but it's not obvious to find out by how much distance the piston should go down to feed ONLY the ink needed for painting that piece
[02:59:12] <V0idExp> My code is generated by our software, which basically builds a NGC program based on things painted by user on screen
[02:59:31] <Valen> presume it'd be related to the length, i mean it'd be similar to how your running now, x units will cover y distance
[02:59:37] <Valen> sounds like it'd be easier in a way lol
[03:00:00] <Valen> currently you turn spindle on and g1 a distance of 100 units
[03:00:06] <V0idExp> yes
[03:00:08] <Valen> you set the spindle speed to match the distance
[03:00:11] <Valen> bah
[03:00:14] <Valen> match the speed rather
[03:00:43] <Valen> so work out how many steps your spindle is going to do over that 100 unit distance
[03:01:08] <Valen> now do a G1 with your A axis doing the same number of steps as your spindle was going to do
[03:02:04] <Valen> if your spindle is controlled by EMC there shouldn't really be a difference, as you cant tweak the spindle speed outside the program anyway
[03:03:12] <V0idExp> ehm... haven't understood well your idea. for example, I have to paint a straight diagonal line:
[03:03:15] <Valen> V0idExp: thoughts?
[03:03:37] <V0idExp> 1) m103 p100 (custom command, turns spindle on and rotates at 100 rpm)
[03:03:55] <dhoovie> if you use G1 and the A axis, I wasn't able to get the machine off exact stop mode though :( wasn't doing exactly the same thing but that may be a consideration.
[03:04:09] <V0idExp> 3) g0 z100 (moves the head down)
[03:04:29] <V0idExp> 3) g01 x100 y100 f100 (paints)
[03:04:35] <V0idExp> *4) :D
[03:04:45] <V0idExp> 6) g0 z0 (moves the head up)
[03:04:50] <V0idExp> 5) m103 p0 (stops the spindle)
[03:04:50] <V0idExp> that's all
[03:05:22] <V0idExp> the step 3) is the only variable thing.... I mean, it all depends from the shape designed by user. so there can be thousand steps like that before the spindle turns off
[03:05:47] <V0idExp> I mean, the painting process can be one line or thousand lines program, all are g01's
[03:06:04] <V0idExp> and the speed also varies
[03:06:26] <V0idExp> sometimes it's f100 (on angles) and sometimes it's f2000, on long straight lines
[03:09:14] <dhoovie> V0idExp: I think Valen means instead of doing m103 p100 attach the head to the A axis and use g01 x100 y100 a(some amount) f100
[03:09:18] <V0idExp> sorry guys, if I'm confusing you, I'm not english and maybe I'm writing stupidities, as it may seem for you
[03:09:50] <V0idExp> I got that... but that "some amount" need to be calculated in some way
[03:10:05] <Valen> well are you controlling the spindle speed now?
[03:10:50] <Valen> ahh there it is
[03:10:57] <Valen> your p100
[03:11:42] <Valen> if you know the feed distance, and the rate then you know how many steps the spindle would make over that time
[03:11:54] <Valen> just have it do the same on an a axis
[03:12:16] <dhoovie> number of a steps = speed * ( distance to be moved / feedrate )
[03:12:25] <dhoovie> approximately
[03:12:35] <Valen> give or take
[03:12:47] <Valen> then you don't need to worry about running out of paint in the middle of a line
[03:13:04] <Valen> in your generation program when a gets close to some limit, trigger your fill
[03:13:28] <dhoovie> though, then you need a stepper or servo on the head
[03:13:38] <Valen> already has a stepper by the sound of it
[03:13:50] <dhoovie> ohh then you are mint
[03:14:05] <dhoovie> also, i don't know how to get off exact stop mode for a moves
[03:14:27] <Valen> as in your in that mode and dont want to be dhoovie?
[03:14:32] <dhoovie> uhh i mean A axis moves
[03:14:38] <dhoovie> yep.
[03:15:09] <Valen> hang on, are you still talking about V0idExps problem or a new one of your own?
[03:15:33] <dhoovie> well, you just have to take it into consideration.
[03:15:43] <dhoovie> but at least it works. it is a new problem though :(
[03:15:52] <V0idExp> suppose I can do that. How does it solves the problem? I mean, every motion has to calculate where the next position will be and store it. But that's not a problem. The problem is that if I trigger the limit switch...
[03:15:53] <Valen> shouldn't really matter
[03:16:03] <V0idExp> it will simply ESTOP everything
[03:16:11] <Valen> your gcode generator should be able to solve the problem
[03:17:15] <dhoovie> V0idExp: a simple test before hand as to the number of rotations before you need a refill. add a bit of a safety factor and after you hit that many degrees go for a refill.
[03:17:54] <V0idExp> good idea.
[03:18:35] <V0idExp> at that point I can simply do the following... still handle the piston as spindle, place two switches, one which notifies about "ink is almost finished!" and one that stops everything.
[03:19:31] <V0idExp> *signal
[03:19:31] <V0idExp> this won't cause great changes in code... the only problem is that I'd have to constantly listen on the trigger...
[03:19:47] <V0idExp> or LinuxCNC can invoke automatically some code when something occurred?
[03:19:57] <V0idExp> Suppose, it's realtime stuff
[03:20:59] <V0idExp> as for now, all I need is LinuxCNC stopping everything immediately when "NO INK" signal is triggered and notify it to me
[03:25:06] <r00t4rd3d> like a limit switch
[03:25:15] <V0idExp> yes
[03:25:36] <r00t4rd3d> so set it up like one
[03:26:47] <V0idExp> ok, think that an A-axis approach is da way
[03:26:57] <V0idExp> the A axis is a normal axis controlled by speed?
[03:27:01] <V0idExp> it can be homed, etc?
[03:27:24] <r00t4rd3d> im not sure but i imagine
[03:27:27] <dhoovie> it is a normal axis
[03:27:36] <r00t4rd3d> never used a 4 axis
[03:27:36] <dhoovie> and its controlled by angle
[03:28:23] <V0idExp> by angle?
[03:28:37] <V0idExp> what the g0 .... A parameter expects?
[03:29:19] <r00t4rd3d> V0idExp, do you have a picture of what your working on?
[03:30:29] <dhoovie> g0 a100 would be move a to 100 degrees
[03:31:39] <V0idExp> wait for a copypaste :)
[03:33:35] <V0idExp> My head goes here and there on XY plane, then, when there's something to paint, the Z stepper pushes the head down near the plane and it starts to paint by activating the piston spindle and moving on plane. [09:39] <V0idExp> as soon as it has finished, the spindle stops (no ink is fed) and the Z motor raises the head up. Thats' all :)
[03:34:04] <V0idExp> anyway, I'll try to set it as another position-controlled axis.
[03:34:27] <V0idExp> as for now, thank you all! I'll notify you about some changes or adopted solutions :)
[05:07:51] <r00t4rd3d> islam is the nazi party of the 21st century
[05:09:59] <r00t4rd3d> w/c
[07:16:48] <cncbasher> setting up a stepper driven machine with shaft encoders , should i use position or velocity contol type
[07:17:26] <jthornton> velocity
[07:17:38] <cncbasher> good .. got that right haha
[07:18:21] <jthornton> also I think your steps need to be finer than the encoder counts by at least 2x
[07:18:49] <cncbasher> never try'd shaft encoders on a stepper machine , so open to guidance
[07:19:26] <cncbasher> 200 steps with 2500 count encoders
[07:19:54] <jthornton> any microstepping on the drive?
[07:20:02] <cncbasher> yes
[07:20:36] <cncbasher> at the moment running half step
[07:21:18] <jthornton> I think it only works if your step count per rev is twice the number of encoder counts... at least that is what I've heard
[07:21:34] <cncbasher> but i can go to 40,000
[07:22:21] <archivist> I would think so because it can never get to a commanded encoder position if below the encoder qty
[07:23:17] <cncbasher> ok i'll have a go with it at 6,000
[07:23:57] <cncbasher> which is the closest i have , it's either 4,000 or 6,000
[07:23:58] <jthornton> is your encoder 2500 pulses per rev or 2500 lines with 10000 pulses per rev?
[07:24:16] <cncbasher> 2500 per rev
[07:24:42] <jthornton> 6k should work from what I've heard
[07:25:19] <cncbasher> ok thanks john interesting to see what results i get
[07:25:41] <jthornton> just remembered I have a stepper with an encoder mounted on...
[07:25:47] <jthornton> yes keep us posted
[09:17:12] <seb_kuzminsky> here's a pretty neat free online feed/speed calculator: http://zero-divide.net/index.php?page=fswizard
[09:50:07] <V0idExp> hi again guys!
[09:50:37] <V0idExp> well, as for now that problem with the stepper-driven-piston is not that important.
[09:51:19] <V0idExp> what I want to know from you, if it's easy to answer, is the following... in PNCConf (using a 7i43 mesa board) the latency matters if i'm using ONLY stepper drives?
[09:51:34] <V0idExp> I mean, setting a wrong value in that field can be a source of problems?
[09:52:10] <V0idExp> cause I'm getting "joint 0 following error"
[09:52:22] <V0idExp> if I try to move at higher speeds
[09:52:44] <archivist_> latency matters regardless of motor type, it matters differently though
[09:53:19] <archivist_> also depends on the driving method, hardware v software stepping
[09:55:03] <V0idExp> suppose, using mesa boards is the "hardware way"?
[09:55:19] <archivist_> yes
[09:55:22] <V0idExp> cause I could reach high speeds without mesa, just only Parallel Port & stepconf...
[09:55:47] <V0idExp> and with mesa I'm getting "joint 0 following error" just when I'm going faster than 2k mm/min
[09:55:53] <pcw_home> joint x following error can be because you dont have enough velocity or acceleration headroom
[09:55:55] <pcw_home> (that is the stepgens mavxvelocity and max acceleration should be set about 20% more than the machine limits)
[09:56:29] <V0idExp> but with same values of velocity and acceleration it worked with software stepping o_O
[09:56:49] <pcw_home> also steplen and stepspace timing will limit your maximum step rate
[09:57:03] <V0idExp> well, I'm sure those are set correctly
[09:57:09] <cncbasher> voidexp: in your ini file change ferror to 1.0
[09:57:23] <V0idExp> so, vel || aceleration || base_thread may be the problem..
[09:57:28] <V0idExp> ok
[09:57:32] <V0idExp> what's ferror?
[09:57:44] <cncbasher> follow error
[09:57:59] <V0idExp> and setting that to 1 what will do?
[09:58:20] <pcw_home> make sure your stepgen acceleration limit is ~20% more than your machine acceleration value
[09:59:09] <cncbasher> which version of linuxcnc are you using and what stepper drivers ?
[09:59:33] <V0idExp> LinuxCNC 2.5.1, LAM Technologies stepper drives (1.7 arms / 0.5 Nm)
[09:59:34] <pcw_home> and make sure that the stepgen maxvel is not limiting velocity
[10:00:03] <V0idExp> oops, stepper drives don't know... have a sheet of them
[10:00:08] <V0idExp> that info was about motors
[10:00:34] <V0idExp> but timings are set well, that is sure 100%
[10:00:37] <cncbasher> it's the stepper drivers we are interested in
[10:00:53] <cncbasher> ok
[10:00:57] <V0idExp> what you want to know about steppers?
[10:01:03] <V0idExp> *drivers
[10:01:26] <V0idExp> dirhold: 100000, dirstep: 100000, step len: 3000, step space: 6000
[10:02:05] <pcw_home> if you get a joint following error with the hardware stepgen, it most likely bad stepgen maxaccel or stepgen maxvel settings
[10:02:18] <V0idExp> ok. i'll try to play with them
[10:02:27] <V0idExp> I'll be back.
[10:03:08] <pcw_home> also those are really long dir setup and hold times, are those really needed?
[10:03:46] <cncbasher> dirhold and setup are far to high as pcw says 20000 should be nearer the mark
[10:04:04] <cncbasher> send me your hal and ini files
[10:04:08] <pcw_home> steplen and step space will limit you to 111 KHz
[10:04:51] <pcw_home> which is probably fine unless you have very high ustep ratios
[10:05:11] <V0idExp> ustep is 200, multiplicator is 4
[10:06:11] <V0idExp> also, motor:screw ratio is 16:1
[10:06:46] <V0idExp> well, just called by a colleague to help him with some programming, I'll be back in some minutes and I'll send you the ini & hal files
[10:08:16] <cncbasher> would be nice to know what stepper drivers you have just so we can check the timings more precisely .. if you have a model number
[10:10:41] <cncbasher> i'll presume there opto coupled inputs so a default of 20000 for dir hold and dir step with step len and space of 3000 should be a resonable start
[10:20:09] <V0idExp> LAM technologies, LS1044/OS1044 passive stepper drivers
[10:20:16] <V0idExp> i'll give you al link in a second
[10:20:38] <V0idExp> we're using "safe" timings
[10:20:46] <V0idExp> doubling the minimal times
[10:21:22] <V0idExp> http://www.lamtechnologies.com/Product.aspx?lng=EN&idp=LS1044
[10:23:39] <cncbasher> yea the default settings i gave should work fine
[10:24:18] <V0idExp> by the way, setting ferror to 1.0 and diminishing the acceleration results in a apparently working configuration
[10:24:36] <V0idExp> I'll investigate on this more. I'll be back.
[10:24:46] <cncbasher> now take the ferror to 0.5
[10:25:04] <V0idExp> ok tnx
[10:30:45] <pcw_home> what are maxaccel and stepgen maxaccel?
[10:32:10] <V0idExp> maxaccel is unknown. if you mean motor's physical acceleration. the stepgen maxaccel we used on software (parallel port) step generation was 1000 m/s^2
[10:32:14] <V0idExp> now is set to 200
[10:33:27] <pcw_home> and what is stepgen maxaccel?
[10:37:26] <pcw_home> For each axis there are the machines maxaccel and the hardware stepgens maxaccel as I said before the stepgens maxaccel must be set to about 20% more than the machines maxaccel or you will get joint following errors
[10:37:28] <pcw_home> The same goes for velocity
[10:39:41] <V0idExp> where machine maxaccels are set?
[10:39:51] <V0idExp> i don't see them in PNCConf them...
[10:41:14] <pcw_home> dont know I just deal with hal file directly
[10:42:41] <pcw_home> pncconf should do this but you can verify by reading the hal file
[10:48:13] <V0idExp> so, you normally write hal files manually?
[10:48:36] <cncbasher> you can see the machine maxaccel values per axis in the ini file
[10:48:50] <V0idExp> ok
[10:48:55] <cncbasher> stepgen values are in the Hal file
[10:49:59] <V0idExp> another question guys. At AXIS shutdown, the MESA fpga/memory/whatever-it-is is not cleared, right?
[10:50:08] <V0idExp> cause LEDs aren't coming back to yellow-red-red
[10:50:32] <V0idExp> and leave the MESA board I/O pins in some strange state
[10:50:35] <cncbasher> the 7i43's are loaded on startup
[10:50:45] <pcw_home> No I dont think its reset
[10:50:56] <V0idExp> yes, it works well as for now
[10:51:17] <V0idExp> I mean, power on - yellow-red-red are ON. Launch AXIS, yellow is on and red-red are off
[10:51:43] <cncbasher> are you using any of the add on extension cards
[10:51:57] <V0idExp> CLOSE axis, yellow is still on and red-red are still OFF... and on I/O pins there are random values, but in order of some volts, 1.7-2.2 volts
[10:52:01] <V0idExp> no
[10:52:04] <V0idExp> only mesa itself
[10:52:18] <pcw_home> firmware is always reloaded (unless you leave out the firmware =xxx) but not reset when LinuxCNC exits
[10:52:45] <V0idExp> well, if firmware is always reloaded, it's ok.
[10:53:37] <cncbasher> the fpga is essentialy dumb until emc starts and is then loaded with configuration
[10:53:51] <V0idExp> understand.
[10:53:58] <pcw_home> You should not have funny values like that at shutdown, all pins (unless driven by external signals) shouls be at ~3.3V
[10:54:24] <cncbasher> so if any inputs or outputs are not what you need , fit some pullup resistors or pull down etc
[10:54:28] <pcw_home> (assuming the watchdog is enabled)
[10:54:43] <pcw_home> Pull ups are already there
[10:54:44] <V0idExp> I don't have Pull-up resistors enabled. (w3 is down). So i expect at shutdown ALL pins going down
[10:55:07] <pcw_home> no You _MUST_ have pullups enabled
[10:55:19] <pcw_home> this is a safety issue
[10:55:20] <cncbasher> no they can float , if you dont have pullups enables
[10:55:33] <cncbasher> arh pcw beat me to it
[10:56:04] <V0idExp> I suspect with enabled pull-ups my board will burn.. already broke one
[10:56:22] <pcw_home> All of our daughter cards assume that the safe state is all high on the I/O pins (IF power is present)
[10:56:23] <V0idExp> but that maybe just a wrong power connections...
[10:56:39] <V0idExp> so, W1 up, W2 down and W3 up, normally?
[10:57:45] <pcw_home> Whatever enables the pre-config pullups. After its configured the FPGA has its own pullups that overide the jumper setting
[10:58:06] <V0idExp> ok
[10:58:07] <V0idExp> thank you
[14:46:50] <FinboySlick> Jymmm: You still around?
[14:47:07] <Jymmm> no, leave a message a the beep............
[14:47:31] <DJ9DJ> beep. memory full
[14:50:41] <FinboySlick> I still have half a mind to build a smaller PSU for my laptop. Considering how small these are http://www.mini-box.com/picoPSU-160-XT, there ought to be some sort of way to pull it off.
[14:52:25] <FinboySlick> Jymmm: You had pretty interesting input last time. What would you say is the biggest hurdle.
[14:52:49] <cradek> I miss the very old laptop style that had the power supply built in and used just a plain cord
[14:53:19] <FinboySlick> Heh, considering the size of my power brick, it would be about as big as those old laptops too.
[14:55:08] <FinboySlick> It seems the ac to dc part is the most space consuming.
[14:55:41] <FinboySlick> dc-dc PSUs are relatively compact.
[14:58:44] <skunkworks> my toshiba satelite pro 110 was that way.
[14:58:50] <skunkworks> kinda nic
[14:58:51] <skunkworks> nice
[14:59:07] <FinboySlick> I had a satellite pro too, first laptop.
[14:59:13] <FinboySlick> Very nice, it even had a quadro in it.
[14:59:58] <skunkworks> It had the little joystick for mouse on the keyboard.. sure took me a while to get used to the mouse pad in conventional laptops..
[15:00:29] <FinboySlick> skunkworks: Likewise. I still haven't given up on those. So I'm only buying Dell Precision or Lenovo.
[15:00:42] <FinboySlick> And I disable the evil evil trackpads.
[15:17:52] <skunkworks> eh - I adapt :)
[15:18:19] <skunkworks> I do disable the pads double click.. mainly because I am shakey
[16:23:48] <DJ9DJ> gn8
[18:54:42] <jp_> evening
[19:00:44] <JT-Shop> and a fine one it is
[19:04:36] <Tom_itx> nice cool rain all afternoon
[19:04:52] <JT-Shop> not a drop here
[19:05:17] <Tom_itx> we really need it
[19:05:22] <JT-Shop> I got to tune the Y axis again... forgot to save it to file... took 10 minutes including screen shots
[19:05:27] <JT-Shop> we do to
[19:05:39] <Tom_itx> you can walk across the arkansas river here
[19:06:38] <JT-Shop> wow a high of 77f saturday
[19:06:45] <Tom_itx> nice
[19:06:47] <Tom_itx> it's about time
[19:31:44] <jp_> JT-Shop: what are you using for a pendant on this machine?
[19:32:00] <JT-Shop> the BP knee mill?
[19:33:18] <jp_> yes
[19:34:24] <JT-Shop> Anilam mounted the MPG on the front of the X slide and it works well there, I'm adding an axis selector and a jog increment selector switch to the button bar under the touch screen
[19:39:21] <PCW> JT-Shop does this servo-dynamics drive look to have a similar pinout as your drive:
[19:39:22] <PCW> https://acrobat.com/app.html#d=x59x38dzNQftieH6cSt4Lw
[19:39:24] <PCW> it seems like it might be similar (same ground-to-disable input)
[19:52:55] <JT-Shop> very similar drive, mine has one led, and 5 pots, 6 test points and generally layed out like that one
[19:54:23] <PCW> what about the input connector does it seem to match?
[19:54:36] <JT-Shop> just looking at that now
[19:54:43] <Tom_itx> JT-Shop, lookin for something last night i found a couple of these in the bottom of my tool box: http://www.mtfca.com/discus/messages/179374/214837.html?1307022870
[19:54:59] <Tom_itx> along side a handfull of unmarked ones
[19:56:15] <JT-Shop> on my drive pin 6 is the disable pin
[19:57:01] <JT-Shop> this one is pin 8
[19:57:22] <JT-Shop> similar enough to be made by the same manufacturer
[19:58:32] <JT-Shop> X axis homes for the first time on the BP since it was built!
[19:58:44] <JT-Shop> chow time guys
[19:58:49] <JT-Shop> see you later
[19:59:07] <PCW> Oh well, I suspect there was a fair amount of copying going one (or maybe the drive are OEM labeled but all made by one company)
[19:59:29] <sliptonic> PCW: I've been looking at the .pdf the last couple days!
[19:59:41] <sliptonic> I recognize the coffee stain on the cover :-)
[20:00:09] <PCW> bon appetite!
[20:00:17] <JT-Shop> thanks
[20:00:40] <JT-Shop> I suspect some OEM labeled drives
[20:01:20] <PCW> Im glad the pdf is available it seems fairly common (a customer asked about it)
[20:02:27] <sliptonic> That was probably me. Ordered my stuff from you today.
[20:04:57] <JT-Shop> PCW: it was sorta easy to tune my drives following your advice on P the FF1 then I added a smidge of FF2 to kill the over/under shoot and start and stop
[20:05:59] <JT-Shop> say goodnigtht Gracie
[20:22:24] <r00t4rd3d> i thought googles page today was michael jackson