Traditionally, in a sailboat we navigate using pre planed routes, but
depending on the weather conditions and other factors, we can skip one
or more waypoints in the route sequence, doing a GOTO to the next
waypoint within the active route; this works well practically in all
Gamin's gps I know and the gps continues changing automatically to
the next waypoint within the route, once it has made the currently
active waypoint.


This is the correct thing to do, as the active route has I high
priority over a GoTo IF the waypoint active pertains to the Active
Route. Of course, if you do a Goto to a waypoint which does nor
pertains to the active route, you are canceling the active route, and
them, when you reach to the waypoint, the gps keeps pointing back to
that waypoint.

In recent software updates, Garmin introduced more options in the
behavior of route waypoint transition, including the manual and
distance algorithms in addition to the traditional automatic way.

Last week we have made a 400 nm trip in a friend's 36 ft sailboat and
have found a problem with the 276C software 3.50, as a skip to a
waypoint in the active route, using a Goto as usual, including if this
waypoint is currently the active waypoint, this incorrectly changes the
algorithm of waypoint transition from automatic to manual, even if in
the route setup, the parameter is in AUTO mode.

As you can understand, this could a cause a very danger navigation
situation, because the Gps keeps pointing back to the waypoint already
made, that is, to back in the route, which is not the expected
behavior. The problem is worst if the navigator has its autopilots
interfaced with the gps, as we have the Raymarine Smart Pilot S1 G
(Gyrocompass is great, giving a XTE ever less than 10 m even in a
crossed sea state).

I found later that this problem does not occurs when the GpsMap 276C is
in Simulation mode, and only happens if it is in Normal system state,
that is, getting the real position using the real gps satellites and
making a real navigation. I confirm that this problem does not happen
with my GpsMap 76.

So I am asking that Garmin confirms this in a REAL test and corrects
the GpsMap 276C software/firmware as soon as possible. Has anybody
observed this too?

Thanks

Pascal Goncalves