NavWorx tech issues - help each other

[FORANE]

Originally Posted by wnplt

Does anyone know where I can get the navworkx config software and latest software? I have the non exp navworks.

Thanks in advance

Steve

Steve,
email incoming...

[rv6n6r]

Originally Posted by gyoung

I just got mine rewired to use my 430W and got the same yellow block [NACv] on the papr. It's not red so I'm going to ignore it and fly on.

The above is from several months back; I just found it in a search since I had the same thing on a recent ADS-B report. About it, the FAA ADS-B Users guide says:

Note on NACv: The FAA has not approved, or otherwise evaluated, any ADS‐B position source
with the horizontal velocity accuracy performance required to transmit a NACv value greater
than 2 (NACv of 2 = Estimated Velocity Uncertainty <3 m/s). When NACv MIN and/or AVG are
highlighted yellow in the Integrity & Accuracy table of the report (i.e. transmitted NACv
MIN/AVG is 3 or 4) you are advised to contact your installer and/or applicable ADS‐B avionics
manufacturer for guidance on how to change the NACv value to that approved by the FAA at
certification, or for non‐certified equipment, a NACv value not to exceed 2 without FAA
evaluation.

Obviously I'm not going to be able to contact my ADS-B avionics manufacturer... any other help here? Position source is a Garmin 400W. Would this be an issue coming from the position source, or the NAVWORX? The "you are advised to..." language is interesting as it seems to imply that this is not a strict requirement or failure. But still..."

[FORANE]

Originally Posted by rv6n6r

The above is from several months back; I just found it in a search since I had the same thing on a recent ADS-B report. About it, the FAA ADS-B Users guide says:

Note on NACv: The FAA has not approved, or otherwise evaluated, any ADS‐B position source
with the horizontal velocity accuracy performance required to transmit a NACv value greater
than 2 (NACv of 2 = Estimated Velocity Uncertainty <3 m/s). When NACv MIN and/or AVG are
highlighted yellow in the Integrity & Accuracy table of the report (i.e. transmitted NACv
MIN/AVG is 3 or 4) you are advised to contact your installer and/or applicable ADS‐B avionics
manufacturer for guidance on how to change the NACv value to that approved by the FAA at
certification, or for non‐certified equipment, a NACv value not to exceed 2 without FAA
evaluation.

Obviously I'm not going to be able to contact my ADS-B avionics manufacturer... any other help here? Position source is a Garmin 400W. Would this be an issue coming from the position source, or the NAVWORX? The "you are advised to..." language is interesting as it seems to imply that this is not a strict requirement or failure. But still..."

I just flew my ADS600-B 200-0012 using a 430W as position source. My compliance report was perfect except for the NACv. My NACv was also yellow with avg: 3.7, min: 3, max: 4. My flight was very short duration, at low altitudes, and around the Appalachian mountains lower than ridges. Suspect low altitude; will try flying a bit and see. A search of this site for NACv yields many results; here's one:
http://www.vansairforce.com/communit...d.php?t=156572

[FORANE]

Just installed an ADS600-B with 430W as position source, 327 transponder.
Passed PAPR report.

Fails to get traffic on 430W (430W ARINC wired per schematic for traffic and setup for 330 transponder per install manual. ADS600-B ARINC 429 port setup display type: ARINC 429 traffic advisories, high baud rate and ARINC 429 installed checkbox checked)

Fails to get traffic on GRT HX (HX serial 7 in wired to serial port 1 out of ADS600-B per install manual; HX serial 7 in setup to receive ads-b, ADS600-B serial 1 out setup for display type: traffic alerts at baud 115,200 both HX and 600-B)

Fails to get traffic on AVARE Samsung TF700 tablet using WIFI and ADS600-B display port 2 set to display type TIS-A.


Any ideas why no traffic?

[FORANE]

Just learned ARINC was not standard on these boxes. Rather, ARINC was an optional add on card. So, if your ARINC doesn't function it may be due to lacking the optional add on card.

[maniago]

Originally Posted by FORANE

Just learned ARINC was not standard on these boxes. Rather, ARINC was an optional add on card. So, if your ARINC doesn't function it may be due to lacking the optional add on card.

Actually, I have an ARINC box and interestingly, the lines are active (ie my GNS480 does not give me a failure and I get a traffic box), but no traffic is being passed on them and the box is just a quiet blank screen, so I pulled them, and I'm passing traffic to my 2xGRT Hxr with no issues.

[maniago]

Originally Posted by FORANE

Just installed an ADS600-B with 430W as position source, 327 transponder.
Passed PAPR report.

Fails to get traffic on 430W (430W ARINC wired per schematic for traffic and setup for 330 transponder per install manual. ADS600-B ARINC 429 port setup display type: ARINC 429 traffic advisories, high baud rate and ARINC 429 installed checkbox checked)

Fails to get traffic on GRT HX (HX serial 7 in wired to serial port 1 out of ADS600-B per install manual; HX serial 7 in setup to receive ads-b, ADS600-B serial 1 out setup for display type: traffic alerts at baud 115,200 both HX and 600-B)

Fails to get traffic on AVARE Samsung TF700 tablet using WIFI and ADS600-B display port 2 set to display type TIS-A.


Any ideas why no traffic?

I have similar gear to you (see sig block)....As noted above, I also cant get traffic on the ARINC lines going to my GNS480 - I get signal, but no traffic, go figure. Gave up on that.

On the HXr, I'm sending from Pin5 to both HXr B23. I found that tho the documentation says you can get traffic off both Navworx Pin 5 or Pin 25, its not true - its one or the other, not both.

As for configurations:
Display side
HXr set to Zaon PCAS Traffic, 9600 baud
Alt Encoder: HxR set to Upsat Format, 9600
ADBS source: 480, 9600
Xpndr receive: 327 , FADC with Alt

Navworx side
Alt Encodr: Upsat Apollo, 9600
Display: Traffic Alerts ,9600
Control Panel: 327
GPS source: ADSB Out and Compliant

I havent flown yet, so I cant comment on if the FAA will like it, but I get traffic alerts in my garage and the Navworx configuration program gives me all green and the traffic shows up on both HxRs.

Do you have a Navworx box with Wifi in it? I'd heard that none of those ever were shipped, and tho I have the 9pin serial output hanging to add a serial-to-wifi dongle, I havnet done that yet. Curious on your implementation in this regard.

[FORANE]

Originally Posted by maniago

I have similar gear to you (see sig block)....As noted above, I also cant get traffic on the ARINC lines going to my GNS480 - I get signal, but no traffic, go figure. Gave up on that.

On the HXr, I'm sending from Pin5 to both HXr B23. I found that tho the documentation says you can get traffic off both Navworx Pin 5 or Pin 25, its not true - its one or the other, not both.

Alot to digest here; will break it down in pieces. There is a known bug in the software that won?t display traffic on both display ports. You can only use one display port at a time.

Originally Posted by maniago

As for configurations:
Display side
HXr set to Zaon PCAS Traffic, 9600 baud
Alt Encoder: HxR set to Upsat Format, 9600
ADBS source: 480, 9600
Xpndr receive: 327 , FADC with Alt

Navworx side
Alt Encodr: Upsat Apollo, 9600
Display: Traffic Alerts ,9600
Control Panel: 327
GPS source: ADSB Out and Compliant

I may try these settings but have a question.
The EFIS I have is a GRT HX. I only use it on the full attitude indicator screen - no split screen, no map, no engine monitoring...
Do you know if it will even display traffic at all when only set to the attitude indicator with synthetic vision screen?

Originally Posted by maniago

I havent flown yet, so I cant comment on if the FAA will like it, but I get traffic alerts in my garage and the Navworx configuration program gives me all green and the traffic shows up on both HxRs.

Getting traffic in your garage is interesting. I wasn't expecting it until above a couple thousand feet. I flew my install yesterday for 8 minutes and passed the PAPR.

Originally Posted by maniago

Do you have a Navworx box with Wifi in it? I'd heard that none of those ever were shipped, and tho I have the 9pin serial output hanging to add a serial-to-wifi dongle, I havnet done that yet. Curious on your implementation in this regard.

I bought Bob's box. No WIFI in it but does have wired serial to WIFI adapter. I have wired it but need to go back to the plane and test its functionality. Was more interested in getting 3 greens, making sure it was a compliant install, getting back in the air after a maintenance hiatus and ensuring the plane didn't have squaks after the maintenance.

[maniago]

Originally Posted by FORANE

Alot to digest here; will break it down in pieces. There is a known bug in the software that won?t display traffic on both display ports. You can only use one display port at a time.

Indeed, I know; didnt know if you knew, but the outcome is the same.

Originally Posted by FORANE

I may try these settings but have a question.
The EFIS I have is a GRT HX. I only use it on the full attitude indicator screen - no split screen, no map, no engine monitoring...
Do you know if it will even display traffic at all when only set to the attitude indicator with synthetic vision screen?

Uh, dont know the Hx presay, tho obviously the HXr is its progeny and I use 95% of the Hx manual to configure the Hxr. In anycase, I get traffic specifically on a traffic inset. I know its supposed to show up on the main synthetic screen, and I think I've seen it, but cant be sure - my traffic blinks in and out and tho its different locations and altitudes, I think its actually my reflection off the concrete floor. But I'll get a hit about once every 5 or 6 secs and then it'll disappear in a few secs. I dont think thats long enough for the synscreen to process it, and if it is, its rarely in my(static) direction of travel.

Originally Posted by FORANE

Getting traffic in your garage is interesting. I wasn't expecting it until above a couple thousand feet. I flew my install yesterday for 8 minutes and passed the PAPR.

Yup I didnt know what to expect, but was digging it when I got hits....good to know on the PAPR

Originally Posted by FORANE

I bought Bob's box. No WIFI in it but does have wired serial to WIFI adapter. I have wired it but need to go back to the plane and test its functionality. Was more interested in getting 3 greens, making sure it was a compliant install, getting back in the air after a maintenance hiatus and ensuring the plane didn't have squaks after the maintenance.

LOL I tried to buy Bobs box as a back up (twice), but low balled him both times because it didnt have ARINC, but he wouldnt respond to me. Oh well.

I spent in inordinate amount of time getting the Navworx box to work - basically zero help really anywhere, I guess cause there are so many diff mfgr boxes that would be in a configuration, and catching a similar person is nae impossible. If you wanna chat via phone, pm me and I'll help you best I can.

[FORANE]

Thanks Mani, I may take you up on that.
I also bought a 200-0013 as a backup. Any idea if there is a way to know if a box has ARINC besides wiring it up and seeing if it works?