Quitting TR. Someone reply when they push an update

Had dropouts for the first time last Sunday (Win 10, ANT+, Tacx Flux S). But - I had another device connected USB on the PC, doing video capture for something totally unrelated. Did another session this morning, without this extra load, and zero dropout. So either there is confusion in the ANT+ driver when there’s too much traffic over USB, or there’s confusion in the driver and/or TR when processor/memory resources get constrained. Needless to say, I was about to die on the trainer attempting to finish Palisade without my tongue ending up caught in my chain, so no real time to diagnoze the problem.

My ride today was a disaster. KICKR + Vector 3 pedals and powermatch. Cadence all over the place on PC version with ant+ and power fluctuations through 2/3 of first interval. Switched to Android with ant+ with similar results. I switched to bluetooth on Android half way through the 3rd interval and that was stable. I quit the workout. It is hard to do a VO2 max ride with power going crazy high and low.

Have to say it was flawless up until few days recently, I get workout paused as well, or ant+ device disappears. I have to remove and plug it again to resume. Whatever TR did me no like.

1 Like

You or @Pete able to say if/when the Beta (2019.10.3.89796) fixes are going to the production version?

It’s been a lot more stable for me.

@Trippy Production now has the fixes! Everyone who was experiencing the problem is welcome to get back on the regular production release and will be all good to go. :+1:

6 Likes

Initial and Updated Beta has been flawless for me - knock on wood. No drops since I’ve begun using the beta and had multiple drops per workout before. What a huge improvement on overall experience. Seriously impressed and appreciate the focused attention. Well done.

2 Likes

@Pete I updated to the newest production version today made available for my MacBook:
Version 2019.10.1.89824.

It is better than the prior version, but there are still dropouts. My rides are public and you can see at 56:50 and zoom in on it.
https://www.trainerroad.com/career/bobmac/rides/53997059-juneau-3m

Did you have a drop-free setup at some point in the past, or have you always experienced some measure of signal drops?

My set up was drop free from Aug 2018 when I joined TR to approximately a month ago when the previous release came out. @larry at TR seemed to be aware of the issue.

Hey @bobmac!

We’re so sorry to hear that you’re still having issues! I have asked a Support Agent to reach out to you at your email linked to your account :slight_smile:

They will be able to take a closer look at what is happening, and send reports to our Test Team and Pete if needed :+1:

2 Likes

I rolled back from the beta to production last night (macbook) & didn’t notice any dropouts in this ride.

However, last nights ride was just an endurance spin & the problem seemed to be worse with sweet sport and above, so I’d not yet put this in the solved category.

Interestingly when I first switched from production to beta the problem seemed to be reduced for a few rides, but over time it got worse. Now I’ve switched back & the first ride seemed better. This could be completely irrelevant but I thought it was worth noting.

1 Like

@Bryce Thanks!

@SteveMoore @Bryce
FWIW: This ride was a sweet spot ride and sole dropout (10 seconds long) was in the SS zone. Prior to this release dropouts would occur at any level - during 45% recovery and during HIT (SS, Threshold, O/U). I’ve only had one ride on this new release but will be happy to provide support more info as needed. But yesterday’s ride with a single dropout in 1hr 30min ride was substantially better than the 4, 5or 6 dropouts I’d experience with the prior release during rides of 1hr30mins-2hr30mins.

Note: I am not upset about this. Having had been in the tech industry for 30 years, I deeply understand that TR is a small company that needs to tradeoff time-to-market new features vs. more extensive QA testing. In just the 7 months that I have been a customer, they have made a lot of improvements and I expect continued improvement as the company matures.

4 Likes

Thanks so much for understanding and helping us work through this issue!

1 Like

Longtime user, always had minor dropouts but put them down to the shared accommodation I live in - a ‘noisy’ RF environment. Got worse with the recent changes. Most notably with a massive torque increase 18:00 mins into a ramp test! Used Beta windows for a few rides this week, still had a few dropouts.

Used new prod version tonight for Budawang +3 (45 min total at 102%). Probably most stable ride I’ve had on TR. Thanks for the work put in to resolve this.

Windows 10
Powermatch ON
Kickr 1 - BT&ANT+ paired
Vectors - ANT+
Tickr - BT&ANT+ paired
Suunto ANT+ dongle
BLED112 USB dongle

1 Like

I switched back from the beta last night and still had issues on the main version, so went back to the beta and it worked fine.

Not sure if my production one hasn’t updated or what…

I’m thinking about going until @chad stops saying Soccer in the work out texts.

1 Like

@stevepetts372

I’m assuming that you’re only allowing either ANT+ or BT to connect to TR though?

Yes, it will only be connected by one method for each device. I mentioned that both where paired because previous posts suggested unpairing if you weren’t actually connected by that means, and I’ve done that myself to reduce possible snags. In this case though, no problems.

Thanks.
Do your devices work OK using the BT connection?

Because I use power match and my Vectors are ANT only I tend to defer to that. I can disconnect my ANT and see how things go, but won’t be until Monday.

1 Like