I finally found a YouTube clip demonstrating something along the lines of what I want:
As you can see in the video this is a direct driven servo motor, not very unlike my setup where I have a direct driven induction drive. With high resolution encoders and a good drive I'm hoping to be able to get something similar, although I realize the resolution and accuracy here is more than I can hope to achieve.
But to give a quick summary, they use a high pole count (8 or 16) permanent servo motor. This makes it possible to get very high torque at the cost of having lower max speed. In this case 500 RPM. With a normal 2 or 4 pole motor we can expect to loose some low speed accuracy, but gain in the top speed. My spindle will have 5000 RPM at 254 Hz.
They also state they use sin encoders. We can assume they are interpolated, just like we talk about here. The question is how many periods/rev they use, and how many bits they use for interpolation.
The accuracy they get are 0.0001 inch, or 2.54 um at a radius of 27 inches, or 685.8 mm. This gives 1,696,460 counts/rev, or 0.76 arc sec resolution.
Now to be able to get motion with this repeatedly is impressive! That would mean the system have an internal resolution possibly 10 times that! after all it's not possible to get repeatability of 1 arc second if your encoder have 1 arc second resolution. To be able to achieve that repeatedly and reliably like they have in this clip they will have to have 10 fold the resolution internally.
Now since this axis has a limited speed of 500 RPM they can (and should) increase the resolution on the encoders used.
The Heidenhain encoders you linked to would most all of them fit right in this range. Many of them comes in resolution in the 10,000 to 150,000 pulses/rev, all in sin/cos. Which mean if you use 10 bit of interpolation you can get 10,000,000 to 150,000,000 counts/rev.
Now this is high enough to do what's shown in this video and then some. So I don't understand what you are saying when you say the mentioned encoders aren't accurate enough.
Now to get true micrometer accuracy at the radius mentioned here would obviously demand highly accurate mapping and temperature compensation and what not. Not something any of us using LinuxCNC would ever dream of.
The main goal for me with wanting this high resolution is to be able to calculate speed in an accurate fashion at low speeds. If you look at even low priced servo/drive system from china they use 20 to 22 bits/rev resolution encoder system these days. And that is because it's easily and cheaply available now.
500 p/rev sin/cos encoders and an iC-House chip is all it takes to get ~1,000,000 counts/rev resolution (not repeatable accuracy that is, resolution only, with spread and inaccuracy between steps). The BISS protocol is an open standard which will handle this easily and reliably. So there is no problem for any of the servo system manufacturers to take advantage of this. They also have magnetic solution with similar capabilities that are even cheaper (as you don't need an analogue encoder).
The question is when LinuxCNC users will start to do the same. I'm hoping we can get out of the limitations quadrature encoders impose. In the same way most of us now have gone beyond the limited frequency possible when using a parallel port for direct step/dir signals as used to be the standard way back when it used to be called EMC2.
Anders