G76, Troubleshooting needed!
08 Nov 2018 15:05 #120270
by Victor
Replied by Victor on topic G76, Troubleshooting needed!
Hi Andy,
Ok, and when we say counts per rev do we mean 2048ppr=2048 counts? or should i make that 4x due to the quadrature? = 2048x4=8192?
If ok i will go with a 2048ppr encoder.
Well i have tried to do as much reading as possible on the subject and i have noticed that line-driver is recommended. And the encoder i suggested do use line-driver if i'm not mistaken?
Br Victor
Ok, and when we say counts per rev do we mean 2048ppr=2048 counts? or should i make that 4x due to the quadrature? = 2048x4=8192?
If ok i will go with a 2048ppr encoder.
Well i have tried to do as much reading as possible on the subject and i have noticed that line-driver is recommended. And the encoder i suggested do use line-driver if i'm not mistaken?
Br Victor
Please Log in or Create an account to join the conversation.
08 Nov 2018 15:22 #120272
by andypugh
In this case it doesn't matter if the 2048 count is 2048 pulses our 8192 pusles, it's still comfortably under the 2Mhz count rate. (and with the filter off I think you can have 10MHz)
Replied by andypugh on topic G76, Troubleshooting needed!
I was deliberately ducking that question. The limit is in counts per second, 4 x slots, but it can be hard to tell whether a given encoder is using slots or counts in the spec.Ok, and when we say counts per rev do we mean 2048ppr=2048 counts? or should i make that 4x due to the quadrature? = 2048x4=8192?
In this case it doesn't matter if the 2048 count is 2048 pulses our 8192 pusles, it's still comfortably under the 2Mhz count rate. (and with the filter off I think you can have 10MHz)
It is. But is also seems to have UVW commutation outputs (which you don't need) and is in a somewhat inconvenient package.Well i have tried to do as much reading as possible on the subject and i have noticed that line-driver is recommended. And the encoder i suggested do use line-driver if i'm not mistaken?
Please Log in or Create an account to join the conversation.
Time to create page: 0.073 seconds