Hi Dennis,
I did a write up a while back on wiring that exact setup for an RV-12. Let me know if you can't find the forum thread and I'll send you a link.
Neil
Hi Dennis,
I did a write up a while back on wiring that exact setup for an RV-12. Let me know if you can't find the forum thread and I'll send you a link.
Neil
Do you have another GPS in the aircraft? If so, you may be able to temporarily swap antenna if the other antenna is supported by Navworx.
Which brand and model of GPS antenna do you currently have on the Navworx? I think I may have mentioned it earlier, but Garmin had a large failure rate on their GA 35. It was limited to a certain time period, which I can't recall at the moment. Mine failed just after the warranty expired.
Now I need the pinouts for the USB side so I can build a cable to test it with.
The red->3/green->33/black->32 is good for the ADS600B side - I need what goes to where on the USB connector side.
Noted one problem with the WiFi. My iPhone 5 did a great job of showing traffic and weather. My newer iPad mini 4 did not show traffic and was indicating that I had 0 stations while the iPhone showed 5. Anybody run into this?
I have an EXP. traffic showed on both my iPad mini 2 and my new iPad mini 4 but the former always showed the same number of stations as my GRT Sport SX whereas the latter always shows zero. Also the 2 showed radar but the 4 does not. Both will show weather at reporting AWOS sites but the 2 seemed to pick them up quickly, the 4 takes forever to update. iOS issue maybe?
Noted one problem with the WiFi. My iPhone 5 did a great job of showing traffic and weather. My newer iPad mini 4 did not show traffic and was indicating that I had 0 stations while the iPhone showed 5. Anybody run into this?
This is a known bug with 4.1.0 on the ADS600-B. Traffic isn't transmitted on both Display ports. Most common occurrence is that your EFIS is on Port 1 and your wifi dongle is on Port 2. The was supposed to be fixed in 5.0.
Please note which unit you have. The OS and issues are different for each platform.
Bill, I Tried to send it directly - your e-mail bounced....
I think I'm ready for the AMOC work.
I made a flight over the weekend and pulled the Public ADS-B Performance Report for the flight. All looked good - no reds. I think that report is the final arbiter of whether my installation is satisfactory.
The only yellow mark was for NACv (Navigational accuracy velocity); Avg=4, Min=3, Max=4. The Avg and Min were marked in yellow, perhaps because they weren't both = 4. It seems that this value is determined by use of the G430w as the GPS source but I'm not clear on it
Unfortunately, I never could get the UAT Console to display "UAT Configured" and "Ready for Flight" consistently in green. I recall getting this readings sporadically but ended my last configuration session with mixed results.
Bill "satisfied but cautious" Watson
Frankly, I assumed that I was taking off in receive-only mode at best. My intent was to get the report and start twiddling with the configuration. I was surprised with the success.That last sentence causes some concern. Which of the three indicators aren?t green? It?s my understanding without all three being green, it won?t transmit.
The AMOC is a simple process, just send a copy of the 430 amoc, State you followed the instructions and placarded the Navworx box, and the n# of your RV-10 to the manager of you local FSDO. It?s just a notification procedure, not an approval.
I had the same problem when I started my testing...
Are you "in" a hangar? Can your 430W's GPS antenna "see" the satellites?
My metal roof hangar was a Faraday cage and prevented GPS reception - even with the doors open. I had to rig up a remote antenna and stick it outside.
Your successful flight implies my solution might help your ground testing as well.....
Frankly, I assumed that I was taking off in receive-only mode at best. My intent was to get the report and start twiddling with the configuration. I was surprised with the success.
I never had the "Ready for Flight" lit.
On the Status page, my last readings were GPS Source = failed, Transmitter Control = passed, Alt Encoder = passed. I had a lot of different combinations of things as I tried different options on the 600B, G430w and G327.
I do still have the internal GPS antenna hooked up but I noticed that the current software doesn't even seem to recognize that GPS as a option so I assume it is 'offline'.
Am I getting a false positive from the FAA report?
I need the UAT console that supports the Garmin 430W/600B AMOC. My version does not have an input option for the 430w. If someone could email version 4.1.0 I would be thankful.
Eulice Curington
RV-10 N104EW
Still Painting
Send me an email, do NOT PM me. If you click on my userid, you?ll find a link to email me.
I was just told by a non-Garmin source that Format 2 is something Garmin made for their GDL 82 device.
So if you're looking for ADSB+, select ADSB+ Format 1
Here's my issue: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: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,