dtourolleandClaude Opus 5
7b511db3dc
Speed now comes from the drivetrain and the load from the road, which is the way round a bike actually works. Speed is cadence x development, filtered lightly. Power, not cadence, decides whether the rider is driving it: on a direct-drive trainer the flywheel keeps the cranks turning after they stop, so cadence alone reads a healthy 80 rpm for someone doing nothing. Below 15 W the speed runs down to whatever the gradient sustains on no power - zero uphill, a real freewheeling speed on a descent. Stopping on a 3.5% climb used to settle at 22 km/h and stay there, because the model wanted to decelerate and a blend toward the flywheel speed outvoted it; that blend is gone. The D100 sends no cadence over FTMS - it is a rebadged Magene T110 with cadence disabled in firmware (qdomyos-zwift#3282) - so it is inferred from wheel speed, which one sprocket and no freewheel make exact. Its Zwift channel does carry cadence, and is now greeted with RideOn and subscribed on every notifying characteristic, so a measured value is used where one arrives. The load is commanded as power, not gradient. The trainer declares 50-600 W in 1 W steps against 0-6% inclination in 0.1% steps refusing negatives, and whether it acts on 0x11 at all is still unconfirmed. Its power target is a ceiling rather than a setpoint, which is very nearly what a road is: exceed it and the surplus becomes speed. Gravity travels on the same channel as watts, so nothing is lost by leaving 0x11 alone. LoadChannel keeps the gradient path selectable and tested. Virtual shifting reaches the trainer for the first time. The physics load model was written but never called, and a paddle press both shifted a gear in Rust and nudged the gradient in the webview - the shift silently, the tilt visibly, so the paddles looked like a gradient trim. Also: a fixed 12 W drivetrain loss, held as a power because that is how it presents; crank length, so a gear can be reported as the force it puts under the foot; gear and pedal force on the ride screen; a drag-race profile for testing gearing on the flat. Two readout bugs fixed on the way. The rolling windows were trimmed by timestamp but fed on a fixed timer, so every second spent on the ride screen before starting pushed samples at t=0 that could never expire - speed read a fraction of the truth for the first 45 s. And the headline speed was a 45 s mean, which took most of a minute to show a gear change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
27 lines
1.2 KiB
YAML
27 lines
1.2 KiB
YAML
name: Drag race
|
|
description: >-
|
|
A standing-start kilometre on a dead-flat road, for testing that the gears and
|
|
the resistance actually do something. Nothing about it is a workout: it is the
|
|
shortest route to the two questions that matter. Start in the bottom gear from
|
|
a stop and wind it up — every shift should land under the pedals immediately,
|
|
and holding the same gear should get harder as the speed rises, because drag
|
|
is the only thing resisting you on the flat and it grows with the square of
|
|
speed. If shifting feels like nothing, or the load never builds, the control
|
|
writes are not reaching the trainer.
|
|
|
|
Flat is deliberate: on a gradient, gravity swamps everything and a broken gear
|
|
ratio still feels like a hill. With no slope, the load you feel is the gearing
|
|
and the aerodynamics, and nothing else.
|
|
|
|
Distance-based, so it ends when you have covered the kilometre rather than
|
|
after a fixed time — which makes the elapsed time your score. Loops, so you
|
|
can go again in a different gear and compare.
|
|
looping: true
|
|
|
|
blocks:
|
|
- type: segments
|
|
segments:
|
|
# The whole course. One flat kilometre; the gears supply all the variety.
|
|
- distance_m: 1000.0
|
|
gradient_pct: 0.0
|