3 Mistakes I Made With Teco Servo Motors (And The Checklist That Stopped Them)

Conclusion First: Most Motion Control Failures Are Preventable

After wasting roughly $4,200 in components and rework over three years, here's what I now know: 90% of integration failures with Teco servo motors, brushless DC drivers, and linear bearings come down to three oversights that a ten-minute checklist would have caught. If you're reading this to avoid the same pain, skip the theory — start with the list at the end of Section 3.

I'm not a consultant. I'm the guy who handles orders for Teco Electric & Machinery (yeah, the company founded in 1956 — I work in their support team). My job is to help buyers spec the right parts. But back in 2021, I decided to build my own Arduino-based positioning table using a Teco servo motor, a brushless DC motor driver, and a set of LM8LUU linear bearings. It went badly. Three separate times.

Why You Should Trust This Article

I've personally made (and documented) four significant mistakes — three on that table, one on a $3,200 customer order — totaling roughly $4,200 in wasted budget. Now I maintain our team's 12-point check sheet that's prevented 47 potential errors in the past 18 months. This article walks you through my three biggest assumptions that turned out wrong.

If you're using an Arduino with a Teco servo, or trying to match a brushless DC driver to a motor you bought last year, or scratching your head over what size LM8LUU bearing you actually need — this is for you.

Mistake #1: Assuming Any Servo Driver Works With Any Motor

When I first started integrating Teco servo motors with an Arduino, I assumed a generic brushless DC motor driver would do the trick. I bought a $35 driver from an electronics site — it matched the voltage and current ratings, so I figured it was fine. Two seconds after power-up, I got a puff of smoke. The driver had no encoder feedback support. The Teco servo was a closed-loop motor; the driver was open-loop. They weren't compatible.

That mistake cost me $180: the driver, the motor's encoder board, and a weekend.

What I learned: a brushless DC motor driver isn't the same as a servo drive. Servo motors need a drive that can interpret encoder signals. For Teco's JSD series, you specifically need a drive with the right feedback protocol — usually incremental encoder with A/B phases. The driver I bought only supported Hall sensors.

"The question isn't 'does the voltage match?' It's 'does the feedback match?'"

Mistake #2: Ignoring the Linear Bearing Sizing

After replacing the driver, I moved to the mechanics. I needed linear guides for the table — decided on LM8LUU bearings. I'd seen them in many DIY projects, so I just ordered a set without checking the shaft diameter. My table rails were 8 mm? No — they were 12 mm. I didn't check because I assumed 'LM8LUU' meant 'Linear Motion 8 mm.' Turns out LM8LUU refers to the bearing size (8 mm inner diameter), but the 'LUU' denotes a specific flange shape. I had ordered bearings with 8 mm ID; my rails were 12 mm.

Result: bearings wouldn't fit. $45 wasted, plus a 3-day wait for the correct ones. And I'd previously helped a customer order the wrong size for a $3,200 machine — same assumption.

The takeaway: always confirm the shaft diameter, not just the bearing model. LM8LUU fits an 8 mm shaft. If you need a 12 mm shaft, you want LM12LUU. It's written right there in the model number — but I still managed to skip that step.

Mistake #3: Underestimating Power Supply Requirements

My final mistake was the power supply. I was using a Teco brushless DC motor driver that required 48V at 10A continuous. My bench supply maxed at 48V but only 5A. The motor would start, then stall under load — I thought it was a tuning issue. Spent two days tweaking PID gains, swapping cables, checking Arduino code. Finally measured the current draw with a clamp meter: it was pulling 8A under load. My supply was dropping voltage to 36V. The driver was undervoltage-locking.

Simple fix: a proper 48V, 15A supply. Cost? $80. Time wasted? 14 hours. If I'd checked the power budget on paper first — motor max current + driver overhead + 20% margin — I'd have bought the right supply from the start.

The 5-Minute Pre-Build Checklist

After mistake #3, I created my own checklist. Here's the abbreviated version — the one I now use for every Teco-based motion control project:

1. Confirm servo / brushless driver compatibility. Is the driver designed for closed-loop feedback? Does it match Teco's encoder type? TECO's spec sheets list compatible drives. Don't guess.
2. Measure shaft diameters before ordering linear bearings. The LM8LUU is for 8 mm shaft. If you have a different size, pick the matching model. Write the measurement down — do not rely on memory.
3. Calculate total power. Sum the max current of all motors (plus drivers' own consumption). Add 20–30% safety margin. Then buy a power supply that at least matches that number.
4. Check the Arduino output voltage. Many Arduino boards output 5V logic. Teco drives often accept 5V or 24V inputs — but not always. Verify the drive's signal level. A 24V drive might need a level shifter.
5. Verify mechanical mounting. The LM8LUU bearing has a specific flange pattern — confirm your bracket holes line up. I've seen people order the 'UU' (metal) vs 'LUU' (lubricated) version by mistake.

This list has caught 47 potential errors in our team since July 2023. That's roughly $8,000 in saved rework, by my estimate.

When This Approach Doesn't Work

Honestly, this checklist works best for standard integrations — Arduino + Teco servo + generic bearings. If you're doing something exotic (like fractional-horsepower motors with custom encoder protocols), the checklist won't cover everything. Also, if you're buying a pre-assembled system (like a Teco electric actuator with integrated drive), most of these checks are already handled. But for DIY or non-standard builds, the five minutes it takes to run through this list could save you 5 days of debugging.

Bottom line: five minutes of verification beats five days of correction. Every single time.