jamesm Posted May 20, 2014 Report Posted May 20, 2014 Hi, I am trying take the data output from a Garmin Aera 560 GPS feed into a Garmin GNC 255 nav/com and into Insight G3 Graphic Engine Monitor. I am using the Garmin aviation wiring harness. When I talk to the people from Insight or Garmin at a recent avaition trade show they give me the simple answer of "oh yeah that is easy" however when I ask a sepific questions about settings and configuration that seems to be a different story. Apparently the General Avaition manufactures don't give much details on (RS232) data output details and they use strange naming convention for their porotcols amoung the different manufactures. I know that the GPS is outputting out data because I can see GPS data being streamed to a serial port on a laptop. I have treid various settings and pinouts configurations but not avial. I must be missing something basic that I am missing. Thinking this would be a simple task I found myself eating a big piece of humble pie.... :-( Anybody successfully done this before ? Is there way of verfiying that data is being seen by the Insight G3 or Garmin GNC 255? Thanks James '67C Quote
Seth Posted May 20, 2014 Report Posted May 20, 2014 James- Without reading in too much detail, I think the flaw may be the following: Garmin tries to ensure that it's products will feed one way. Panel based to portable, but not the other way around. The GPS singnal from the Aera is a portable, and it's feeding at panel based GNC 225 - they may have put some code to not allow that. If the signal came from a 650, 750, 430, 530, it may work, as that's panel based to panel based. I know it seems as if a signal feed is a signal feed, but I'm pretty sure people of tried and cannot get the portables to feed anything on the panel. A panel installed 430 feeds my aera for nav data so I don't have to enter a flight plan twice, but not the other way around. I hope this wards of hours of trying to figure things out, or someone else can speak up and show what works to "work around" the system. Take care, -Seth 1 Quote
LANCECASPER Posted May 20, 2014 Report Posted May 20, 2014 James- . . . but I'm pretty sure people of tried and cannot get the portables to feed anything on the panel . . . -Seth This makes sense since most panel mounts are certified for enroute or approach, etc. They wouldn't want the portable (non-certified) feeding the certified unit the flightplan, only the other way around. Quote
N201MKTurbo Posted May 20, 2014 Report Posted May 20, 2014 You need to make sure your wiring is correct. That you don't have TX and RX reversed. RX needs to hook to TX and TX needs to hook to RX (sometimes). This has tripped up just about everybody. The portables are usually capable of outputting different protocols. Make sure you are using the correct one. Make sure the Baud rates match. Quote
Marauder Posted May 20, 2014 Report Posted May 20, 2014 Ok James, I just read the online manual for the 560. http://static.garmincdn.com/pumac/190-01117-02_0C_web.pdf They mention an interface capability for data between different devices using the NMEA protocol (same as they used for years). Take a look at the pages starting at page 162. The unit is capable of interfacing with a variety of hardware including a GTX-330 (for TIS-A - traffic), Nav/Com (upload channel frequency), XM receivers for weather, panel mounted GPS (for loading destination information) and even an autopilot. There are different cables that can be bought and used depending on your application. The NMEA protocol is explained but based on the different things you are trying to connect, you will need to know what is being transmitted and what can be received. The Garmin site says you can get a copy of the Garmin proprietary protocol on their site. The NMEA 0183 has standard output language. You will need to know what the G3 can use and what it can accept. Same for the 255. Hope this helps a little. Sent using Tapatalk Quote
N201MKTurbo Posted May 20, 2014 Report Posted May 20, 2014 FWIW The Garmin protocol is proprietary and not the same as NMEA 0183. You will need to choose one or the other. Quote
Marauder Posted May 20, 2014 Report Posted May 20, 2014 FWIW The Garmin protocol is proprietary and not the same as NMEA 0183. You will need to choose one or the other. I think that is the challenge he is going to have. If he wires it to the Garmin 255, he will use the Garmin protocol and if he wires it to the GEM, it will most likely be NMEA. Sent using Tapatalk Quote
jamesm Posted May 21, 2014 Author Report Posted May 21, 2014 Thanks, I have been going through the different combinations of wiring and protocols but haven't hit the correct match yet. Thanks for all comments and suggestions. James '67C Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.