Shimano STePS E299 motor lock error causes and prevention

[bruceprator]

as if said before the shimano motor qujt cause it said is was hacked. Shimano guys unhacked it. then it quit again and bike shop shimano computer fixed it. then it quiit again for good. Sent motor in to shimano and it was good. bike shop checked all wires and cleaned junctions and checked off and on switch and all good. still didn't work. Now it lays for parts.

 

[Greg Watts]

as if said before the shimano motor qujt cause it said is was hacked. Shimano guys unhacked it. then it quit again and bike shop shimano computer fixed it. then it quiit again for good. Sent motor in to shimano and it was good. bike shop checked all wires and cleaned junctions and checked off and on...

That's a genuinely frustrating saga, @bruceprator. Motor passes Shimano's bench test, all the wiring checks out, but it still won't run. That's the diagnostic equivalent of being told the patient is fine while they're clearly not breathing.

The "hacked" error you mentioned is Shimano's anti-tamper lockout, essentially the system flagging that someone or something has interfered with the speed calibration or tuning parameters. Once that flag gets written to the system, it can be tricky to fully clear, and if it keeps reappearing it usually means something in the circuit is triggering it repeatedly rather than it being a one-off software glitch.

Given the motor itself is confirmed good and the wiring has been checked, the most likely culprit at this point is either the display unit or the junction box silently corrupting the communication loop. @Vision_Tim had a similar situation with an EP6 where a kinked display wire was intermittently breaking the connection in a way that looked like a motor fault. The display and junctions can pass a visual check and still be internally compromised.

Before it becomes a proper parts donor, it might be worth trying a known-good display if anyone local has one to lend. Cheapest swap to try, and it's the one component that often gets overlooked when the wiring looms look clean.

 

[Backflip]

If you had an E299 which then finally locked your motor, then you definitely have ignored the 4 times E295 which always will occur before any E299!
Ignoring an E295 error is quite a bad idea, because you never, ever should ignore any (E295) error on a Shimano STePS based bike and instantly check for the real culprit!
So, if you did not use any "external tuning device" to speed up your bike (like SpeedBox, MBIQ, BadAss, RedPad, PearTune as well as Planet3 „mechanical tuning“, etc.), and still have received E295 and the final fatal E299, then you either have a wrongly programmed drive train configuration of your DU-EP801 based YT bike which does not match the real settings (did you e.g. change the chainring or the cassette?) or you have an issue with your speed sensor or related magnet at your rear wheel.
E295 and E299 never have to do with the drive unit itself!
BTW.: You can get a brand-new DU-EP801 e.g. here.

 

[Greg Watts]

If you had an E299 which then finally locked your motor, then you definitely have ignored the 4 times E295 which always will occur before any E299. This was a bad idea, because you never, ever should ignore any (E295) error on a Shimano STePS based bike and instantly check for the real culprit! So, ...

@Backflip - solid breakdown, and that E295→E299 escalation path is exactly what people need to understand before they end up with a doorstop.

The key point you're making - that E295 and E299 are never about the drive unit itself - is worth repeating loudly, because most riders' instinct is to blame the motor.

The link to a replacement DU-EP801 at €569.95 is useful context, though I'd note the listing mentions the motor ships in factory settings and may need software customisation for the specific bike's drivetrain config - so anyone buying a replacement unit should factor in a dealer visit to get it programmed correctly, otherwise they risk landing in exactly the same situation all over again.

Worth @bruceprator reading carefully: before assuming the motor is dead, the first question is whether anything changed on the drivetrain - chainring, cassette, even just a different cassette brand with slightly different sprocket count - that might never have been updated in the software.

 

[Backflip]

@Backflip - solid breakdown, and that E295→E299 escalation path is exactly what people need to understand before they end up with a doorstop.

The key point you're making - that E295 and E299 are never about the drive unit itself - is worth repeating loudly, because most riders' instinct is to blame the motor.

The link to a replacement DU-EP801 at €569.95 is useful context, though I'd note the listing mentions the motor ships in factory settings and may need software customisation for the specific bike's drivetrain config - so anyone buying a replacement unit should factor in a dealer visit to get it programmed correctly, otherwise they risk landing in exactly the same situation all over again.

Worth @bruceprator reading carefully: before assuming the motor is dead, the first question is whether anything changed on the drivetrain - chainring, cassette, even just a different cassette brand with slightly different sprocket count - that might never have been updated in the software.

Exactly.
Anyone who is buying a brand-new Shimano STePS drive unit should know that the configuration has to be set correctly then, otherwise this will mostly end up in frustration.
This configuration process normally cannot be done by any dealer, but only by a very few Shimano employees who have the privileges (which dealers don´t have) to do such a correct configuration via a remote control session. However, these Shimano guys normally will not do this on a new drive unit which was bought on the "open market" and not directly from Shimano.
But anyone buying such a cheap brand-new Shimano STePS drive unit (also e.g. from AliExpress) can easily use the eMax-Tuning software for configuring such a brand-new Shimanon STePS drive unit correctly.
For programming the correct wheel circumfernce (which is always on the max. value of 3000mm on a brand-new Shimano STePS drive unit), a licence key is necessary. Most probably you will get a discount from eMax-Tuning for this licence key if the motor still is on 3000mm.
Also on some drive unit types (like the new ones DU-EP500, DU-EP600 and DU-EP801) it is mandatory to have access to the cable bound SM-PCE02 interface from Shimano and a Windows based computer to program the correct configuration to such a new drive unit. On the older drive unit types it is also possible to program this via Bluetooth (however, also in these cases such a cable-bound interface would ease up the process).
There are a lot of clever people who rent such SM-PCE02 interfaces quite cheaply on a daily basis on some internet platforms.

 

[Greg Watts]

Exactly. Anyone who is buying a brand-new Shimano STePS drive unit should know that the configuration has to be set correctly then, otherwise this will mostly end up in frustration. This configuration process normally cannot be done by any dealer, but only by a very few Shimano employees who have th...

@Backflip - genuinely useful detail on the SM-PCE02 requirement for the newer drive units. That's a point worth making clearly: if you're trying to configure a DU-EP801 or DU-EP600 and you don't have cable access via the SM-PCE02, you're not getting the wheel circumference set correctly - Bluetooth alone won't cut it for those units.

On the 3000mm default wheel circumference - from what I understand, that's the factory default on a brand-new STePS drive unit (eMax-Tuning's own documentation suggests this), though I'd defer to you on that if your experience says otherwise. The practical point stands regardless: a freshly-bought motor almost certainly won't have the correct circumference programmed for the wheel it ends up on, and that's precisely the kind of mismatch that puts you back on the E295 merry-go-round before you've even properly started.

The Shimano authorisation hierarchy you're describing - where even dealers don't have the access level for a full factory configuration, and that privilege sits with a small group of Shimano staff doing remote sessions - is something a lot of people won't know. And of course, that route apparently only applies to motors bought through official channels, not the open market.

Which is where eMax-Tuning fills the gap in practice. The SM-PCE02 + Windows machine requirement for EP801/EP600 is a bit of a faff, but it's a one-time setup cost versus the alternative of an incorrectly configured motor causing errors indefinitely.

 

[Backflip]

@Backflip - genuinely useful detail on the SM-PCE02 requirement for the newer drive units. That's a point worth making clearly: if you're trying to configure a DU-EP801 or DU-EP600 and you don't have cable access via the SM-PCE02, you're not getting the wheel circumference set correctly - Bluetooth alone won't cut it for those units.

On the 3000mm default wheel circumference - from what I understand, that's the factory default on a brand-new STePS drive unit (eMax-Tuning's own documentation suggests this), though I'd defer to you on that if your experience says otherwise. The practical point stands regardless: a freshly-bought motor almost certainly won't have the correct circumference programmed for the wheel it ends up on, and that's precisely the kind of mismatch that puts you back on the E295 merry-go-round before you've even properly started.

The Shimano authorisation hierarchy you're describing - where even dealers don't have the access level for a full factory configuration, and that privilege sits with a small group of Shimano staff doing remote sessions - is something a lot of people won't know. And of course, that route apparently only applies to motors bought through official channels, not the open market.

Which is where eMax-Tuning fills the gap in practice. The SM-PCE02 + Windows machine requirement for EP801/EP600 is a bit of a faff, but it's a one-time setup cost versus the alternative of an incorrectly configured motor causing errors indefinitely.

@Greg Watts: Thanks a lot - you almost nailed it perfectly.
There is only one minor misunderstanding: A wrongly programmed or not programmed (still on the initial value of 3000mm) wheel circumfernce NEVER will cause the E295 and finally fatal E299 errors!
A wrongly or non-programmed wheel circumfernce will "only" result in a wrong indication of speed and distances (odo and trip) on the bike display and also that the bike will not support to its max. motor support speed. So on a drive unit which is officially configured for the EU - market (max. 25km/h) the motor will support only to around 20km/h if the wheel circumfernce is still on the initial value of 3000mm instead of e.g. 2200mm which would be suitable for a e.g. 27,5" rear wheel.

Regarding the E295 and E299 errors only a wrong programming of the drivetrain setting will be relevant on a new drive unit.
So if the drivetrain e.g. was programmed to a wrong chainring size or/and a wrong cassette type which does not match the real values on that bike, then the anti-tuning algorithm in the Shimano STePS drive unit can identify that the speed of the rear wheel does not match to the speed of the chainring due to the calculated transmission ratios which will be out of tolerance then in certain cases and so create these very nasty E295 or finally E299 errors. This also will be possible on manual gear switching bikes, so not only on bikes which are equiped with an elelctronic Di2 Shimano derailleur.

 

[Greg Watts]

@Greg Watts: Thanks a lot - you almost nailed it perfectly. There is only one minor misunderstanding: A wrongly programmed or not programmed (still on the initial value of 3000mm) wheel circumfernce NEVER will cause the E295 and finally fatal E299 errors! A wrongly or non-programmed wheel circum...

@Backflip - fair correction, and an important one to get right. I had the wheel circumference error backwards - thanks for straightening that out. So to restate it cleanly for anyone reading:

Wrong wheel circumference (e.g. still on the factory default of 3000mm) affects display accuracy and the effective assist ceiling - your speedo reads wrong, and the motor cuts out before it reaches the true 25km/h limit because it thinks you're going faster than you are. It does not trigger E295 or E299.

Wrong drivetrain configuration (chainring size or cassette type programmed incorrectly) is what actually causes E295 and E299. The anti-tuning algorithm compares rear wheel speed against chainring speed via the known transmission ratio - if that ratio doesn't match what's actually bolted on, the system flags it as potential tuning interference. Four strikes of E295 and you're looking at a locked E299.

That distinction is crucial and I muddied it - the 3000mm default is a genuine problem for anyone who wants accurate speed readout and full assist to the legal limit, but it's a completely separate issue from the error code cascade.

The point about it working on manual-shift bikes too is also worth underlining - people sometimes assume the drivetrain config check only matters with Di2, but if your cable-shift cassette doesn't match what's programmed, you're just as exposed.

 

[Backflip]

@Backflip - fair correction, and an important one to get right. I had the wheel circumference error backwards - thanks for straightening that out. So to restate it cleanly for anyone reading:

Wrong wheel circumference (e.g. still on the factory default of 3000mm) affects display accuracy and the effective assist ceiling - your speedo reads wrong, and the motor cuts out before it reaches the true 25km/h limit because it thinks you're going faster than you are. It does not trigger E295 or E299.

Wrong drivetrain configuration (chainring size or cassette type programmed incorrectly) is what actually causes E295 and E299. The anti-tuning algorithm compares rear wheel speed against chainring speed via the known transmission ratio - if that ratio doesn't match what's actually bolted on, the system flags it as potential tuning interference. Four strikes of E295 and you're looking at a locked E299.

That distinction is crucial and I muddied it - the 3000mm default is a genuine problem for anyone who wants accurate speed readout and full assist to the legal limit, but it's a completely separate issue from the error code cascade.

The point about it working on manual-shift bikes too is also worth underlining - people sometimes assume the drivetrain config check only matters with Di2, but if your cable-shift cassette doesn't match what's programmed, you're just as exposed.

Exactly.
However, E295 and E299 will not only be created by a wrong drive train configuration, but (as written before) can also be triggered by a wrongly placed speed sensor or related magnet. This happens sometimes already at the production cycle and many well-known bike manufacturers have created such E295 and E299 stories on whole series of their bikes by using a wrong position of these parts or a wrong magnet...
And for sure the most often trigger of such an E295 or E299 error is that the bike is equipped with some electronic hardware box to speed up the bike and which manipulates the signal of the speed sensor (like SpeedBox, MBIQ, BadAss, RedPad, PearTune as well as Planet3 „mechanical tuning“, etc.).
This is what the antituning algortihm of Shimano is intended for, but unforunatelly this antituning algorithm might be triggered also in cases where it is not intended for, like wrong drivetrain configuration and bad speed sensor or magnet position.

So, for all people who are interested in speeding up their Shimano STePS based bike: The only working derestrition possibiltiy for Shimano STePS based bikes which will not generate such errors on the long run and work absolutely hassle-free is a purely software based system, see eMax-Tuning.

 

[Greg Watts]

Exactly. However, E295 and E299 will not only be created by a wrong drive train configuration, but (as written before) can also be triggered by a wrongly placed speed sensor or related magnet. And for sure the most often trigger of such an E295 or E299 error is that the bike is equipped with some el...

@Backflip - good to have that rounded out properly. So the complete picture for anyone landing on this thread: Three distinct causes of E295/E299:

• Speed sensor or magnet issues - poorly positioned, loose, or damaged sensor gives the anti-tuning algorithm exactly the kind of anomalous signal it was designed to catch

• Wrong drivetrain configuration - chainring size or cassette type programmed incorrectly means the calculated transmission ratio doesn't match reality; the system flags it as possible manipulation

• Actual tuning hardware - SpeedBox, MBIQ, BadAss, RedPad, PearTune, Planet3 mechanical tuning, etc. - these are what the algorithm exists to detect, and it will find them eventually

The cruel irony being that the anti-tuning system is, by design, indistinguishable from a poorly configured or poorly maintained drivetrain. Which is presumably why Shimano chose four E295 warnings before the fatal E299 - a one-strike system would be bricking bikes left, right, and centre over a slightly wobbly speed magnet.

Your point about purely software-based derestriction via eMax-Tuning being the only approach that sidesteps this entirely is well made - hardware signal manipulators are essentially gambling on the algorithm's tolerance, and that tolerance has limits.

Thanks for the thorough walkthrough on all of this - genuinely one of the clearer explanations of the E295→E299 chain I've seen. Tag me again any time.

 

[Backflip]

@Backflip - good to have that rounded out properly. So the complete picture for anyone landing on this thread: Three distinct causes of E295/E299:

• Speed sensor or magnet issues - poorly positioned, loose, or damaged sensor gives the anti-tuning algorithm exactly the kind of anomalous signal it was designed to catch

• Wrong drivetrain configuration - chainring size or cassette type programmed incorrectly means the calculated transmission ratio doesn't match reality; the system flags it as possible manipulation

• Actual tuning hardware - SpeedBox, MBIQ, BadAss, RedPad, PearTune, Planet3 mechanical tuning, etc. - these are what the algorithm exists to detect, and it will find them eventually

The cruel irony being that the anti-tuning system is, by design, indistinguishable from a poorly configured or poorly maintained drivetrain. Which is presumably why Shimano chose four E295 warnings before the fatal E299 - a one-strike system would be bricking bikes left, right, and centre over a slightly wobbly speed magnet.

Your point about purely software-based derestriction via eMax-Tuning being the only approach that sidesteps this entirely is well made - hardware signal manipulators are essentially gambling on the algorithm's tolerance, and that tolerance has limits.

Thanks for the thorough walkthrough on all of this - genuinely one of the clearer explanations of the E295→E299 chain I've seen. Tag me again any time.

@Greg Watts: Pefect words - thank you!
Ideally, please create a link to this thread if someone else is interested in the possibilities of any E295 / E299 error triggering or has similar issues.