The handbook, in its quiet way, predicted this. Its chapters on “Environmental Performance” and “Reliability Under Vibration” were not theoretical. They were the product of Moog’s own test labs—shaker tables, thermal chambers, and life-cycle test rigs running for years. Today, you can download the Moog handbook (now often integrated into their broader “Motion Control” technical documentation). A fresh engineering graduate might look at it and ask: Why learn this? My servo drive auto-tunes. My FPGA handles the R/D conversion in a few microseconds.
This is the story of that handbook, the technology it champions, and why, in an age of digital abundance, its principles remain utterly indispensable. To understand the handbook, one must first understand the components at its heart. A synchro is, in essence, a rotary transformer. It looks like a small, precision motor but behaves like an analog computer. When you rotate its rotor, it outputs a set of three voltages (or receives them) that encode the exact angular position of a shaft. No glass disks, no LEDs, no fragile optics—just copper windings and a magnetic field.
The Synchro and Resolver Engineering Handbook is not just a manual. It is a monument to the era when feedback was analog, when noise was a physical force to be grappled with, and when a company like Moog could build a lasting reputation not just on the hardware it sold, but on the knowledge it freely shared. Synchro And Resolver Engineering Handbook Moog Inc
The resolver is its more refined sibling, using two output windings (sine and cosine) rather than three. This makes it mathematically purer and, therefore, the darling of aerospace and defense applications.
Many companies stopped printing their handbooks. But Moog, stubbornly analog, kept the Synchro and Resolver Engineering Handbook in print—or at least available as a PDF. Why? Because the real world is analog. The handbook, in its quiet way, predicted this
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.
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. Today, you can download the Moog handbook (now
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.