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

kolyany4

@Dimitrios-Kanellopoulos said in S9 (2.4.14) 'Calibrate FusedTrack' interface problem. Suunto Case #01853829:

@kolyany4 Hmmm. What I would do is not to use the fused track and keep the navigation screen on. That screen also requires the compass to be calibrated. So it should expose the same behavior. Then we can wipe out a potential SW bug (if that also happens with normal navigation).

Will it suffice if I’ll do that using Walking Exercise?
What I should pay attention to during such test (with GPS==Best, NavScreen(e.g. Breadcrumb)==On)?

But hey I am no expert, but just a tester and doing my best to guess and help.

No worries!
I just wondered, whether you have secret kung-fu you can share with ordinary user to ease locate/eliminate the problem…

Dimitrios Kanellopoulos

Yeah walking is even better.

The navigation (breadcrumbs) screen uses the compass when you are static. Else it uses the bearing.

So I would:

Walk a bit, stop and check if it asks for compass calibration.

Repeat the above a couple of times. Compass calibration should be asked only once.

kolyany4

Ok.
Gone to make that test…

kolyany4

@Dimitrios-Kanellopoulos
Calibrated compass before walking.
Set Battery mode = Performance.
During walk it showed navigation breadcramp ok.
But, once I stopped longer than 10 seconds watch asked for compass calibration.

After about 30 minutes of such walking I’ve stopped exercise and went directly to General->Navigation->Compass.

While staying I’ve calibrated compass several times and tried to use compass (while not moving). Calibration tooks about 30-60 moves which is strange, though I was in a park (surrounded by trees).

Compass screen appeared a couple of times for a few seconds, and then screen with “Calibrate compass” appears permanently again.

My questions are:

Does internal compass require open sky view (by some reason) to calibrate?
How one can check what data has been stored as a result of calibration?
Should compass work inside appartment (even with errors caused by some electromagnetic emmiters)?

Dimitrios Kanellopoulos

In my experience I dont have to calibrate compass more than once when walking or using it.

I tend to feel its a hardware issue.

No compass can be calibrated indoors etc. It just might not work so great depending to metals etc.
I dont know if that is possible.
Yes

kolyany4

@Dimitrios-Kanellopoulos

How one can understand why watch keep asking to calibrate compass each time General->Navigation->Compass is entered?

Would there be any suggestions to solve this issue except reflashing of the watch?

What proof I can give to my local dealer that there’s HW problem in order to initiate guarantee change of the watch?

Dimitrios Kanellopoulos

Hmmm. There is no way yo figure that out except what other users experience.

I just tried it out, I had not calibrated the compass since 2 days and it did not ask me now.

Perhaps do a drag and drop on the fw to the suuntolink.

Find the fw file in the suunto link folder then drag and drop it to suuntolink. That should flash the fw without wipe of data. The fw file should be something like Ibiza
Zip

Dimitrios Kanellopoulos

You can ask for repair or replacement directly with suunto.

If you have tried all reset options that is the last way to go.

In this case open the request and I can help perhaps. But let’s first reach this point.

kolyany4

@Dimitrios-Kanellopoulos

Just reflashed according to your instruction (saw v.2.4.14 -> v 2.4.14.1170 during reflash).
Recalibrated compass.

Now when I enter General->Navigation->Compass watch does not requires me to do calibration.
Seems, problem with constant ‘Compass recalibration’ is solved.

Perhaps, problem with faulty tracks will go away as well - I will check that during next few days.

Thanks a lot!

PS. Perhaps, this trick regarding compass calibration and working steadily (without persistent recalibration request when entering General->Navigation->Compass) should be placed into the FAQ (as a prerequisitive for correct work of FusedTrack) …

Dimitrios Kanellopoulos

@kolyany4 yeah. I opened a bug about this. Let’s see.

Keep me posted please about the outcome of this.

Brad_Olwin

@kolyany4 replying to your off topic. If you turn off sleep tracking and 24/7 HR monitoring and have 1h or 2h exercise per day on Performance mode the battery will last a long time between charges.

kolyany4

@Brad_Olwin said in S9 (2.4.14) 'Calibrate FusedTrack' interface problem. Suunto Case #01853829:

@kolyany4 replying to your off topic. If you turn off sleep tracking and 24/7 HR monitoring and have 1h or 2h exercise per day on Performance mode the battery will last a long time between charges.

Thanks for hint, but I need 24/7 WHR & sleep tracking.
Otherwise (if I wouldn’t need WHR), I’d take entirely another product.

btw, actual off-topic was related to missing information about MIL-STD-810G compliance of S9 Baro.

Brad_Olwin

@kolyany4 The 24/7 HR and Sleep Tracking are the biggest hits on my battery. So if you need them I guess your are stuck. Personally, I would like to see the Sleep and HR used for recovery and health, I am not interested in just tracking. I can concur with @Dimitrios-Kanellopoulos as my FusedTrack does not reapeatedly ask for calibration. If I switch from Performance to either Endurance or Ultra during a run, i will be asked for a calibration but only once. Hope you get it resolved.

kolyany4

@Dimitrios-Kanellopoulos
Here’s intermediate follow-up.

Today during morning run I’ve encountered both the same initial problem as earlier (constant ‘FusedTrack calibration’ message) and ‘compass calibration’ message as soon as I enter General->Navigation->Compass.
Tried to calibrate both compass and FusedTrack several times during run, but it didn’t helped.

As soon as I’ve returned home I calibrated compass again, but strangely watch compass constantly pointed to the North wrong (in opposite direction).
I explicitly checked temperature that watch showed, at it was 14 degrees of Celsius at that time.

Lately, at the evening I’ve entered General->Navigation->Compass and watch both did not asked again for ‘compass calibration’ and pointed to the North correctly. At that moment watch showed temperature about 28 degrees of Celsius.

And here is my question:
Is there any problem expected with compass functionality in low temperature conditions (about 0 degrees of Celsius)?

Dimitrios Kanellopoulos

I dont know to be honest

Brad_Olwin

@kolyany4 I use my watch for SkiMo this time of year in low temps and no issues with compass. I will know more this weekend as well.

kolyany4

@Dimitrios-Kanellopoulos said in S9 (2.4.14) 'Calibrate FusedTrack' interface problem. Suunto Case #01853829:

I dont know to be honest

Hope, that’s not a reason why there’s no MIL-STD-810g compliance notices for S9 Baro…

kolyany4

@Brad_Olwin said in S9 (2.4.14) 'Calibrate FusedTrack' interface problem. Suunto Case #01853829:

@kolyany4 I use my watch for SkiMo this time of year in low temps and no issues with compass. I will know more this weekend as well.

Please, let us know what will be temperature readings on your watch during your tests.

Mff73

@kolyany4

Hi,
Honestly, you may have a defect in HW. Maybe compass component, or something else that make it mad.
If you already reset firmware, and try all @Dimitrios-Kanellopoulos 's tricks, last chance is return back to suunto for repair.
We all suppose you are not wearing magnets or some huge metallic part on you near the watch
Good luck with support, and maybe don’t wait too much for their answer before requesting online a repair (it is more time to wait with a faulty unit )

kolyany4

Today during morning run I covered watch by sleeves (to diminish influence of low temperature).
Unfortunately, encountered the same problem:

Here, what I’ve got from my watch:

And here, what actual track was:

Btw, at the end of running I had to reset watch (to skip ‘FusedTrack calibration’ message) and see temperature readings. Temperature was 22 degrees of Celsius.
Thus, I suppose, that hypothesis of ‘low temperature misbehavior’ is declined.

Taking into account, that exercise started at about 08:24:05, while watch stopped to track movement in about 20 minutes (According to SA “pure” running time was 00:24:49),
following watch logs seems to be interesting:

…
#18695 07.11.2018 08:24:05 : EVT LOGGER : Exercise started
…
#18714 07.11.2018 08:24:19 : EVT SPEEDFUSION : INFO # autopaused
#18715 07.11.2018 08:24:19 : EVT LOGGER : Exercise paused
#18716 07.11.2018 08:24:19 : EVT <Unknown> : Update fusedtrack mode 0
#18717 07.11.2018 08:24:19 : TRC GPS : Unsubscribed
#18718 07.11.2018 08:24:19 : EVT <Unknown> : stopFusedLocation() called and send 0 points to the logg
#18719 07.11.2018 08:24:23 : EVT SPEEDFUSION : INFO # autopause end
#18720 07.11.2018 08:24:23 : EVT PLANNEDMOVES : Start:FALSE
#18721 07.11.2018 08:24:23 : EVT LOGGER : Exercise continue
#18722 07.11.2018 08:24:23 : EVT <Unknown> : Update fusedtrack mode 2
#18723 07.11.2018 08:24:23 : EVT <Unknown> : startFusedLocation() called
#18724 07.11.2018 08:24:23 : TRC GPS : Full GNSS data subscribed
#18725 07.11.2018 08:24:27 : EVT SPEEDFUSION : INFO # autopaused
#18726 07.11.2018 08:24:27 : EVT LOGGER : Exercise paused
#18727 07.11.2018 08:24:27 : EVT <Unknown> : Update fusedtrack mode 0
#18728 07.11.2018 08:24:27 : TRC GPS : Unsubscribed
#18729 07.11.2018 08:24:27 : EVT <Unknown> : stopFusedLocation() called and send 0 points to the logg
#18730 07.11.2018 08:25:15 : EVT SPEEDFUSION : INFO # autopause end
#18731 07.11.2018 08:25:15 : EVT PLANNEDMOVES : Start:FALSE
#18732 07.11.2018 08:25:15 : EVT LOGGER : Exercise continue
#18733 07.11.2018 08:25:15 : EVT <Unknown> : Update fusedtrack mode 2
#18734 07.11.2018 08:25:15 : EVT <Unknown> : startFusedLocation() called
#18735 07.11.2018 08:25:15 : TRC GPS : Full GNSS data subscribed
#18736 07.11.2018 08:38:28 : EVT ALTIFUSION : Altitude search failed
#18737 07.11.2018 08:38:28 : EVT ALTIFUSION : Init AltiBaro
#18738 07.11.2018 08:38:28 : TRC GPS : Full GNSS data subscribed
#18739 07.11.2018 08:38:28 : TRC GPS : GnssServiceLevel::OK or GOOD
#18740 07.11.2018 08:38:29 : TRC GPS : Done:GST
#18741 07.11.2018 08:38:29 : TRC GPS : GSTP repeated 6 times
#18742 07.11.2018 08:38:29 : TRC GPS : Send: GSOP 2 120000 0
#18743 07.11.2018 08:38:29 : TRC GPS : Done:GSO
#18744 07.11.2018 08:38:29 : TRC GPS : Send: GSP
#18745 07.11.2018 08:38:30 : TRC GPS : Done:GSP
#18746 07.11.2018 08:38:30 : TRC GPS : Gnss Filter mode: Default
#18747 07.11.2018 08:38:30 : EVT DRT : 865124 tpmrun:62474 tpmwait:32253 tpmstop:768158
#18748 07.11.2018 08:38:30 : EVT DRT : 865124 cbletx:929 cblerx:922 cgnssr:364711
#18749 07.11.2018 08:38:30 : EVT ANALYTICS : #Act id:3
#18750 07.11.2018 08:38:30 : ERR ANALYTICS : colflags2
#18751 07.11.2018 08:38:30 : EVT ANALYTICS : #GPS mode:OK soc:-1
#18752 07.11.2018 08:38:30 : EVT ANALYTICS : Battery-> 7 soc:55
#18753 07.11.2018 08:38:31 : EVT SPEEDFUSION : INFO # speed source 3
#18754 07.11.2018 08:38:47 : EVT SPEEDFUSION : INFO # speed source 2
#18755 07.11.2018 08:43:40 : TRC APPLICATION : Notification n-act-s-tdy not allowed
#18756 07.11.2018 08:49:25 : TRC APPLICATION : Notification n-act-e-tdy not allowed
#18757 07.11.2018 08:58:10 : EVT EXT_FLASH : ExtFID 0x20,0xba,0x19
#18758 07.11.2018 08:58:10 : TRC APPLICATION : Start 2.4.14 in mode 5 (asked 5h)

NB.

records from 08:24:19 till 08:58:10 are given as they are (without skipping any records);
I have not stopped during run and those messages about autopause seems to be suspicious (first signs of ‘FusedTrack calibration’ messages?)
At 08:58:10 watch reset was initiated.

PS. Unfortunately, I’ve not been contacted by Suunto techsupport regarding opened case. Probably, if they would show me how to increase debug to provide them more clear logs from their watch to find a problem source, that could lead to more productive output from my efforts…

@Dimitrios-Kanellopoulos,
could you give me an advise what should I do next?