Skip to content
Miatafy
Search Miatafy

Find something for your Miata.

Good places to start

    Buy ScreenTune
    Menu

    ND MX-5 Battery and Winter Storage

    The ND MX-5 runs a small battery: a group 51R, 12V, ~325 CCA from the factory. That is a deliberate weight call in a roughly 2,300 lb car, but it leaves little reserve. Combined with the CMU’s parasitic draw, a tired battery is the single most common cause of “infotainment” problems on the ND: random reboots, slow boots, dropped Bluetooth, and a clock that resets overnight are usually voltage, not firmware.

    Before you chase a software bug, measure the battery. Most of the symptoms below clear up once voltage is back where it belongs.

    ParameterValue
    Group size51R
    Voltage12V
    CCA325 (OEM); aftermarket options run 370–500
    LocationEngine bay, passenger side, under the plastic cover
    AccessRemove the plastic engine bay cover

    The OEM unit is physically small. Stepping up to a higher-CCA 51R (the Odyssey 51R and the Braille i-series both fit the tray and give more reserve and cold-cranking margin) is a common first move for owners who store the car or run accessories.

    With the car off, the CMU and other modules keep pulling current:

    ComponentDrawNotes
    CMU (sleep mode)20–50 mAHigher right after shutdown, drops over the first hour
    Keyless entry receiver5–10 mAAlways listening for the fob
    Clock / memory1–5 mAHolds radio presets and clock
    Alarm / immobilizer5–10 mASecurity standby
    Typical total30–75 mAVaries with options and CMU state

    At roughly 50 mA average draw, a healthy battery holds usable charge for about 30–40 days parked. A degraded battery can drop below cranking voltage in 2–3 weeks. This is why a car that “ran fine last month” cranks slow after sitting.

    Low-voltage symptoms that look like infotainment faults

    Section titled “Low-voltage symptoms that look like infotainment faults”

    Below about 11.5V the CMU starts producing symptoms that read as software problems:

    SymptomLooks likeActually is
    CMU reboots while drivingFirmware bugVoltage sag under electrical load
    Bluetooth pairing failsCMU Bluetooth faultRadio module starved for voltage
    Boot slower than usualPerformance degradationCPU throttling at low voltage
    Clock resets to wrong timeCMU memory failureMemory lost during a low-voltage event
    Black screen on startupDisplay failureCMU can’t complete boot
    Distorted or no audioAmplifier faultAmplifier brownout

    Measure resting voltage (engine off, several hours after driving) before touching anything else:

    • 12.6V+: fully charged, healthy
    • 12.4V: ~75%
    • 12.2V: ~50%, intermittent symptoms likely
    • 12.0V: ~25%, expect CMU issues
    • Below 11.8V: charge immediately; the CMU may refuse to boot

    If voltage is healthy and a slow boot persists, that’s a firmware-side issue rather than a battery one; see slow boot fix.

    • Drive 20–30 minutes at a stretch weekly; short hops never fully recharge the battery.
    • If the car will sit more than two weeks, put it on a tender.
    • Plan to replace the battery around 3–4 years. The small case runs hot and gets worked hard.
    • Check terminals yearly. Corrosion shows up as voltage drop and odd electrical behavior.
    • Tender it whenever it’s parked.
    • Use a maintainer with an automatic float mode; CTEK, Battery Tender, and NOCO all make solid units.
    • For multi-month storage, either tender it or disconnect the negative terminal.
    TypeUse caseExamples
    Automatic maintainerGarage storage with an outletCTEK MXS 5.0 (4.3A), Battery Tender Junior (0.75A)
    Solar trickle chargerOutdoor storage, no outlet5–10W panel, enough to offset parasitic draw
    Smart multi-mode chargerSeasonal storage plus reconditioningNOCO Genius series

    The Battery Tender Junior is enough to hold a parked ND; the CTEK MXS 5.0 also recovers a deeply discharged battery, which matters if you’ve already let one sit flat.

    For owners who park the ND for the cold months.

    StepWhy
    Fill the tank, add stabilizerLimits moisture and varnish
    Change oil if near intervalDon’t let contaminated oil sit on bearings
    Verify coolant freeze protectionConfirm it covers your expected low temps
    Inflate tires to 32–36 psi (3–5 psi over normal)Reduces flat-spotting
    Clean inside and outPrevents staining and mold
    Connect a tenderHolds charge through the layoff
    Crack windows slightly (indoors only)Reduces cabin moisture
    Dryer sheets in the cabinDeters rodents
    Cover the exhaust tipsKeeps rodents out
    Leave the parking brake offPrevents pads seizing to the rotors
    Leave a manual in gearHolds the car without the parking brake
    • The tender should read green / maintained.
    • Check monthly for fluid under the car.
    • If you start it, run it to full operating temperature; do not short-idle, which leaves moisture in the exhaust.
    StepWhy
    Check all fluid levelsMay have settled or leaked
    Inspect tires and pressuresFlat spots normally work out after a few miles
    Remove rodent deterrentsClean the cabin
    Test brakes gently firstSurface rust on rotors clears in a few stops
    Let the CMU boot and acquire GPSClock and position will be stale
    Verify electrical systemsConfirm nothing failed while parked
    Drive easy for the first 10–15 minutesLet everything reach temperature
    • Age past 3–4 years (preventive)
    • A load test shows more than ~20% CCA loss from rating
    • Symptoms persist after a full charge
    • Slow cranking in mild weather

    The battery sits in the engine bay on the passenger side:

    1. Remove the plastic engine bay cover.
    2. Disconnect the negative terminal first, then positive.
    3. Remove the hold-down bracket.
    4. Fit the correct group size (51R).
    5. Reconnect positive first, then negative.
    6. Reset the clock and radio presets; both are lost on disconnect.

    After reconnection the CMU does a fresh boot. Bluetooth pairings survive (stored in NVRAM, not RAM); the clock re-syncs once GPS locks. If the screen behaves oddly for the first drive or two after a disconnect, that’s the CMU re-learning state, not a fault.