And then there were the application diagrams. Beautiful, messy schematics showing how to use a single resolver to measure both azimuth and elevation via a mechanical differential. Circuits for “electronic gearing” that predated digital motion controllers by twenty years. A diagram for a “synchro-to-digital converter” built from discrete comparators, counters, and a precision D/A converter—a project that would take a month to debug but teach you more about sampling theory than any textbook. By the late 1990s, the writing was on the wall. Optical encoders with 16-bit resolution were dropping in price. Resolver-to-digital (R/D) converters existed as single-chip solutions from Analog Devices or DDC. The need to understand the analog soul of a resolver seemed to be fading.
The answer lies in edge cases. When a resolver cable runs 50 meters through a factory with VFDs spewing common-mode noise, the handbook’s sections on “Shield Termination” and “Twisted-Pair Routing” become priceless. When a resolver’s output voltage sags because the excitation frequency drifted due to a cheap oscillator, the handbook’s graphs of “Output vs. Frequency” show you exactly how much error to expect. When you need to build a redundancy management system—three resolvers on one shaft, voting on position—the handbook’s discussion of “dual-speed resolvers” and “electrical zero alignment” is the only guide you’ll find. Synchro And Resolver Engineering Handbook Moog Inc
In a conference room in East Aurora, New York (Moog’s global headquarters), there is probably a worn copy on a shelf. And somewhere right now, an engineer is opening a PDF of that same handbook. They are trying to figure out why their resolver’s sine-cosine mismatch is 0.5% at 25°C but 1.2% at 85°C. They will find the answer in a footnote on page 4-17. And they will be grateful. And then there were the application diagrams
Moreover, the handbook teaches a mindset. It teaches that a position sensor is not a black box that spits out bits. It is an impedance network, a transformer with a rotating coupling coefficient, a source of quadrature error and harmonic distortion. To truly debug a motion system, you must think like the handbook: with a vector network analyzer in one hand and a deep respect for analog imperfections in the other. If you are lucky enough to find an original printed copy from the 1980s—spiral-bound, with a faded blue cover and the old Moog “M” logo—you possess a piece of engineering history. Flip to any random page. You will see hand-drawn figures, typewritten equations (with corrections in pen from some long-ago applications engineer), and a purity of purpose that modern documentation rarely achieves. not simple checklists.
For over half a century, this handbook has been more than a product catalog. It is a Rosetta Stone for translating the physical world of rotating machinery into the precise, unforgiving language of electronic feedback. Before optical encoders became cheap and ubiquitous, before Hall-effect sensors saturated the market, the synchro and the resolver were the undisputed kings of angular measurement. And Moog Inc.—a company more famous for its hydraulics on fighter jets and amusement park rides—wrote the definitive text on how to wield them.
The most revered section was always the troubleshooting guide. “Synchro system hunting?” the handbook would ask. “Check velocity damping. Increase tachometer gain or add a lead network.” “Null voltage too high?” “Verify orthogonality of stator windings.” It was diagnostic jazz, not simple checklists.
The handbook was Moog’s bid to standardize the industry. Before it, every defense contractor had their own way of testing, specifying, and wiring these components. Noise margins varied wildly, compensation networks were treated as dark arts, and a resolver from one vendor might not talk to a servo amp from another. Moog’s engineers, led by a cadre of analog gurus whose names are now lost to corporate history, sat down and wrote the canonical text.
