Suunto 9 Picasso Edition

[freeheeler]

what do you do when Picasso annexes your baro sensor during an activity?

[Fenr1r]

@TELE-HO Turn the graph 90 degrees counter-clockwise and play “Guess the Famous Profile”?

[Dimitrios Kanellopoulos]

@TELE-HO was that a pause ?

[freeheeler]

@Dimitrios-Kanellopoulos
no, non stop recording…

@Fenr1r
hehe, the roman empire has crumbled long time ago

Edit:
I forgot to mention that after I’ve stopped the activity and the activity was saved the watch did an auto reboot

[Dimitrios Kanellopoulos]

@TELE-HO ok. How is the temperature chart ?

[Fenr1r]

@TELE-HO said in Suunto 9 Picasso Edition:

@Fenr1r
hehe, the roman empire has crumbled long time ago

Plus ça change, plus c’est la même nose.

[freeheeler]

@Dimitrios-Kanellopoulos
that’s alright …hmm not existing?!?
…and now that you mention it I notice that the vertical speed profile is missing, too. I thought I saw both, but when I doublechecked they were both missing

[freeheeler]

@Dimitrios-Kanellopoulos
resynced and temperature is back… but not correct as you can see.
temperature went bananas well before the baro did.

[Dimitrios Kanellopoulos]

@TELE-HO I know this issue. Might sound strange but it might be an edge case that happens rarely. Not 100% sure why but it’s known and fixed afaik

[sartoric]

Maybe something went nuts on satellite data … This morning my short run on the usual path was 100m off (less)

[freeheeler]

@Dimitrios-Kanellopoulos
means it comes with the next update?

[isazi]

@Fenr1r said in Suunto 9 Picasso Edition:

@TELE-HO Turn the graph 90 degrees counter-clockwise and play “Guess the Famous Profile”?

That nose… I guess it’s me

[isazi]

@TELE-HO not related, but I had an issue with altitude too today

The profile is not wrong, maybe a little hiccup here and there, but the ascent/descent are: I got a 12 up 37 down in the Suunto App. Runalyze recomputes ascent/descent based on the alti data and gave me a more reasonable 48 up 38 down.

[freeheeler]

@isazi
nice, it corrects it?
my recording stays wrong. the value on the watch during the activity was wrong all of a sudden, the graph in SA is wrong, the total ascent is missing 1/3 of the meters the highest point was wrong and the end altitude is wrong, too. And of course it is now wrong in SA, Stravagram (hence Elevate) and QS. At least in QS I would have the possibility to correct it. But I don’t, because then it is not in line with the other databases anymore

[zhang965]

another sad story, the same day, same exercise, left is recorded with suunto app on my phone and right is recorded with suunto9baro.

the distance is 3.3km vs 2.6km…

[freeheeler]

@zhang965
looks like you have a nice phone!

[surfboomerang]

@zhang965 what says the gps information in the JSON file?

[zhang965]

@surfboomerang said in Suunto 9 Picasso Edition:

@zhang965 what says the gps information in the JSON file?

Wa-pa-pa-pa-pa-pa-pow!
Wa-pa-pa-pa-pa-pa-pow!
Wa-pa-pa-pa-pa-pa-pow!"
What the JSON say?

[Brad_Olwin]

@zhang965 Well, it is clear that the S/N and satellite numbers are poor, that explains the poor tracks. Not sure what you can do about that but no watch would be any better with the satellite number and S/N you have.

[freeheeler]

@Brad_Olwin
but why is the phone’s track so much better? Cell location does not do it so much better, does it?