Selection guide
Selecting a Replacement Servo Drive for Resolver Motors
Short answer
Screen the resolver interface before the power ratings: excitation frequency and voltage, transformation ratio between 0.2 and 1 V/V, pole relationship, pinout, and whether the resolver carries commutation. Then check the supply input range and continuous current against the motor nameplate. For a 1.3–1.5 kW axis the current screen passes easily; the resolver match decides the drive.
On this page
- Match the resolver interface first
- Establish whether the resolver carries commutation
- Screen the power section
- Sizing the current screen for a 1.3–1.5 kW axis
- Four ways to put a resolver motor back in service
- Candidates worth verifying
- Commissioning checks before load
- The decision for this requirement
- Questions asked
A resolver-input label and a nameplate kW figure do not select a drive. Work in this order: establish the resolver's electrical signature — excitation frequency and voltage, transformation ratio, pole relationship, pinout — and whether it also carries commutation; then screen the survivors for a documented input range that covers the supply and continuous current against the motor nameplate. On a 1.3–1.5 kW axis the current screen is easy to pass; the resolver interface decides the choice. Keep the resolvers on the motors, because a brushless servo that commutates from the resolver needs them, and the correct replacement is a drive with a native resolver input rather than a feedback conversion.
Match the resolver interface first #
A resolver is a rotating transformer: the drive feeds the rotor winding a sine excitation and reads two stator windings whose amplitudes follow the sine and cosine of shaft angle. Three things must therefore agree between drive and resolver, and none of them is carried by the words "resolver input" on a datasheet.
- Excitation. The resolver is wound for a rated excitation frequency and voltage, and the drive must be configurable to supply exactly that. Take the values from the motor or resolver datasheet, not from the old drive's settings guessed at.
- Amplitude window. Published resolver application literature puts the transformation ratio — secondary amplitude per volt of excitation — between 0.2 and 1 V/V. The drive's converter expects the returned signals inside its own window; a resolver at the low end of that range paired with a drive built for the high end starves it, and the reverse risks clipping.
- Poles and pinout. When the drive derives commutation from the resolver, the resolver's pole-pair count must match what the drive assumes for the motor. The wiring — excitation pair, sine pair, cosine pair — is also pinned differently by different motor makers, so work from the motor's drawing, not from the old drive's terminals.
Resolution comes after those pass: many resolver drives offer selectable 12-, 14- or 16-bit conversion, giving 4,096, 16,384 or 32,768 counts per resolver cycle. Set 16 bits unless the controller's count-rate limit says otherwise.
Establish whether the resolver carries commutation #
On a brushless servo motor sold with resolver-feedback drives, the resolver almost always does two jobs at once: it tells the drive which windings to energize, and it reports position and speed. That dual role is what sinks the common suggestion to strip the resolvers and fit encoders — unless the replacement scheme provides commutation by another route, an encoder in the resolver's place leaves the drive blind to winding angle and the motor will not commutate.
If the motors arrived without paperwork, settle what is actually on the shaft before shopping: identifying resolver and encoder feedback on old servos comes first, and geared resolvers read differently from direct-mounted ones. Count mismatches then announce themselves loudly — feedback that reports a different number of counts than the axis expects produces scaled travel, the mechanism behind servo travel error after a resolver and encoder swap.
The decision from this section: if the resolver commutates, it stays on the motor. A second feedback device can be added; the resolver is not replaced.
Screen the power section #
Three checks, in the order they are usually gotten wrong:
- Input range. The supply must sit inside the drive's documented input range. Servo drives come in low-voltage and 400 V-class families, and the family label is not a rating — read the range on the exact model.
- Current. The drive's continuous output current must meet or exceed the motor's nameplate continuous current, and its peak rating must cover the motor's peak.
- Motor-side details. The drive must accept the thermal sensor wired into the motor connector and support the motor's rated speed.
A candidate that fails any of these is out before the resolver questions matter.
Sizing the current screen for a 1.3–1.5 kW axis #
Inputs, with sources:
- Required power: 1500 W, the top of the stated 1.3–1.5 kW need for the axis.
- Supply: 480 V three-phase, line to line, as specified for the machine.
- Motor nameplate continuous current: not documented for these motors — it is the one number that must be read off the nameplate or motor datasheet before purchase.
Rule in words: three-phase line current equals power divided by the product of the square root of three and the line-to-line voltage. This is a floor, not an operating point — it assumes unity power factor and zero losses, so measured current runs higher by whatever efficiency and power factor cost.
Arithmetic:
1.732 × 480 V = 831 V 1500 W ÷ 831 V = 1.8 A per axis 2 axes × 1.8 A = 3.6 A total at the supply
Result: the supply must deliver at least about 1.8 A per axis. The drive is rated against a different number — continuous output current versus motor nameplate current — because motor phase current and supply line current are not the same quantity.
Decision: reject any candidate whose continuous output current is below the motor's nameplate continuous current; that threshold is absolute, whatever the kW label says. For this requirement the screen is undemanding — the 27 A the Baldor FlexiDriveII line was reported to reach clears a 1500 W axis on this supply even if motor phase current runs several times the 1.8 A supply floor. Current will not be the constraint here; the resolver interface is.
Four ways to put a resolver motor back in service #
| Path | Feedback handling | Controller cost | Fits when | Verdict |
|---|---|---|---|---|
| Drive with native resolver input | Excites and demodulates the resolver; commutation and position from one device | One command channel per axis | Motors keep their resolvers | The choice for this requirement |
| Resolver kept, shaft encoder added | Resolver commutates; encoder reports position | Encoder, mounting, one controller feedback input | Machine needs finer position than the resolver gives | Valid as an addition, never as a swap |
| Controller synthesizes the sine and cosine pair into a simple drive | Drive carries no resolver circuit; the motion controller generates the two sinusoids | Two controller channels per axis; two axes need a four-axis card | A multichannel motion card is already in hand | Fallback, paid for in controller channels |
| Resolver removed, encoder fitted alone | Nothing carries commutation | Encoder plus drive change | Resolver proven to carry no commutation | Rejected for motors that commutate from the resolver |
The synthesized-sine path trades resolver hardware in the drive for double controller channels; with two axes it commits a four-axis card, so weigh that against a native resolver drive before choosing it.
Candidates worth verifying #
- The installed Control Techniques Digitax units take resolver signals only, so like-for-like means a current-production servo drive with the same native interface.
- The Baldor FlexiDriveII was reported in the field with resolver, encoder or Hall feedback and analog or step-and-direction command; verify the exact catalog number, input voltage and feedback option in current documentation before relying on any of it.
- Resolver support is per model, not per maker. Parker's general-purpose brushless servo line with resolver feedback lists TPD-M, SLVD-N and HIDRIVE drives as its documented pairings, while in the Siemens G120 family the resolver input exists only on the CU250S-2 control unit and only in vector control mode — a vector-control-only drive regulates speed, it does not position an axis. Read the exact model's documentation; a family brochure is not a compatibility statement.
Commissioning checks before load #
- Wire and unwire with the supply locked out and verified dead; this is qualified-person electrical work under NFPA 70E where you operate.
- Enter the resolver settings the drive's commissioning section asks for — excitation, resolution, pole relationship — from the motor data, not from memory of the old drive.
- Set the commutation offset by the drive's own procedure with the motor free to rotate.
- Run unloaded at low speed and confirm rotation direction, steadily increasing feedback counts, and smooth, quiet torque.
- Apply load, compare continuous current with the nameplate, then tune the velocity and position loops.
The offset step is the one that punishes shortcuts: aligning the drive's commutation with the windings is the same resolver offset and commutation work documented for robot-axis retrofits, and a wrong value typically shows up as rough low-speed torque with excess current at standstill.
The decision for this requirement #
Two 1.3 kW motors with resolvers that commutate, on this supply: buy two current-production servo drives with a native resolver input, a documented input range that includes the supply voltage, and continuous output current at or above each motor's nameplate figure; set the resolver conversion to 16 bits; leave the resolvers on the motors. Add a shaft encoder only if the machine's positioning tolerance demands finer counts than the resolver loop delivers. Reject any candidate whose resolver support stops at vector control, and treat the synthesized-sine architecture — two controller channels per axis, a four-axis card for this pair — as the fallback only if no native resolver drive survives the screen.
Questions asked
Can one resolver-input drive run both motors?
No. Each servo axis needs its own drive, because the drive closes that motor's current loop and demodulates its own resolver. The pair shares the supply and the controller command signals, nothing else. Budget two drives, and set each drive's resolver parameters from that motor's data.
What goes wrong if the drive's excitation does not match the resolver?
A resolver is a transformer wound for a rated excitation frequency and voltage. Drive it at the wrong frequency or voltage and the secondary amplitudes leave the window the converter expects, so position readings lose accuracy or the drive reports feedback loss. Set the drive's excitation to the resolver datasheet value before any tuning.
Is 12-bit conversion enough for a positioning axis?
If one resolver cycle spans one motor revolution, 12-bit conversion gives 4,096 counts per revolution, about 0.088 degrees per count, while 16-bit gives 32,768 counts, about 0.011 degrees. Many axes run acceptably on 12 bits; set 16 bits when the drive offers it, because it costs a parameter change, not hardware.
Should I add encoders to these motors?
Only if the machine needs finer position feedback than the resolver loop provides. The resolver stays on the motor for commutation, and a shaft-mounted encoder is added mechanically and wired to the controller as the position source. Treat it as an addition with its own mounting and wiring checks, never as a swap.