> > Until this is solved I calculate number of periods and where phase is > > located within period in average for all values each time. It will > > work to calculate by using each value every time even though it use a > > ridiculous amount of clock cycles. > > That's just a hardware counter ticking away between arrival times, reset > after reading, isn't it? The elapsed time is the sample value, IIUC. > (Why do I feel there's something I'm missing here?)
Phase may be calculated from for example 128 arrival times: 1. Choose an arbritrary reference point t0 in time. 2. Calculate average period. 3. Average of difference between n periods is the average phase shift. Now I want this as a moving average which require some more thinking. I will stick with the above until it works. Average phase is what I consider as the synchronization point. Micro controller period also have to be adjusted to the average period so that it consume values at the same rate as linuxcnc produce them. Without averaging jitter of position arrival times there will be speed jitter which is a problem because of inertia. Nicklas Karlsson ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
