Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello

I am a newcomer in this Forum and I do not have much expirience with the internals of the FS software.

I am using gpsout on FS2004 and cannot get the the NMEAoutput from the simulator into my Garmin 495.

The GPSMAP 495 also includes NMEA INPUT with support of the BWC, DBT, DPT, MTW, VHW, VTG, and XTE sentences.

Setting the 495 in Simulator mode and Interface to AVIATION IN, or NMEA IN/OUT does not work, and I tried also all kind of settings of the NMEA output in GPSOUT

I am using the Garmin serial Cable, and COM port settings are ok

GPSOUT is working together with Fugawi and sends correct position, speed and altitude.

Is it possible, that there is a problem with the NMEA sentence coming out of GPSOUT

If possible, I would be very glad to get assistance to use my 495 in combination with the FS2004.

best regards

gerhard

Posted

Is it possible, that there is a problem with the NMEA sentence coming out of GPSOUT

No. All the NMEA sentences it produces are fine, but Aviation 400 protocol does NOT use NMEA sentences at all. It is a completely separate aviation protocol, and selected separately in GPSout. We know from feedback here that it works fine with the Garmin 296 and others in the x96 range. I've not heard of or seen any feedback so far about a 495.

If it says it supports Aviation protocol and is set to receive that, then the only things you need to get right in GPSout are COM port (or USB port), Speed ("baud rate") and the protocol selection. Do NOT select anything else with Aviation -- it is a free-standing protocol.

I do not know of any Garmin units which accept NMEA input for GPS operation. They only use that for routing data. The reference you have for NMEA sentences is probably referring to the NMEA output you can get from the 495 -- it feeds moving map programs in the same way as GPSout does.

Regards

Pete

Posted

Thank you for your quick answer

The Owners Manual of the GPS495 says

The GPSMAP 495 also includes NMEA INPUT with support of the BWC, DBT, DPT, MTW, VHW, VTG, and XTE sentences.

So, I got the idea to use my Garmin in the same way, like other users told about using the 196 or the 296.

I set the GPSOUT to Com1, 4800, 8, N, 1 , AV400 (I tried also VTG) and the Garmin to SIMULATOR and AVIATION IN mode, but no respond on the 495.

I also made a record from the output of the grmin, but when I want o feed it back into the 495 there is also no respond, and the

Output of the 495 does not work together with AMAP and Fugawi.

It seems to be a problem with Garmin, and Garmins Support seems to be very lousy, because their answer didnt match my question, and now I get no answer any more.

This sentences does my 495 send out.

$GPRMC,172030,V,4753.1299,N,01602.3155,E,130.0,272.0,010210,2.6,E,S*1B

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,1700,,*20

$GPRMC,172031,V,4753.1312,N,01602.2619,E,130.0,272.0,010210,2.6,E,S*16

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2100,,*25

$GPRMC,172032,V,4753.1325,N,01602.2083,E,130.0,272.0,010210,2.6,E,S*14

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2100,,*25

$GPRMC,172033,V,4753.1337,N,01602.1547,E,130.0,272.0,010210,2.6,E,S*18

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172034,V,4753.1350,N,01602.1011,E,130.0,272.0,010210,2.6,E,S*18

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172035,V,4753.1362,N,01602.0475,E,130.0,272.0,010210,2.6,E,S*1F

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172036,V,4753.1375,N,01601.9939,E,130.0,272.0,010210,2.6,E,S*15

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172037,V,4753.1388,N,01601.9403,E,130.0,272.0,010210,2.6,E,S*12

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172038,V,4753.1400,N,01601.8867,E,130.0,272.0,010210,2.6,E,S*15

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172039,V,4753.1413,N,01601.8331,E,130.0,272.0,010210,2.6,E,S*1E

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172040,V,4753.1425,N,01601.7794,E,130.0,272.0,010210,2.6,E,S*11

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172041,V,4753.1438,N,01601.7258,E,130.0,272.0,010210,2.6,E,S*19

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2600,,*22

$GPRMC,172042,V,4753.1451,N,01601.6722,E,130.0,272.0,010210,2.6,E,S*1C

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172043,V,4753.1463,N,01601.6186,E,130.0,272.0,010210,2.6,E,S*14

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172044,V,4753.1476,N,01601.5650,E,130.0,272.0,010210,2.6,E,S*18

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172045,V,4753.1488,N,01601.5114,E,130.0,272.0,010210,2.6,E,S*1F

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172046,V,4753.1501,N,01601.4578,E,130.0,272.0,010210,2.6,E,S*13

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172047,V,4753.1514,N,01601.4042,E,130.0,272.0,010210,2.6,E,S*1A

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172048,V,4753.1526,N,01601.3506,E,130.0,272.0,010210,2.6,E,S*16

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172049,V,4753.1539,N,01601.2970,E,130.0,272.0,010210,2.6,E,S*15

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172050,V,4753.1551,N,01601.2433,E,130.0,272.0,010210,2.6,E,S*19

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172051,V,4753.1564,N,01601.1897,E,130.0,272.0,010210,2.6,E,S*1F

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172052,V,4753.1576,N,01601.1361,E,130.0,272.0,010210,2.6,E,S*1D

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172053,V,4753.1589,N,01601.0825,E,130.0,272.0,010210,2.6,E,S*16

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2300,,*27

$GPRMC,172054,V,4753.1602,N,01601.0289,E,130.0,272.0,010210,2.6,E,S*1D

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2000,,*24

$GPRMC,172055,V,4753.1614,N,01600.9753,E,130.0,272.0,010210,2.6,E,S*11

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,2000,,*24

$GPRMC,172056,V,4753.1627,N,01600.9217,E,130.0,272.0,010210,2.6,E,S*17

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,1800,,*2F

$GPRMC,172057,V,4753.1639,N,01600.8681,E,130.0,272.0,010210,2.6,E,S*13

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,1800,,*2F

$GPRMC,172058,V,4753.1652,N,01600.8145,E,130.0,272.0,010210,2.6,E,S*1E

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

$PGRMH,V,0,,,,1600,,*21

$GPRMC,172059,V,4753.1665,N,01600.7609,E,130.0,272.0,010210,2.6,E,S*1B

$GPRMB,V,,,,,,,,,,,,A,S*0E

$PGRMZ,4416,f,3*2C

Next week, I will meet a pilot, who uses his 495 together with XPlane, so I can check, if there is a bug in my device.

best regards

Gerhard

Posted

The Owners Manual of the GPS495 says

The GPSMAP 495 also includes NMEA INPUT with support of the BWC, DBT, DPT, MTW, VHW, VTG, and XTE sentences.

Those are all concerned with things like water depth, water speed, and waypoints at sea. The only one of those supported by GPSout is VTG for ground speed and track. None of those sentences provide latitude, longitude or altitude, so useless for use in aviation. I think they are only designed to connect to additional equipment on a boat (depth gauge, sonar, water-driven transducers), with the GPS still receiving satellite positions for Latitude and Longitude.

So, I got the idea to use my Garmin in the same way, like other users told about using the 196 or the 296.

I'm pretty sure the others use Aviation protocol.

I set the GPSOUT to Com1, 4800, 8, N, 1 , AV400 (I tried also VTG) and the Garmin to SIMULATOR and AVIATION IN mode, but no respond on the 495.

Maybe it is not 4800 (that's only the default speed for NMEA). I seem to recall the others use 9600. Have you checked? I found this link on Google:

http://www.baron58.com/gps_garmin_296.htm

This sentences does my 495 send out.

Yes, they are similar to those sent out by GPSout if you select the right sentences, and should drive a moving map perfectly well. You have some setting incorrect, probably port speed.

Regards

Pete

Posted

Hello Pete,

Now I checked out my Garmin GPSMAP495 with XPLANE 9 and it worked well.

There is an module, similar to gpsout in the fs2004, which sends out Aviation Data which can be used in combination with the 495 and the data coming out of XPLANE look like the following sample. It is the output from the Apple version of XPLANE.

"========= START" is the begin, and

"END =========" is the end of one sentence.

the line brakes are part of the protocol.

========= STARTz09296

AN 53 4986

BE 009 4730

C193

D128

QW000

T----------

w01@

END =========

========= STARTz09296

AN 53 4986

BE 009 4730

C193

D128

QW000

T----------

w01@

END =========

Is this the same, gpsout does send out in AV400 ?

best regards,

Gerhard

Posted

Is this the same, gpsout does send out in AV400 ?

Yes, that looks like AV400, except of course you don't show the unprintable STX character (x02) at the start and the ETX (x03) at the end.

I think all the Garmin x96 units are confirmed working with GPSout's AV400, certainly the 296 and 496.

Pete

Posted

Hello Pete,

I dont wan to be boring, but it seems that there is a difference inbetween the sentences the garmin 295 understands and the garmin 495.

495 and 496 are similar, but the 496 has more features - street navigation and weather information - which is only useful for flying in the united states, because for wheather information is no infrastructure in european airspace.

The readout of the protocol in my former posting is originally that, which xplane sends out and which works together with the 495.

So, I want to ask you, if you could be so kind to make changings in your gpsout module that the sentences are formed into the same format like them, I wrote you in my former posting.

I think, you could also contact siegfried.hanisch@hanisch.com, he wrote an plugin for xplane (apple version) and the garmin aviation in protocol, and i visited him to check out my 495 and it worked fine.

He is software author and his homepage is www.hanisch.com from where a download of the garmin NMEA converter for apple is possible, so I think, he could tell you better than I, how a sentence has to look like.

If I would be able to write or understand programes I would try to fix it by myself.

best regards

gerhard

Posted

So, I want to ask you, if you could be so kind to make changings in your gpsout module that the sentences are formed into the same format like them, I wrote you in my former posting.

The format I produce is exactly to the AV400 specification I have.

I am not in a position to compare a specific example to yours -- you omitted non-printable control characters in any case. You need to capture the actual frame, the whole of it, and show it in hexadecimal, or saved to a file and Zipped for me to look at. If you can do the same from GPSout and see what the differences are, I'll check to see if I can make those changes without affecting others. If you can't do that I'll see what I can do if you provide better information.

Without any GPS devices here which can accept anything from GSPout I am dependent on feedback, and so far, for 12 years now, the AV400 format I provide has been accepted. I am therefore reluctant to change anything without knowing why and what, and I cannot do that with only the information you gave because that is only partial.

I you need to send me anything do so to petedowson@btconnect.com.

Regards

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.