VansAirForceForums  
Home > VansAirForceForums

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

- Today's Posts | Insert Pics


Go Back   VAF Forums > Avionics / Interiors / Fiberglass > ADS-B
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 02-03-2017, 08:53 AM
recapen recapen is offline
 
Join Date: Dec 2006
Location: Laurel, DE
Posts: 328
Default NavWorx tech issues - help each other

Folks,

I know there are at least a couple of us out here with NavWorx equipment with non-AD related technical issues...while waiting for NavWorx to respond to our technical issue help requests, we should attempt to help each other.

To that end, I have a 6A with a NavWorx ADS600B -13 connected to a 430W, SL-70, and MX-20...

My unit displays "Ready for Flight" and "TX/RX Error", while not actually working. The "TX/RX Error" only showed up after I was able to get the transmitter turned on...which required installation of an older version of software as the "Activate Transmitter" feature had been removed from later software versions - then upgrading to the latest required software.

All of the other attached equipment in my environment appears to be working properly and communicating with the ADS600B -13 unit.

I can offer my environment to help test other folks units that are having technical issues. I would also request that others make available their working environment to test our non-working equipment in as well as known-good equipment for testing in our environment. Since we have some time before the 2020 mandate and don't know the NavWorx ongoing support status - this is most likely our best solution...aside from abandoning the NavWorx hardware and repurchasing an alternate solution.

Thanks for your collective consideration,
__________________
Ralph E. Capen
RV6AQB N822AR @ N06
"Patience"
Reply With Quote
  #2  
Old 02-03-2017, 10:53 AM
krhea krhea is offline
 
Join Date: Nov 2011
Location: Peck, Kansas
Posts: 125
Default Navworx tech issues

Ralph:

I am not qualified to help your situation in any way that I know of.

I had my own problems with my ads600b -0012. They were of my own doing.

First I managed to buy a TT21 transponder when I should have bought a TT22.
That TT21 is sold and in the hands of someone that can install it and be compliant. A Sandia STX165R is going in shortly.

I also have an MGL IEFIS Explorer light. My error is in not knowing and not finding that in the Transponder control from the Iefis that altitude data (Barometric altitude) is transmitted in that serial control. So I had another serial port set up to transmit Icarus altitude data to a serial port on the Navworx. 2 sources of bar altitude data.

I think I finally have a better grasp of my installation but I have spent a lot of time going over the myriad of manuals to arrive at what I hope to be a working system.

Maybe we ought to have a Navworx fly-in just to learn and discuss these sort of issues.

What really got me to concentrate on my installation was a Call from the FAA which in essence was to let me know that my barometric altitude was intermittent, he even sent me the Google earth files. I think understand where the altitude stops. If I turned the TT21 off, then the Navworx would get passing results. So maybe in replacing the transponder I can get some good scores and not be concerned with that.
No I did not have suppression connected, I thought the Iefis controlled that?

I would help any way I can.

thanks

Keith Rhea
RV7 250 hours in 26 months( 24 months to build)
2017 dues paid
Reply With Quote
  #3  
Old 02-03-2017, 10:59 AM
Mike S's Avatar
Mike S Mike S is offline
Senior Curmudgeon
 
Join Date: Sep 2005
Location: Dayton Airpark, NV A34
Posts: 14,855
Default

Quote:
Originally Posted by recapen View Post
Folks,

I know there are at least a couple of us out here with NavWorx equipment with non-AD related technical issues...while waiting for NavWorx to respond to our technical issue help requests, we should attempt to help each other.
Great idea, gonna make this thread a "Sticky" so it will be easy to find in the future.
__________________
Mike Starkey
VAF 909

Rv-10, N210LM.

Flying as of 12/4/2010

Phase 1 done, 2/4/2011

Sold after 240+ wonderful hours of flight.

"Flying the airplane is more important than radioing your plight to a person on the ground incapable of understanding or doing anything about it."
Reply With Quote
  #4  
Old 02-03-2017, 11:15 AM
recapen recapen is offline
 
Join Date: Dec 2006
Location: Laurel, DE
Posts: 328
Default

Thanks...To Mike for making this a sticky...until NavWorx starts answering their phones and e-mails, I think user collaboration is our best next steps!

Keith, once you get yours working consistently, I would like to send you my -13. The main difference is mine has ARINC - if I recall, they both have "non-tso'd" GPS in them. If you don't mind putting it in your plane and configuring it like yours and let me know if you get the same "TX/RX Error" message that I get....that should tell me that it is the NavWorx box and not my environment. Let me know if you're OK with this...and when! Mine's not working meanwhile anyway - due to something that my initial conversation with Bill Moffitt needed to be cleared...he provided some tests to perform which did not change the outcome.
Thanks,
__________________
Ralph E. Capen
RV6AQB N822AR @ N06
"Patience"
Reply With Quote
  #5  
Old 02-03-2017, 11:30 AM
krhea krhea is offline
 
Join Date: Nov 2011
Location: Peck, Kansas
Posts: 125
Default Navworx tech issues

Ok by me, will let you know in a couple of weeks, new transponder cert set for week of Feb 13?

Thanks

Keith
Reply With Quote
  #6  
Old 02-03-2017, 07:27 PM
rzbill's Avatar
rzbill rzbill is offline
 
Join Date: Nov 2005
Location: Asheville, NC
Posts: 2,616
Default

I have a NavWorx ADS600-BG (not affected by AD) running to a GRT EFIS display.

When I have the system set to show Metars, no matter how hard I press on the screen, I can't get the airports shown as IFR to change to VFR.
__________________
Bill Pendergrass
ME/AE '82
RV-7A: Flying since April 15, 2012. 850 hrs
YIO-360-M1B, mags, CS, GRT EX and WS H1s & A/P, Navworx
Unpainted, polished....kinda'... Eyeballin' vinyl really hard.
Yeah. The boss got a Silhouette Cameo 4 Xmas 2019.
Reply With Quote
  #7  
Old 02-07-2017, 05:39 PM
krhea krhea is offline
 
Join Date: Nov 2011
Location: Peck, Kansas
Posts: 125
Default Good adsb performance report

I finally got my new transponder installed and set up only to find out after about 6 hours of head scratching that I had crossed TX-TX and RX-RX for the transponder control to the Navworx. Once that got fixed, had a good configuration and a "Ready for Flight" so I took off did a short 30 minute flight up the east side of Wichita at 5500 feet and got a good report with only a .069% errors on flight ID.


Keith Rhea
RV7 0-320 Catto prop, MGL, Navworx, Sandia
Paid 2017.
Reply With Quote
  #8  
Old 01-19-2018, 08:12 AM
cardmarc cardmarc is offline
 
Join Date: Jan 2018
Location: tx
Posts: 4
Default Navworx issues after AMOC work, GNS 480 port 3 ADSB+ out position info

Quote:
Originally Posted by recapen View Post
Folks,

I know there are at least a couple of us out here with NavWorx equipment with non-AD related technical issues...while waiting for NavWorx to respond to our technical issue help requests, we should attempt to help each other.

To that end, I have a 6A with a NavWorx ADS600B -13 connected to a 430W, SL-70, and MX-20...

My unit displays "Ready for Flight" and "TX/RX Error", while not actually working. The "TX/RX Error" only showed up after I was able to get the transmitter turned on...which required installation of an older version of software as the "Activate Transmitter" feature had been removed from later software versions - then upgrading to the latest required software.

All of the other attached equipment in my environment appears to be working properly and communicating with the ADS600B -13 unit.

I can offer my environment to help test other folks units that are having technical issues. I would also request that others make available their working environment to test our non-working equipment in as well as known-good equipment for testing in our environment. Since we have some time before the 2020 mandate and don't know the NavWorx ongoing support status - this is most likely our best solution...aside from abandoning the NavWorx hardware and repurchasing an alternate solution.

Thanks for your collective consideration,
Here's my issue:
Used AMOC to connect compliant position source to Navworx box and disconnected the internal Navworx gps via rs232
Equipment interconnected:
Navworx 600B-13 (AD unit) with 429 option, wifi adapter
Aspen PFD & MFD (mfd did get traffic prior to this change)
GMX 200 using 422 lines from Navworx box (port 1?)
SL 70 set up as 'remote' to supply rs232 baro alt and squawk code to Navworx box

Issues:
1. never got Navworx wifi to send traffic via wifi on port 2 to my Wing x pro, but FIS worked (will we ever get a fix for that? UAT 5.0?)
2. After connecting the GNS 480 port 3 ADSB+ out, I had to select the 430/530 drop down to get the 3 green 'ready for flight' boxes on the 4.1 UAT console outside test
3. (This is bad) I cannot now get the GMX200 port 4 422 to show the Navworx test traffic/FIS or my N #. DATA SEEMS INTERMITTENT, when looking at data tab on mx200 data tab
Any ideas on WHAT is going on?
MW
Reply With Quote
  #9  
Old 01-19-2018, 08:13 AM
cardmarc cardmarc is offline
 
Join Date: Jan 2018
Location: tx
Posts: 4
Default Navworx issues after AMOC work, GNS 480 port 3 ADSB+ out position info

Quote:
Originally Posted by recapen View Post
Folks,

I know there are at least a couple of us out here with NavWorx equipment with non-AD related technical issues...while waiting for NavWorx to respond to our technical issue help requests, we should attempt to help each other.

To that end, I have a 6A with a NavWorx ADS600B -13 connected to a 430W, SL-70, and MX-20...

My unit displays "Ready for Flight" and "TX/RX Error", while not actually working. The "TX/RX Error" only showed up after I was able to get the transmitter turned on...which required installation of an older version of software as the "Activate Transmitter" feature had been removed from later software versions - then upgrading to the latest required software.

Add me to you list. More later.

All of the other attached equipment in my environment appears to be working properly and communicating with the ADS600B -13 unit.

I can offer my environment to help test other folks units that are having technical issues. I would also request that others make available their working environment to test our non-working equipment in as well as known-good equipment for testing in our environment. Since we have some time before the 2020 mandate and don't know the NavWorx ongoing support status - this is most likely our best solution...aside from abandoning the NavWorx hardware and repurchasing an alternate solution.

Thanks for your collective consideration,
Here's my issue:
Used AMOC to connect compliant position source to Navworx box and disconnected the internal Navworx gps via rs232
Equipment interconnected:
Navworx 600B-13 (AD unit) with 429 option, wifi adapter
Aspen PFD & MFD (mfd did get traffic prior to this change)
GMX 200 using 422 lines from Navworx box (port 1?)
SL 70 set up as 'remote' to supply rs232 baro alt and squawk code to Navworx box

Issues:
1. never got Navworx wifi to send traffic via wifi on port 2 to my Wing x pro, but FIS worked (will we ever get a fix for that? UAT 5.0?)
2. After connecting the GNS 480 port 3 ADSB+ out, I had to select the 430/530 drop down to get the 3 green 'ready for flight' boxes on the 4.1 UAT console outside test
3. (This is bad) I cannot now get the GMX200 port 4 422 to show the Navworx test traffic/FIS or my N #. DATA SEEMS INTERMITTENT, when looking at data tab on mx200 data tab
Any ideas on WHAT is going on?
MW
Reply With Quote
  #10  
Old 01-19-2018, 08:49 AM
flightlogic's Avatar
flightlogic flightlogic is offline
 
Join Date: Nov 2013
Location: Prescott, AZ
Posts: 1,568
Default Kudos

I want to take time out to thank Bob Leffler. In trying times, an individual will often step forward to help those in need. I see tech support from the back end, since I work for Dallas Avionics. We are trying hard to make right what Navworx made wrong. Bob is helping those who are still trying to work around the bad GPS receiver chip set. The combinations of black boxes and hence, serial data streams becomes increasingly complex... exponentially.
I see posters here who are brand new.... and struggling for information. We need to recognize the effort of those who do it purely from an altruistic drive.
Thanks Bob.
__________________
"Kindness is never a bad plan."

Work bio: Avionics tech support; ATP rated in planes and Helicopter Instructor law enforcement tactical radio systems. Blessed to fly my RV9A to work every week.
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 03:02 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.