New "TSDZ2 Torque Sensor Central Motor"

[Blacklite]

Doing a bit more digging it seems that the lowest figure should be ~300 at 0 input.

If that's correct, then mine appears to be reading very low...which also makes sense why it would be underpowered.

I've ordered the bits to make up a data link and been playing with the OSF software...

I’m not sure that value is correct. I think the stock firmware does what most of the OSF’s do if you haven’t chosen to do a software calibration, which is to read the unweighted value at startup and use that as a zero. Because of safety there has to be a bit of leeway, it might use 10-15 under the read value on startup. If you’ve only got a total range of 60 then there is not much to work with if the multiplier of that value is hard coded. I’d suggest MBrusa’s firmware… can fix the problem either with software calibration, which basically remaps that range of values to a larger one, or just by adjusting the actual power multiplier for each level. If the hardware range is small then obviously there is a low resolution. I’ve found mine ok with a range of about 85 from resting to standing on the pedals which has been satisfactory.

There is also the question of linearity of the sensor signal compared to input torque. Mbrusa firmware has some further calibration that can be done to try and more straight-line the curve, so to speak.

[Elinx]

....
There is also the question of linearity of the sensor signal compared to input torque. Mbrusa firmware has some further calibration that can be done to try and more straight-line the curve, so to speak.

The curve of the torque sensor will not be corrected.
"Further calibration" is done if you want a more exact torque display reading at the lower (linear) side of that curve.
Mbrusa has already calculated an estimated value inside OSF, depended of the measured torque range, so enabling this estimated value could be enough for most people.