---------------------------------------------------------- RV-List Digest Archive --- Total Messages Posted Mon 02/09/15: 3 ---------------------------------------------------------- Today's Message Index: ---------------------- 1. 09:53 AM - NavWorx ADS600B integration to Garmin based panel -> the saga continues (Ralph E. Capen) 2. 10:14 AM - Re: NavWorx ADS600B integration to Garmin based panel -> the saga continues (bigdog@bentwing.com) 3. 10:55 AM - Re: NavWorx ADS600B integration to Garmin based panel -> the saga continues (Ralph E. Capen) ________________________________ Message 1 _____________________________________ Time: 09:53:38 AM PST US From: "Ralph E. Capen" Subject: RV-List: NavWorx ADS600B integration to Garmin based panel -> the saga continues Folks, Here's another update since getting the details on implementing the "Extended" mode from the NavWorx folks: I was able to get the SL70 configured for the "Extended" mode per their instructions. The extended mode data did not interfere with passing altitude data to the MX20 as currently connected. Their additional requirements are causing some interoperability issues.... The ADS600B requires the "Extended" mode output from the SL70 at 9600 baud - which the SL70 is capable of delivering. The 9600 baud setting is not compatible with the MX20 - which only allows 1200 baud communications. I have a note in to NavWorx to see if they are going to allow 1200 baud in the future...I'm not the only one with this issue! As a potential workaround, I looked at the documentation for my GNC420W. It indicates that it is capable of transmitting the altitude data to the MX20 along with the existing connection that provides lat/long. I tried that too - it doesn't work. I have a note in to Garmin to see if there is a configuration setting that I missed or if there was a printing error. If all else fails - throw money at it.....I can replace the installed altitude encoder with one that has a 1200 baud serial port as well as the Gray code. I'm starting to see why everyone is screaming about the cost vs benefit of ADS-B in the first place..... Ralph ________________________________ Message 2 _____________________________________ Time: 10:14:51 AM PST US From: "bigdog@bentwing.com" Subject: RE: RV-List: NavWorx ADS600B integration to Garmin based panel -> the saga continues I was originally going to use their TransMonSPE instead of hard wiring to my transponder. It's a device that clips over the transponder cable and picks up the altitude and code from the RF leakage. Since it looked like I could wire everything I backed off that but have that as an option if I hit the same snags as you. It's fairly cheap, <$80 I think. Greg Young -----Original Message----- From: owner-rv-list-server@matronics.com [mailto:owner-rv-list-server@matronics.com] On Behalf Of Ralph E. Capen Sent: Monday, February 09, 2015 11:53 AM Subject: RV-List: NavWorx ADS600B integration to Garmin based panel -> the saga continues Folks, Here's another update since getting the details on implementing the "Extended" mode from the NavWorx folks: I was able to get the SL70 configured for the "Extended" mode per their instructions. The extended mode data did not interfere with passing altitude data to the MX20 as currently connected. Their additional requirements are causing some interoperability issues.... The ADS600B requires the "Extended" mode output from the SL70 at 9600 baud - which the SL70 is capable of delivering. The 9600 baud setting is not compatible with the MX20 - which only allows 1200 baud communications. I have a note in to NavWorx to see if they are going to allow 1200 baud in the future...I'm not the only one with this issue! As a potential workaround, I looked at the documentation for my GNC420W. It indicates that it is capable of transmitting the altitude data to the MX20 along with the existing connection that provides lat/long. I tried that too - it doesn't work. I have a note in to Garmin to see if there is a configuration setting that I missed or if there was a printing error. If all else fails - throw money at it.....I can replace the installed altitude encoder with one that has a 1200 baud serial port as well as the Gray code. I'm starting to see why everyone is screaming about the cost vs benefit of ADS-B in the first place..... Ralph ________________________________ Message 3 _____________________________________ Time: 10:55:59 AM PST US From: "Ralph E. Capen" Subject: RV-List: Re: NavWorx ADS600B integration to Garmin based panel -> the saga continues An update from NavWorx - they support 1200 baud communications. Should solve all of the issues I am experiencing! -----Original Message----- >From: "'Ralph E. Capen' recapen@earthlink.net [RV7A]" >Sent: Feb 9, 2015 12:52 PM >To: rv-list , "avionics-list@matronics.com" >Cc: RV7 Yahoo list , EXP-AVIONICS >Subject: [RV Builders] NavWorx ADS600B integration to Garmin based panel -> the saga continues > >Folks, > >Here's another update since getting the details on implementing the "Extended" mode from the NavWorx folks: > >I was able to get the SL70 configured for the "Extended" mode per their instructions. The extended mode data did not interfere with passing altitude data to the MX20 as currently connected. > >Their additional requirements are causing some interoperability issues.... The ADS600B requires the "Extended" mode output from the SL70 at 9600 baud - which the SL70 is capable of delivering. The 9600 baud setting is not compatible with the MX20 - which only allows 1200 baud communications. I have a note in to NavWorx to see if they are going to allow 1200 baud in the future...I'm not the only one with this issue! > >As a potential workaround, I looked at the documentation for my GNC420W. It indicates that it is capable of transmitting the altitude data to the MX20 along with the existing connection that provides lat/long. I tried that too - it doesn't work. I have a note in to Garmin to see if there is a configuration setting that I missed or if there was a printing error. > >If all else fails - throw money at it.....I can replace the installed altitude encoder with one that has a 1200 baud serial port as well as the Gray code. > >I'm starting to see why everyone is screaming about the cost vs benefit of ADS-B in the first place..... > >Ralph ------------------------------------------------------------------------------------- Other Matronics Email List Services ------------------------------------------------------------------------------------- Post A New Message rv-list@matronics.com UN/SUBSCRIBE http://www.matronics.com/subscription List FAQ http://www.matronics.com/FAQ/RV-List.htm Web Forum Interface To Lists http://forums.matronics.com Matronics List Wiki http://wiki.matronics.com Full Archive Search Engine http://www.matronics.com/search 7-Day List Browse http://www.matronics.com/browse/rv-list Browse Digests http://www.matronics.com/digest/rv-list Browse Other Lists http://www.matronics.com/browse Live Online Chat! http://www.matronics.com/chat Archive Downloading http://www.matronics.com/archives Photo Share http://www.matronics.com/photoshare Other Email Lists http://www.matronics.com/emaillists Contributions http://www.matronics.com/contribution ------------------------------------------------------------------------------------- These Email List Services are sponsored solely by Matronics and through the generous Contributions of its members.