NavWorx tech issues - help each other

[flightlogic]

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.

[recapen]

MW,

Port 2 has not ever worked (regardless of whether it was configured as 232 or wifi)...supposed to be a fix in 5.0(don't hold your breath).

Getting the three Green Ready for flight indicates that you are getting position from your 480 while getting squawk and altitude from your SL-70. What baud rate are you running the SL-70 at and is it configured in the NavWorx box as SL-70R? The reason I ask this question specifically is from my installation, the SL-70R configuration (Extended output and 9600baud) is the only one that will receive changes to the squawk code from the transponder. I had been working with NavWorx on this issue prior to them shuttering operations...running the transponder at 9600Baud prohibits it from communicating altitude data to my MX-20 - I'm working around that by replacing my Alt Encoder with a serial capable ACK A30.9.

I have the MX-20 instead of the GMX200 - but they should be similar... My MX-20 is configured to receive GDL90 UAT Radio on port 4. Are you using both the transmit and receive 422 pairs? I would ring out the wiring for the GMX200 - ADS600B interconnect...at one point I had one itty-bitty shield wire touching one of my signal wires and it went intermittent on me.

With the exception of the ADS600B/SL-70/MX20 interoperability mismatch, mine works well - I get traffic and weather on my MX-20 and traffic on my 430W.

[cardmarc]

Recapen,
Thanks for your reply.
I have a panel mount SL70 connected to my panel mount GNS480 and both connected via RS232. I also have an Aspen PFD connected to the GNS480 via the 429 lines. The Aspen PFD send its' encoded altitude to the 480, which sends it to the SL70, which sends it to the Navworx 600B.
However, the NavWorx MUST be set to the 'remote' SL70 to allow the NavWorx to accept the squawk code and alt from my panel mount SL70. My SL70 is set on the 'extended' mode (this was discovered by Navworx when we went thru my initial installation years ago). I seem to recall it is set on 9600 baud. Counter-intuitive, but it works!
Also counter intuitively, the NavWorx 4.1.0 console input tab MUST be set to the drop down tab for the 430/530 ADSB+ out (AND NOT the 480 drop down, if using the 480 newish port 3 output, not the 743 output) in order for the NavWorx to accept the ADSB+ position info. Supposedly 5.0 was supposed to 'fix' that (and the port 2 traffic output to Xpro via wifi--surprising the FIS works!). I see little hope 5.0 will EVER be issued.
My GMX200 422 port 4 display is working fine now (shows traffic and weather) on the NavWorx port 1 422 output. I goofed up one of the 422 wires-shield bad, just like you said- when I added the circuit for the ADSB+ position output-my bad. Fixed now, it's fine.

All I need now is to get a new performance report with no red boxes. Last one I had (ran for less than a min), I had a red box on the baro alt box, but I am thinking that is a fluke due to the short low altitude short run time.
MW

[rleffler]

Originally Posted by flightlogic

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.

I appreciate the recognition. I try to help where I can.

Unfortunately I?ve been overwhelmed with requests from various folks requesting assistance. Many don?t understand the technology or Avionics installed in their aircraft. It?s one thing to answer a quick question. It?s totally different in helping somebody figure out their installation or why something doesn?t work correctly.

I just don?t have the time to respond to all the requests. I would recommend calling Saint Aviation, SteinAir, or Aerotronics for Support. They do this for a living and can be much more responsive than I can. You will most likely have to pay for that Support.

The most often question is for specific schematic information. I can tell you that all the AMOCs that are available on AOPA state to follow Navworx installation instructions. There is no other magic required for the AMOC.

The second most often request is for a copy of the manual or software. The -39 version of the manual is what the AMOCs are based upon, using 4.1.0 code. It always amazes me that people have the ADS600-B installed in their aircraft, but don?t have either of these.

There are many issues with distributing large EXE files. Most mail clients will not allowing receipt of such files. Please do not ask me for them. I would recommend a post on VAF requesting help. You will get a much quicker,response than I can provide.

If you post a request in this thread for assistance, please State which model Navworx unit you may have. The only AMOC available for the EXP is to turn the transmitter off. All the other AMOCs are for the 600-B.

I only speak for myself and not the othe AMOC authors. However, I?ve been told they are experiencing similar requests. I apologized for being so long winded. Thanks for understanding. I will continue to assist where I can, but only through posts here on VAF, and not via PMs or emails.

[recapen]

Thanks to Bob Leffler referring Roy Thoma to me...allowing Roy to get rid of his unit and allowing me to test it with my configuration.

Come to find out that my original unit was not fully repaired when it went back for its serial port issues. The unit was not allowing the use of serial port input from my SL-70 unless it was configured as a SL-70R @ 9600 Baud - rendering it useless in providing data to my MX-20...which only takes 1200 baud inputs.

This is reinforcing my desire to abandon this platform as well.

Looking at a FreeFlight RANGR as a functional drop-in replacement.

Again Thanks Bob and Roy!

[Warrior161]

I was reading mauledrivers posts on your progress and you have a similar problem that i have. Garmin 430w as portion source and I get Yellow highlighted NACv min avg on the papr report my numbers are the same too 4 avg and 3 min. Everything else is perfect!! Did you ever get that resolved? Is the FAA not worried about it? Or are you taking the approach they don't ask I won't bring it up either. BTW the last idea is my choice for now. Anybody having the same problem as mauledrivers and me.

Thanks on any info it is truly appreciated.

[DavidBunin]

Originally Posted by rleffler

Unfortunately I?ve been overwhelmed with requests from various folks requesting assistance. Many don?t understand the technology or Avionics installed in their aircraft. It?s one thing to answer a quick question. It?s totally different in helping somebody figure out their installation or why something doesn?t work correctly.

I just don?t have the time to respond to all the requests.

Let me be the first to say that Bethany knows EXACTLY how you feel.

And, while being far from the first one to do so, I also want to say Thank You.

David

[flightlogic]

Folks might want to review the search function here on Van's. There is another thread discussing how to convert from Navworx to uAvionix products. Since I work for a distributor that sells replacement systems to end users, I have had my share of calls seeking assistance. Some of the requests have turned into multi-hour quests for wiring schematics. I kind of find this fun... to a certain extent. I always suggest builders and owners keep a good file of these schematics, as you don't know when you will have to reference them again. If an owner did not install the avionics, this ADS-B process is a good opportunity to learn much more about your aircraft. Knowledge is power... and power is 14.7 volts. (well, technically we might refer to amps...)
Anyway, have fun and watch for traffic out the canopy TOO!

[hilltopkid]

We are trying to evaluate our ADS600-B for AMOC and cannot communicate with the unit. We have the 4.1 install software (includes 4.1 console sw) which runs in Win 10, but there are no COM ports presented in the selection box. Our serial-USB adapter works and is configured to the correct baud rate, etc. We also have verified the wiring to the maintenance port.

Has anyone encountered this type problem?

Any ideas?

Thanks,

Dee

[gyoung]

Originally Posted by Warrior161

I was reading mauledrivers posts on your progress and you have a similar problem that i have. Garmin 430w as portion source and I get Yellow highlighted NACv min avg on the papr report my numbers are the same too 4 avg and 3 min. Everything else is perfect!! Did you ever get that resolved? Is the FAA not worried about it? Or are you taking the approach they don't ask I won't bring it up either. BTW the last idea is my choice for now. Anybody having the same problem as mauledrivers and me.

Thanks on any info it is truly appreciated.

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