GPSrChive Discussion Forum

Greetings, i write from Italy (sorry for my english),

I have a GPSMAP 65S with software version v. 4.60.
I use it for walking and mountain biking, I have therefore created several profiles, and I noticed that if I activate the cadence and speed sensor (garmin) for bike activity I still find it active in all the other profiles created, vice versa if I deactivate it there is no they are problems.

How can I solve the problem ?
Have We solutions ?

Thanks,
Claudio

Unfortunately (or fortunately, depending on your point of view) Garmin have elected to make some of these connections a 'Global' setting, which means they are not profile dependent, and can not be enabled/disabled based on the selected profile.

No, it's not like that, each profile keeps the settings independently.
To confirm, I only find this anomaly with the "cadence and speed sensor". If I enable it, I find it enabled, in every profile.

It's a problem or a bug, i think, or something that escapes me, because if I enable the cadence and speed sensor in the profile dedicated to the bicycle, it would make no sense to find it in the trekking profile too, where this sensor does not exist.

We just tested some ANT+ sensors with our GPSMAP 65 and found that the Tempe sensor is also a 'Global' setting, which makes sense.

We also agree that 'Fitness' related sensors should be profile dependent.

Are you using the individual 'Speed' and 'Cadence' sensors, or the combo 'Speed/Cadence' sensor?

I'm using 'Speed/Cadence' sensor.

Which 'Speed/Cadence Sensor' are you connected to?

The model is the GSC 10 (Garmin).

My opinion the problem isn't so much in the model of the sensor, as in a bug/anomaly of the 65s that looks for this sensor when it shouldn't.

I was going to test with the same sensor of possible, but I do not have the GSC 10, so will test with something else.

If it is useful, I attach the 3 gpf files of the profiles that are contained within the 65s
They are: TREK, MTB and CAR.
As far as I understand, the configuration of the TREK and CAR, are correct, while MTB has an error/anomaly
TREK only has tempe active, while CAR has no sensor.

MTB, presents an anomaly on because I think the right parameter is 1 and not 0

Although the value is 0, the sensor in the MTB profile is regularly active, but it shouldn't be in the others.
All in all, it's a bit confusing

It's correct *** Reformatted to conform with Forum Guidelines ***

profiles

profiles.zip