Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Cateye V3-second sensor problem

  • 16-01-2012 3:48pm
    #1
    Registered Users, Registered Users 2 Posts: 415 ✭✭


    I acquired a second speed/cadence sensor for a Cateye V3. The computer is not picking it up. I've checked the 'cateye-knowledgebase' website and tried what it recommended (i.e have sensors 5 m apart when syncing the second, and checking the battery followed by pressing the reset button). Maybe I'm missing something obvious? Has anyone had, and overcome, this problem??

    Thanks


Comments

  • Registered Users, Registered Users 2 Posts: 1,100 ✭✭✭clog


    This is from my v3 manual but it worked fine for me.
    Press menu. Go to sensor id(press m1 until it comes up) then press SSE. press m1 again twice to get SP2 showing . Press SSE and spin crank/wheel while unit is searching , unit will search for a while and then should come up Id ok. Press menu twice to confirm and return to home screen.
    hope this helps


  • Registered Users, Registered Users 2 Posts: 182 ✭✭velogirl


    100Suns wrote: »
    I acquired a second speed/cadence sensor for a Cateye V3. The computer is not picking it up. I've checked the 'cateye-knowledgebase' website and tried what it recommended (i.e have sensors 5 m apart when syncing the second, and checking the battery followed by pressing the reset button). Maybe I'm missing something obvious? Has anyone had, and overcome, this problem??

    Thanks

    I had one of these - I still have the remains of it somewhere. I had nothing but trouble with mine from the word go. It sounds as if yours is not picking up anything - I would check the batterys first - they don't last very long and the ones they come with die very easily.

    I found it impossible to get both the speed and cadence to work at the same time - I could have either one or the other - not both. In the end I gave up and bought a Garmin 500 and love it - everything works perfectly and all at the same time.


  • Registered Users, Registered Users 2 Posts: 415 ✭✭100Suns


    clog wrote: »
    This is from my v3 manual but it worked fine for me.
    Press menu. Go to sensor id(press m1 until it comes up) then press SSE. press m1 again twice to get SP2 showing . Press SSE and spin crank/wheel while unit is searching , unit will search for a while and then should come up Id ok. Press menu twice to confirm and return to home screen.
    hope this helps

    Thanks clog. That sorted it.

    Note to self: Keep manuals somewhere safe.


  • Registered Users, Registered Users 2 Posts: 415 ✭✭100Suns


    velogirl wrote: »
    I had one of these - I still have the remains of it somewhere. I had nothing but trouble with mine from the word go. It sounds as if yours is not picking up anything - I would check the batterys first - they don't last very long and the ones they come with die very easily.

    I found it impossible to get both the speed and cadence to work at the same time - I could have either one or the other - not both. In the end I gave up and bought a Garmin 500 and love it - everything works perfectly and all at the same time.

    I've had mine for a few months and apart from the above problem which is wholly attributable to my tecnhical ineptitude, I think it's a great piece of kit. I'd put it way ahead of my previous Polar CS500 which was troublesome, had a poor display function and generally annoyed me. I haven't tried Garmin yet for fear it's way too technical.


Advertisement