E-Bikes: Cadence-Sensing Motors vs. Torque-Sensing Motors

Jon Sully

4 Minutes

Different sensors for different types of rides!

E-Bikes: Cadence-Sensing Motors vs. Torque-Sensing Motors

I stumbled upon a really interesting Reddit thread some days ago that happened to be on a topic I’d been recently considering in some depth. Tl;dr: the writer switched from a cadence-sensing motor to a torque-sensing motor and now feels like they’re using a lot more energy to accomplish the same commute.

This comes only a handful of days after riding one of Cannondale’s latest-and-greatest e-gravel bikes with a torque-sensing Bosch motor system built in. It was at that point that I realized all of this: cadence-sensing motor systems are for when the point of the ride isn’t the ride. Torque-sensing motor systems are for when the point of the ride is. Let me explain

Cadence based hub motors are pretty simple. Once you start moving, the motor within the hub kicks in and works to get you up to some determined speed (typically this is split into levels: PAS#1 = 10mph, PAS#2 = 13mph, etc.). Along the way the motor might get the wheel spinning faster than your feet are spinning the cranks and chain. Now you’ve entered the “ghost pedaling” zone — you’re pedaling, but it’s not connected to (or contributing to) the propulsion of the bicycle. You are a ghost in the motor’s world! This is an easy fix for hub motors. Shift up. And keep shifting up until you feel that you’re connected to the drivetrain again. At that point you have the best of both worlds: you’re mechanically connected to your drivetrain and spinning with it, but the motor is actually doing most (or all) of the work. As you spin, you can continuously choose to flex your thighs more or less and the hub-motor will compensate in kind. If you want to spin with the drivetrain but not actually put any ‘oomph’ into your pedals, that’s fine! You’re not ghost pedaling, but the motor is doing all of the actual effort (someone has to! 😜). Conversely, if you do want to put ‘oomph’ into your pedals, the motor will ease off proportionally — now you’re essentially splitting the effort required to keep your bike going at this speed.

But the idea critical to the Reddit writer’s point here is that with a cadence-sensing system, you can operate the bike in a state of ‘the motor is doing all the work’ even though you’re still pedaling with the system.

(Cadence-sensing mid-drive motors can accomplish this too, but it’s more difficult to tune just right. I cracked that sauce for the BBSHD, but most mid-drive systems aren’t configurable this way. Luckily, most OEM mid drive systems are torque-based, so this isn’t an issue for most folks.)

All of this contrasts with torque-sensing motors. The idea that you can be mechanically connected to your drivetrain riding ‘with’ the motor but the motor is doing all the work… just fundamentally isn’t how torque-sensing works. Torque-sensing will always be a multiplier of your input torque. You will always have to be putting torque into the system for it to multiply. “Eco” may be multiplied by 1.5x (adds half the watts your foot is putting out), “Tour” may be 2x (what you put in, the motor does too), “Turbo” may be 3 or 4x etc.. but that still requires you to provide a level of input torque yourself. Especially if you want to maintain high speeds. Even if you’re on a flat, trying to maintain 25mph on a typical bike/rider setup is probably 200-300 watts continuous. If you’re on a 4x “Turbo” setting, that means you still have to continuously output 75 watts yourself (the motor does the other 225). Which ain’t nothing! When you hit a hill you might need 600-700 watts to get up that hill with moderate speed. Again, on a 4x “Turbo” mode, that’s 150-175 watts of output from you! Which is definitely something!

Anyway, all that to say, I realized a couple of weeks ago that for riding styles where the point of the ride is the ride (bike touring, cycling workouts, etc.. anything where you’re doing cycling as a sport), torque-sensing motors are for sure the better option. They’re more intuitive, they keep you involved in the drive-train all the time, you cannot ghost pedal or throttle your way to glory — all good things for that type of riding. They’re great! I would totally ride one on a road bike with all my spandex. But for riding where the point of the ride is not the ride, but rather that you’re just using the vehicle to get somewhere (commuting, cargo bikes with kids, getting groceries, etc.), cadence-sensing (when setup correctly!) just is the better option (IMO).

Comments? Thoughts?

Anonymous

you’re not wrong… but a cadence bike is basically just a throttle bike with really terrible throttle control. just get a real throttle.

Jon Sully (Author)

My anonymous friend! I’ll have to disagree with you there — or at least wonder if you consider torque-sensing to also just be “terrible throttle control” (?)

Cadence sensing is continuously sensing your cadence RPM and using that real-time data to guide the motor’s efforts. My belief is that my BBSHD programming epitomizes this sensing best: continuously monitor the rider’s RPM and add power until they’ve reached a known RPM band (their ‘happy cadence’) then continuously monitor and modulate power to keep them in that band as road grades change and/or they shift to different gears (which obviously impacts cadence). This is a fantastic programming for ‘spinning’ while still being connected to the drive-train of the bike yet not actually having to put in much effort if you don’t want to. Torque-sensing bikes cannot do this. Throttle control alone could not do this.


“just get a real throttle”

There are many, many people in the bike community that would roll their eyes at this very shallow, naive take. Perhaps this is why you opted for anonymity. Not everyone rides bikes the way you do nor wants the same things from them that you do. Where you say “just get a real throttle” someone else might say “hey maybe get a real bike”. I would encourage you to not throw stones. You don’t know everyone’s life.

Anonymous

my experience on cadence sensing bikes has been jarring. they just very very loosely kinda do what I want it to do. they respond to pedalling inputs slowly (both starting and stopping), and power inputs are imprecise and also often slow. control this terrible would never be tolerated in any other form of motorized vehicle.

I agree, this is fine for a “just get me there” sort of ride, but fail to see what poor control offers over a throttle that can provide a similar experience of desired, but with far more control. you can pedal with a throttle too! I guess some would prefer to be forced to idly spin their legs even if they want the motor to do all the work. I think it mostly exists just to skirt some regulations.

meanwhile, torque sensing bikes can offer excellent control, albeit very differently from a throttle. power can be started, stopped, and varied nearly instantly - well enough that torque sensing mountain bikes can ride a fine line of traction and provide sudden busts of power to make it over obstacles on technically challenging climbs, things a cadence bike could never dream of.

and hey, with lines like these, “very shallow, naive take”, who’s throwing stones?

Reply

Please note: spam comments happen a lot. All submitted comments are run through OpenAI to detect and block spam.