Garmin Basecamp 3.2.2 bug

Former Member over 13 years ago

In this version, the proximity alarms don´t works with the Garmin Montana.
If i create proximity alarms for waypoints, and then i send this waypoints to the Montana, when see the waypoints in the Montana, don´t have proximity alarms. It´s a big error, because i have to put my proximity alarms manually in the Montana.
Best regards

0 FrensicPic over 13 years ago

OSCARBLUR...I see the same thing with my GPSMAP 62s. Proximities set in BaseCamp do not appear on the device...I have to set them on the device itself.

I've also noticed symbol compatibility issues between BC and the 62s. Not all symbols in BC will appear on the device. Also, custom symbols that appear on the device do not appear in BC and custom symbols in BC do not appear on the 62s! There is a difference in naming format.
In my case, I'm using BC 3.2.2 for Windows.
regards, John

0 Former Member over 13 years ago

The waypoint proximity data is being sent by BaseCamp. Here is the GPX XML sent to my Montana.

<wpt lat="47.836549775674939" lon="-119.945660512894392">
        <time>2011-10-17T01:39:48Z</time>
        <name>241 McNeil Canyon Rd</name>
        <cmt>241 McNeil Canyon Rd</cmt>
        <desc>241 McNeil Canyon Rd</desc>
        <sym>Pin, Red</sym>
        <extensions>
            <gpxx:WaypointExtension>
                <gpxx:Proximity>160.9344</gpxx:Proximity>
                <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
            </gpxx:WaypointExtension>
        </extensions>
    </wpt>

For some reason the device is not reading the Proximity setting.

Cheers,

0 Former Member over 13 years ago

The waypoint proximity data is being sent by BaseCamp. Here is the GPX XML sent to my Montana.

<wpt lat="47.836549775674939" lon="-119.945660512894392"> <time>2011-10-17T01:39:48Z</time> <name>241 McNeil Canyon Rd</name> <cmt>241 McNeil Canyon Rd</cmt> <desc>241 McNeil Canyon Rd</desc> <sym>Pin, Red</sym> <extensions> <gpxx:WaypointExtension> <gpxx:Proximity>160.9344</gpxx:Proximity> <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode> </gpxx:WaypointExtension> </extensions> </wpt>

For some reason the device is not reading the Proximity setting.

Cheers,

I report this bug to Garmin Montana team, and they said to me that is not a bug from the Montana, but after reading this i think that is a bug in the Montana.
Proximity alarm info is in the *gpx file
Best regards

0 Former Member over 13 years ago

OSCARBLUR...I see the same thing with my GPSMAP 62s. Proximities set in BaseCamp do not appear on the device...I have to set them on the device itself.

I've also noticed symbol compatibility issues between BC and the 62s. Not all symbols in BC will appear on the device. Also, custom symbols that appear on the device do not appear in BC and custom symbols in BC do not appear on the 62s! There is a difference in naming format.
In my case, I'm using BC 3.2.2 for Windows.
regards, John

+1
Símbols compatibility issues too

0 Former Member over 13 years ago

I report this bug to Garmin Montana team, and they said to me that is not a bug from the Montana, but after reading this i think that is a bug in the Montana.
Proximity alarm info is in the *gpx file
Best regards

Yep, they said the same to me. But, . . .

I've edited this to reflect info I just received from the Montana Team. Turns out the MT uses different Waypoint XML syntax than the older Garmin units and BC doesn't yet support that syntax. So, Prox-Alerts sent from BC will work on older GPS's but not on newer (Montana series for one).

Cheers,