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.
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. Synchro And Resolver Engineering Handbook Moog Inc
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
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. It looks like a small, precision motor but