S9P crashing randomly

freeheeler

@jjpaz
I don’t do that on a regular basis. only if I have the feeling the watch is having issues… which is very rare in my case.

jjpaz

Is very interesting start analycing .FIT files.

These are the last entries in the “after crash” .FIT file:

= TYPE=5 NAME=record NUMBER=20
--- timestamp=1043065778=2023-01-19T12:29:38Z
--- position_lat=481284491=40.3408000 deg
--- position_long=-45354435=-3.8015648 deg
--- distance=273400=2734.00 m
--- altitude=5907=681.4 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=5 NAME=record NUMBER=20
--- timestamp=1043065779=2023-01-19T12:29:39Z
--- position_lat=481284644=40.3408128 deg
--- position_long=-45353938=-3.8015232 deg
--- distance=273700=2737.00 m
--- altitude=5907=681.4 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=9 NAME=record NUMBER=20
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- distance=274100=2741.00 m
--- altitude=5906=681.2 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=10 NAME=lap NUMBER=19
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043065462=2023-01-19T12:24:22Z
--- total_elapsed_time=318307=318.307 s
--- event=9=lap
--- event_type=1=stop
--- lap_trigger=0=manual
--- total_timer_time=318307=318.307 s
==
= TYPE=0 NAME=event NUMBER=21
--- event=0=timer
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- event_type=1=stop
--- timer_trigger=0=manual
==
= TYPE=0 NAME=session NUMBER=18
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043064862=2023-01-19T12:14:22Z
--- event=8=session
--- event_type=1=stop
--- sport=1=running
--- first_lap_index=0=0
--- num_laps=2=2
--- min_heart_rate=95=95 bpm
--- avg_heart_rate=130=130 bpm
--- max_heart_rate=144=144 bpm
--- avg_speed=2980=10.728 km/h
--- max_speed=3180=11.448 km/h
--- total_timer_time=918400=918.400 s
--- total_elapsed_time=918401=918.401 s
--- total_distance=274100=2741.00 m
--- max_altitude=2850=70.0 m
--- min_altitude=2840=68.0 m
--- training_stress_score=102=10.2 tss
==
= TYPE=0 NAME=activity NUMBER=34
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- num_sessions=1=1
--- type=0=manual
--- event=26=activity
--- event_type=1=stop
--- local_timestamp=1043069380=1043069380
==
# CRC: expected=0xE833, calculated=0xE833

We can see the last samples (without heartrate nor HRV, last 16 seconds) and at the end we can see a “STOP” event.
So it seems that the watch stopped itlself the activity and then reboots, is that correct?

= TYPE=0 NAME=session NUMBER=18
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043064862=2023-01-19T12:14:22Z
**--- event=8=session
--- event_type=1=stop**
--- sport=1=running
--- first_lap_index=0=0
--- num_laps=2=2
--- min_heart_rate=95=95 bpm
--- avg_heart_rate=130=130 bpm
--- max_heart_rate=144=144 bpm
--- avg_speed=2980=10.728 km/h
--- max_speed=3180=11.448 km/h
--- total_timer_time=918400=918.400 s
--- total_elapsed_time=918401=918.401 s
--- total_distance=274100=2741.00 m
--- max_altitude=2850=70.0 m
--- min_altitude=2840=68.0 m
--- training_stress_score=102=10.2 tss

==
= TYPE=0 NAME=activity NUMBER=34
--- timestamp=1043065780=2023-01-19T12:29:40Z
**--- num_sessions=1=1
--- type=0=manual
--- event=26=activity
--- event_type=1=stop**
--- local_timestamp=1043069380=1043069380
==

DMytro

@jjpaz I think so (too lazy to check the code tho), but its a feature built into suunto watches, s.t. no matter what (i.e. battery dead/crash/etc) the activity is saved.

isazi

@jjpaz never a soft reset, but sometimes if I have to travel by airplane and carry many watches in my luggage I turn the watch off.

Ketoohs

Today during the night my watch crashed (it was the second crash in about a year (first one was about half a year ago) , and when I woke up it said it has recovered…
The problem was, that it did not wake me, as alarm was removed…

@isazi I sent logs at around 6:00 AM CET…

Dimitrios Kanellopoulos

@isazi can you PM me on teams the TP?

isazi

@Ketoohs send me a PM with your username on SA.

DF130

@DF130 Latest update, managed a hard reset and reconfiguration, but that did not help either. Now I am just using the stock running mode, so far no issues (and not with any other sports, where I admittedly only use stock modes). So somewhere between custom modes (or the specific customisation I had chosen, “target” screen maybe?), S+, and a bunch of sensors (Suunto heart rate belt and Stryd), the conditions for a crash seem to develop…

DF130

@DF130 Last update, using stock mode was not a solution either, watch has crashed again today (when running as usual). Not quite sure what to do, maybe waiting for the next firmware update and hoping for the best…

el2thek

@DF130 Did you see this: https://forum.suunto.com/post/115420

DF130

@el2thek No, not yet. Thanks for pointing out !

Panagiotis Kritikakos

First time happened to me as well today, during bike exexrcise after 30minutes with HR belt on. However, the activity up to that point was saved. Logs have been submitted.

Kramble

Same for me two days ago and I couldn’t synch the activity after the crash, the sync of the activity was endless. It was the first time.

zhang965

@Kramble said in S9P crashing randomly:

Same for me two days ago and I couldn’t synch the activity after the crash, the sync of the activity was endless. It was the first time.

Time for vertical!

isazi

A new firmware should come soon, May or June.

cs2nd

I hope to update in near future also brings the S9PP interface to the S9P.

DMytro

@cs2nd this won’t happen unfortunately. Was mentioned upon s9pp release.

DF130

New firmware worked quite well for my S9P - until today. Forgot to activate navigation after starting my activity (stock trail running), probably too excited as it was a race, but I should not have tried to use a route after that. Watch froze on the route selection screen and crashed after that. Seems that recording stopped some time during the freeze, maybe the last mile/km S+ is to blame as everything works perfectly when I try now. On the upside, the S9P survived my rolling breakfall down the mountain without a scratch