I have now made the auto shifter fully automatic and possibly a world first. As far as I know this is the first time BioShift type, cadence varying depending on power, shifting has been used with a CVT. Power meter is now connected 
.
The NRF24L01 modules work really well and like I2C if both Arduinos are running the code then data is transferred. No delays and messing around connecting.
I’ve programmed the shifter to be a torque selector instead of cadence. This alters the relationship between power and cadence. At the moment I’m not using cadence correction, the power data just alters the multiplier and therefore cadence. The worn out hub is really beginning to show with a wide cadence range for a set servo position. A combination of slack in the system, planet axles flopping about in the worn stator slots and the plastic hub interface.
Dispite this the first test ride was a very different experience. Reminded me of when I first uploaded the code to achieve auto shifting. So weird to start applying power and feel that I’m pedalling faster but there isn’t the increase in torque normally required. I think its going to take a bit of fine tuning as I’m finding the cadence changes a little to much but that’s probably due to riding with constant cadence for so long. According to the past data recorded it should be about right. I’m used to knowing my power output from the amount of torque I apply to the pedals. Somewhere in between will probably turn out to be the best.
Example of some data recorded via Bluetooth from the auto shifter. Great to have all the data together for logging. The Bluetooth app allows 7 values to be received they are power, cadence, speed, auto shifter and power meter battery voltage, programmed servo position and power meter zero error. The last one is really useful for checking the power meter as it’s the current stain gauge value minus the zero value calculated during setup.
![[Image: Im4Hcp.jpg]](http://imageshack.com/a/img924/5885/Im4Hcp.jpg)
.The NRF24L01 modules work really well and like I2C if both Arduinos are running the code then data is transferred. No delays and messing around connecting.
I’ve programmed the shifter to be a torque selector instead of cadence. This alters the relationship between power and cadence. At the moment I’m not using cadence correction, the power data just alters the multiplier and therefore cadence. The worn out hub is really beginning to show with a wide cadence range for a set servo position. A combination of slack in the system, planet axles flopping about in the worn stator slots and the plastic hub interface.
Dispite this the first test ride was a very different experience. Reminded me of when I first uploaded the code to achieve auto shifting. So weird to start applying power and feel that I’m pedalling faster but there isn’t the increase in torque normally required. I think its going to take a bit of fine tuning as I’m finding the cadence changes a little to much but that’s probably due to riding with constant cadence for so long. According to the past data recorded it should be about right. I’m used to knowing my power output from the amount of torque I apply to the pedals. Somewhere in between will probably turn out to be the best.
Example of some data recorded via Bluetooth from the auto shifter. Great to have all the data together for logging. The Bluetooth app allows 7 values to be received they are power, cadence, speed, auto shifter and power meter battery voltage, programmed servo position and power meter zero error. The last one is really useful for checking the power meter as it’s the current stain gauge value minus the zero value calculated during setup.
- Oran