New error message "speed is excessive" ?!

Egika

Here is some Q&A about abnormal speed message:

Q2. If user dismiss the reminder or reminder disappears after time out, does the reminder pop up again? Just pops up once?
ANSWER: Just once. This count is reset when the exercise state is changed. That includes pausing.

Q3. Under what conditions will the current speed be determined as an abnormal speed? Is there any basis for judgment?
ANSWER: The abnormal speed is checked only in selected activities: running, trail running, walking, trekking, hiking, golf, nordic walking, orienteering and open water swimming. Resume reminder is active always.

@surfboomerang abnormal speed should not be active during windsurfing activities. If it is and you have not used a different sport mode, please let me know. Thx

surfboomerang

@Egika I’m pretty sure I got the warning last time I was windsurfing. I do however use a custom profile. Don’t know if that makes any difference?

Egika

@surfboomerang maybe, but should not.
If you can confirm, I can file a bug.

surfboomerang

@Egika ok, I’ll keep an eye on it once I’m back home from my holiday. And when there is sufficient wind to gain some speed

surfboomerang

@Egika I was able to reproduce it on a local bus ride
The basic windsurfing profile doesn’t give the excessive speed warning. My custom windsuring profile still does.

Egika

@surfboomerang thank you for checking.
Bug reported

surfboomerang

@Egika Not a big deal, but this issue isn’t fixed with the latest firmware

Inge Nallsson

@Egika said in New error message "speed is excessive" ?!:

@MRC01 the abnormal speed detection has been there for around a year or so.
It was introduced together with the moving while paused message.
Nothing new and buggy here. Working as designed.

I am a new user (3 weeks) of a Race S. At my last run, or second from last, I was surprised by this ‘moving while paused’ message since it happened while the watch was saving the activity. True, I was moving - I always walk at least 3 minutes after a run - but shouldn’t there be a kind of embargo on that message while doing such an important activity as saving?

Am on latest FW 2.39.20 and the saving of the 70 minutes run took longer than the shorter (about 30 minutes) runs I had done on the previous FW 2.37.48. Perhaps the quicker savings is why I haven’t encountered the message before.

Dimitrios Kanellopoulos

@Inge-Nallsson since before save it’s pause can that be ?

Inge Nallsson

@Dimitrios-Kanellopoulos No, after having clicked the upper right button to indicate a STOP, I immediately clicked the lower (red marked) save button.

Inge Nallsson

@Inge-Nallsson Should perhaps add that I use a custom profile of the Run activity but have only rearranged data fields on the first screen, not added other screens from the default.