VansAirForceForums  
Home > VansAirForceForums

- POSTING RULES
- Donate yearly (please).
- Advertise in here!

- Today's Posts | Insert Pics

  #41  
Old 09-22-2017, 08:38 AM
jimfaber jimfaber is offline
 
Join Date: Aug 2013
Location: Cocoa Beach FL
Posts: 21
Default

Thanks for everyone's input. My EFIS is An AFS 5500 on port 1. I will try all of your suggestions. I have also spoken to Scott Edwards. He seems to think it might be a software issue since everything was working before the upgrade. He is reaching out to Bill Moffitt for help. I will keep you updated on my progress /resolution so anyone else can learn from my problem. I'll keep in touch.

Thanks
Reply With Quote
  #42  
Old 09-25-2017, 10:13 AM
MauleDriver's Avatar
MauleDriver MauleDriver is offline
 
Join Date: Aug 2006
Location: Lake Ridge Aero Park - Durham NC
Posts: 199
Default

Thanks to Bob and everyone here for all the work and the effort to share it! I think I see the light at the end of this tunnel.

I have installed and been operating with this unit for a few years:
ADSB600-B PN: 200-12-09-00 SN: 945 (running 4.1.0)
It is installed with:
GRT HX, GTX-327, G430w
The GRT is configured as Display 1 and shows TIS and FIS - I love the 3D TIS in the synthetic vision view.

I'm using the internal GPS and therefore have the SIL=0 problem.
The only other problem I'm aware of is that I got a call from the FAA saying I wasn't transmitting Baro Alt, which I guess means I'm only sending GPS alt.
Even though the G430w is wired up and I assume configured for display 2, I've never looked for or seen TIS information there.

With the AMOC for the G430w, it looks like I can make myself legal for 2020 by wiring the G430 GPS serial out to the GPS rec input and reconfiguring the unit to use it.

Is that generally correct? Will it broadcast Sil=1 without further software upgrades?

I've seen some mention of issues with Baro altitudes but is anyone have trouble with the GTX327?
Reply With Quote
  #43  
Old 09-25-2017, 10:43 AM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default

Quote:
Originally Posted by MauleDriver View Post
Thanks to Bob and everyone here for all the work and the effort to share it! I think I see the light at the end of this tunnel.

I have installed and been operating with this unit for a few years:
ADSB600-B PN: 200-12-09-00 SN: 945 (running 4.1.0)
It is installed with:
GRT HX, GTX-327, G430w
The GRT is configured as Display 1 and shows TIS and FIS - I love the 3D TIS in the synthetic vision view.

I'm using the internal GPS and therefore have the SIL=0 problem.
The only other problem I'm aware of is that I got a call from the FAA saying I wasn't transmitting Baro Alt, which I guess means I'm only sending GPS alt.
Even though the G430w is wired up and I assume configured for display 2, I've never looked for or seen TIS information there.

With the AMOC for the G430w, it looks like I can make myself legal for 2020 by wiring the G430 GPS serial out to the GPS rec input and reconfiguring the unit to use it.

Is that generally correct? Will it broadcast Sil=1 without further software upgrades?

I've seen some mention of issues with Baro altitudes but is anyone have trouble with the GTX327?
Ralph's AMOC has you covered for the 430W. No, it will broadcast a SIL=3. You select the certified GPS option and unplug the antenna to the internal GPS. 4.1.0 is going to report a SIL=3 regardless. (that's what pissed off the FAA) When 5.0 is release it will autodetect the 430w and still transmit a SIL=3. You will want to upgrade to 5.0.

The pressure altitude needs to come from your EFIS or a dedicated source. What is providing the pressure altitude to the 327? Perhaps you have an open circuit that just occurred recently. I would go to the status page to validate that you are getting pressure altitude to the navworx unit.

Also, there is a software bug in 4.1.0 that prevents traffic from being sent on Display Port 2. That is supposed to be fixed in 5.0 as well.
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
  #44  
Old 09-25-2017, 02:15 PM
MauleDriver's Avatar
MauleDriver MauleDriver is offline
 
Join Date: Aug 2006
Location: Lake Ridge Aero Park - Durham NC
Posts: 199
Default

Perfect, Thanks Bob!
Reply With Quote
  #45  
Old 09-27-2017, 11:28 AM
recapen recapen is offline
 
Join Date: Dec 2006
Location: Laurel, DE
Posts: 347
Default

MauleDriver - If you have questions about the 430W install, ask...there are some idiosyncrasies with that set-up...in and out!
__________________
Ralph E. Capen
RV6AQB N822AR @ N06
"Patience"
Reply With Quote
  #46  
Old 09-28-2017, 12:08 PM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default

Just got this in an email. While I don't like the delay, at least they're communicating.

bob

Attention: Customers Awaiting ADS600-B Upgrade & Certified ADS600-B NexGen 2.0

NavWorx Customers,

During a recent meeting between the FAA and NavWorx, the FAA has requested additional data from NavWorx referencing the upgrade for AD compliance of the certified system. Once this data is submitted the FAA has conservatively given a time period of 2 months to review.

Be assured that it is a priority for NavWorx to complete certification, not only for AD compliance but for 2020 Compliance as well.

We understand the urgency and frustration that may result with this delay. Be assured that NavWorx is working diligently to reach final certification.

To ensure customers are up to date on NavWorx' progress during this time frame, Dallas Avionics, Inc. will send out updates periodically.


Attention: NavWorx ADS600-EXP GPS Module for AD Compliance (P/N 200-9013)

NavWorx has received FAA approval for the experimental GPS Module "Doghouse" for AD resolution/compliance of existing ADS600-EXP Systems.

The part number of the ADS600-EXP will change to 200-9013, with the addition of the new GPS module, eliminating the AD on the original ADS600-EXP 200-8013 part numbers. No AMOC is required nor will be issued.

NavWorx has completed all design and verification to 14 CFR 91.227 and is waiting for shipment of the new GPS module from the manufacturer.

Thank You,
Dallas Avionics, Inc.
2525 Santa Anna Ave.
Dallas, TX 75228
Phone 214-668-7466
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
  #47  
Old 09-28-2017, 01:49 PM
recapen recapen is offline
 
Join Date: Dec 2006
Location: Laurel, DE
Posts: 347
Default

Bob - thanks for posting this update.
__________________
Ralph E. Capen
RV6AQB N822AR @ N06
"Patience"
Reply With Quote
  #48  
Old 10-02-2017, 07:52 AM
DavidBunin DavidBunin is offline
 
Join Date: Jan 2017
Location: Rockwall, TX
Posts: 57
Default

The "two months" or "60 days" phrasing is standard when seeking FAA approval (whether it is an STC, or a new type design, or a component).

What happens is that the FAA's internal review process for data can take up to 60 days. (Or at least their response is internally considered "overdue" if it runs longer than 60 days, not that being overdue means much.)

But the response to the data review can be one of (at least) two things. The happy response, of course is approval. The other response the FAA can give is to ask a question. Usually asking for more data. Then of course the ball is in the applicant's court to answer the FAA's question or provide the requested data. Once the FAA receives the applicant's response, a new 60-day clock starts before their review is again overdue.

If this sounds like it could potentially go on forever, it can. It is one of the more frustrating parts of certification.

My fingers are crossed that NavWorx can supply whatever data the FAA has most recently requested, and that the current request is the last one the FAA sends their way before approval.

My concern now is that the FAA rarely gets anything accomplished or approved after mid-November due to the holidays and office staff that need to burn off their vacation days prior to end-of-year. I think a late-September smack at that 60-day chess-move clock makes the chances of an approved solution (prior to AD compliance deadline) ... slimmer.

David

Last edited by DavidBunin : 10-02-2017 at 07:55 AM.
Reply With Quote
  #49  
Old 10-10-2017, 11:08 AM
txshan130 txshan130 is offline
 
Join Date: Oct 2011
Location: Katy, TX
Posts: 138
Default

Anyone else out there have a GRT Avionics Safe-Fly 2020 Compliant GPS Module and wondering if it could be used as a valid GPS position input for the Navworx ADS600-B? I have asked GRT for answers but still waiting on a response...

It outputs NMEA0183 position output via RS232...

For the guys who submitted the AMOC, I realize the Navworx manual doesn't specify the GRT GPS module as a possible position source, but then it also doesn't list any of the Garmin units (Garmin GTN 625, 635, 650, 725, or 750 GPS) that were approved with the AMOC. How did you get around this? I would have assumed that the Navworx manual would have to list any potential position source if the FAA were going to approve an AMOC for it.

So 2 questions for those who might know the answer:

1) Can the GRT Safe-Fly interface to the Navworx ADS600B via RS232 as a position source?

2) If able to interface, would it be possible to submit an AMOC for it?

Thx in advance...
__________________
Brian Shannon
Katy, TX
RV6 N7463B
Reply With Quote
  #50  
Old 10-10-2017, 11:19 AM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default

Quote:
Originally Posted by txshan130 View Post
Anyone else out there have a GRT Avionics Safe-Fly 2020 Compliant GPS Module and wondering if it could be used as a valid GPS position input for the Navworx ADS600-B? I have asked GRT for answers but still waiting on a response...

It outputs NMEA0183 position output via RS232...

For the guys who submitted the AMOC, I realize the Navworx manual doesn't specify the GRT GPS module as a possible position source, but then it also doesn't list any of the Garmin units (Garmin GTN 625, 635, 650, 725, or 750 GPS) that were approved with the AMOC. How did you get around this? I would have assumed that the Navworx manual would have to list any potential position source if the FAA were going to approve an AMOC for it.

So 2 questions for those who might know the answer:

1) Can the GRT Safe-Fly interface to the Navworx ADS600B via RS232 as a position source?

2) If able to interface, would it be possible to submit an AMOC for it?

Thx in advance...
To get an AMOC approved, you have to substantiate to the FAA that the GPS meets all their requirements. Doing this from scratch is a rather onerous task.

The reason we were able to turn the AMOCs around quickly was that the Garmin GPSs were already approved position sources for other ADSB vendors. We didn't have to prove they met the requirements, since they were previously approved by others. All we had to do was document how they were going to be interfaced with the ADS600-B.

In other words, if you don't see the GPS on this list (https://www.faa.gov/nextgen/equipadsb/equipment/), you'll have a whole lot of data you'll have to document and get reviewed by the FAA.

While the Navworx manual may not have listed all the Garmin GPS by specific model number, it does have the interface requirements, which are identical for all of them. You mentioned the GTN series, which was my AMOC. You have two interface options (ARINC and RS-232) and the protocol is ADSB+. Per the second round of AMOCs, any of the GTN family will meet these requirements.
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -6. The time now is 06:12 AM.


The VAFForums come to you courtesy Delta Romeo, LLC. By viewing and participating in them you agree to build your plane using standardized methods and practices and to fly it safely and in accordance with the laws governing the country you are located in.