Use the following settings, for a 5 second countdown timer which beeps/vibes whenever the countdown reaches 0
(The forums are broken, so please replace square brackets with round brackets below)
Formula: Alert[Timer gte 5 and Round(timer) mod 5 gte 0 and Round(timer) mod 5 lte 2] ; 5 - [Round(timer) mod 5] Display Format: Time
Explanation Timer: The unpaused activity time, in decimal seconds Round[Timer]: Timer, rounded the nearest whole number Round[Timer] mod 5: The activity time, in the range 0 to 4 seconds (resets every 5 seconds). X Mod Y gives you the remainder of dividing X by Y. Alert[X]: Triggers a beep/vibe (according to device settings), when the condition X goes from false to true gte: Greater than or equal to lte: Less than or equal to
The first part of the formula specifies the beep/vibe alert. The alert condition becomes true when the timer hits 5, 10, 15, etc. (so you can get an alert then) and becomes false at 7, 12, 17, etc (so you can get the next alert).
The second part, after the semicolon, specifies what to display in the data field -- the countdown from 5 seconds to 0.
The formula looks a little more complicated than it might need to be because the formula is evaluated roughly (but not exactly) every second, and sometimes a bit longer (e.g. 1.2 seconds). (It's just how Connect IQ works, and out of the app's control).
Hence the rounding and the 2 second "leeway" in the alert condition. (You can't just use timer mod 5 eq 0, unfortunately...). In general, I wouldn't round anything except the final result (which is normally automatically rounded), but since we're dealing with pretty small numbers (5 seconds), it makes sense here. (Rounding the numbers before doing the calculations for the 5-second alert and countdown display will make the results a bit more stable. If it was, say, a 30 second countdown, it really wouldn't matter.)