BenJackson wrote:BenJackson wrote: All my settings are identical from parallel port to FPGA, except the FPGA is actually able to make the 1us pololu pulses. I assume I will need to stretch those a bit, which shouldn't have any effect on my max speeds. I could also put a scope on the pololu if I want to do some contortion to check the signal quality.
I made another spool with the timings bumped from 1us/200ns to 2us/400ns and no lost steps. Makes sense that you'd have to consider the waveform at the pololu and be less aggressive. The min step time on the pololu is around 30us anyway so the signalling time hardly matters.
(float r/w) maxvel
Maximum speed, in position units per second. If set to 0, the
driver will always use the maximum possible velocity based on
the current step timings and position-scale. The max velocity
will change if the step timings or position-scale changes.
Defaults to 0.
BenJackson wrote:I hope I have this nailed down!
BenJackson wrote:"Trigger on pulse width < 1us" was super handy.
cvoinescu wrote:BenJackson wrote:"Trigger on pulse width < 1us" was super handy.
That's a good oscilloscope you have there. I have a Tektronix 2465B, but now I have scope envy.
educa wrote:Does that mean that it now works out of the box on 2.5 ? Or are people still experiencing problems with rastering ?
educa wrote:Thats not a problem Ben, as soon as possible (I believe in about 1 week) I'll setup another HDD with your configs on it (I suppose its best to test on a fresh machine, since I don't think I can add both your and jvccs config on 1 machine ? You don't use the same freq component ?
Users browsing this forum: No registered users and 1 guest