S9 (2.4.14) 'Calibrate FusedTrack' interface problem. Suunto Case #01853829

Dimitrios Kanellopoulos

@surfboomerang Ok give me some time. @kolyany4 btw goes for HW replacement.

surfboomerang

@Dimitrios-Kanellopoulos Ok, I’m curious if this fixes the issue for @kolyany4.

In my case I have never had to calibrate my compass during an activity, nor had messed up tracks. But I almost always use the GPS best setting. So maybe I was lucky all the time.

Dimitrios Kanellopoulos

@surfboomerang lets see how it goes …

Dimitrios Kanellopoulos

I am also curious

kolyany4

@surfboomerang
I have requested to HW replacement, and last notification I’ve received was a week ago about my request being analyzed by Suunto Headquarters. Though, I’m aware that @Dimitrios-Kanellopoulos is pushing my request a lot from his side.

But I almost always use the GPS best setting

As I understand, compass is not used in “GPS best” mode in order to fill gaps between “GPS-located”-points. Thus, in “GPS best” mode such error should not occur.

Dimitrios Kanellopoulos

@kolyany4 I am on your case. It takes a few due to Russia service etc

Dimitrios Kanellopoulos

Hi ONLY FOR THE COMPASS calibration perhaps we have found a bug.

I want to keep this seperate from @kolyany4 that was loosing GPS.

Also this relates to best mode as I had been asked for compass calibration a few times.

I ll keep you updated

surfboomerang

@Dimitrios-Kanellopoulos Good to hear you found something.

kolyany4

Yesterday I got a replacement watch from local service, thanks to Dimitrios.

And I just had a half of my usual run, which, unfortunately, demonstrate presence of the problem (with replaced watch as well):
1.76 km instead of 2.79 km with persistent request to Calibrate FusedTrack during run.

Here’s what watch has tracked:

while actual track was:

NB. Serial number of previous watch was 18371000xxxx, while S/N of current one is 18481000xxxx.

Dimitrios Kanellopoulos

@kolyany4 Afaik that does not happen with performance right?

Can I ask, I would love to see how it performs in another area.

We had cases in Russia where users could not get GPS due to some areas being scrambled.

Can this be the case here ?

kolyany4

@Dimitrios-Kanellopoulos

Afaik that does not happen with performance right?

Yes. In performance mode no such problem is encountered.

Can this be the case here ?

I doubt due to following reasons:

I use Glonass mode On.
I run in a park far from any areas where such scrambling could be reasonable.
at last, but not at least, Actual track I provide from runtastic app which is launched on my Sony Xperia XZ1 Compact smartphone (with probably the same GPS chip) during my run. Thus, if GPS/Glonass signal were actually scrambled, then, I think, it would influence on track created by smartphone app.

Do you agree?

Dimitrios Kanellopoulos

@kolyany4 I do agree. Pffff…

This is getting more strange.

Please PM me with the logs

kolyany4

@Dimitrios-Kanellopoulos

Here’s part of my log:
NB. had to cold-reset watch in order to finish my exercise.

#2674 27.12.2018 10:21:05 : EVT LOGGER : Exercise started
#2675 27.12.2018 10:21:05 : ERR WBMAIN : *0: app 558 Event 37 805b0315
#2676 27.12.2018 10:21:05 : ERR WBMAIN : 1: mea 0 Event 7 80255803
#2677 27.12.2018 10:21:05 : ERR WBMAIN : 2: ui 468 Wait 0 00000000
#2678 27.12.2018 10:21:05 : TRC GPS : Full GNSS data subscribed
#2679 27.12.2018 10:21:05 : EVT TRAININGLAB : TLab: ~Mode T 4291 + 3496 A 160 + 230
#2680 27.12.2018 10:21:05 : EVT TRAININGLAB : TLab: Change mode 2 -> 3
#2681 27.12.2018 10:21:05 : EVT TRAININGLAB : ModeUnsub:2198
#2682 27.12.2018 10:21:05 : EVT TRAININGLAB : ModeSub:4400
#2683 27.12.2018 10:21:07 : ERR WBMAIN : *0: app 2028 Event 4 805b3365
#2684 27.12.2018 10:21:07 : ERR WBMAIN : 1: mea 9 Wait 0 00000000
#2685 27.12.2018 10:21:07 : ERR WBMAIN : 2: ui 51 Proc 0 00000000
#2686 27.12.2018 10:21:07 : EVT TRAININGLAB : TLab: Input source 1
#2687 27.12.2018 10:21:07 : EVT DRT : 1914728 tpmrun:87281 tpmwait:38421 tpmstop:1786957
#2688 27.12.2018 10:21:07 : EVT DRT : 1914728 cbletx:2221 cblerx:2152 cgnssr:310784
#2689 27.12.2018 10:21:07 : EVT ANALYTICS : Battery-> 3 soc:93
#2690 27.12.2018 10:21:07 : EVT ANALYTICS : #FusHr src:2 time:0
#2691 27.12.2018 10:21:07 : EVT ANALYTICS : #Act id:3
#2692 27.12.2018 10:21:07 : EVT ANALYTICS : #GPS mode:OK soc:-1
#2693 27.12.2018 10:23:05 : TRC GPS : preBurner time 120s done
#2694 27.12.2018 10:23:07 : TRC GPS : Done:GST
#2695 27.12.2018 10:23:07 : TRC GPS : GSTP repeated 6 times
#2696 27.12.2018 10:23:07 : TRC GPS : Send: GSOP 2 120000 0
#2697 27.12.2018 10:23:07 : TRC GPS : Done:GSO
#2698 27.12.2018 10:23:07 : TRC GPS : Send: GSP
#2699 27.12.2018 10:23:07 : TRC GPS : Done:GSP
#2700 27.12.2018 10:23:07 : TRC GPS : Gnss Filter mode: Default
#2701 27.12.2018 10:23:09 : EVT SPEEDFUSION : INFO # speed source 3
#2702 27.12.2018 10:23:19 : EVT SPEEDFUSION : INFO # speed source 2
#2703 27.12.2018 10:42:14 : EVT EXT_FLASH : ExtFID 0x20,0xba,0x19
#2704 27.12.2018 10:42:14 : TRC APPLICATION : Start 2.5.18 in mode 5 (asked 5h)

PS. Unfortunately, I’ve failed to find how to send (attach) log-files and send them as private message (PM) via this forum…

Dimitrios Kanellopoulos

Hey wait! Are you using walking ?

kolyany4

@Dimitrios-Kanellopoulos
Nope.
There were 2 exercises today:
1st - Running (which results I’m showing here),
2nd - Walking (on a way back… tried compass - bread crumps test)…

Dimitrios Kanellopoulos

Ok just checking because fued track does not work with walking for example

kolyany4

Just finished another run with GPS==OK to ensure whether problem still exists.
For short, it does:
only 0.12 km instead of 5.17 km has been tracked.

Sent Suunto log ID: 566938655933400

Here’s data collected by watch:

Here’s actual track:

Dimitrios Kanellopoulos

@Brad_Olwin anything to suggest ?

Brad_Olwin

I have used both Endurance and Ultra modes with no serious issues. When setting the battery profile to either Endurance or Ultra, a compass calibration request will appear. Once finished, the exercise can be started. I am getting requests to calibrate the compass during the run. I did not have the screens locked but in Ultra mode the watch does go dark. I recalibrated the compass and all was fine. When the calibration is called for the watch is not responsive, button presses and swipes do not work. I believe this is by design. I am a bit confused by your problem as I have not seen a “Calibrate FusedTrack” only a request for compass calibration. Below is a comparison screenshot for a run with two S9 watches. One in Performance mode and one in Ultra mode. The distances are not exact between the two watches but they are close and considering Ultra mode is an infrequent GPS fix this is not surprising. I do not understand what your specific problem is. If you are interrupting the compass calibration you will likely not obtain an accurate track. It is important to calibrate away from buildings, etc. if possible. For me, both Endurance and Ultra modes are working as designed. I think you can agree that the tracks below are very similar. Green is ultra and pink is performance. The watch normally should not ask to recalibrate during a run AFIAK. During my short run, I was asked to recalibrate twice, which I did.
Distance Ultra 9.06 km; Performance 9.28 km

I would suggest that you first do a soft reset (upper button for 12s) do NOT ignore the compass calibration and do not try to exit by button presses or screen swipes, perform the calibration until successful. This usually requires 30s of figure 8 movements for me. When you can then start the exercise. If a calibration request occurs again, perform the calibration until it is successful. Then see if your tracks are ok. If not perform a hard reset and follow the above instructions. If your distance and tracks are not close to the distance and tracks you have run then I would believe you may have a hardware issue. This is about all I can suggest as these features are working as designed on two S9 watches I have.

kolyany4

@Brad_Olwin
could you try custom mode (GPS = OK, Low color = On, Display timeout = On, Touch screen disabled) with Sensors = Measure HR during your run?

The watch normally should not ask to recalibrate during a run AFIAK.

Agreed. But, I’m facing this unwanted/buggy behaviour of the watch. Of two watches, to be specific, the old watch and one I got as a warranty replacement.

do NOT ignore the compass calibration and do not try to exit by button presses or screen swipes

I always perform requested calibration before run till it finishes. However, if watch asks me to recalibrate during run, I can’t do that (since the watch is under my sleeve), and, frankly speaking, I do not want to do any calibration during (in the middle of) my run…