RojoRacing
Donut Powered Wise-guy
I haven't gotten one of those alerts since my first month on zwift. Doesn't seem odd though since my fitness never really changes, I just learn to dig deeper.
FTP 296 and climbing
That's pathetic, I remember back in the day when I was just a lad it being higher. Man it sucks getting old
Ray Maker has it projected as the trainer to beat for 2018I nice review on a new trainer option coming very soon.
Stymied! I have had this problem for awhile but it's time to find a solution. Daisy rocks the heck out of the Neo and the front or rearof the bike moves to the point it is a game stopper during a race. She isn't gonna get any smoother pedaling so I need a way to anchor the darn thing. Any ideas?
I was the one who asked him to test the trainer response time to grade changes in zwift. We agreed all trainers suffer from this and all around 2 seconds with Shane feeling the Kickr being the quickest to respond. He and I think this will need further collaboration between Zwift and trainer manufacturers so hopefully they will continue to work on this.
I dropped my chain on that little staircase during last night's race which almost ruined my run to the finish. I just can't doing up that 17% staircase and still leave it in the big ring. I wish the trainers could take current speed into consideration and more smoothly apply resistance. If you hit that staircase at 35 mph you should be able to power up in the big ring.
I bet the math and science guys on BROL could tell you ten way they think it should be solvable.Stymied! I have had this problem for awhile but it's time to find a solution. Daisy rocks the heck out of the Neo and the front or rearof the bike moves to the point it is a game stopper during a race. She isn't gonna get any smoother pedaling so I need a way to anchor the darn thing. Any ideas?
Those both sound like a software issue.
For the first one Zwift just needs a database that says; Trainer X suffers a delay of Y seconds. Calculate the speed of the virtual bike and distance to the next incline change; then signal the trainer Y seconds before you get there to change the resistance. You just have to do it. TrainerRoad finally got around to doing that for the starts of intervals and it's much much better. Granted their calculation is just Time based and not virtual speed, but Zwift is already do all those calculation for the graphics so they have it. Getting the database of "delays" that you trust is the big problem. If you really wanted to do it right you'd have to do a calibration ride for every trainer; and we all know no one would do it.
The second is one is a lot harder; that's going to mean calculating Power Required to Maintain Velocity on a grade. IF the rider's weight and the bike's weight are known; then you should be able to compute the rate of speed decay with zero power based on grade, speed, and altitude. That's just Newtoning physics...... easy so far. But the problem then is determining how much resistance to GIVE the user to be used to pedal against to input power; that going to be some relative resistance to the strength of the rider, and it has to increase as the bike slows. I bet you could put that on a Logarithmic curve; pick a speed at which FTP is required for a given grade to not fade. Then as you travel up and down the range of speeds resistance moves on the curve. You give enough power to maintain speed pedalling doesn't get hard; give too little and it steadily gets harder. That probably would be best done with a heuristic model; just build it; and then test it and tweak it until it feels right; much simplier than modeling the real world and every variable which would probably be beyond computing power at this.
Stymied! I have had this problem for awhile but it's time to find a solution. Daisy rocks the heck out of the Neo and the front or rearof the bike moves to the point it is a game stopper during a race. She isn't gonna get any smoother pedaling so I need a way to anchor the darn thing. Any ideas?
Those both sound like a software issue.
For the first one Zwift just needs a database that says; Trainer X suffers a delay of Y seconds. Calculate the speed of the virtual bike and distance to the next incline change; then signal the trainer Y seconds before you get there to change the resistance. You just have to do it. TrainerRoad finally got around to doing that for the starts of intervals and it's much much better. Granted their calculation is just Time based and not virtual speed, but Zwift is already do all those calculation for the graphics so they have it. Getting the database of "delays" that you trust is the big problem. If you really wanted to do it right you'd have to do a calibration ride for every trainer; and we all know no one would do it.
The second is one is a lot harder; that's going to mean calculating Power Required to Maintain Velocity on a grade. IF the rider's weight and the bike's weight are known; then you should be able to compute the rate of speed decay with zero power based on grade, speed, and altitude. That's just Newtoning physics...... easy so far. But the problem then is determining how much resistance to GIVE the user to be used to pedal against to input power; that going to be some relative resistance to the strength of the rider, and it has to increase as the bike slows. I bet you could put that on a Logarithmic curve; pick a speed at which FTP is required for a given grade to not fade. Then as you travel up and down the range of speeds resistance moves on the curve. You give enough power to maintain speed pedalling doesn't get hard; give too little and it steadily gets harder. That probably would be best done with a heuristic model; just build it; and then test it and tweak it until it feels right; much simplier than modeling the real world and every variable which would probably be beyond computing power at this.
Wow .awesome work.... I had to look up heuristic.....much abashed. Ratz u be the ducks nuts.
Jason, this race has Rojo Racing all over it. BTW Innovation is the baddest of the teams in zwift.
12:40AM EDT
Innovation Cycling – Figure my 8 - 3.5 - 5.5 (18.5 mi / 29.8 km)
DESCRIPTION
The Innovation Cycling - Climb my Hill is 1 lap of the Waitopia Figure 8 circuit to work on standing climbs staying as a group at an estimate 4.2 - 5.0 watts per kg climbing pace. We will regroup at the top of each lap.The last lap will be a race from the base of the climb, all riders must be behind me at this point.We will all push and motivate each other whilst having a bit of banter. The aim of this is to ride together and hurt together, lift the level and go faster.The key with this is to moderate speed and stay with the group, stronger riders go on the front to pull up the back.
And remember this is a training ride aimed to push and make you pop, if you pop try and rejoin at the top otherwise come back and go further next time.
Pace Guidelines
• Warmup pace - 3.2• Flat pace 3.8 - 4.0
• Climbing Pace - 4.2 - 4.4We will aim to regroup at the top of the climbs.
Use the INC (Innovation Cycling) acronym in your Zwift name so that we can identify you.
GROUPS
Ok, the hunt is on to stop the trainer from moving. Starting simple and moving up. The first try is to put industrial velcro on the little rubber footies and the rubber mat. Why? It took one minute and I have the velcro. If this doesn't work but shows potential, will move to a big arse piece of velcro around both sides of the Neo and place massive velcro strips on the rubber mat. Why? Because it will take another minute. If this doesn't work I'll place nails through the little footies that will penetrate the rubber mat but not reach the floor. Why? I have the nails and an obsession to muck up my floor. If this doesn't work I'll ask BROL. Why?---------Gotcha-- No freaking chance, just pulling your leg on that one.