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 now just realized that the cpu Saris replaced for me about a year ago didn't have the ANT+ upgrade but the one I received when they shipped my wheel back to me did have the upgrade. I'm seeing a common denominator here. What's hard to tell is if there is another variable that factors into the problem. For example, is it a combination of having the ANT+ upgrade with the latest firmware? I'm pretty sure I was running the latest firmware on my previous cpu but not positive.

Anyone seeing this problem who doesn't have the ANT+ upgrade?

Most importantly, why is Saris continuing to ignore us?

Thanks, Chris

First off an apology- certainly did not mean to make anybody feel ignored or slighted by our silence on the forum and lack of info. for those who have called in.

But, we've heard you loud and clear and are actively pursuing this issue. As you all know from reviewing this thread the issue isn't easy to pin down but you've all contributed a valuable piece to puzzle. We think we have the root cause isolated to the LYC firmware but need to confirm via some testing. We will then make the necessary patches available via PowerAgent.

Sorry for the lack of detail here but we're still investigating and I don't want to jump to any conclusions and give anybody the wrong idea. More details soon.