This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

1040 Cadence invalid RPMs

On my 1040 I have the Cadence sensor and am seeing that it is often recording values that I feel are impossible on a bike.

I first noticed this when it had a reading of 2 RPM when I was free-wheeling down a hill. Others times values of 1 RPM. For me that is not realistically possible, especially as I stop pedalling immediately, no slow down revs. This does not happen every time, but occasionally on stop pedalling as well as start. To test one time a started up spinning, it showed 1 RPM then went directly to 105 RPM. (There is an inherent lag in the RPM registering due to the sensor sending to the device, however this was roughly the same for both the 1000 & 1040.)

Yesterday I had it at 4 RPM on a downhill for at least 10secs. I also had the Edge 1000 up to test this problem, the 1000 does not display this trait, it goes from xRPM > 0 > xRPM where x equals a valid RPM. 

This is not only annoying when you look at it, as it is yet another 1040 bug, but also affects the avg. Cadence. Yesterday the 1000 had avg. 78, the 1040 avg. 74. This is one of my metrics for seeing how well I am going, 

Version 12.16, non-Solar.

  • All Garmins do this.  What’s your point. You really need to think about sending the unit back as clearly from the amount of posts your doing you can’t seem to enjoy your device. You just seem to be trying as hard as possible to find any fault, perceived or otherwise, and come on this forum to post. 

  • Surely the Edge is just showing the Cadence being broadcast by the sensor?  If it’s showing 1 then that the sensors fault,  A lag would just be a delay before it changes, but that will also be mainly down to the sensor have to calculate the RPM over a set period of time.  For me, it is my Garmin Vector 3 pedals that broadcast the cadence.  I checked today and it seems to be working fine.  If I stop pedalling it goes to 0 in 2-3 secs.  When I start pedalling it takes just 2-3 secs to show the actual cadence, as expected.

  • Read my post, I had the 1000 also on the stem. It does NOT do this and never has! . This is new for me on the 1040! It is not possible on a bike to do that cadence. I also tried just turning slowly, it didn’t pick that up, so the 1040 is somehow finding revs that are fully invalid.

    So what devices do you have for the statement - “all Garmin do this” - what are you talking about? Certainly not my 1000!

    The 1040 is abysmal considering it is 8 years on from the 1000 and the price is extremely high considering the functionality.

    As for finding any fault, there are far too many to find, look at all the posts here. I have zero perceived faults, they are all fact and proven.

    Do you work for Garmin? Stay on Twatter, that’s the place to abuse people.

  • Read my post, a cadence of 1, 2 4, is not realistically possible on a bike especially if you stop pedalling directly. A cadence of 4 for 10secs when free-wheeling downhill is not 2-3secs, which I also state is the normal lag of the sensor to send zo the device.

    Read the part where I state that the 1000, with the same lag, was recording, after the lag, the correct 0 revs. The 1040 staying on a crazy cadence for up to 10secs and the ride avg. cadence significantly different for a 2hr ride.

    Your pedals and the standard sensor are not the same thing. I had the same standard cadence sensor for both devices mounted.

  • Easy enough fix. Please return it as soon as possible.  I think your other equipment is allergic to Garmin's.

    Peace out.

  • Would those advocating the pathetic "return it" please stop the petulant and sad advice.

    Why don't you to tell Garmin to fix all the basic 1040 problems - Gradient; Temperature; Cadence and all rest.

    Garmin need to sit down and look at all the issues raised in this forum and start a project to analyse and resolve them, that is the best "easy fix".

    Going back to how the 1000 worked would help that in several areas, the main being Gradient and Cadence.

    ______________________________________________

    Just another one for them:

    Is there anybody at Garmin who is not embarrassed by the fact the "Make a U-turn" is still based on car navigation after all these years? This one is very easy to fix

    "Make a U-turn when convenient or follow the suggested route"

    - end of problem.

  • You are of course correct. It is unfair for me to say return it and end your problems.

    I also think it's utter crap the amount of bitches and moans there ate about the 1040. I feel that garmin has been quite pro active in fixing issues since the release.  

    I'm sick of reading about people whining about certain issues that really only affect them and thinking that garmin will actually do something about it. I would prefer they open a ticket and try and get a resolution that way.  

    Is the 1040 perfect?  Not even close. For a new garmin product it is pretty darn good.

    In the future I will just try to ignore the useless posts on this forum.  

    Thanks for setting me straight.

    Good luck to you.