NMEA Revealed
NMEA Revealed
$ECRMB,A,0.000,
R,
?,
NM001,2714.427,N,08018.831,W,0.1 48,166.032,0.000,V*2E
$GPRMB,A,0.66
,L,
003,
004,4917.24,N,12309.57,W,001.3,052.5,000.5,V*0BField Number:
- Status, A= Active, V = Void
- Cross Track error - nautical miles
- Direction to Steer, Left or Right
- TO Waypoint ID
- FROM Waypoint ID
- Destination Waypoint Latitude
- N or S
- Destination Waypoint Longitude
- E or W
- Range to destination in nautical miles
- Bearing to destination in degrees True
- Destination closing velocity in knots
- Arrival Status, A = Arrival Circle Entered
- FAA mode indicator (NMEA 2.3 and later)
- Checksum
Example: $GPRMB,A,0.66,L,003,004,4917.24,N,12309.57,W,001.3 ,052.5,000.5,V*0B
Yes, it looks to me like it may have something to do with the names of the Waypoints and the fact that there is no To Waypoint Name.
But how do we know it will accept the RMC sentence?
It should as this is the "RMB - Recommended Minimum
Navigation Information"
So next step is to get it well formed I guess.
Can you change the names of your waypoints to just be numbers, 3 digits and try that?
----
If that simple approach does not
work, maybe you need to try using a beta
plugin called
oBabel by Mike R. [Rasbats]
I compiled that and tried some testing for him awhile ago and some have found it useful, but I've
lost track of it.
It uses another well known program called
GPS Babel that helps with conversions. You should read about that on the link.
oBabel helps to tranfer a
route to
garmin, if it works. Then you'd use that for the
autopilot.
I've read that
Garmin is very particular about their waypoint names and cannot have greater than a certain number of places (5 I think) and must be a number etc.. Read oBabel and gpsbabel it will help you I think.