Back
[00:00:03] <pfred1> he made a fortune doing industrial controls and building machines
[00:00:21] <pfred1> he just liked to make stuff
[00:00:32] <Jymmm> that's cool
[00:00:34] <tjb1> dr wayne dyer…sounds like a hoot
[00:02:44] <tjb1> ewww pfred1 a hf multimeter
[00:03:11] <pfred1> tjb1 some of them are suprisingly accurate
[00:03:19] <pfred1> some don't work at all
[00:03:31] <tjb1> play the lottery enough and youll win something
[00:04:05] <pfred1> hey for what they cost I can cut the banana jacks off the leads and I'm still ahead of the game
[00:04:58] <tjb1> i like mine
[00:05:05] <pfred1> I've fried more than my fair share of expensive meters by now too
[00:05:37] <pfred1> so I hook the cheap ones up first
[00:05:55] <tjb1> lol
[00:06:55] <tjb1> I have this one -
http://easthillsinstruments.com/store/media/catalog/product/cache/1/image/9df78eab33525d08d6e5fb8d27136e95/f/l/fluke-87-1.jpg
[00:07:33] <pfred1> flukes are nice don't leave it out in the cold though
[00:07:55] <pfred1> buddy of mine did that with his the LCD was never quite the same after that
[00:08:27] <tjb1> for the price that thing cost…fluke should fix it
[00:08:59] <pfred1> I never need that kind of accuracy
[00:09:08] <pfred1> that is what you're paying for with expensive meters
[00:09:20] <pfred1> well it is what you should be paying for
[00:09:23] <tjb1> I didnt want to keep buying them
[00:09:26] <tjb1> So I just got a good one
[00:09:39] <tjb1> I just need one of those amperage clamps
[00:09:42] <pfred1> good ones burn up just as quickly as cheap ones do
[00:10:20] <pfred1> I want a current probe for my scope
[00:10:32] <tjb1> I got a cheap scope too, havent mastered it yet
[00:10:42] <pfred1> I just don't want to pay a grand for it
[00:10:52] <tjb1> Cant remember the name of mine...
[00:10:59] <tjb1> Its those cheap ones that everyone firmware hacks
[00:11:00] <pfred1> mine is easy t oremember
[00:11:09] <pfred1> Tektronix
[00:11:41] <tjb1> rigol ds1052e
[00:11:43] <pfred1> I have a 2336 with the Y option
[00:12:11] <pfred1> let me tell you the Y option is the snizzle too
[00:12:20] <tjb1> I dunno what the Y option is
[00:12:23] <pfred1> that doubles the value of the instrument
[00:12:31] <pfred1> oh time cursors
[00:13:06] <tjb1> one day ill learn to use mine
[00:13:07] <pfred1> you can measure time in the wave
[00:13:53] <pfred1> I've used my scope as a characteristic curve tracer
[00:14:04] <pfred1> which if you know what that is is pretty cool
[00:14:22] <tjb1> Nopr
[00:14:24] <pfred1> it is about as advanced as scoping gets
[00:14:24] <tjb1> *Nope
[00:14:59] <pfred1> you can do stuff like match transistors
[00:15:23] <pfred1> for a while I was on an audio amplfier kick
[00:15:28] <tjb1> can you download what you know about electronics to my head?
[00:15:58] <pfred1> I spent a lot of time messing with the stuff
[00:16:27] <tjb1> well I have to get to sleep
[00:16:34] <tjb1> cya
[00:16:45] <pfred1> nite
[00:51:36] <Loetmichel> mornin'
[02:05:25] <DJ9DJ> moin
[03:40:48] <Jam628> does th
[03:43:38] <Jam628> I'm trying to set up Mesa 7i43 with steppers, but getting all the time joint 0 following error. FERROR = 0.005 and MIN_FERROR = 0.0005 (mm) by default with PnnConf but even if i set those values to 5 and 0.5 I have the same error.
[03:45:53] <Jam628> What BASE_PERIOD should be set for 7i43? In actual confog there is no such parameter now. Can this be the problem? The velocity and accel values I couldn't increase to the desired one, so the movements (ramps) are very long...
[05:46:28] <cncbasher> jam628 : make min_ferror 0.5
[05:46:59] <cncbasher> jam628: and make your ferror 1.0 , base period is not used with 7i43
[06:41:25] <Tom_itx> no base period on the mesa 7i43
[06:41:29] <Tom_itx> use the servo period
[06:43:23] <Tom_itx> oh well he didn't stick around long enough
[06:53:08] <cncbasher> he'll be back .. i'm not convinced thats the problem
[06:55:10] <Tom_itx> probably but he didn't hear either one of us
[09:06:13] <pcw_home> Jam628 (should you read this later) usual cause of following error on Mesa Stepgens is that the stepgen maxaccel parameter is not set. This should be set to about 1.25 times the machine maxaccel.
[09:25:44] <JT-Shop> ways look good but they put the rollers in wrong on the V way
[09:26:24] <archivist> they...I thought someone more local rebuilt said item recently :)
[09:28:06] <Xabster> hi, my onboard gfx chip interferes with the latency as the site's guide says
[09:28:23] <Xabster> so now i need a pci express card just to avoid this and i'm considering Radeon HD 5450
[09:31:04] <pcw_home> which gfx chip?
[09:31:42] <Xabster> CGAX-5452LI
[09:32:55] <pcw_home> I mean which onboard graphic chip
[09:33:12] <JT-Shop> I assume it was the shop that used to own it... I just noticed at some point they had ordered a set of rollers from notes in the parts book
[09:33:29] <Xabster> pcw_home: why?
[09:33:56] <pcw_home> Because there are workarounds for some
[09:35:02] <pcw_home> because its typically not the hardware thats a problem, but rather the driver
[09:35:44] <Xabster> pcw_home, it's a G530 celeron and all i can find on the gfx chip is "Intel® HD Graphics"
[09:35:54] <Xabster> the CPU*
[09:37:33] <archivist> do you have any video cards lying around to try before you buy something
[09:37:40] <Xabster> no
[09:37:56] <Xabster> thats my problem
[09:38:00] <pcw_home> Hm I wonder if that uses the same driver that the Atoms use
[09:38:29] <Xabster> "Graphics card capable of at least 1024x768 resolution, which is not using the NVidia or ATI fglrx proprietary drivers, and
[09:38:29] <Xabster> which is not an onboard video chipset that shares main memory with the CPU"
[09:38:46] <Xabster> my onboard does that
[09:38:46] <pcw_home> Oh thats obsolete
[09:38:53] <Xabster> oh really?
[09:38:58] <pcw_home> Yes
[09:39:59] <Xabster> do you have any suggestions on what i can do? my idle-latency is about 11 uS and if i view youtube video it goes to twice that
[09:40:03] <Xabster> about 24 uS
[09:40:07] <pcw_home> Atoms and AMD fusion have onboard graphics and are OK and the Intel HD graphics should be fine
[09:40:18] <pcw_home> live with it
[09:41:01] <cradek> but 24 is a fine number
[09:41:13] <pcw_home> you may be able to improve latency with the isolcpus trick
[09:41:17] <Xabster> that's only 25k hz
[09:43:50] <pcw_home> well 1/24 uSec is 41 KHz and with 2x margin thats 20 KHz
[09:43:52] <pcw_home> which is 600 RPM for 1/10 ustep ratio so not bad
[09:45:03] <pcw_home> 1500 RPM with 1/4 stepping which is very likely faster than the step motors will go
[10:02:43] <Loetmichel> hmmm... depends... on the stepper driver voltage ;-)
[10:18:15] <mazafaka> I did it! Not sex with female twins yet, but already something like in GTA San Andreas!
http://www.youtube.com/watch?v=t4WlwKSCkaA Next time I will have stolen a car. :)
[10:21:35] <DJ9DJ> hmm, chasing your dog?
[10:21:43] <DJ9DJ> at least the first seconds ;)
[10:21:51] <Xabster> but i want it better, pcw_home :)
[10:22:45] <archivist> define better
[10:26:35] <mazafaka> DJ9DJ: just rode to garage, and took my dogs
[10:26:54] <DJ9DJ> :)
[10:27:00] <Xabster> faster movement with higher microstepping
[10:27:11] <Xabster> it's about 5 cm per second with 600 rpm
[10:29:29] <IchGuckLive> hi folks a reamer for a Stepper is this available in the USA 6.35mm
[10:30:11] <IchGuckLive> or what is the shaft of a ordanary Nema 23 1/8 7/16
[10:30:39] <awallin> 6.35 mm does sound familiar...
[10:30:55] <skunkworks> Xabster: you do know microstepping doesn't help with accuracy?
[10:31:19] <Xabster> i dont know a whole lot about anything, no
[10:31:22] <Xabster> what does it do then?
[10:31:57] <skunkworks> manly gets rid of resonance issues at certain rpms of the stepper.
[10:32:05] <archivist> 6.35 is 1/4"
[10:32:14] <skunkworks> but you will not get any better accuracy than about 1/2 step.
[10:32:51] <Xabster> so, let's say i experience resonance then I *could* change to a different microstep to avoid it?
[10:33:00] <Xabster> but that's about it?
[10:33:10] <skunkworks> yes - raising the microstep will usually help
[10:33:43] <IchGuckLive> archivist: Thanks
[10:34:03] <IchGuckLive> Xabster: Half step 400/rev is the best to go
[10:35:10] <IchGuckLive> Xabster: what are you going to drive
[10:35:25] <IchGuckLive> Laser Mill lathe plasma ...
[10:36:59] <Xabster> parts for a RC car
[10:37:02] <Xabster> or cars, rather
[10:37:22] <Xabster> but it's a hobby project and we're 2 on it and we're both trying to get our respective "tasks" to perform optimal
[10:37:27] <Xabster> mine is the software and PC setup
[10:37:39] <Xabster> and some more, and he's building the machine more or less from scrathc
[10:37:41] <Xabster> scratch
[10:37:51] <Xabster> unfair workload? :D
[10:37:55] <skunkworks> neat!
[10:37:57] <IchGuckLive> where are you from Europ USA ...
[10:38:14] <Xabster> europe, denmark
[10:39:33] <Xabster> do you think a non-onboard GFX card would solve some of the latency?
[10:39:39] <Xabster> since idle latency is about 12 uS
[10:39:47] <Xabster> and if i view a youtube video it's 25 uS
[10:42:16] <IchGuckLive> Xabster: with 12000 you are well over 350 inch per minite
[10:42:56] <Xabster> but 12000 ns is only when the PC is idle
[10:43:06] <Xabster> viewing GFX stuff increases latency
[10:45:20] <IchGuckLive> up to 50k you are also good on hobbyist
[10:45:37] <IchGuckLive> as your mill will not need to go that fast
[10:46:19] <IchGuckLive> Xabster: im in germany DID you check for SMI so the latecy jumps on this PC issue
[10:46:59] <Xabster> sorry what?
[10:47:44] <IchGuckLive> the latecy jumps high on pulses 20-30sec
[10:48:04] <IchGuckLive> Reset it and see
[10:48:06] <Xabster> what is SMI ?
[10:49:40] <IchGuckLive> a PC safty behavier somthing like a Watchdog
[10:50:10] <IchGuckLive> Xabster:
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?FixingSMIIssues
[10:51:43] <Xabster> i see, but those numbers don't quite match my problem
[10:51:54] <Xabster> SMI is a real-time killer and to avoid latencies of several 100 microseconds up to a few milliseconds, you need to disable them
[10:51:59] <Xabster> i'm not close to 100 uS really
[10:52:44] <skunkworks> Xabster: a plugged in video may help
[10:52:56] <IchGuckLive> no it happens every whatabout secondes so reset your latesy and see if it is happening
[10:53:07] <Xabster> hmm
[10:53:19] <Xabster> well, my friend on skype just rushed to the store to get a pci gfx card
[10:53:25] <Xabster> he's got 20 min to get there =)
[10:53:53] <Xabster> if that doesn't help we'll take a look at the SMI thing
[10:53:58] <IchGuckLive> i woudt check first if a standard fix cand get you to <50K
[10:54:38] <IchGuckLive> The SMI interrupt usually is very periodic so check
[10:54:53] <Xabster> i'm not 100% sure how to check this stuff
[10:55:01] <IchGuckLive> reset laitency wait if it jumps reset again
[10:55:04] <Xabster> do you mean to look at the max latency?
[10:55:30] <IchGuckLive> just start your latency script in the CNC folder
[10:55:40] <IchGuckLive> yes
[10:56:03] <IchGuckLive> look at the max latency rset it when it goes high
[10:56:25] <IchGuckLive> lok again if it jumps up maybe 12k -> 80k
[10:56:39] <IchGuckLive> reset again and look
[10:57:04] <IchGuckLive> if this happens at maybe periodic its smi
[10:57:20] <IchGuckLive> im off By till 7pm Berlin time
[10:57:28] <Xabster> oki
[11:36:00] <tjb1> Anyone use DSLRs in here?
[11:37:06] <awallin> hm yes, why?
[11:38:47] <tjb1> Im looking at getting one, my phone does horrible video. Canon Rebel T3 looks to be good price
[11:39:04] <tjb1> $375 refurbished
[11:40:00] <awallin> the big money will go into lenses if you get hooked
[11:40:26] <awallin> they have different model-numbers in europe... 1000D or 1100D might be the base model now
[11:41:38] <awallin> now they are listing the 6D for preorder also, interesting..
[11:41:46] <tjb1> Im not looking to go pro or anything just a good one that will last
[11:43:00] <awallin> all the cheaper models are fairly similar, you have to jump to 7D to get a bit of pro-feel into the body (metal frame etc)
[11:43:21] <awallin> or maybe 60D
[11:44:07] <tjb1> Doesnt even have to be canon…any recommendations in the $300-$400 range that includes at least 1 lense
[11:45:05] <awallin> go with canon or nikon, there are so many more lenses for those
[11:57:58] <alex_joni> I settled for canon
[11:58:12] <alex_joni> but you can also grab a sony (less lenses available, but stabilisation in the body)
[11:58:37] <alex_joni> they had a 49% off for the 60D the other day over here
[11:58:54] <alex_joni> that would have been nice to catch ;).. but I already had one
[12:26:51] <IchGuckLive> Hi all
[12:27:07] <IchGuckLive> Fog all over the Freeway
[12:27:56] <IchGuckLive> Xabster: all clear on latency
[12:28:15] <Xabster> we installed new GFX card and that solved the latency
[12:28:17] <Xabster> yay
[12:28:27] <Xabster> but now youtube videos are played at 30x speed or something
[12:28:30] <Xabster> ridiculously fast
[12:28:41] <Xabster> we formatted and reinstalled, same problem
[12:28:45] <Connor> jdh: You around ?
[12:29:32] <IchGuckLive> Xabster: its on the realtime kernel did you check on the SMI
[12:29:41] <Xabster> no i didn't check SMI
[12:29:55] <IchGuckLive> is 10.04 on the system
[13:04:28] <IchGuckLive> Loetmichel: died you see the sun today
[13:05:37] <archivist> you cannot see the sun if you died
[13:05:55] <IchGuckLive> O.O B)
[13:08:07] <awallin> just saw this on the fi forum. the 1:1 5th axis coupling sounds weak. what do you guys think?
http://www.ebay.com/itm/CNC-Rotary-Axis-4th-5th-Axis-CNC-Rotary-Table-/261118755481?pt=BI_Tool_Work_Holding&hash=item3ccbe40299
[13:08:33] <syyl_ws> the whole thing looks weak Oo
[13:08:43] <syyl_ws> there is no gearing in it?
[13:08:45] <syyl_ws> just belt?
[13:09:07] <awallin> I think so
[13:09:22] <awallin> don't take out the 100mm face mill with that one :)
[13:10:22] <archivist> and one cannot be sure of being on centre
[13:10:59] <archivist> better off with a couple of vertex rotaries and an angle plate
[13:12:58] <IchGuckLive> for some folks it might work he did the 4th 5th axis but not for real milling
[13:16:43] <pcw_home> 5th axis is direct, you could spin it with your little finger
[13:17:14] <IchGuckLive> b)
[13:17:16] <awallin> yeah that's what I feared... :)
[13:17:23] <archivist> only use would be foam and wax
[13:17:32] <IchGuckLive> no foam
[13:17:38] <IchGuckLive> i must know
[13:17:55] <IchGuckLive> you might be impressed on the foam milling foarce
[13:18:06] <archivist> I might not
[13:18:59] <IchGuckLive> Im off By till tomorow :D
[13:21:27] <awallin> pcw_home: with SPI, does 2 chip-select lines means you can have 2 devices or 4? or more?
[13:26:21] <pcw_home> 2 CS bits will give 2 devices (but 3 bits could give you 4: 2 select bits and one frame signal)
[13:26:39] <pcw_home> (and a 1/4 decoder)
[13:28:54] <awallin> hm, ok. the raspberry pi seems to have 2 cs bits. then it has i2c also but I guess that is slower.
[13:30:05] <pcw_home> You can use GPIO bits to expand the SPI channels
[13:30:24] <awallin> as extra CS bits?
[13:30:58] <pcw_home> basically you need a frame signal and a decoder enabled by frame (no just plain old GPIO bits)
[13:32:20] <awallin> for raspberry pi, having HAL + some simple GUI (gladevcp) and a driver for SPI and the GPIO would be nice. would enable all kinds of tinkering..
[13:32:44] <pcw_home> Yeah the SPI is probably fairly fast
[13:33:57] <awallin> 3 or 4 or maybe more SPI-devices, and real-time with 1ms thread would already be nice
[13:34:05] <pcw_home> i2c is dismal speed wise
[13:37:26] <pcw_home> Yeah HAL is a nice tool for combined measurement and control without ~= text Labview
[13:38:07] <pcw_home> without coding I mean
[13:39:20] <mevon> hi everyone
[13:41:09] <mevon> I have troubles with the managment of home switches, but I have no home switches, for some reason the machine always resets on the first move I ask
[13:41:41] <mevon> I need help on the homing too, for some reason to start a task you need to be at home position?
[13:43:12] <mevon> do I need debouncing on my virtual/software home?
[13:44:25] <andypugh> mevon: Read the INI setup page, especially NO_FORCE_HOMING
[13:44:45] <andypugh> And just don't connect the home switches in your HAL
[13:44:50] <mevon> Ill check that ty andypugh
[13:46:01] <mevon> andypugh, do you recommand a home-min combination?
[13:46:13] <andypugh> It's what I use.
[13:46:42] <andypugh> But I would make sure your machine is going to work _at_all_ before bothering with them
[13:51:29] <cradek> what do you mean by "the machine ... resets"
[13:53:09] <mevon> andypugh, oh its working now
[13:53:27] <mevon> cradek, have to press f1+f2 to put it online again
[13:53:38] <mevon> how do you call that?
[13:54:55] <pcw_home> a fault?
[13:56:00] <andypugh> It seems to toggle the limits whenever it starts up.
[13:57:50] <mevon> well its impossible, and its mainly linuxcnc based actings because unless I sent the msg, nothing changes, I sure I dont sent a switch toggle anytime nothing is happening
[13:58:30] <mevon> maybe because my homing is not disabled
[14:00:57] <cradek> I have not seen this behavior. maybe you should tell us a lot more about what you have set up and something will ring a bell.
[14:03:54] <mevon> I get a "cannot un home while moving" error
[14:04:12] <mevon> on the z axis
[14:07:26] <mevon> is it better to have a home switch or a min-limit switch?
[14:08:25] <andypugh> Both. But they can be the same switch.
[14:08:36] <mevon> so combined is the best
[14:09:41] <andypugh> combined it easiest, with limited pins. Separate is best, then you can have the home switch somewhere convenient (like with the vice under the spindle)
[14:11:39] <mevon> lets say I put a home sw like you described, is it toggled or active on one precise position? Im sry I have lots of questions I just want to learn all I can
[14:13:01] <andypugh> Ideally a centrally-placed home switch is on for one half of travel and off for the other (so might be operated by a cam-plate). Otherwise the machine can't tell which way to go to find home.
[14:13:08] <mevon> because Im guessing, mechanically it would be rather odd to use a tact sw to do the job
[14:13:26] <andypugh> This is why home switches are normally at one end of travel, and outside the normal range.
[14:13:33] <mevon> ok :/ thks for the info
[14:13:43] <mevon> outside you say?
[14:13:52] <andypugh> I wouldn't want to use a physical switch that way, but a prox or opto would be fine.
[14:14:01] <mevon> so I had it all wrong
[14:15:08] <mevon> my home is 0.0, my min is -0.1 and max is 6 or 8 or 1.5
[14:15:24] <mevon> only z axis min is -0.5
[14:15:26] <mevon> inches
[14:19:00] <tjb1> Your z negative is only .5?
[14:19:06] <andypugh> The home switch doesn't have to be at the home position. In fact typically it is HOME_OFFSET from the home position.
[14:20:05] <mevon> here is my .ini
http://pastebin.com/B83ts6an
[14:20:23] <mevon> tjb1, yeah :S
[14:20:27] <mevon> idk :(
[14:20:42] <mevon> figured it was the best for pcb milling
[14:20:52] <mevon> its a mantis
[14:21:10] <tjb1> Your ini says -.25 and 1.5
[14:21:49] <mevon> seems I havent changed it yet but what do I dont see that makes it a problem here?
[14:22:18] <mevon> i kept it safe for now
[14:22:51] <tjb1> Do you home your z axis at max height or close to it?
[14:23:06] <mevon> that was my goal
[14:23:38] <mevon> makes it easier for tool change
[14:23:57] <mevon> though Ive set a tool_change position to 0 0 1
[14:24:20] <tjb1> Im not sure since my homing doesnt work yet but shouldn't your min be greater since Z is working in a negative direction from the home position?
[14:24:39] <mevon> makes sens :P
[14:25:39] <mevon> but I made that so the top of my material is always 0
[14:26:00] <mevon> when the tool touches the mat, thats my z=0
[14:26:51] <tjb1> but that isnt home
[14:27:11] <mevon> well I wanted it to be a software home
[14:27:30] <mevon> i mean for all that I know it could be home
[14:27:42] <mevon> since i have a toolchange_pos
[14:28:13] <tjb1> Im not the best person to get advice from :P
[14:28:19] <tjb1> But I believe the home is get to g53
[14:28:19] <mevon> but like you said maybe its not the best choice
[14:28:26] <tjb1> touch offs are set to g54+
[14:28:43] <tjb1> andypugh: is that right?
[14:29:42] <andypugh> G53 refers to the machine coordinate system, that will correspond to the INI file numbers.
[14:30:13] <andypugh> You don't work in that system though. (Unless you actively put a G53 before every single move)
[14:30:43] <tjb1> So home coordinates are set in g53?
[14:32:07] <andypugh> More G53 is set by home coordinates
[14:33:28] <tjb1> and then software limits work off the g53 system?
[14:33:46] <tjb1> If you MDI g0 x0 y0, does that just default to g54?
[14:35:38] <mevon> send the wrong ini file :S I was using the wrong configs..... meh
[14:36:48] <andypugh> tjb1: Yes, soft limits sort-of live in G53. I think that you start up in the same working CS as you last shut down in. I think it is sticky.
[14:36:56] <mevon> the best way to troubleshoot them sw is with show HAL config, or Hal meter?
[14:37:15] <tjb1> I know if I home, it doesnt reset the coordinates in the display
[14:37:27] <tjb1> only a touch off does and even then sometimes that doesnt work if I forget to remove G92 :P
[14:37:56] <mevon> tjb1, how do you set touchoffs?
[14:37:59] <tjb1> Can you apply codes to happen when linuxcnc starts or make it just reset?
[14:38:07] <tjb1> beside the home button
[14:38:12] <andypugh> mevon: Whichever works best. Halscope is handy too.
[14:38:44] <mevon> ahhh tjb1 now I know what that is ty
[14:39:01] <tjb1> the "End" key does that
[14:40:13] <mevon> much appreciated
[14:41:27] <tjb1> andypugh: Can it be made to reset everything on restart?
[14:43:28] <andypugh> tjb1: Yes, RS274NGC_STARTUP_CODE
http://www.linuxcnc.org/docs/html/config/ini_config.html#sub:[RS274NGC]-section
[14:43:44] <tjb1> That will even run when it wont allow a G92.1 without homing?
[14:49:54] <gmouer> PCW around to peek at a servo runing screenshot?
[14:53:30] <pcw_home> I'm off but will be back in an hour or so
[14:54:07] <gmouer> great, thanks, could really use your help analyzing a halscope plot
[14:58:10] <gmouer> anybody: what is that website used for posting screenshots here on irc? Need to get one ready to post
[14:58:22] <JT-Shop> imagebin.ca
[14:58:34] <JT-Shop> no .org
[14:58:41] <gmouer> thanks John !
[14:58:50] <JT-Shop> yw
[14:59:24] <gmouer> servo tune driving me bonkers, need to get help
[15:07:30] <mevon> how can I reset the axis to the 0 0 0 position?
[15:07:57] <gmouer> main menu under machine, zero the coordinate system
[15:09:30] <mevon> ok nice thaks
[15:09:36] <gmouer> sure
[15:13:55] <mevon> trying to reprogram the arduino while linuxcnc is running is bad
[15:18:01] <mevon> what is SCALE used for in the .ini
[15:18:41] <gmouer> scale can be used for several things, it is basically like a multiplier used to scale a value
[15:18:42] <andypugh> steps per inch
[15:19:42] <mevon> as in INPUT_SCALE in the [AXIS x] sections
[15:21:49] <gmouer> assuming you have encoders, its the encoder resolution in quadrature per inch... andy correct me if I am wrong please
[15:42:25] <gmouer> andypugh: got time to peek at a halscope servo plot and comment?
[15:43:10] <andypugh> Not right now, sorry, dinner just happened. (and I am actually no expert)
[15:43:33] <gmouer> no problem, enjoy dinner! your a lot more expert than me
[16:13:06] <tjb1> If I did "G10 L2 P0 X0.0 Y0.0 Z0.0" would that reset all axis to 0 upon startup if in the RS272 startup code
[16:14:46] <tjb1> I cant understand the difference between G10 L2 and L20
[16:21:07] <gmouer> PCW: you around? could use help with a halscope servo plot
[16:21:38] <cradek> gmouer: since others could probably help, instead of asking for a certain person, you should always just ask your question.
[16:22:05] <gmouer> ok, thanks! here is the plot
http://www.youtube.com/watch?v=717vb7kLKKk
[16:22:08] <JT-Shop> G10 L2 offsets the origin of the axes in the coordinate system specified to the value of the axis word.
[16:22:14] <JT-Shop> G10 L20 is similar to G10 L2 except that instead of setting the offset/entry to the given value, it is set to a calculated value that makes the current coordinates become the given value.
[16:22:35] <tjb1> I read that, dont understand the calculated part
[16:22:38] <gmouer> it is open loop, velocity loop in the drive, pos loop in linuxcnc, PID all zero'd only FF1 active
[16:23:20] <DJ9DJ> gn8
[16:23:29] <gmouer> my convern is those overshoots at the start and stop of motion, refuse to tune away, tried a diff brand servo amp and diff motor even, same result
[16:23:38] <JT-Shop> if you move to point X and say G10 L20 X0 then an offset is calculated to make the current location be X0
[16:23:57] <cradek> gmouer: that probably isn't the URL you intended
[16:24:06] <tjb1> What would L2 do at the same position?
[16:24:08] <gmouer> oh oh your right !
[16:24:18] <JT-Shop> try it in the MDI window and see
[16:24:27] <tjb1> Not at home :)
[16:24:36] <gmouer> this one is better LOL
http://imagebin.org/236498
[16:24:45] <tjb1> G10 L2 P1 X0 Y0 Z0 (clear offsets for X,Y & Z axes in coordinate system 1)
[16:25:03] <cradek> gmouer: ok what's your question about it?
[16:25:10] <tjb1> So if L20 X0 sets the x to 0 and L2 X0 sets the x to 0…I dont get it
[16:25:27] <gmouer> the overshoot at the start and end of movement, it refuses to tune out
[16:25:50] <gmouer> when closed loop, it translates into following error the same way
[16:25:58] <cradek> gmouer: oh I see, you have overshoot with ff1 only.
[16:26:22] <gmouer> yes, and I tried a different brand servo drive and a diff motor, same results
[16:26:33] <gmouer> also the same results on my other axis, I am stumped
[16:26:46] <JT-Shop> G10 doesn't set X it sets an offset from the origin of X
[16:26:46] <cradek> when you say it refuses to tune out what do you mean? what have you tried?
[16:27:08] <PCW> Needs velocity loop tuned at drive
[16:27:40] <gmouer> yes PCW, but I have tuned till blue in face, overshoot is unaffected
[16:28:00] <gmouer> open loop, drive adjustments do not effect that overshoot at all
[16:28:04] <cradek> you tried to tune the velocity loop? knobs or software on the amp?
[16:28:19] <gmouer> yes, even tried a different brand servo drive
[16:28:23] <gmouer> same results
[16:28:31] <tjb1> Ok so L2 sets the coordinates to that value, L20 sets an offset that will equal to the value you call…ex X-8.0 and you call X5.0 it sets an offset of X13.0?
[16:28:34] <gmouer> thats my problem
[16:28:34] <cradek> is this velocity loop a tach on the motor?
[16:28:45] <gmouer> no, its encoder derrived
[16:28:58] <cradek> encoder hooks directly to the amp?
[16:29:58] <gmouer> yes, amc drive, also ran diff drive with emc generating a fake tach feedback for that other drive, same results, same results using real tach also
[16:30:25] <cradek> where is the encoder?
[16:30:29] <gmouer> on motor
[16:30:43] <cradek> did you check the set screw?
[16:30:46] <gmouer> x and z are diff brand motors, both do the same overshoot
[16:31:05] <cradek> ah ok
[16:31:18] <gmouer> yes, checked for mechanical "lag", putting force against cross slide has no effect on halscope trace
[16:31:29] <gmouer> I have a idea, but its a long shot
[16:31:45] <cradek> then your velocity gain is just too high. are you sure you're setting it right? distant memory tells me the amc amps set a gross gain with dip switches and fine gain with a pot...?
[16:31:50] <PCW> tuning the drives velocity loop has to change this
[16:32:06] <cradek> I agree with pcw
[16:32:30] <PCW> nothing much LinuxCNC can do about it
[16:32:49] <gmouer> the gain pot is 10 turns, 5 turns makes no diff, more gain will oscillate, less trace stays about the same
[16:32:54] <cradek> are you also 100% positive you have switches set correctly for encoder velocity feedback? check everything again
[16:32:56] <gmouer> always overshoot
[16:33:32] <PCW> Is this just FF1?
[16:33:36] <gmouer> yes, positive, I had identical problem with z axis, and that uses a real tach, also on the x with a diff drive
[16:34:10] <gmouer> I am wondering if the 7i77 has a very fast spike on its analog output and the various amps are trying to respond to it
[16:34:54] <PCW> still looks like drive tuning (you should be able to set the velocity gain low enougg that it lags considerably)
[16:35:17] <cradek> there are at least 3 switches that you should be experimenting with
[16:35:23] <PCW> 7I77 outputs are glitchfree (~100 usec risetime)
[16:35:24] <gmouer> I had gain backed down just about all the way with no effect to those overshoots
[16:35:33] <gmouer> on 2 diff brand amps
[16:35:49] <gmouer> I tried all the obvious things before I came here
[16:35:59] <cradek> current loop gain, current scaling, integrator capacitor
[16:36:10] <gmouer> x and z are diff motors too, z has a actual tach on its sem motor
[16:36:13] <cradek> gmouer: but we don't know what you think and don't think is obvious :-)
[16:36:40] <gmouer> gotta agree there cradek!
[16:37:12] <gmouer> after hours of tuning, over the weekend I tried the amc amp with direct encoder input, found the same behavior
[16:37:20] <JT-Shop> G10 L2 X2 changes the offset from the origin from what ever it was to 2, it does not set the current coordinates to anything
[16:37:47] <gmouer> all the tune adjustments on the amp behave as expected but with no effect on that overshoot at the beginning and end of movement
[16:38:21] <cradek> gmouer: perhaps you just can't accelerate that fast. if you zoom in to that rising edge we'd be able to see more
[16:38:35] <PCW> is it just tha you are exceeding the motors maxaccel?
[16:38:41] <PCW> ha
[16:38:44] <cradek> PCW: good grief
[16:38:58] <gmouer> ? if it was exceeding the motors accel, why would it overshoot?
[16:39:00] <cradek> PCW: the velocity loop does have an integrator
[16:39:17] <cradek> PCW: you can set it to one of two values :-/
[16:39:31] <cradek> gmouer: ^
[16:39:59] <cradek> gmouer: share a new plot with it zoomed in
[16:39:59] <gmouer> let me post a link to the drive being used
[16:40:23] <cradek> yeah, I'm going on a guess (B25A40)
[16:40:48] <PCW> Yes that would do it that looks like 10 ms to 15% of full speed so that very aggressive acceleration
[16:40:54] <gmouer> http://www.a-m-c.com/download/datasheet/be15a8.pdf
[16:41:05] <gmouer> good guess, its smaller brother
[16:41:24] <gmouer> running a dc brushed motor which it is spec'd to do
[16:42:05] <gmouer> as a note, the overshoot is directly proportional to the velocity requested
[16:42:22] <gmouer> the machine is 200 ipm, the plot was at 50ipm
[16:42:53] <PCW> I thin the accell is just way too high
[16:42:55] <gmouer> I varied accel in the ini file over a wide range but it did not seem to change the display much
[16:43:24] <gmouer> varied it from about 10 to 30
[16:43:32] <gmouer> inch units
[16:44:17] <tjb1> JT-Shop: L2 is moving machine coordinates then? g53
[16:44:18] <gmouer> I run the same motors on another lathe at 15 accel and it is moving much much more iron, this is a linear rail small machine, very easy to move
[16:44:26] <PCW> umm you trace shows cruise speed in 10 ms... thats not very realistic
[16:45:43] <cradek> zoom in zoom in
[16:46:13] <gmouer> I had accel up at one point, sort of simulating a battery for open loop
[16:46:57] <PCW> Well step inputs are good but cause trouble if you have any integral term
[16:47:29] <gmouer> being new, I am confused, it is actually going beyond the commanded speed, then slowing back down, it would seem to me that it is accelerating even more than requested. what am I missing?
[16:47:42] <PCW> if the velocity loop has any integral term you need to limit the accel to something the machine can track
[16:48:10] <gmouer> this is open loop, P, I , D all at zero, only FF1 in effect
[16:48:21] <andypugh> gmouer: "Integral Windup"
[16:48:40] <andypugh> Integral Windup in the _velocity_ loop in the drive
[16:48:47] <gmouer> yes, I have seen that windup in the past, but I is at zero, open loop
[16:48:50] <PCW> if you enter a ramp faster than the drives velocity loop can track and the drive has any integral term on its internal velocity loop it will overshoot
[16:49:02] <cradek> no it's not. You can't set velocity loop I=0 on these drives
[16:49:05] <PCW> I in the drive
[16:49:08] <gmouer> ahhhhh in the drive !
[16:49:21] <gmouer> ok, PCW, now I am getting the picture
[16:49:40] <andypugh> cradek, run along and write us a finite-jerk tp, there's a good chap.
[16:49:51] <cradek> oh go fly a kite
[16:50:00] <PCW> jerk
[16:50:36] <gmouer> ok, so I in the drive is suspect, but there is no independent adjustments on the drive, just a overall gain pot
[16:50:52] <JT-Shop> tjb1: no
[16:51:19] <PCW> Well that means you need to tune with a velocity ramp the drive can follow (reduce accell)
[16:52:31] <gmouer> ok PCW, gottcha I will play with that theory on the machine and see what happens. I have learned a lot about servo behavior in the last few weeks, much from reading your posts on the forum
[16:53:00] <PCW> so if you want to tune with a step you need to turn 'I' off in the drive
[16:53:21] <PCW> Ive just done it (too many times)
[16:53:35] <gmouer> don't think that can be done in the amc drive (short of a soldering iron)
[16:54:52] <gmouer> how do you turn the I off in a drive that does not have independent adjustments for pid? only a overall gain pot?
[16:55:13] <andypugh> Lower accel in LinuxCNC should give lower velocity ramp, should reduce the problem.
[16:55:32] <PCW> I would not bother, I would just reduce the accell
[16:55:37] <gmouer> ok
[16:55:47] <gmouer> you guys are fantastic teachers !
[16:56:13] <gmouer> thank God you don't charge LOL
[16:56:31] <andypugh> That's what you think :-)
[16:56:36] <tjb1> Ok JT-Shop, I think I got it…L2 moves the origin of the specified coordinate system, L20 sets the current coordinates to the numbers specified?
[16:56:43] <PCW> no guarantees...
[16:57:47] <gmouer> guess I am out to the garage for a few hours tuning tonight, armed with great info, thanks so much guys
[16:58:26] <andypugh> Some controllers zero the I term the instant you cross the setpoint.
[16:59:08] <gmouer> drives like the amc don't tell you much about the inner workings unfortunately
[16:59:32] <gmouer> and I am far too new at servos to tell by the symptoms
[17:00:03] <PCW> if you zoom into the leading edge of the step you should get a good idea of the drives acceleration capabilities
[17:00:54] <gmouer> I just never expected excessive accel would cause a overshoot in velocity, you set me straight though
[17:00:59] <JT-Shop> #5221 is the offset for the X axis in the G54 coordinate system
[17:01:45] <gmouer> I kind of assumed excessive accel would round off the corner as it came up to speed
[17:01:49] <JT-Shop> G10 L2 P1 X2.5 will change the value of #5221 to 2.5
[17:03:23] <JT-Shop> If your sitting at X10 in machine corrdinates and say G10 L20 P1 X2.5 it will change the value of #5221 to 7.5
[17:03:30] <gmouer> thanks again guys, hopefully the new info will allow me to get the fine tune done
[17:04:18] <andypugh> gmouer: It would, generally, except that all the time there is a position error the I term keeps winding up in a (failed) attempt to corect it. Then when the error is the other side, it takes just as long to unwind it.
[17:06:16] <tjb1> JT-Shop: X-2.5?
[17:06:17] <gmouer> I didn't think the drive had a PID loop internal, just a single op-amp rather than a complex pid loop in play
[17:06:47] <PCW> Just PI I think
[17:07:20] <gmouer> now, I do recall reading about integration in the various drive docs I have been though,\
[17:08:07] <gmouer> the P is done with the op-amp and its gain pot, the I done with R/C components? is that the basic idea?
[17:08:17] <PCW> Probably
[17:09:20] <gmouer> the amc drive was just a experiment, the orig drives are servo-dynamics with the machine
[17:10:16] <gmouer> think I got it, the amp gain system is not a simple fixed gain amp, but they ususally have PI loops in play
[17:10:43] <PCW> so if you put a step velocity input, the integrator sees a huge error and ramps very quickly so overshoots
[17:11:27] <gmouer> ahha docs I have read don't mention that when describing the battery method
[17:13:11] <JT-Shop> http://imagebin.org/236510
[17:13:39] <tjb1> Lovely purple primer
[17:15:25] <JT-Shop> should be of interest to you
[17:15:55] <tjb1> Might be, what is it for
[17:16:04] <tjb1> water table input?
[17:16:14] <JT-Shop> it's a bulkhead elbow for the water tank
[17:16:26] <JT-Shop> water tank input/output
[17:16:30] <tjb1> Why arent you using steel? :P
[17:16:46] <JT-Shop> it doesn't glue well
[17:16:46] <tjb1> Mc Master has some nice weld in fittings for like $3 for 3/4 npt
[17:17:08] <JT-Shop> yes but they only have threads on one side... think about it
[17:17:30] <tjb1> weld into pan, screw pipe in?
[17:17:44] <JT-Shop> tank not pan
[17:17:49] <JT-Shop> tank under pan
[17:18:10] <tjb1> Here is the thcud that I used -
http://pastebin.com/widDGH3p
[17:18:34] <tjb1> What really gripes me is PVC and CPVC...
[17:19:28] <tjb1> I must go…driving home so I wont get there until probably 9pm est :)
[17:19:30] <tjb1> bye all
[17:37:55] <Jymmm> ve7it: yo
[17:42:46] <ve7it> Jymmm, ho ho
[17:46:35] <Tom_itx> JT-Shop what did you end up with for a tank?
[17:46:41] <Tom_itx> beer kegs?
[17:50:53] <JT-Shop> a 40 gallon water heater
[17:53:31] <JT-Shop> http://imagebin.org/236514
[17:56:20] <Tom_itx> is that goin under the table?
[17:56:26] <Jymmm> ve7it: you're alive?
[17:56:26] <JT-Shop> yea
[17:57:35] <ve7it> yup... trying to build a tig welder at the moment.... I always have to do things the hard way!
[17:57:45] <Tom_itx> did you epoxy your floor? that's entirely too clean
[17:58:06] <JT-Shop> no, just raw concrete... I do keep it clean
[17:59:29] * JT-Shop puts on his chef hat
[18:01:47] <andypugh> seems like about 4 too many chairs for a workshop
[18:02:15] <Jymmm> andypugh: those aren't chairs, those are saw horses
[18:02:23] <Tom_itx> it's for all the other kids to come and watch
[18:02:31] <andypugh> <Ponder>
[18:02:52] <andypugh> I intend to motorise my new dividing head.
[18:03:23] <andypugh> For compactness I am thinking of mounting the motor shaft rigidly in the worm gear.
[18:03:58] <andypugh> That saves the length of a coupling, and the motor flange can fit tight up against the body.
[18:04:37] <andypugh> Then, because that can't work just like that, I want to mount the motor on a torsionally rigid but axially/angularly complaint mount.
[18:06:10] <andypugh> This is pretty common for encoders, viz:
http://www.clrwtr.com/Images/Red-Lion-Controls/Red-Lion-ZOD-ZOH-Encoders.jpg
[18:06:33] <andypugh> Reckon it will work?
[18:07:03] <andypugh> (I could, alternatively, use a rose-joint torque-arm)
[18:08:35] <skunkworks> I have thought of using that for mounting servos/steppers.. I don't see why it wouldn't work..
[18:09:32] <andypugh> It makes things a lot shorter.
[18:10:38] <skunkworks> yes
[18:12:00] <andypugh> (not to self, save before make before run)
[18:13:42] <jthornton> I need to CNC the surface grinder once it is back together
[18:14:42] <andypugh> There probably aren't many of those.
[18:14:55] <andypugh> Most have at least 2 aut-axes
[18:15:02] <andypugh> (auto-axes)
[18:15:28] <andypugh> Bonus marks for web-cam based auto-stroke.
[18:15:55] <jthornton> yea, I don't think I want to go that far just have the X and Y be automagic
[18:16:11] <andypugh> They aren't already?
[18:16:28] <jthornton> totally hand operated
[18:16:44] <andypugh> How strange
[18:16:55] <jthornton> I figure a couple of steppers would do the trick
[18:17:21] <andypugh> I would err towards step-servoing the X
[18:18:05] <jthornton> it has a belt reduction now and the handle is pretty easy to move
[18:18:45] <andypugh> (Actually, perhaps a VFD and AC motor, I have worked with at least one that just plug-reversed a 3-phase motor with a cam switch)
[18:21:26] <jthornton> maybe do something with my ardunio, G203v and a nema 23 stepper... for X to see
[18:21:35] * jthornton goes back to the kitchen
[18:22:26] <roh> should be harder mechanically than electric/electronic nowadays
[18:22:48] <roh> btw.. we also got chairs
http://hackerspaces.org/wiki/Raumfahrtagentur
[18:59:24] <andypugh> I really ought to get in touch with my local Hackerspace. Apart from anything else they have a Stratasys machine
[19:20:15] <andypugh> seb_kuzminsky: I just noticed that hal/drivers/mesa-hostmot2/bitfile.h includes <linux/firmware.h> and hostmot2/bitfile.c includes <linux/firmware.h> _and_ bitfile.h. Does that make sense?
[19:20:52] <andypugh> Also, we have two very different bitfile.h and bitfile.c pairs, one in hostmot2 and one in hal/utils.
[19:21:48] <andypugh> I know just enough to know that I don't know if that makes sense.
[19:35:11] <roh> andypugh: wow.. how could they afford something nice like that (and the material supply pricing) ?
[19:35:36] <andypugh> I don't know.
[19:36:55] <andypugh> Hmm, 1c free delivery from China? How does that work?
http://www.ebay.co.uk/itm/Free-500pcs-Black-Snap-Lock-Pin-Security-Loop-Plastic-Tag-Fastener-5-130mm-C63-/110977720593?pt=LH_DefaultDomain_0&hash=item19d6c9a111
[19:38:11] <andypugh> Ah, I know, they already bid their reserve themselves.
[19:38:27] <Tom_itx> andypugh
[19:38:36] <Tom_itx> http://www.cnczone.com/forums/attachment.php?attachmentid=51626&d=1201239292
[19:38:45] <Tom_itx> how would you drive such a beast?
[19:39:00] <andypugh> With the right drive.
[19:39:04] <Tom_itx> heh
[19:39:18] <andypugh> 5-phase steppers are apparently quite good.
[19:39:22] <Tom_itx> most bldc are 3 phase though
[19:39:39] <roh> well.. its just one half bridge per pin.. so whats the worries?
[19:39:41] <Tom_itx> have you seen any drivers for them?
[19:40:05] <andypugh> Yes
[19:41:06] <andypugh> (many on eBay)
[21:16:29] <Tecan> tjb1 you around ?
[21:16:36] <tjb1> always
[21:16:46] <Tecan> lol :)
[21:17:19] <Tecan> check pm
[21:17:34] <Tecan> want to pick ur brain on thc
[21:18:05] <tjb1> you can try
[21:36:28] <mevon> yay arduino cnc is alive. implamenting pos-fb now :)))
[21:37:51] <mevon> id like to thank andypugh for being such an... a good advisor and telling me that I couldnt do it, that just did it :P
[21:38:21] <mevon> oinks!
[21:48:58] <jdh> what did you do?
[21:51:59] <roh> gnnnh. fsck. this machine has nearly 1ms jitter on the latency test for the 1ms thread. *sigh*
[21:55:59] <Tom_itx> mevon what firmware did you use?
[21:58:21] <Tecan> would a good jitter cause the gcode to not get processed or would it be like da daaa da dad ad
[21:58:29] <Tecan> on the cnc
[22:01:21] <Tecan> would a jitter cause machine damage ?
[22:03:08] <roh> what i don't get.. its near exactly the same chipset
[22:03:17] <roh> via kt400 vs km400
[22:04:02] <roh> kt400 on the mill which is working fine for a long time now (old 8.04 setup)
[22:04:17] <roh> km400 on the machine which drives the lasercutter
[22:13:47] <mevon> Tom_itx, sanguino
[22:14:48] <pcw_home> Jitter mainly causes stalls with software step generation but also position noise in servo systems when in motion
[22:16:21] <Tom_itx> mevon what software?
[22:16:23] <Tom_itx> marlin?
[22:16:25] <roh> oh. stupid me... acpi is still enabled
[22:17:22] <mevon> Tom_itx, it is EMC2Arduino I am tweaking
[22:17:53] <Tom_itx> what chip does sanguino use?
[22:18:09] <Tom_itx> is it the one with the usb chip on it...1287
[22:18:34] <mevon> atmega644
[22:18:49] <mevon> pdip 20 MHz
[22:19:00] <mevon> over usb
[22:19:20] <Tom_itx> stick a sd on it
[22:19:24] <Tom_itx> and you won't need usb
[22:19:55] <mevon> nah I still need linuxcnc
[22:19:58] <mevon> :S
[22:20:14] <jdh> what does it do?
[22:21:13] <roh> fsck. thats not it
[22:21:15] <mevon> for now Im engraving pcbs
[22:21:41] <jdh> what does the arduino do?
[22:22:06] <Tom_itx> controls the steppers etc
[22:22:13] <jdh> why?
[22:22:22] <Tom_itx> because it can
[22:24:03] <roh> think mesa for poor people (no pun intended)
[22:24:57] <jdh> 7i43 quantity 1 is $79
[22:25:22] <jdh> find 4 other cheap bastards and they are $63/each
[22:25:40] <roh> jdh: i know. just saying.
[22:26:02] <roh> btw.. would a mesa board make using a machine with 1ms jitter feasible?
[22:26:16] <roh> or should i rather go hunt for another 10 year old pc?
[22:26:52] <jdh> SERVO_PERIOD = 1000000
[22:27:02] <jdh> that's my 7i43
[22:27:22] <roh> well.. does it hurt if its nearly 2ms sometimes? ;)
[22:27:36] <jdh> throw it away.
[22:28:02] <roh> *g*.. i need to keep it for now. its what the laser runs on when winxp is booted atm
[22:28:33] <Tom_itx> jdh, i suppose it's the challenge of it
[22:28:44] <roh> just hoped i can keep the machine, since its really similar to the one which runs emc fine. did anything change from 2.3.1 to 2.5.1 regarding old amd crud with via chipsets?
[22:29:11] <jdh> are you two talking about the same thing?
[22:29:35] <jdh> <mevon> yay arduino cnc is alive. implamenting pos-fb now :)))
[22:29:37] <Tom_itx> who two
[22:29:41] <Tom_itx> you two?
[22:30:01] <jdh> what does arduino cnc do? interpret gcode? motion planner? io?
[22:30:36] <Tom_itx> yeah
[22:30:47] <mevon> 3axis /w servo actuators
[22:30:52] <mevon> and switches
[22:31:19] <mevon> it can go to 9axis but not sure how rly
[22:32:09] <mevon> i also integrated the stepper driver controller in the arduino so I use 2 Hbridge motor drive for the stepper
[22:32:48] <jdh> 4 IO per axis?
[22:32:49] <mevon> so maybe I could make it to 4axis easily
[22:32:53] <mevon> 5
[22:33:13] <mevon> enable
[22:33:23] <mevon> I mean I got the enable
[22:33:34] <mevon> on the drives
[22:34:00] <jdh> was it fun?
[22:34:31] <jdh> 'fun' counts for about 79% for me :)
[22:35:08] <roh> well.. its quite a bit more till one has pins on the desk.
[22:36:06] <roh> 85€+vat+shipping for me for a 7i43
[22:50:46] <mevon> it still is :P gotta learn some more python now ttyl
[23:55:21] <r00t4rd3d> I made a speaker:
http://i.imgur.com/rqZP0.jpg
[23:58:35] <tjb1> whats that crap in the middle?
