New TCU Firmware Update 25.B.0

[congerball]

Afternoon,

After some info if possible please, just picked up my bike after a service (2019 levo) from local spesh store (uK) and they told me they’d updated the firmware on it, before it went in it had 1A.B.0 now it has 25.B.0...anyone know what changes/fixes the new firmware has?
Any release notes for new revision? Can’t find anything anywhere...

Thanks

edit: looks like the startup/shutdown sequence of blue LED’s on the TCU has changed slightly? Looks smoother? Or am I just imagining it? ?

 

[Mikerb]

Firmware on what? Motor, TCU, or battery?

 

[congerball]

Apologies....TCU (updated thread title)

 

[Paul Carruthers]

25 or 22?

 

[congerball]

25?

 

[Paul Carruthers]

25?

Must be really new got mine done a few weeks ago and it’s 22

 

[congerball]

 

[NULevo]

Must be really new got mine done a few weeks ago and it’s 22

View attachment 24010

Same here - Got mine Mid November

 

[Paul Carruthers]

Must be really new got mine done a few weeks ago and it’s 22

View attachment 24010

Same here - Got mine Mid November

Ludicrous that updates are not communicated and require dealership to update

 

[congerball]

Ludicrous that updates are not communicated and require dealership to update

Agreed. I wouldn’t have been aware of the new update 25.B.0 had I not asked them to do my free 6 week service (and chuck a new chain on that Santa brought me?) after 6 months of ownership.

I wasn’t even aware that version 22.B.0 was available so I’ve been on 1.A.B.0 since i picked it up in July.

Maybe the updates to TCU firmware are so small/not notable to the user there’s not much point Specialized communicating them? Unless a major update to functionality? Just guessing but it would be nice to know.

@Specialized Rider Care if you’re out there on the internets can you provide any clarification on this please? Or do any dealers out there know? With hindsight I should have really asked what the update actually did when I was told about it in first place....I didn’t...I just said “nice” ?

 

[Paul Carruthers]

Agreed. I wouldn’t have been aware of the new update 25.B.0 had I not asked them to do my free 6 week service (and chuck a new chain on that Santa brought me?) after 6 months of ownership.

I wasn’t even aware that version 22.B.0 was available so I’ve been on 1.A.B.0 since i picked it up in July.

Maybe the updates to TCU firmware are so small/not notable to the user there’s not much point Specialized communicating them? Unless a major update to functionality?

Who knows, owners certainly won’t that’s for sure

 

[Mikerb]

Mine was serviced October and its on 22.

 

[congerball]

Noticed I no longer need to press and hold the power button until the lights come on/go off. A single quick press does the job now. Or maybe it’s been like that since I had it and haven’t noticed it before ??

 

[Mikerb]

I am on 22. To switch off is always a quick press. Switching on is a press until the light appear when first switching the motor on but if for example the motor switches off during a break the restart is just a quick press.

 

[Mikerb]

The 25 release could be anti tamper detection. All pedelec software has to introduce that to concur with EU regulations.

 

[congerball]

Thanks Mikerb?

 

[dobbyhasfriends]

ive got 25 as of yesterday, the sequence of lights has changed for certain, but ive only noticed it when turning off.
weirdly, the motor behaves differently now, its doing stuff ive not noticed it do before.

today I rode across the beacons and was just spinning at my usual RPM and I had been for a while when the motor just 'took off' and it drove me along instead of me pushing the bike along. I had to change a few gears in order to keep up with it. like I say, never happened before but it happened many times today.. I also had the flashing red/blue lights out of nowhere..

 

[Mikerb]

Sounds like nothing to do with new firmware and everything to do with whatever is causing the fault code. Souns like your motor power is cutting in and out. Why was the bike in the lbs?

 

[dobbyhasfriends]

Sounds like nothing to do with new firmware and everything to do with whatever is causing the fault code. Souns like your motor power is cutting in and out. Why was the bike in the lbs?

could well be... variety of issues going on, none of em sorted.

 

[congerball]

ive got 25 as of yesterday, the sequence of lights has changed for certain, but ive only noticed it when turning off.
weirdly, the motor behaves differently now, its doing stuff ive not noticed it do before.

today I rode across the beacons and was just spinning at my usual RPM and I had been for a while when the motor just 'took off' and it drove me along instead of me pushing the bike along. I had to change a few gears in order to keep up with it. like I say, never happened before but it happened many times today.. I also had the flashing red/blue lights out of nowhere..

Interesting, yes I’m sure somethings changed although I haven’t experienced any error codes....yet?....noticed my settings on the tune page in mission control had changed too....shuttle mode was on 100% and acceleration down to 0% so I had to reset my all assist levels etc etc

 

[dobbyhasfriends]

Interesting, yes I’m sure somethings changed although I haven’t experienced any error codes....yet?....noticed my settings on the tune page in mission control had changed too....shuttle mode was on 100% and acceleration down to 0% so I had to reset my all assist levels etc etc

yea, I had the same

 

[congerball]

Something caught my eye in the 2020 Levo owners thread....some users are seeing a red LED light up for a split second (literally blink and you miss it) during power on...I used to notice this every now and again but thought nothing of it as it only lit up (barely) for a nano second.....I’ve checked mine and it’s definitely not there anymore ?

**edit** no it’s still there ??

 

[Mikerb]

It is understandable that any firmware update onbthe TCU would change all settings to default. The lbs should have noted the original settings and reapplied them after the update. Given that v22 does not have any bugs the update to 25 has some other purpose and I suspect it could be tamper detection. Given that no one who has been updated to 25 has been given any information it cannot be the sort of anti tuning process like the bosch gen 4......that in any case probably needs an additional pcb chip such as a gps or accelerometer chip.

 

[congerball]

You’re probably right Mikerb ?

 

[Rob555]

I’ve not done anything with any updates since purchase! The bike runs great so I don’t want to risk it. Or am I missing out on something?

 

[congerball]

I’m not sure as I can’t find any official information on the changes made to different firmware versions (Display/TCU)....it would be nice to know for sure though?

 

[Rob180]

I’ve not done anything with any updates since purchase! The bike runs great so I don’t want to risk it. Or am I missing out on something?

I am of the same mind. Even on firmware updates where a change log is provided, I have experienced undocumented changes and the inability to revert the firmware. So, I’m going to stay where I’m at until I hear something conclusive.

 

[Joss]

I just picked my bike up from a warranty job yesterday and the shop had updated the firmware on the TCU. The only mentioned was error logging via the app. So, if you get an error code then fire up the app and the fault will be communicated to Specialized and logged with them. This in turn can be relayed to a dealer for remedial work to be properly targeted rather than relying on an individuals account - particularly useful for intermittent faults, I'd have thought. I expect this links in with tamper-detect procedures.
Now, I don't recall my old firmware version so this may have been introduced previously.

 

[Mikerb]

Interesting. So it logs error reports and I assume the log is visible once the lbs Spesh app is connected. Logically the error code reporting does little morr than what an owner could tell the lbs so for it to of use for diagnostics the TCU would also need to log the sensor signals it was recieving when the error code occured in order to indicate what part of the system caused the fault. This is the same as a car's EMS.

 

[Joss]

That's pretty much exactly how it was described to me. I can't vouch for its level of sophistication but I think anybody who has tampered might want to revert to original configuration before launching the app.
I suspect the agenda is broader than delivering the best possible service but the intention as described was to assist the lbs by having more specific information than might otherwise be communicated. I'm sure they get plenty of reports of the bikes "doing something funny" etc. Also it reduces the time spent diagnosing problems, in some instances at least.
I think the idea is that if a rider takes their bike in, the lbs plugs into it and/or submits the frame number and any data stored by Specialized is communicated to them. No doubt any relevant alarms begin sounding too......

Note - this is all based on a 5 minute conversation!