Related
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

Sensor Connection Attempt while in Activity - Possible Bug

badbri
over 5 years ago

There is a difference when searching for an external sensor while in-activity vs not.  

This morning I attempted to find a lost Tempe on a mountain bike trail by repeatedly attempting to connect to it when in the vicinity of where I think I lost it.  But while in a bike activity, going to menu/sensors/tempe/connect it will search for 10-15 seconds and then just timeout back to the activity.  When I do this NOT in an activity, it gives me a "couldn't connect" error, then times-out back to the sensor screen (which is preferable).

Is this by design (I wouldn't think so), and if not am I doing something wrong here? 

I'm also open to suggestions on how to search for this missing Tempe device.  Unfortunately my 945 apparently IMMEDIATELY defaulted to internal temperature when the tempe came off my shoe because I can't discern any "blip" or gap in temperature recording by looking at the activity where it was lost.

  • 0 over 5 years ago

    I would guess that this is the intended behaviour and therefore by definition not a bug.

    I have just put a quick and dirty Connect IQ datafield together that searches for Tempe Sensors and sounds an alarm if any is found. You can find it on the app store here once it is approved by Garmin (normally takes a day or two).

    If you use this make sure you disable the Tempe in the sensor menu on the watch. Also be aware that Tempe sensors only transmit every 30 seconds or so and they can have quite a range (I am sitting at my PC and pick up the one in my shed in the garden, a good few meters away).  If you do pick  up a signal from your Tempe you'll have to find a way to home in on it to locate it.

    Good luck, hope you find it.

  • 0 over 5 years ago in reply to CloggyAbroad

    That is fantastic, thanks very much for doing that.

    I'm aware of how far the Tempe can transmit, I often pick one up attached to some old running shoes in my garage when I'm in my shed 40yds away getting ready to bike.  But in this case if I can narrow it down to a 50 yard stretch I'm fairly confident I can locate it on this patch of trail.

    I'm kinda tired of losing these things as they get detached from my shoe, I'm on pace for having to buy a new $26 one every year now.  :-(

  • 0 over 5 years ago
    badbri said:
    it gives me a "couldn't connect" error, then times-out back to the sensor screen

    First, I'm sorry to hear about your lost Tempe. I have done this myself during a muddy trail race so I feel your pain. Frowning2

    I am only able to recreate this, as I cannot get the 945 to search for a sensor and then time out with no message. I have tried this: 

    • In an activity with the timer running
    • In an activity with the timer paused
    • In an activity without starting the timer
    • From the main menu

    What scenario exactly were you able to get the search to timeout with no message. Also, thank you for the CIQ solution. I hope that helps in the search. 

  • Former Member
    0 Former Member over 5 years ago in reply to badbri

    badbri said:
    But in this case if I can narrow it down to a 50 yard stretch I'm fairly confident I can locate it on this patch of trail.

    perhaps you can verify this by uploading your fit file here and check for rising temp?

    this is my tempe

    and this is an example data record with temp

    happy & safe sporting

  • 0 over 5 years ago in reply to Former Member

    That's interesting, so you're proposing to check for rising temps within that long list of code?  Would that tell me anything different than just looking at the temp graph in a view of the activity?

  • 0 over 5 years ago in reply to Garmin-Blake

    I am only able to recreate this, as I cannot get the 945 to search for a sensor and then time out with no message. I have tried this: 

    • In an activity with the timer running
    • In an activity with the timer paused
    • In an activity without starting the timer
    • From the main menu

    Thanks Blake, I've tried to respond/quote this reply a few times now and it keeps not posting - in any event, it's bullet 1 a Bike activity with the timer running.

  • 0 over 5 years ago in reply to Garmin-Blake

    If I search for a Tempe while in an activity with timer running it times out without a warning and returns to the activity.

    If I search while in an activity before starting the timer or with the timer paused (using the stop button but not saving it)  it times out with a warning and the option to search again.

    It somehow makes sense to me that during an activity with the timer running you don't want to get involved in lengthy searches for external sensors and therefore it was intended to work like this.

  • Former Member
    0 Former Member over 5 years ago in reply to badbri

    badbri said:
    That's interesting, so you're proposing to check for rising temps within that long list of code?  Would that tell me anything different than just looking at the temp graph in a view of the activity?

    nice, you found it, happy to have been of service Smile

    happy & safe sporting

  • 0 over 5 years ago in reply to CloggyAbroad
    CloggyAbroad said:

    If I search while in an activity before starting the timer or with the timer paused (using the stop button but not saving it)  it times out with a warning and the option to search again.

    It somehow makes sense to me that during an activity with the timer running you don't want to get involved in lengthy searches for external sensors and therefore it was intended to work like this.

    I can sorta see that but to me it seems odd that in one case you have an option to dismiss/re-search and then another you don't even have the option.  That seems like an oversight.

  • 0 over 5 years ago

    the Tempe finder datafield has been approved in time to go Tempe hunting during the weekend. Let me know how you get on.