Riding Data & Regen
Power consumption, regenerative braking and thermal management in your Zero's riding logs — and the drivetrain that produces them: the Z-Force motor, the controller that sets the current ceiling, the single belt reduction, and what actually derates when the numbers fall away.
TL;DR
Positive amps mean energy leaving the pack; negative amps while riding mean regenerative braking. BattAmps and MotAmps never match because they are measured on opposite sides of the inverter. The MotAmps ceiling is a number written into the controller — Zero publishes it, from 420 A to 900 A depending on model and year, and from MY2024 it is explicitly a firmware setting. No manual publishes a temperature at which power is cut; what Zero does publish is a second top speed, and the gap between maximum and sustained is its own statement of what derating costs.
Every Zero motor is passively air-cooled. No Zero of any generation has a liquid-cooled motor. Of the 90 model-year spec sheets extracted from Zero's own owner manuals, 87 say “passively air-cooled” in so many words — including every SR/F, SR/S and DSR/X sheet — and the remaining three (the 2026 LS1, XB and XE) state no cooling method at all. Cooling is not a generation difference, and nothing on this page should be read as one.
What does differ by generation is the controller and which channels reach the log. Gen1/Gen2 (XMX and SDS platforms) run a Sevcon Gen4 controller and record motor RPM, motor current and the odometer in the MBB. Gen3/FST (SR/F, SR/S, DSR/X) are Cypher III machines with traction control and stability control; their manual fault tables contain no Sevcon entries and their logs contain no Sevcon events, and the MBB record carries none of the motor channels — see Key Riding Log Fields below, and the controller section for the evidence behind the Sevcon attribution and the current ceiling each generation enforces.
Understanding Current Flow
The current fields (BattAmps, MotAmps, I) tell you what the bike is doing. The sign and context determine the state:
Positive current means energy flowing from battery to motor. This is normal acceleration or maintaining speed.
Negative current while riding = motor acting as generator, pushing energy back to the battery.
Negative current with Charge mode = plugged in and charging from external power.
Near-zero current means bike is on but stationary, or coasting with throttle released.
The motor those amps are going into
Every current, temperature and RPM channel on this page is a measurement of one machine: a Z-Force motor bolted to the frame, fed three-phase alternating current by a controller, driving the rear wheel through a single belt reduction. Nothing about that layout changed between 2015 and 2026. What changed is the size of the motor, the rotor inside it and the amount of current the controller is allowed to push — and every one of those changes shows up in the log before it shows up anywhere else.
Zero names its motors by a two-number designation: a nominal stack diameter of 75, then a length. Across the 117 model-year specification rows in our manual index there are 6 of them, and the pattern is simple — a longer stack is a bigger motor. Every one of those 117 rows describes the motor as passively air-cooled in Zero's own words, and not one describes anything else. There is no pump, no radiator and no fan on the motor of any Zero in this table, which is the single most important fact for reading a MotTemp trace: the only thing carrying heat away is the case, the air moving over it and time.
Every Z-Force designation Zero prints in an owner manual, MY2015–2026
| Designation | Models | Model years | Peak power | Peak torque | Controller phase current |
|---|---|---|---|---|---|
| Z-Force 75-10 | SR, SR/F, SR/S | MY2020–2026 | 52 kW (≈70 hp) – 84 kW (≈113 hp) | 140 Nm (≈103 lb·ft) – 190 Nm (≈140 lb·ft) | 665 A / 785 A / 900 A |
| Z-Force 75-10 5T | DSR/X | MY2023 | 75 kW (≈101 hp) | 225 Nm (≈166 lb·ft) | 900 A |
| Z-Force 75-10X | DSR, DSR/X | MY2024–2026 | 52 kW (≈70 hp) – 75 kW (≈101 hp) | 170 Nm (≈125 lb·ft) – 229 Nm (≈169 lb·ft) | 670 A / 765 A / 900 A |
| Z-Force 75-5 | DS, FX, FXE, FXS, S | MY2017–2025 | 33 kW (≈44 hp) – 34 kW (≈46 hp) | 106 Nm (≈78 lb·ft) | 420 A / 550 A |
| Z-Force 75-7 | DS, S, SR | MY2015–2026 | 44 kW (≈59 hp) – 51 kW (≈68 hp) | 109 Nm (≈80 lb·ft) – 132 Nm (≈97 lb·ft) | 420 A / 550 A / 600 A / 660 A |
| Z-Force 75-7R | DSR, SR | MY2016–2023 | 51.5 kW (≈69 hp) – 52 kW (≈70 hp) | 146 Nm (≈108 lb·ft) | 660 A / 775 A |
Power and torque are the ranges printed across the model years each motor covers; they move with the controller current and the firmware, not with the motor casting. Pre-2024 manuals give a UNECE R85 net figure and 2024-onward manuals a peak figure, so a range that spans that boundary spans two different measurements — the lookup below shows which one a given year uses.
The rotor changed in 2016, and Zero wrote it down in one word
The community archive states that Zero moved from a surface-magnet rotor to an interior-magnet rotor for 2016, that the interior design produces less heat for a given output and spreads what it does produce more evenly, and that the changeover was not clean: some models kept the older rotor through the model year. That is a substantial technical claim with no citation on the page. It is also correct, and Zero's own manuals prove it in a single word.
Zero never writes “IPM” or “surface magnet”. It writes a Magnet Configuration line, and in 2015 and earlier that line reads radial flux permanent. From 2016 onwards the same line on most models reads radial flux interior permanent. One inserted word, in 62 statements across the index, dates the change precisely — and the 2016 manuals are the interesting ones, because they print both.
What the MY2016 manuals actually say, model by model
| Model | Pack | As the manual words it | Rotor type | Source |
|---|---|---|---|---|
| DS | ZF13.0 | radial flux INTERIOR permanent | interior-magnet (IPM) | OM-SDS-MY16-English-06.pdf, p121 |
| DS | ZF9.8 | radial flux permanent | surface-magnet (SPM) | OM-SDS-MY16-English-06.pdf, p121 |
| DSR | all packs | radial flux INTERIOR permanent | interior-magnet (IPM) | OM-SDS-MY16-English-06.pdf, p123 |
| FX | all packs | radial flux permanent | surface-magnet (SPM) | OM-XMX-MY16-English-04.pdf, p121 |
| FXS | all packs | radial flux INTERIOR permanent | interior-magnet (IPM) | OM-XMX-MY16-English-04.pdf, p123 |
| S | ZF13.0 | radial flux INTERIOR permanent | interior-magnet (IPM) | OM-SDS-MY16-English-06.pdf, p117 |
| S | ZF9.8 | radial flux permanent | surface-magnet (SPM) | OM-SDS-MY16-English-06.pdf, p117 |
| SR | all packs | radial flux INTERIOR permanent | interior-magnet (IPM) | OM-SDS-MY16-English-06.pdf, p119 |
Read down the Rotor column. In the same model year, and in two cases on the same spec page, Zero specifies a surface-magnet rotor for one pack size and an interior-magnet rotor for the other. The pack size is the tell because the smaller pack is the cheaper bike; the older motor was being used up.
The archive was right, in detail
The archived page claims: “2016 models S/DS/SR/DSR/FXS have the IPM design.” and “FX and S/DS models with a 3-brick battery retained the SPM design (presumably to be phased out with inventory).”
The MY2016 manuals give the interior-magnet wording for DS, DSR, FXS, S, SR and the older wording for DS, FX, S, with the split on the S and DS drawn between the ZF13.0 and ZF9.8 packs. That is the archive's claim, including the detail about the smaller-pack bikes, confirmed from the manufacturer's own specification pages rather than from a forum thread. Where a rescued page turns out to be this well informed, the right response is to cite it and give it a source, not to paraphrase it away.
What the motor cannot tell you about itself
Two things a rider reasonably wants are simply not in any manual. There is no published maximum motor speed for any Zero — searching the full text of all 36 in-scope owner manuals for an RPM limit returns nothing at all. And there is no published temperature at which the motor derates, only the behaviour it produces, which the derating section below sets out. The archive fills the first gap with a figure of 6,000 rpm and an argument about winding inductance rather than a measurement; the final-drive section takes that figure apart using Zero's own gearing.
The motor also has to be told where its own rotor is. Both the encoder and the controller hold a calibrated offset angle, and Zero treats that calibration as a serviceable item rather than a factory setting: the owner-manual maintenance schedule lists Drive Motor — commissioning and timing as a periodic check, and the service manuals route it through the dealer Diag4 software with the motorcycle on a stand and the rear wheel spinning under its own power. The FST procedure adds a tolerance that tells you how tight the setting is: if the newly measured offset differs from the stored one by more than five degrees, the manual says do not return the motorcycle to service. A motor that has been unbolted and refitted without that step is not finished, whatever the belt tension says.
Wrong in the community archive: motor mount bolts are not a 12 Nm job
The archive's motor-removal page says: “Disconnect the motor from the bike. On the motor there are 8 M8 bolts holding the motor in place: 4 on the drive side, 4 on the rear side. Those bolts only have about 12Nm of torque on them.”
That is an observation of how one bike's bolts felt coming off, written in a removal procedure where a reader will use it as the reassembly target. Zero's service manuals specify 27–35 Nm on the same fasteners, with thread lubricant, so the archive figure is between 56% and 66% light. Loose motor mounts do not announce themselves; they present later as belt misalignment and accelerated belt wear.
Torque to the table in your own manual for your own model year. The owner-manual figures, and the model year at which Zero split them into different left- and right-hand values, are on the torque reference, which owns the fastener story.
Motor mount torques as Zero's service manuals give them
| Side | Torque | Document | Source |
|---|---|---|---|
| left (drive) side | 27 Nm (20 lb·ft) | S / DS / SR / DSR service manual | SDS_Service_Manual_-8811965-AD.pdf, p62 |
| left (drive) side | 35 Nm (26 lb·ft) | FX / FXS / FXE service manual | XMX_Service_Manual_8811943-AF.pdf, p72 |
| right side | 27 Nm (20 lb·ft) | S / DS / SR / DSR service manual | SDS_Service_Manual_-8811965-AD.pdf, p62 |
| right side | 27 Nm (20 lb·ft) | FX / FXS / FXE service manual | XMX_Service_Manual_8811943-AF.pdf, p72 |
Zero's two service manuals do not agree with each other on the drive side: 27 Nm and 35 Nm for the same four bolts on two platforms. That is not a transcription error on this page — both figures are printed, on the pages named. Use the manual for your own platform and model year, and note that the owner manual and the service manual for the S platform can also differ; the torque reference sets out which is which.
The controller, and the number that really caps MotAmps
The motor controller is the only thing on the motorcycle that decides how much current reaches the motor. It takes direct current from the pack across two terminals, switches it into three alternating phases across three more, and holds the phase current to a ceiling written into its own configuration. When you see a MotAmps trace flatten off at the same value ride after ride, that ceiling is what you are looking at — and Zero publishes it, in amps, on the specification page of every owner manual it has ever printed.
Reading it out of all 36 in-scope owner manuals gives 103 controller lines and 10 distinct ratings between 420 A and 900 A. Grouped by platform, they form a ladder that maps exactly onto the hardware changes riders already know about.
Phase-current ceiling by platform and model year, from Zero's specification pages
| Model years | Models | Motor | Phase current | Controller | Source |
|---|---|---|---|---|---|
| 2015–2016 | DS, S | Z-Force 75-7 | 420 A | Sevcon Gen4 | OM-SDS-MY15-English.pdf, p16 |
| 2015–2016 | FX, FXS | Z-Force 75-5 | 420 A | Sevcon Gen4 | OM-XMX-MY15-English.pdf, p12 |
| 2015–2016 | DSR, SR | Z-Force 75-7 / Z-Force 75-7R | 660 A | Sevcon Gen4 | OM-SDS-MY15-English.pdf, p14 |
| 2017–2023 | DS, S | Z-Force 75-5 / Z-Force 75-7 | 550 A | Sevcon Gen4 | OM-SDS-MY17-English-AH.pdf, p129 |
| 2017–2025 | FX, FXE, FXS | Z-Force 75-5 | 550 A | Sevcon Gen4 | OM-XMX-MY17-English-AE.pdf, p125 |
| 2017–2023 | DSR, SR | Z-Force 75-7R | 775 A | Sevcon Gen4 | OM-SDS-MY17-English-AH.pdf, p133 |
| 2020–2026 | SR, SR/F, SR/S | Z-Force 75-10 | 900 A | Cypher III integrated controller | OM-SRF-MY20.pdf, p150 |
| 2023–2026 | DSR/X | Z-Force 75-10 5T / Z-Force 75-10X | 900 A | Cypher III integrated controller | 23_DSRX_OM_-_English_-_88-09970-AK.pdf, p152 |
| 2024–2026 | DS | Z-Force 75-7 | 600 A | Cypher III integrated controller | 24MY_FST_ADV_OM_-_English-_EU_-_8811908-AH.pdf, p152 |
| 2024–2026 | S | Z-Force 75-7 | 600 A | Cypher III integrated controller | 24_FST_Street_OM_-_English_-_EU_-_8811911-AI.pdf, p154 |
| 2024–2025 | SR | Z-Force 75-10 | 665 A | Cypher III integrated controller | 24_FST_Street_OM_-_English_-_EU_-_8811911-AI.pdf, p162 |
| 2024–2025 | DSR | Z-Force 75-10X | 670 A (firmware-limited) | Cypher III integrated controller | 24MY_FST_ADV_OM_-_English-_EU_-_8811908-AH.pdf, p160 |
| 2024–2025 | DSR | Z-Force 75-10X | 765 A (firmware-limited) | Cypher III integrated controller | 24MY_FST_ADV_OM_-_English-_EU_-_8811908-AH.pdf, p164 |
| 2024–2025 | SR | Z-Force 75-10 | 785 A | Cypher III integrated controller | 24_FST_Street_OM_-_English_-_EU_-_8811911-AI.pdf, p166 |
Model years are the span of manuals in our index that print the figure, not a claim about when the part changed; a missing intervening manual would shorten a span. Page numbers are PDF pages in the file named.
Gen2 is a Sevcon. Gen3 is not, and Zero says so by omission
On the S, DS, SR, DSR, FX, FXS and FXE the controller is a Sevcon. Zero does not advertise that in the specification chapter, but it says it twice elsewhere. The diagnostic trouble code list in 22 manuals contains three codes named after the supplier — 31 Sevcon CAN Error, 33 Sevcon Error Turn Off, 48 Sevcon Startup Disable — and the Motor Controller Replacement procedure in the S-platform service manual is written in two variants, headed Size 4: and Size 6:, which is Sevcon's own size nomenclature for the Gen4 family. The archive's controller table asserts exactly that mapping, uncited.
The archive's uncited Gen2 controller table, tested against Zero's manuals
| Archive years | Archive models | Archive controller | Archive phase current | In Zero’s own manuals |
|---|---|---|---|---|
| 2013-2016 | S/DS/FX/FXS/MMX | Sevcon Gen4 Size 4 | 420A | 7 manual rows, DS, FX, FXS, S (MY2015–2016) |
| 2013-2016 | SR/DSR | Sevcon Gen4 Size 6 | 660A | 3 manual rows, DSR, SR (MY2015–2016) |
| 2017+ | S/DS/FX/FXS/MMX | Sevcon Gen4.5 Size 4 | 550A | 48 manual rows, DS, FX, FXE, FXS, S (MY2017–2025) |
| 2017+ | SR/DSR | Sevcon Gen4.5 Size 6 | 775A | 12 manual rows, DSR, SR (MY2017–2023) |
4 of 4 in-scope rows are corroborated: every phase-current figure the archive gives for MY2015 and later appears in Zero's own specification pages for the models and years it names. What the manuals do NOT corroborate is the Sevcon model naming — no owner manual contains the strings "Gen4", "Gen4.5", "Size 4" or "Size 6", and only the service manual's procedure headings use the size names. Treat the current figures as manufacturer data and the controller part numbers as a community attribution. The archive's XU row is left out: that model was gone before MY2015 and no manual in our index covers it, so we can neither confirm nor contradict it.
The MY2017 step in that ladder is the one worth pausing on, because three independent specification fields move in the same model year. The phase current rises on both variants. The final drive changes belt family and sprocket counts, as the final-drive section below shows. And the archive records, separately, that the motor shaft went from keyed to splined at the same point, which is why a 2016 motor and a 2017 sprocket do not fit each other. We can confirm the splines exist — the FST service manual has you inspect the motor shaft splines for damage — but no manual in our index documents the changeover itself, so the date remains a community claim on a page that has been right about everything else we could test.
On the SR/F, SR/S and DSR/X there is no Sevcon. Not “a different Sevcon”: across every FST manual in the index the string appears zero times, the Sevcon-named fault codes are gone, and the fault list is renumbered into a different vocabulary entirely. Meanwhile the Sevcon codes are still in the FX and FXE manual as late as MY2025. The two architectures ran side by side for years, which is why a single “what controller does a Zero have” answer is always wrong.
From 2024 the ceiling is a firmware setting, and Zero prints both numbers
The clearest evidence that the phase-current ceiling is configuration rather than hardware arrives in the MY2024 manuals. The same motorcycle, with the same motor, is specified twice — once for each licence category it can be sold under — and the two specifications differ in the controller line. Zero even uses the word: firmware-limited.
One motor, two current ceilings, set in firmware by licence class
| Model | Motor | Model years | Ceiling by licence class | Spread | Zero writes “firmware-limited” |
|---|---|---|---|---|---|
| SR | Z-Force 75-10 | MY2024–2025 | 665 A → 785 A | 18% | not in words |
| DSR | Z-Force 75-10X | MY2024–2025 | 670 A → 765 A | 14% | yes |
Both figures are printed on the same specification page, in adjacent columns headed by licence category. A restricted bike and an unrestricted one are the same castings; what differs is the number the controller enforces. Zero uses the word "firmware-limited" on 1 of these rows and simply prints two figures on the rest, which is the same thing said less plainly. Worth knowing before you compare your MotAmps ceiling with someone else’s.
How the controller gets rid of its own heat
CtrlTemp is not measuring air. On the Gen2 platforms the controller is bolted to a separate finned heat sink with thermal compound between the two faces, and the service manual is emphatic about it: a layer of thermal grease must be applied, spread with a small roller, and the manual describes the correct thickness by appearance — white, but with the grey of the metal still showing through. Too little leaves gaps; too much stops the joint closing when the bolts are tightened. Either way the controller runs hotter for the same current, and the only place that shows up is CtrlTemp climbing faster than it used to on a ride you have done a hundred times.
On the FST platform the split disappears. Up to MY2021 the controller sits on a carrier; from MY2022 the service manual's section is titled Motor Controller with Heatsink and the mounting torque changes with it. The five power terminals stay five throughout, on both architectures — two for the pack and three for the motor phases — which is why the FST power-pack procedure, which comes out past the controller, calls for five new controller cable seals and five new O-rings.
Wrong in the community archive: the controller terminal torque, twice over
Two archived pages give a figure for the bolts that carry full powertrain current into and out of the controller, and they disagree with each other by more than a factor of two. The removal page calls them “torqued low-spec at 12ft-lbs”; the installation page says 7 Nm per Sevcon and then, in the same sentence, also recommends 12 ft-lb.
Zero specifies 11–12 Nm for those bolts (XMX_Service_Manual_8811943-AF.pdf, p72 and SDS_Service_Manual_-8811965-AD.pdf, p62). 12 lb·ft is 16.3 Nm, which is 36% over the highest OEM figure; 7 Nm is 36% under the lowest. The arithmetic points at the cause: the manual figure is 12 Nm, and the archive page prints 12 ft-lb. A unit was dropped somewhere and the number survived.
The archive's own connections page has it right, and agrees with the factory: it gives the Sevcon specification as 11 Nm ±2 Nm for the M8 terminals, in the order “Main terminals are, in order from front to rear: M1, B-, M2, B+, M3”. Use 11–12 Nm from the service manual for your platform, with a wrench you have checked, and understand that these are high-voltage joints: nothing here authorises the work, and the de-energise and lockout sequence comes first.
Powertrain electrical joints, from Zero's service manuals
| Joint | Torque | Platform | Source |
|---|---|---|---|
| Controller to carrier (FST, 22MY onwards) | 5.5 Nm (4 lb·ft) | FST Street | SRS_Service_Manual_8811934-AI.pdf, p134 |
| Controller to carrier (FST, 22MY onwards) | 5.5 Nm (4 lb·ft) | FST Street | S_SR-SRF_Service_Manual_8811935-AJ.pdf, p136 |
| Controller heat-sink bolts | 11 Nm (8 lb·ft) | XMX | XMX_Service_Manual_8811943-AF.pdf, p73 |
| Motor phase cables (M1/M2/M3) onto the controller | 11 Nm (8 lb·ft) | XMX | XMX_Service_Manual_8811943-AF.pdf, p72 |
| Controller cable bolts (reassembly) | 12 Nm (9 lb·ft) | SDS | SDS_Service_Manual_-8811965-AD.pdf, p65 |
| Motor phase cables onto the controller | 12 Nm (9 lb·ft) | SDS | SDS_Service_Manual_-8811965-AD.pdf, p62 |
| Controller to frame, four bolts | 26 Nm (19 lb·ft) | SDS | SDS_Service_Manual_-8811965-AD.pdf, p65 |
These are service-manual figures for the joints between pack, controller and motor. They are not in the owner-manual Component Fasteners table and are not owner-serviceable; they are reproduced here because the community archive publishes contradictory numbers for the same joints and a reader who has already read those needs the real ones to recognise them by.
Look up your own machine
The answer to “what is in mine” depends on the model, the model year and, from MY2024, the licence category the bike was sold under. Rather than print 117 rows, this reads the same generated index the tables above use.
- Motor
- Z-Force 75-10
- Rotor
- interior permanent magnet
- Controller
- Cypher III integrated controller
- Phase current
- 900 A
- Peak power
- 83 kW (≈111 hp)
- Peak torque
- 190 Nm (≈140 lb·ft)
- 30-minute rated power
- 35 kW (≈47 hp)
- Top speed (max)
- 200 km/h (≈124 mph)
- Top speed (sustained)
- 170 km/h (≈106 mph)
- Final drive
- 20T → 90T (4.50:1)
- Belt
- Gates Poly Chain HTD Carbon
- Motor speed at max top speed
- ≈ 7,581 rpm (derived, not published)
Read from 26_FST_Street-_EU_-_English-_8812119-AC.pdf, p162 (FST Street platform). A dash means the field is not printed on that manual's spec page — several pre-2024 pages cover two battery sizes at once and give two values for one row, and those are left out rather than guessed at.
Regenerative Braking
Regenerative braking is one of the key efficiency advantages of electric vehicles. When you release the throttle or apply brakes, the motor becomes a generator:
Energy flows from battery to motor for propulsion
How It Works
1. You release the throttle or brake
2. Controller reverses motor field to create resistance
3. Wheel momentum spins motor, generating electricity
4. BMS directs recovered energy to battery cells
5. You see negative amps in logs during this process
Typical Efficiency
Real-world regen recovery is typically 60-70% efficient. Energy lost to:
- • Conversion losses in motor/controller
- • Internal resistance in battery
- • Heat dissipation
Temperature Management
Heat is the enemy of battery life and component longevity. Your logs track multiple temperature points to ensure everything stays within safe limits:
| Field | Location | Normal | Warning | Action |
|---|---|---|---|---|
| MotTemp | IPM Motor | <80°C | >100°C | Power derating |
| CtrlTemp | Motor controller | <65°C | >80°C | Power derating |
| PT / PackTemp | Battery Pack | up to 48°C | >55°C | Charge limit |
| BT | BMS Board | <50°C | >60°C | Monitoring |
| AmbTemp | Ambient Air | Any | — | Reference only |
Where these numbers come from. The pack row is the product's own rubric: the diagnosis engine treats battery temperature up to 48 °C as normal (“normal in summer or during fast charging”) and only raises a finding above 55 °C. The motor and controller rows are community-derived: they come from one 2016 SR read over its CAN bus, and no manual publishes a numeric temperature at which any Zero derates. Zero does publish numeric motor and pack gauge bands on the FST platform, which sit well above the figures in this table — that correction, and what it means for reading MotTemp, is in What derates, and how the log shows it below. What the manuals publish instead of a threshold is a behaviour: a Temperature Warning telltale that goes solid once power is being reduced. Treat the °C figures in this table as orientation, and the trend across rides as the real signal.
CtrlTemp is the motor-controller temperature. On Gen1/Gen2 that controller is the Sevcon Gen4 — the FX, FXS and FXE manual fault tables each list three SEVCON codes, and Gen2 logs are full of Sevcon Turned On / Sevcon CAN Link Up events. The FST manual tables list none, and the native Gen3 files in our corpus contain the string “Sevcon” zero times.
Thermal Limiting
When components get too hot, the bike reduces available power ("derating") to prevent damage. If you notice reduced performance after spirited riding, check your logs — high temps are likely the cause.
What derates, and how the log shows it
“Derating” on a Zero is not a fault and not a single mechanism. It is a thermal strategy that reduces available power so that a passively cooled powertrain can keep running, and Zero describes it in the same words in every manual from MY2014 to MY2026: the powertrain cannot be operated indefinitely at high power and high rpm without reaching its thermal limitations, so the motorcycle reduces speed and power until it reaches a state it can sustain. The FST manuals add, pointedly, that the indicator coming on does not mean anything is malfunctioning — it means the strategy is working.
What the manuals do not give is a threshold. There is no temperature in any of them at which derating begins. What they give instead is something better and almost universally overlooked: a second top speed. Every Zero specification page prints an estimated top speed (max) and an estimated top speed (sustained), and the gap between them is the manufacturer's own statement of how much the thermal strategy takes away. It appears on 59 of our specification rows, across 7 models.
Zero's own numbers for how much derating costs, one row per distinct pair of figures
| Model | Model year | Motor | Top speed (max) | Top speed (sustained) | Difference |
|---|---|---|---|---|---|
| DS (Full Power) | MY2026 | Z-Force 75-7 | 167 km/h (≈104 mph) | 120 km/h (≈75 mph) | −47 km/h (−28.1%) |
| DS (A1) | MY2026 | Z-Force 75-7 | 139 km/h (≈86 mph) | 105 km/h (≈65 mph) | −34 km/h (−24.5%) |
| S (Full Power) | MY2026 | Z-Force 75-7 | 167 km/h (≈104 mph) | 130 km/h (≈81 mph) | −37 km/h (−22.2%) |
| S (A1) | MY2026 | Z-Force 75-7 | 139 km/h (≈86 mph) | 110 km/h (≈68 mph) | −29 km/h (−20.9%) |
| S | MY2021 | Z-Force 75-5 | 158 km/h (≈98 mph) | 129 km/h (≈80 mph) | −29 km/h (−18.4%) |
| DSR (A2/A3) | MY2025 | Z-Force 75-10X | 150 km/h (≈93 mph) | 125 km/h (≈78 mph) | −25 km/h (−16.7%) |
| SR/F (A3) | MY2026 | Z-Force 75-10 | 200 km/h (≈124 mph) | 170 km/h (≈106 mph) | −30 km/h (−15%) |
| SR/S (A3) | MY2025 | Z-Force 75-10 | 200 km/h (≈124 mph) | 170 km/h (≈106 mph) | −30 km/h (−15%) |
| DSR | MY2019 | Z-Force 75-7R | 164 km/h (≈102 mph) | 145 km/h (≈90 mph) | −19 km/h (−11.6%) |
| SR/F | MY2023 | Z-Force 75-10 | 200 km/h (≈124 mph) | 177 km/h (≈110 mph) | −23 km/h (−11.5%) |
| SR/S | MY2023 | Z-Force 75-10 | 200 km/h (≈124 mph) | 177 km/h (≈110 mph) | −23 km/h (−11.5%) |
| DSR | MY2020 | Z-Force 75-7R | 163 km/h (≈101 mph) | 145 km/h (≈90 mph) | −18 km/h (−11%) |
| DSR/X (A3) | MY2026 | Z-Force 75-10X | 180 km/h (≈112 mph) | 161 km/h (≈100 mph) | −19 km/h (−10.6%) |
| SR (A2/A3) | MY2025 | Z-Force 75-10 | 150 km/h (≈93 mph) | 135 km/h (≈84 mph) | −15 km/h (−10%) |
| SR | MY2019 | Z-Force 75-7R | 164 km/h (≈102 mph) | 153 km/h (≈95 mph) | −11 km/h (−6.7%) |
| SR | MY2020 | Z-Force 75-7R | 163 km/h (≈101 mph) | 153 km/h (≈95 mph) | −10 km/h (−6.1%) |
| DSR (Full Power) | MY2025 | Z-Force 75-10X | 167 km/h (≈104 mph) | 161 km/h (≈100 mph) | −6 km/h (−3.6%) |
The widest gap in the whole index is the DS (Full Power) at MY2024: 167 km/h maximum against 120 km/h sustained, a drop of 28.1%. 6 rows print the SAME figure twice, which is Zero saying that machine has no sustained-speed penalty at all. Neither number is a temperature, and neither is a promise about your ride.
Retracted: this page used to say Zero publishes no numeric motor temperature
Retracted: “Zero's manuals publish no numeric temperature limit for any model”
That sentence appeared above this section on this page, and it is wrong as stated. Every FST owner manual — 13 of them, MY2020–2026 — prints the numeric colour bands of the dash motor temperature gauge, and all of them give identical figures.
What remains true, and is the reason the claim was made, is narrower: no manual publishes a derate threshold. The gauge band is a display range, not the point at which power is cut. The corrected version of the claim is that Zero publishes numeric motor and pack temperature bands on the FST platform and no numeric threshold for any platform.
The dash motor-temperature gauge, from OM-SRF-MY20.pdf, p84
| Gauge colour | Motor temperature | Same in °F |
|---|---|---|
| White | 20 °C to 118 °C | 68 °F to 244 °F |
| Red | 118 °C to 150 °C | 244 °F to 302 °F |
Zero notes on the same page that these gauges have no numeric display, which is exactly why the bands are worth knowing: the dash tells you which band you are in and the log tells you the number. The pack gauge is on the same page and is covered by the thermal-limits reference.
Those bands change how the archive's motor table reads. It puts “normal” at up to 100 °C. Zero's own dash still shows white — its unremarkable colour — up to 118 °C, which is 18 °C higher, and does not go red until 118 °C. A rider using the archive table would conclude their motor was in trouble at a temperature Zero considers ordinary.
Wrong in the community archive: the motor and controller Stage tables are one bike's CAN bus
The archive prints three temperature tables in Normal / Stage 1 / Stage 2 columns. Under the controller one it says the figures were “Pulled from a 2016 Zero SR... through CAN bus MBB other years, firmware revisions, and dash temperature lights may be different.” The motor table immediately above it carries no caveat at all — and has exactly the same origin.
No motor or controller temperature threshold appears anywhere in the 35+ manuals indexed here. The figures are not corroborated, not contradicted, and not specifications: they are one owner's observation of one 2016 SR over CAN, which is genuinely useful for reading your own trace and useless as a limit.
Use them as orientation for the shape of a normal trace, not as a pass mark. If your dash raises a temperature warning, the threshold that fired is whatever your firmware uses.
The archive's Stage tables, reproduced with their real provenance
| Component | Normal (°C) | Stage 1 (°C) | Stage 2 (°C) | Provenance on the archive page |
|---|---|---|---|---|
| Motor | ... 100 | 100 ... 145 | 145 ... | no caveat printed on the page |
| Controller | ... 70 | 70 ... 75 | 75 ... | one 2016 SR, read over CAN |
Reproduced from the rescued archive, not from a manual. Nothing on this row is a Zero specification. It is here so that a rider who has already seen these tables can recognise them and weigh them correctly.
Two fault vocabularies for the same two components
Zero does name the stages — it just never numbers the temperatures. The Gen1 and Gen2 diagnostic trouble code list carries four powertrain-thermal codes, two for the motor and two for the controller, each split into Stage 1 and Stage 2. That is where the archive's column headings come from: the vocabulary is Zero's, the numbers are the community's. On the FST platform the list is renumbered and the stages collapse into single codes whose description is the action rather than the severity.
Powertrain fault codes in both vocabularies, with the manual that prints them
| Vocabulary | Code | As the manual names it | Model years | Source |
|---|---|---|---|---|
| Gen1 / Gen2 DTC | 2 | Motor Temperature Warning Stage 1 | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 3 | Motor Temperature Warning Stage 2 | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 4 | Controller Temperature Warning Stage 1 | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 5 | Controller Temperature Warning Stage 2 | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 31 | Sevcon CAN Error | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 33 | Sevcon Error Turn Off | MY2015–2025 | OM-SDS-MY15-English.pdf, p110 |
| Gen1 / Gen2 DTC | 48 | Sevcon Startup Disable | MY2015–2025 | OM-SDS-MY15-English.pdf, p111 |
| Gen3 error code | 9 | Controller Fault — Motor Controller Fault. | MY2020–2026 | OM-SRF-MY20.pdf, p144 |
| Gen3 error code | 41 | Motor High Temperature — Performance will be reduced. | MY2020–2026 | OM-SRS-MY20.pdf, p151 |
| Gen3 error code | 57 | Controller High Temperature — Performance will be reduced. | MY2020–2026 | OM-SRS-MY20.pdf, p152 |
The FST rows say "Performance will be reduced" in Zero’s own words, which is the closest any manual comes to defining derating as an event you can be told about. Full code tables, and what to do about each, are on the error catalogue.
The final drive, and the speed nobody measures
There is no gearbox. Every Zero in this reference is specified as Clutchless Direct Drive: the motor shaft carries a toothed pulley, a single toothed belt runs back to a much larger sprocket on the rear wheel, and that one reduction is the entire transmission. It has two consequences for the log. Motor speed and wheel speed are locked in a fixed ratio, so MotRPM is a proxy for road speed with no gear to guess at. And the belt is the only mechanical component between the motor's torque and the road, which is why belt tension appears in the maintenance schedule at the same interval as safety items.
Every belt Zero names in a specification page, MY2015 onwards
| Belt as Zero names it | Models | Model years | Sprocket counts | Width |
|---|---|---|---|---|
| Gates Poly Chain GT Carbon | DSR, FX, FXS, S, SR | MY2015–2018 | 130T/28T, 130T/30T, 132T/25T, 132T/28T, 132T/30T, 90T/20T | not printed |
| Gates Poly Chain HTD Carbon | DSR, FX, FXE, FXS, S, SR, SR/F, SR/S | MY2017–2026 | 90T/18T, 90T/20T | not printed |
| Gates Carbon Drive Moto X9 | DS, DSR, DSR/X | MY2023–2026 | not printed | 25 mm |
The HTD belt first appears at MY2017, the same model year the sprocket counts change to 90T/20T. A GT line survives in the MY2018 S-platform manual alongside the HTD one, on a page that already gives the new sprocket counts — an un-updated row rather than a second belt, which is why the two spans overlap here instead of meeting. The DSR/X is on a different belt again, and its manual is the only one that prints a width.
That MY2017 row is the same model year the controller current rose and, per the archive, the motor shaft went splined. Three specification fields and one community claim all point at a single drivetrain revision rather than three coincidences — which is a useful thing to know before assuming a part from a 2016 bike fits a 2017 one. Belt tension, alignment and wear are their own subject and have their own page: the drive belt reference covers the tension bands by model year, including the ones our own spec data used to get wrong.
What the gearing says about motor speed
No manual gives a maximum motor speed. But a fixed reduction, a sprocket count and a tyre size are enough to work it out from the top speed Zero does publish, and doing that across 70 model years is the only way we have of testing the archive's 6,000 rpm ceiling.
Motor speed implied by Zero's own gearing at Zero's own maximum top speed
| Model year | Sprockets | Reduction | Top speed (max) | Implied motor speed |
|---|---|---|---|---|
| S MY2016 | 28T → 130T | 4.64:1 | 153 km/h (≈95 mph) | 6,003 rpm |
| S MY2019 | 20T → 90T | 4.50:1 | 153 km/h (≈95 mph) | 5,818 rpm |
| SR MY2019 | 20T → 90T | 4.50:1 | 164 km/h (≈102 mph) | 6,236 rpm |
| DS MY2019 | 20T → 90T | 4.50:1 | 158 km/h (≈98 mph) | 5,896 rpm |
| DSR MY2019 | 20T → 90T | 4.50:1 | 158 km/h (≈98 mph) | 5,896 rpm |
| FX MY2016 | 25T → 132T | 5.28:1 | 137 km/h (≈85 mph) | 5,911 rpm |
| FX MY2019 | 18T → 90T | 5.00:1 | 137 km/h (≈85 mph) | 5,598 rpm |
| SR/F MY2026 | 20T → 90T | 4.50:1 | 200 km/h (≈124 mph) | 7,581 rpm |
| SR/S MY2025 | 20T → 90T | 4.50:1 | 200 km/h (≈124 mph) | 7,581 rpm |
| DSR/X MY2025 | 22T → 90T | 4.09:1 | 180 km/h (≈112 mph) | 6,144 rpm |
Derived, not published: rear tyre circumference divided by the reduction ratio, then the published maximum top speed divided by that. The circumference is the unloaded figure, so a real rolling circumference is a couple of per cent smaller and the true motor speed correspondingly higher — these are floors.
Across 31 Gen2 model years the answer lands between 5,187 and 6,330 rpm, which brackets the archive's figure closely enough that it is very probably a real number for the machine it was written about. The SR/F and SR/S do not fit it: their gearing and their 200 km/h (≈124 mph) maximum imply about 7,581 rpm, roughly 26% past it. So the ceiling is not wrong so much as dated: it describes the Sevcon-era motor, and the archive page it sits on was last edited before the SR/F reached customers. Repeating it as a fact about a modern Zero is the error, not the number itself.
Retracted, our own: the speed constants this app derives km/h from do not match Zero's gearing
No Zero log records road speed, so every speed you see in this application is MotRPM multiplied by a per-model constant. The gearing above fixes what that constant has to be, and 5 of the 7 constants in our parser are more than a tenth too large. The worst is the S: we use 0.0345 km/h per rpm where Zero's 4.50:1 reduction and its own rear tyre give 0.0263, an overstatement of 31.2%.
The check that settles it is what rear wheel each constant would need in order to be right: 0.0345 km/h per rpm at that reduction requires a rear wheel 824 mm in diameter. The bike has one of 628 mm. No Zero has ever had a wheel that big, so this is not a tyre-choice tolerance.
Until we have re-derived them against real MotRPM from the log corpus, read the speed trace on a chart as a shape and not as a number, and take distance from the odometer or the ride session instead. Only the DS and DSR constant sits within ten per cent of its own gearing.
This app's derived-speed constants against Zero's published gearing
| Model year | App constant | Zero’s gearing | Overstated | Real wheel Ø | Ø it would need |
|---|---|---|---|---|---|
| S MY2019 | 0.0345 | 0.0263 | +31.2% | 628 mm | 824 mm |
| SR MY2019 | 0.0345 | 0.0263 | +31.2% | 628 mm | 824 mm |
| FX MY2019 | 0.0314 | 0.02447 | +28.3% | 649 mm | 833 mm |
| SR/F MY2026 | 0.032 | 0.02638 | +21.3% | 630 mm | 764 mm |
| SR/S MY2025 | 0.032 | 0.02638 | +21.3% | 630 mm | 764 mm |
| DS MY2019 | 0.028 | 0.0268 | +4.5% | 640 mm | 668 mm |
| DSR MY2019 | 0.028 | 0.0268 | +4.5% | 640 mm | 668 mm |
Read at build time from the constants in backend/app/parser.py, so this comparison cannot go stale without the page changing with it. The manual column is the arithmetic result of Zero’s sprocket counts and rear tyre size for the model year named.
Motor alignment is not two steps
The motor is not simply bolted to the frame. Its rear face carries jack screws that set its position relative to the swingarm pivot, and that position is what keeps the belt tracking straight. The archive documents the adjustment in two lines — loosen four screws, turn the silver nut — and both lines are true. They are also nowhere near the whole job.
Incomplete in the community archive: the motor alignment procedure
Zero's own sequence, in the FX/FXS/FXE service manual, has the motor bolts come apart and go back in a defined order with thread lubricant on the threads and different torques per side; the jack screw is expanded only far enough to take up the clearance between motor and frame; and the job is not finished until the belt has been re-tensioned and the motor re-commissioned with Zero's programming tools, which the same manual says must always be done before operation. An alignment that stops at the jack screw leaves a motor whose rotor offset the controller no longer knows, and that is a dealer-tooling step, not an optional one.
Typical Efficiency by Model
These figures are not community folklore — they are computed from Zero's own numbers. Every row is nominal pack kWh × 1000 ÷ rated range km, taken straight from the model-year spec sheets in the owner manuals. Zero's “city” range is the EPA UDDS cycle; “highway” is its sustained high-speed figure. Where a model spans several manual years the spread is shown.
| Model | Manual years used | City (Wh/km) | Highway (Wh/km) |
|---|---|---|---|
| Zero S | 2014–2016, 2024–2026 | 44–51 | 73–89 |
| Zero SR | 2014–2016, 2024–2025 | 44–54 | 73–89 |
| Zero DS | 2014–2016, 2024–2026 | 48–54 | 80–102 |
| Zero DSR | 2016, 2024–2025 | 48–55 | 84–101 |
| Zero SR/F | 2024–2026 | 53 | 80 |
| Zero SR/S | 2020, 2024–2025 | 49–55 | 81–95 |
| Zero DSR/X | 2023–2026 | 52 | 88 |
| Zero FX | 2014–2016, 2024–2025 | 38–45 | 61–104 |
| Zero FXS | 2016 | 39 | 95 |
| Zero FXE | 2024–2025 | 37 | 59–66 |
| Zero LS1 | 2026 | 32 | — |
| Zero XE | 2026 | 43 (combined) | — |
| Zero XB | 2026 | 32 (combined) | — |
Read the table as a floor, not a target. Rated ranges are measured under favourable conditions, so a real ride almost always costs more per kilometre — and cold weather alone can add roughly 30 %. Across every model Zero documents, the derived city figure sits between 32 and 55 Wh/km and the highway figure between 59 and 104 Wh/km. If your own number lands in those bands, nothing is wrong with your motorcycle.
Only some model years publish separate city and highway ranges; the rest publish a single combined figure, which is why some rows cover fewer years than the model ran. The DS and DSR are the thirstiest of the legacy street bikes on the highway (up to ~102 Wh/km), and the SR/S is not measurably more efficient than the SR/F despite the fairing — on the 2024–2025 sheets it is a whisker worse.
Key Riding Log Fields
These are the Gen1/Gen2 MBB field names — the S, SR, DS, DSR, FX, FXS and FXE. They also survive on the 538XX firmware variant, which decodes pack voltage, battery current, SOC, RPM, temperatures and a real odometer. Read the caveat under the table before you go looking for them in a Gen3 file.
| Field | Meaning | Insight |
|---|---|---|
| BattAmps | Battery current | Overall power flow (+out, -in) |
| MotAmps | Motor phase current | Motor torque demand |
| MotRPM | Motor speed | Proportional to wheel speed |
| Odo | Odometer | Total distance traveled |
| PackSOC | Battery % | Range indicator |
| Vpack | Pack voltage | Sags under load, recovers at rest |
On a Gen3 / FST bike, four of these six fields do not exist
The SR/F, SR/S and DSR/X write a binary ring buffer, and their MBB telemetry record has no motor RPM, no motor current, no odometer and no road speed — not “those bytes read zero”, there is no field for them. What the MBB record does carry is the bike state, the temperatures and the discharge and charge power limits. The record also holds a pack voltage and a battery current that no shipped decoder currently reads, so in practice the BMS log is the electrical source on those bikes: SOC, pack voltage, current and cell voltages all come from it. Upload the MBB and BMS files together and the two are merged by timestamp.
One field is derived everywhere, in every generation: no Zero log of any generation records road speed. Where you see a speed it was computed as motor RPM × a per-model constant (0.0314 on the FX family, 0.0345 on S/SR, 0.032 on SR/F and SR/S, 0.028 on DS/DSR) — good enough for a chart, not a measurement, and five of those seven constants do not match Zero's own gearing. Likewise, throttle position is never logged on any generation.
Full field-by-field breakdown in the Gen3 log format reference and the generation comparison.
Sources:
- Zero Motorcycles — owner manuals (official downloads)
- Zero Motorcycles — support and service
- Wikipedia: Regenerative braking
- Wikipedia: Interior permanent magnet synchronous motor
- Gates — Poly Chain GT Carbon belts
- Gates Carbon Drive — Moto belt systems
- BorgWarner (Sevcon) — Gen4 motor controllers
- Unofficial Zero Manual, Z-Force Motor (Wayback, 2020 snapshot)
- Unofficial Zero Manual, Motor Controller Versions (Wayback, 2020 snapshot)
- Unofficial Zero Manual, Temperature Limits (Wayback, 2019 snapshot)
Where the drivetrain figures come from. Every motor, controller and final-drive number in the four sections added to this page was read out of Zero's own manuals: 117 model-year specification rows from 31 owner manuals covering MY2015 to MY2026, plus the service manuals for the powertrain joint torques and the commissioning sequence. The extraction is backend/scripts/gen_drivetrain_specs.py, which emits a generated TypeScript module; the prose interpolates the same data the tables render, so a figure in a sentence cannot drift from the table beside it. Re-run it and the page follows. 49 specification blocks were deliberately skipped because one page covered two battery sizes and would have needed a guess, and 1 figure was rejected for failing an imperial-to-metric consistency check. Last extracted 2026-08-09.
Every page number here was checked against the PDF. Zero prints each figure twice, “69 hp (52 kW)”; the metric half is published exactly as printed, so the number in the table is the number on the page. The bracketed imperial figure is converted by us and marked ≈, because Zero rounds its own imperial half independently and the two can differ by one unit. The page reference itself does not come from the text index — a search index entry covers four or five pages of a specifications appendix in which every model looks alike — but from re-extracting candidate pages from the PDF and finding the one that actually carries the figure. All 672 citations on this page resolved that way; the extractor publishes a page_verified flag, and a figure whose page could not be confirmed would be marked rather than presented as a reference.
The community archive is a source, not an authority. The rescued zeromanual.com pages on the Z-Force motor, the motor controller and the temperature limits supplied the questions this page answers, and several of their claims turned out to be right in detail and unsourced — the interior-magnet rollout and the phase-current ladder both survive contact with the manuals. Where an archived figure is wrong it is reproduced above with the measurement that settled it, rather than quietly replaced, because a rider who has already read the wrong number needs to recognise it. Archive links go to the Internet Archive because zeromanual.com stopped responding in March 2026.
Temperature limits and behavior may vary by model year and firmware version. Consult your Zero Owner's Manual for your specific bike.