Team BKool CycleChat

[gbrown]

If anyone wants to try again tomorrow evening, or indeed any other time, I have tweaked the handicaps based on new PB's for normalized power.

Those that were based on FTP or some other run may well have gone down now a normalized power for the course has been set, so you may well want to try setting a new time, although there will hopefully be a rerun next Tuesday.

It certainly seemed a close race tonight, from second to ninth were all within 1 minute and 8 seconds of each other!

 

[gbrown]

Ta Andy. I had unclipped painfully when sprinting to the front at the start but felt goodish so just wanted to hang in there. You guys were just so fast, taking LB's lead i guess. Mind you, i see you were coming back at me near the end and another 100m or so and you might have caught me.

re the 9% limit i honestly feel like i feel that additional resistance, even if no one else seems to!

At the lower handicap weights, the resistance should be able to cope with higher gradients (one of the reasons it's best to reduce weight rather than handicap with more weight).

 

[bridgy]

If anyone wants to try again tomorrow evening, or indeed any other time, I have tweaked the handicaps based on new PB's for normalized power.

Those that were based on FTP or some other run may well have gone down now a normalized power for the course has been set, so you may well want to try setting a new time, although there will hopefully be a rerun next Tuesday.

It certainly seemed a close race tonight, from second to ninth were all within 1 minute and 8 seconds of each other!

Oh if only losing a kilo and a half was as quick and easy in real life!

 

[gbrown]

@JLaw, what happened to you at the finish, you just seemed to loose all power for a moment and just about stopped dead?

 

[Goldwolfie]

Looking at normalized power for this run (mostly with new firmware/software) and the previous run, most people were slightly down on power, with a few notable exceptions, Rob, Bob and AAAC!

View attachment 131931

New firmware and software for the first time tonight.

Same power as last attempt, but 90 seconds quicker.

It will be interesting to see how I get on when I put my weight back to normal.

 

[Add]

If anyone wants to try again tomorrow evening, or indeed any other time, I have tweaked the handicaps based on new PB's for normalized power.

Those that were based on FTP or some other run may well have gone down now a normalized power for the course has been set, so you may well want to try setting a new time, although there will hopefully be a rerun next Tuesday.

It certainly seemed a close race tonight, from second to ninth were all within 1 minute and 8 seconds of each other!

Try it AGAIN? Why would I want to do that?? My fan broke towards the end, and I don't think I've ever been so hot and sweaty. Found that very hard!

 

[Soarerv8]

Turns out no matter what the weight I am slow as a slow thing covered in honey being held back by a bear......who likes honey.

Looks like I will have to rely on the helicopter and Jag to get the girls instead of my bike skills.

 

[AAAC 76C]

Turns out no matter what the weight I am slow as a slow thing covered in honey being held back by a bear......who likes honey.

Looks like I will have to rely on the helicopter and Jag to get the girls instead of my bike skills.

Just get the helicopter to fly behind you and you can take advantage of the ground cushion

 

[JLaw]

@JLaw, what happened to you at the finish, you just seemed to loose all power for a moment and just about stopped dead?

View attachment 131936

Bkool glitch. I feel them fairly regularly. It's been going on for a couple months. There are times I'm cruising along at a known grade and the actual resistance starts bouncing all over the place, which is then seen in the reported wattage, speed, etc.

My first thought was it was just drops, possibly due to radio interference. But I've seen this both at home (where there is a fair amount of noise in the 2.4Ghz spectrum), but also at the vacation house where there's dramatically less noise in the ether. I've also seen it happen with the simulator running on the mac as well as on an android tablet.

I've noticed a couple other glitches in the last 24hrs. Essentially it felt like the resistance was way too low for the duration of a segment (when compared to the claimed gradient in the simulator). It lasts for the duration of the segment, during which my speed stays blue. No bloody clue what's going on as it's not at particularly steep sections (7%).

Maybe next time I'll keep the garmin connected and hit the lap counter at the start/end of these glitches for later analysis.

 

[JLaw]

@JLaw are you leading out the first 0.15 miles today?

If the KICKR start problem is solved, please can you accelerate up to full speed gradually, to give everyone a chance to cluster behind you for the end of the neutralised section.

Thanks,

Geoff

Now that I've watched the video, I'm pretty sure the kickr start problem is resolved. I never really had to pedal hard and I was at a reasonable speed. In fact, I was throttling back over the last 10 seconds or so to try and hit the requested 36s through the neutral zone.

 

[CXRAndy]

Where as I was asleep at the start, with a slow internet connection, left me spinning 10 secs on the line with no forward motion, moving time 15.22. It was a big effort to get back on, then claw my way up the race, burnt my matchbox at the start and just survived the end.

Going back on the kickr, is tougher but is what I need to try and get extra power

 

[CXRAndy]

@JLaw If you didn't know already there is a firmware update KICKR 1.4.46 12May 16 adds ant+ FE C functionality with improvements Update using Wahoo utility via android/iphone

Superceded by 1.4.47

 

[gbrown]

@JLaw If you didn't know already there is a firmware update KICKR 1.4.46 12May 16 adds ant+ FE C functionality with improvements Update using Wahoo utility via android/iphone

Looks like there is now a 1.4.47 version, I'm just updating. I guess .46 had some bugs?

Found this... they must have just released .47, but it sounds like some people are going back to 1.3.32. I love the computer industry!

Shane Miller | ZwiftOzMay 22, 2016 01:32

John - There is a known issue being worked on with v1.4.46 of the Kickr firmware.

Beta 1.4.47 is in testing by Wahoo that addresses this issue. I believe the public update should be available soon.

In the mean time, displaying 3 second average within Zwift might help with the distraction.

Posted 24 May 2016 - 03:36 PM

I upgraded to 1.4.46 this morning prior to my TrainerRoad workout. I was getting big power spikes on the recorded graph at random intervals. Half way through I paused and checked the Wahoo utility and it offered me 1.4.47 so I upgraded to that one. The problem is still there, although TrainerRoad seems to remove them from the workout graph when you finish the workout and it processes it.

It was showing dropouts on my Garmin 510 too, but they have disappeared when I view the workout on garmin connect. Not happy though because it's very distracting.

 

[CXRAndy]

You're right Geoff, mine went straight to .47 version. Will see how it goes on the next chaingang session

 

[JLaw]

@JLaw If you didn't know already there is a firmware update KICKR 1.4.46 12May 16 adds ant+ FE C functionality with improvements Update using Wahoo utility via android/iphone

Superceded by 1.4.47

I've been running the stock 1.3.32 firmware since purchasing the beast. So I'd ruled firmware out as the source of the glitches as they started immediately after one of the bkool simulator updates (April/May). Now it may be the case that there's a bad interaction between the bkool sim and the kickr 1.3.32 firmware -- so I've installed 1.47 and will try to do a ride today or tomorrow and see if it glitches.