Generic Ant Channel Freezing

I have been getting reports of the Generic Ant channel freezing on both Apps and Data fields. Everything starts and runs like normal, but then at some point the SmO2 and THb values on the screen will freeze. The value in the FIT file will be frozen too. The sensor is continuing to function properly because the data in it's memory continues to be stored properly and it has been verified that a second display device (PC running PerfPro) will continue to receive data from the sensor.

Most reports have been very infrequent, but now I have a user that can't even make a mile run without the problem happening. I have reports from an Edge 520, a VivoActive3, and a Fenix 5.

There is no error log files produced.

The problem resolves by stopping and restarting the App.

One user sent me a full copy of their VA3 watch. I noticed that there is a SNS_ERR.TXT file that has entries with dates that correspond to the freezes.

Does anyone know what the information in this file means or if it might be related to the freezes?

Sensor hub AFE HW ID check failed
Sensor hub AFE HW ID check failed
Sensor hub AFE HW ID check failed
Sensor Hub Reset, v580
01/23/18
00:02:42
5885,1061293
5885,1062293
5885,1063293
5885,1064293
5885,1065292

Sensor Hub Reset, v580
01/23/18
00:37:37
5832,3156758
5885,3157205
5885,3158205
5885,3159206
5885,3160206

Sensor Hub Reset, v580
01/23/18
00:37:41
5832,3156758
5885,3157205
5885,3158205
5885,3159206
5885,3160206

Sensor Hub Reset, v580
03/13/18
22:11:38
5832,20426631
5832,20426632
5832,20426633
5832,20426634
5832,20426635

Sensor Hub Reset, v580
03/13/18
22:47:59
5885,22611329
5885,22612329
6756,22612794
5885,22613329
6756,22613794

Sensor Hub Reset, v580
03/15/18
20:06:30
5885,185721112
6756,185721997
5885,185722112
5885,185723112
5885,185724113

Sensor Hub Reset, v580
03/16/18
19:15:03
5885,269035188
6756,269035427
5885,269035885
6756,269036426
5885,269036886

Sensor Hub Reset, v580
03/17/18
19:33:30
6756,356538014
5885,356538035
5885,356539036
5885,356540035
5885,356541035

Sensor Hub Reset, v580
03/17/18
19:33:34
6756,356538014
5885,356538035
5885,356539036
5885,356540035
5885,356541035

Sensor Hub Reset, v580
03/18/18
20:35:56
5885,446686717
6756,446687659
5885,446687717
6756,446688660
5885,446688718

Sensor Hub Reset, v580
03/19/18
00:22:32
5832,460283927
5832,460283928
5832,460283929
5832,460283930
5832,460283931

Sensor Hub Reset, v580
03/19/18
00:22:36
5832,460283927
5832,460283928
5832,460283929
5832,460283930
5832,460283931

lcj2 over 7 years ago

I have heard and seen of the issue you describe but might not be the same thing. Specifically the application will appear to freeze but the native data continues to record. So for example, I have a generic channel open to connect to ANT-FE and then use the native sensor API for heart rate. The Connect IQ general connection will fail but the native heart rate is recorded in the file. I was never able to figure out what happened. The FIT file having the same frozen value till the end is expected since the value written to the FIT file will be the same unless you actively change it which doesn't occur because you're not receiving ANT pages ... I don't believe that it writes on FIT value per call to record data.

MoxyRoger over 7 years ago

lcj2, this sounds like the same issue. The symptoms sound the same.

Here's a FIT file that has data before and after freezing. The freeze is at 00:05:34 This is from a Moxy data field. It's interesting that the HR made a sudden jump in value at the exact same time as the freeze. It was at 165 bpm before the SmO2 freeze and 70 bpm immediately after. There's also something like 6 seconds of data missing at the time of the freeze plus some additional header-like rows written in the FIT file at the time of the freeze. I don't know if any of this is a cause or and effect of the freeze. This was on a VA3. I don't know if they were using optical HR or a HR strap. The user wasn't doing anything at the time of the freeze. You can see that cadence and pace are smooth right through the freeze event.

http://www.moxymonitor.com/wp-content/uploads/FitData.jpg

https://connect.garmin.com/modern/activity/2565964608

MoxyRoger over 7 years ago

Here's an example of a data field Generic ANT data freezing on a 520. The freeze occurs at 1:02:42. There is a short gap in the HR data about the same time. Also the temperature made a step change after the freeze. I don't know where the temperature data was coming from.

https://connect.garmin.com/modern/activity/2566556118

jim_m_58 over 7 years ago

Roger, with the 520, it can't pair with a Tempe, so that data is from the internal temperature sensor.

Brandon.ConnectIQ over 7 years ago

I've got a ticket reported to have this investigated further.