Quote:
Originally Posted by recapen
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