2012/4/9 Jeshua Lacock <jes...@3dtopo.com>: > > On Apr 9, 2012, at 3:16 AM, Viesturs Lācis wrote: > >> 2012/4/9 Jeshua Lacock <jes...@3dtopo.com>: >>> >>> How is that possible? The encoders are connected to the Geckos, not through >>> the parallel port.... >> >> I do not understand, what exactly is not clear to You :) >> AFAIK Gecko drives will need the encoder signal for them to function, >> so each encoder signal will have to be splitted/doubled/copied to both >> PC and Gecko drive. > > Hi Viesturs, > > Well OK, that was never explained to me. You were saying that perhaps no > rewiring would be required, and Peter was saying that the encoders would be > wired to the pins of the 5i22, but no one ever told me that they would have > to be wired to *booth*. > > I have stated this already, but it would have been immensely helpful if I > could see a simple schematic. I am a bit surprised Peter or Mesa hasn't > provided one.
When I joined this mailing list, one of the things I learned, is that proper formulation of question considerably increases the chance of receiving an answer :) Please, be as specific as possible, do not be afraid of sharing details. For example, schematics of what exactly do You mean? How to split the encoder signal to feed in two devices - Gecko drive and PC? Or how exactly connect that "PC" signal to Mesa board? The first one might get tricky, just like Steve mentioned, and I also think (do not rely on my opinion as I am only beginner with electronics) that additional hardware will be needed for splitting the encoder signal. The second one is brain-dead easy - take GND of the incoming signal and connect to GND of appropriate gpio pin on Mesa card and the same for the signal lead - connect it to appropriate gpio input pin. > >>> From the way You wrote Your first message I understand that You >> already have a working system with encoder signal going also to PC: >> 2012/4/6 Jeshua Lacock <jes...@3dtopo.com>: >>> >>> My Z axis is about 10,000 lines per inch, so it uses up my available >>> bandwidth really fast. Right now I have the Z's max speed set to a mere 3 >>> inches per sec. My Y is 24 inches per sec, and X is 10 inches per sec. That >>> uses up my available 71khz. >>> >>> So, I understand that something like Mesa's 4I30 4 channel quadrature >>> counter card will allow me much more bandwidth to run my servos faster. >>> >> >> What kind of "10,000 lines per inch" are You talking about, if that is >> not encoder signal? It could be also step signal, but encoders were >> the only thing discussed in that message... >> >> Could You, please, expand on what exactly You have there? Where are >> encoders currently connected? > > As I have stated, the encoders are currently connected to the Geckos. Ok, great! Then could You, please, explain in a lot more detail, what is that 10000 lines per inch bandwidth You were talking about? The way I initially understood this: there are 10K pulses from encoder on 1 inch travel and exceeding the velocities, mentioned in Your first post, would simply exceed the LinuxCNC's capability to read them on parport. Since there are no encoder signals on parport, I see that I have been totally wrong. Viesturs Viesturs ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
