I've had this issue reported on the released version of the MoxyRun App running on a Fenix 3. I think I've reproduced the issue on a VivoActive, but I'm not certain this is the same issue as reported.
The problem only occurs once in a while, not every time. It seems like it will happen 5 times in a row and then I can't make it happen at all for many tries in a row.
To cause the problem:
1) Open the App
2) Do not turn on the Moxy sensor, but wait for the searching to time out ( > 25 seconds...I don't push a timeout message, but I should add that)
3) Turn the Moxy sensor on
4) Press the menu button and select Pair to Moxy sensor.
Most of the time it pairs just fine and continues to function properly.
Sometimes it won't find the Moxy sitting right next to the watch. If I back out of the searching view and then select pair to a Moxy sensor again, it will usually find the Moxy sensor. Sometimes this takes 2 or 3 tries. Once it finds the Moxy, I go back to the main screen and the SmO2 and THb values are frozen at a certain value. Everything else in the App works fine.
I added in some println's to capture what's going on when it fails like this.
function onMessage(msg) {
// Parse the payload
var payload = msg.getPayload();
Sys.println("Time: " + Sys.getClockTime().hour + ":" + Sys.getClockTime().min + ":" + Sys.getClockTime().sec + " msgId: " + msg.messageId.toNumber());
for (var i = 0; i < 2; i++) {
Sys.println("p" + i + " " + (payload.toNumber() & 0xFF));
}
if (Ant.MSG_ID_BROADCAST_DATA == msg.messageId) {
[/CODE]
Below is the output that I get from the printlns. I added in the text that says what each event message is afterwards.
Everything looks fine up through the "EVENT_RX_SEARCH_TIMEOUT" message. When I tried again to pair at about 7:51:17, I should have had a very similar series of messages again, but instead, I got 1 close message, then 1 broadcast message, then 1 close message.
I don't know where the close message is coming from. I don't think I'm sending it.
It showed on the screen that it actually paired to the sensor so I'm assuming that the values in the 1 broadcast message are the values that were frozen on the screen, but I didn't print the whole message, so I don't know for sure.
Any ideas on what I need to do differently to get this to function properly? Is this related to the issues that the Tempe app had with pairing? I can send the code in if needed.
Time: 7:46:15 msgId: 64
p0 110 Lib Config
p1 0
Time: 7:46:16 msgId: 64
p0 65 Unassign Channel
p1 0
Time: 7:46:17 msgId: 64
p0 66 Assign Channel
p1 0
Time: 7:46:18 msgId: 64
p0 81 Channel ID
p1 0
Time: 7:46:18 msgId: 64
p0 69 Channel RF Freq
p1 0
Time: 7:46:19 msgId: 64
p0 67 Channel Period
p1 0
Time: 7:46:20 msgId: 64
p0 99 Low Priority Search Timeout
p1 0
Time: 7:46:20 msgId: 64
p0 68 Search Timeout
p1 0
Time: 7:46:21 msgId: 64
p0 71 Transmit Power
p1 0
Time: 7:46:28 msgId: 64
p0 71 Transmit Power
p1 0
Time: 7:46:34 msgId: 64
p0 71 Transmit Power
p1 0
Time: 7:46:40 msgId: 64
p0 71 Transmit Power
p1 0
Time: 7:46:45 msgId: 64
p0 1
p1 1 EVENT_RX_SEARCH_TIMEOUT
Time: 7:51:17 msgId: 64
p0 76 Close Channel
p1 0
Time: 7:51:53 msgId: 78
p0 1 Broadcast Data
p1 221
Time: 7:51:53 msgId: 64
p0 76 Close Channel
p1 0
