Very weird... there are $5 computers that get speed, time, and distance correct.

Hey - yep.

Most frustrating part to me is that my SRM was/is flawless - and the only reason i switched to powertap was for a new bike.

Now I have quarks to deal with on the new bike and quarks to deal with on the new power meter.

I love my life.

My PT computer dropped the ball severely at timberman.

The power didn't seem right for what I was doing while I was riding, power seemed pretty low, distance was fine. Rode a low 2:38:xx on... 145 avg power (I'm 165lb or so).

Downloaded it a few days later and according to the download I rode.... 16 miles. It's been fine up till that race, since I've transitioned to marathon training since the race, I haven't investigated it much.

---

---------------------------------------------------------
All we have to decide is what to do with the time that is given to us. ~Gandalf

I have had to set my wheel circumference to 2092 to get it to stop overstating the ride distance, on both the LYC and the Joule.

Also, fwiw, since I now have to download my Joule to PA, and then export that to WKO+ (I have v2, doesn't support direct Joule download), the distance and time overstating issue has gone away. I was advised to try this for the LYC, but I'm not using the LYC anymore - perhaps one of you kids could try it out.

---

float , hammer , and jog

THe distance being overstated isn't happening on download (atleast not for me) - it's prior to download.

Mine was too. Same thing.

The "time expansion effect" is what happened after downloading to WKO. The LYC head unit display agrees almost perfectly w/ my watch/GPS/HRM in terms of time elapsed, assuming I didn't have any stops.

---

float , hammer , and jog

Poweragent downloads it the same way. So does WKO+2.

Interestingly when you look at the avergae speed as displayed on the computer - it gets calculated with the expanded time - not the displayed time.

I.e. 20 miles in 60 minutes = 19.6 mph average displayed depending on what the expansion coefficient is.

I have seen this too. Correct avg speed based on true elapsed time/distance is more than what PT head unit shows while on the bike (i.e. PT unit is off on the low side).

---

-------------------------
http://trirochester.com

I've seen this as well. Always wondered if it was due to extra distance from passing / not travelling in exactly in a direct line from start to end. Now methinks it's something with the PT.

---

-------------------------
http://trirochester.com

In my case I had two different computers with the same tire circumference loaded, and the distances and times were substantially different. Every other computer I've used gives ~10.15 miles for this course... that's a Cateye, Sigma, and two iBikes.

Seems like people are having different issues, which makes this all the more mysterious.

ya know - I don't mind hounding saris on this, but the more people call in and can give explicit details on what they are observing - the more data the developers will have to figure out what's wrong with their firmware.

Gotcha thanks. Never got around to try putting another computer on my bike with the PT (which as you showed answers that question).

---

-------------------------
http://trirochester.com

I keep thinking more and more of switching back to SRM. But that means selling 3 PT wheels one which is a disc, the other an 808, 2 lyc and it seems like a BIG hassle.

On the other hand what good is having a PM if it can't get basic data correct?

---

Brian Stover USAT LII
Accelerate3 Coaching
Insta

Willing to cut a sweet deal on the disc?


I know where you're coming from - it's really, really annoying to me to look at my training logs and see the time of rides inflated by 1% to 2%. I'm actually about to just save off the "bad" files - export them to a CSV and apply a correction to the time stamps.

In some ways it might mess the data up more...


I've made arrangements to ship my LYC bad to saris for them to rip apart. It'll arrive in their hands with a ride: 3:54 that downloaded as 4:00, and calculates average speed based on 4:00. hopefully it will tell them something.

The replacement LYC - seems to still have the distance issue - i.e. distance is not accurate for a given rollout.

However - the replacement LYC seems to be much better time wise. When downloading into Poweragent it is as expected i.e. moving time matches displayed time.

When downloading into WKO+ the "moving" time is long, but seems to match up correctly for extra time at stops and such. Will see how it goes at IMWI and a sprint two weeks later.

FWIW - a 40 minute and change interval matched up time wise on interval display length and download time into WKO+ on a ride yesterday.

Will see how things go this week on rides - but the time display issue preliminarily thus far appears to be a "hardware" issue.

I'd consider it :-)

---

Brian Stover USAT LII
Accelerate3 Coaching
Insta

Just did a TT at Moriarty (40k) and both the distance and time were inflated by 1.8% on download. The time displayed on the unit during the race was correct. This is very weird...

I have the same problem and i'm pretty sure it's a WKO+ issue, not a powertap issue. I get same inconsistencies when I transfer data from my garmin or lyc (different data on the watch/lyc versus what I get in WKO+).

---

_____________________
Don't forget to attack!

My issue is occurring with Power Agent.

borrowed a buddies joule tonight.

Did a ride with the wheel sync'd to both of them.

Was a trainer ride about 45 minutes.

Wheel stopped moving @ about 45:05 on my stop watch. Joule stopped ticking @ 45:08 - cervo @ 45:18.

That seems consistant to me as I've observed the cervo has a fairly long "cool down" period.

Downloaded into power agent.

Joule - 45:08 moving time

Cervo - 45:44 moving time


f'd up.

This is a big problem, imho. I've been having it for at least 6 - 8 months now. I've called Saris at least 3 times now and have made no progress other than "try this, try that...." The problem was that I didn't have enough data at the time to determine exactly where the issue was. I wasn't sure if it was Wko+, although I had made zero upgrades to Wko+ when the problem started occurring, or some place else.

So, here's my data from Kona:

CPU -- Ride time = 5:20; Distance = 116.36
Wko+ -- Ride and total time = 5:34; Distance = 116.3 (this was actually a rare case where my mileage matched my cpu display but time was WAY off)
PowerAgent == Ride/moving time = 5:34; Distance = 114.8 (what was really strange here is that total time = 5:28 which was less than ride time)

Now when I exported my PowerAgent file to a csv and imported it into Wko+, I got the following:

Ride time = 5:25; Total time = 5:28; Distance = 114.8

I started my computer right out of T1 so mileage should be right around 112 miles (even if wheel circumference was off slightly). My official ride time was 5:24. I also wore a 310XT which I started about 1/4 mile after T1. It has my mileage at 111.8 and ride time was 5:24.

I have this problem on every single ride. As Scott stated, the longer the ride, the worse it gets. One thing I just remembered is that I sent my old YLC back to Saris last season along with my hub (due to a hub problem). I remembered they told me that they replaced my old YLC with a new one. I thought that was cool. Apparently that wasn't cool because that was about the time when I started having the problem.

Thanks, Chris

I've had the same problem since I got the ANT+ hub upgrade to my PT 2.4 about a year ago. Prior to that, my ride distances were exactly correct (based on comparison with GPS and mapmyride). Since the upgrade, the distances I get from the CPU are about 3% high - just about exactly the error you are reporting here. Ride times are wacked too, although I have tracked these less carefully.

I went through Saris support and they were even kind enough to send out a new head unit to see if that fixed the problem (it didn't). I was told that my only other option was to send in the hub for service. I have a feeling they won't find anything wrong and I will waste my time and money sending it in, only to get it back with the problem unresolved. This is clearly a software problem and it is time that Saris wakes up to that, comes up with a solutiion, sends out a patch to affected customers and restores confidence in their product.

Yeah, I've had a very similar experience except they haven't asked me to send my hub in for service. I wouldn't bother. I have two hubs and it's happening on both. I've sent an e-mail to Jesse (Product Manager) but haven't received a response.

Thanks, Chris

Yup. I have a Joule and LYC on my aerobars and the LYC reads longer every time. I put another email in to Saris. This problem should be their number one issue to resolve.

For sure!

A bit more background on my problem (for the benefit of any Saris support people reading this as much as anything). I have been basically been struggling with this problem the whole past summer. I'm using the ANT+ upgraded PT 2.4 with the LYC and downloading to PA. THe LYC and PA are both upgraded to the most recent firmware/software. I have done numerous tests on the same test course (approximately 9km long) and find that the distance is approximately off (high) by about 3% every time - primarily comparing to my Garmin 310XT but I have also tested against mapmyride and my 2009 Honda Accord odometer. The distance they measure agrees, the distance measured by the LYC is high by 3%. The strange thing is that the speed measured by the LYC and the Garmin 310XT agree exactly, once I get to a steady state (the speed averaging on these units is different). This tells me my wheel circumference is very accurate and clearly not the problem.

The distance error also persists when I upload from the LYC to PA. I don't use WKO+, I upload my data to TrainingPeaks - there error persists there, as expected.

If the Joule fixes this problem, I'd consider replacing the LYC. However, I'd prefer that Saris come up with a software patch to resolve this issue.

I bought a joule last week specifically because it doesn't experience this issue at this time.