You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Anywhere Map Compatibility to Autopilot
- Thread starter rock5219
- Start date
- Joined
- Mar 23, 2005
- Messages
- 13,226
We don't really have any experience with the Anywhere map products. I'm not sure if they even put out NMEA data yet- in the past they have not so there was nothing for us to listen to. If they do put out standard NMEA data now, we should technically be able to fly it, but none of that has been tested.
Ken_Kopp
New Member
i have AWMXP connected as my 2nd gps through the hs34 to the
Auto pilot. it does output nmea but in control visions infinite wisdom
they do not output the course so you cannott use the NAV function.
But gps trk works fine...which is probably more a function of the
Garmin gps than AWM....
Auto pilot. it does output nmea but in control visions infinite wisdom
they do not output the course so you cannott use the NAV function.
But gps trk works fine...which is probably more a function of the
Garmin gps than AWM....
- Joined
- Mar 23, 2005
- Messages
- 13,226
See http://wiki.dynonavionics.com/GPS_Serial_Compatibility_and_Configuration_Settings for a list of the NMEA sentences we're looking for.
See http://wiki.dynonavionics.com/GPS_Serial_Compatibility_and_Configuration_Settings for a list of the NMEA sentences we're looking for.
So you are saying that the autopilot will work fine with AnyWhereMap? Just the OBS will always read 360.
- Joined
- Mar 23, 2005
- Messages
- 13,226
Based on Ken's post, you can use AWM to fly GPS track, but they do not output the data required for us to fly to a specific waypoint. If the OBS is stuck at 360, there's nothing for the AP to fly to. It can't fly missing data better than a person can.
Again, this is totally a function of AWM not outputting the data, not the Dynon system being unable to read it.
Again, this is totally a function of AWM not outputting the data, not the Dynon system being unable to read it.
The latest version of AnyWhere Map puts out GPRMC, GPRMB, GPGGA, and GPBOD. They did this specifically to be compatible with Dynon autopilots. However, while navigating to a waypoint, my CRS says 360. What is up? Do I need to adjust any settings? I do get winds, so the D-10A must be getting GPS data. BTW, I tapped into the gps via HyperTerminal and I see all four strings. It sounds like a lot of folks like Anywhere Map so it would be nice to get this working. Thanks.
- Joined
- Mar 23, 2005
- Messages
- 13,226
If you can send us a file with the strings you captured, that'd be very helpful to us in understanding what's going on.
If you can send us a file with the strings you captured, that'd be very helpful to us in understanding what's going on.
Here is an excerpt
$GPGGA,000052,3116.5391,N,09318.6506,W,1,11,0.8,4074.0,M,000.0,M,,*55
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.9,288.6,000.0,A*6E
$GPRMC,000053.00,A,3116.5539,N,09318.7014,W,165.0,289.0,,003.0,E*40
$GPGGA,000053,3116.5539,N,09318.7014,W,1,11,0.8,4073.0,M,000.0,M,,*50
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.8,288.6,000.0,A*6F
$GPRMC,000054.00,A,3116.5689,N,09318.7518,W,165.3,289.0,,003.0,E*45
$GPGGA,000054,3116.5689,N,09318.7518,W,1,11,0.8,4072.0,M,000.0,M,,*57
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.8,288.6,000.0,A*6F
$GPRMC,000055.00,A,3116.5839,N,09318.8026,W,165.3,289.0,,003.0,E*46
$GPGGA,000055,3116.5839,N,09318.8026,W,1,11,0.8,4071.0,M,000.0,M,,*57
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.7,288.6,000.0,A*60
$GPRMC,000056.00,A,3116.5989,N,09318.8529,W,165.3,289.0,,003.0,E*45
$GPGGA,000056,3116.5989,N,09318.8529,W,1,11,0.8,4071.0,M,000.0,M,,*54
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.7,288.6,000.0,A*60
$GPRMC,000057.00,A,3116.6139,N,09318.9038,W,165.3,289.1,,003.0,E*41
$GPGGA,000057,3116.6139,N,09318.9038,W,1,11,0.8,4072.0,M,000.0,M,,*52
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.7,288.6,000.0,A*60
$GPRMC,000058.00,A,3116.6290,N,09318.9541,W,165.1,289.1,,003.0,E*47
$GPGGA,000058,3116.6290,N,09318.9541,W,1,11,0.8,4073.0,M,000.0,M,,*57
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.6,288.6,000.0,A*61
$GPRMC,000059.00,A,3116.6441,N,09319.0049,W,164.8,289.1,,003.0,E*41
$GPGGA,000059,3116.6441,N,09319.0049,W,1,11,0.8,4074.0,M,000.0,M,,*5E
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.6,288.6,000.0,A*61
$GPRMC,000100.00,A,3116.6592,N,09319.0553,W,164.5,289.2,,003.0,E*43
$GPGGA,000100,3116.6592,N,09319.0553,W,1,11,0.8,4075.0,M,000.0,M,,*53
$GPBOD,289.2,T,286.2,M,K25TE,HOME*1A
$GPRMB,A,0.24,L,HOME,K25TE,3227.0085,N,09724.0179,W,219.5,288.6,000.0,A*62
..... BTW, I tapped into the gps via HyperTerminal and I see all four strings. .....
Oh good, I needed to know it was possible to see the GPS data stream with HyperTerminal. It will help me troubleshoot my GPS to D10A problems.
It pays to read all the forums, even if you don't have an autopilot.
..... BTW, I tapped into the gps via HyperTerminal and I see all four strings. .....
Oh good, I needed to know it was possible to see the GPS data stream with HyperTerminal. It will help me troubleshoot my GPS to D10A problems.
It pays to read all the forums, even if you don't have an autopilot.
You will need to tap into the serial wire and go to a separte port to use hyperterminal. Otherwise, you will need to use a port spy program to peak in on the stream.
- Joined
- Mar 23, 2005
- Messages
- 13,226
cguarino: According to our software engineers, the relevant sentence, $GPBOD, looks formed OK. So there's either a bug, or perhaps one of the other sentences isn't being parsed correctly. Are there any NMEA settings you can play with on the device? Beyond that, I'll make sure this gets filed as a bug for us to fix in the next version of firmware (which currently isn't scheduled).
cguarino: According to our software engineers, the relevant sentence, $GPBOD, looks formed OK. So there's either a bug, or perhaps one of the other sentences isn't being parsed correctly. Are there any NMEA settings you can play with on the device? Beyond that, I'll make sure this gets filed as a bug for us to fix in the next version of firmware (which currently isn't scheduled).
Found the problem. When I pulled the avionics cover off to check the wiring, I saw my AWM output rolled up and and stowed next to the D-10A. I had the EFIS hooked directly to the gps instead of to the AWM. I did this because when I installed the EFIS, it couldn't use the AWM output. So I ran the AWM output to the EFIS but didn't connect it. I was prepared and waiting for the EFIS and AWM to become compatible but I forgot that I had done it. Swapped the wires and it works ok now.