VansAirForceForums  
Home > VansAirForceForums

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

- Today's Posts | Insert Pics

  #141  
Old 11-09-2017, 02:51 PM
MauleDriver's Avatar
MauleDriver MauleDriver is offline
 
Join Date: Aug 2006
Location: Lake Ridge Aero Park - Durham NC
Posts: 199
Default

My reading of the yellow spots doesn't suggest that there is necessarily a problem.

As far as the FSDO is concerned, they didn't ask for it, and while I broke the rule of not offering up more than asked, the report was mentioned in our communications.

I have the feeling that it will not be part of my next report.
Reply With Quote
  #142  
Old 12-28-2017, 01:49 PM
MauleDriver's Avatar
MauleDriver MauleDriver is offline
 
Join Date: Aug 2006
Location: Lake Ridge Aero Park - Durham NC
Posts: 199
Default

I still get the yellow spots. No concern on the part of my FSDO. I don't think the yellow NACv result is a problem.
Reply With Quote
  #143  
Old 01-03-2018, 07:20 PM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default Garmin ADSB + Format 1 and Format 2

Charlie Waffles brought this to my attention.

I upgraded to 6.41 after I worked on the AMOC. At that time, the only choices were ADSB and ADSB+. After upgrading to 6.41, there is now an ADSB+ Format 1 and an ADSb+ Format 2. The question that I was asked was which one of these are the right option for the AMOC. This caught me totally off guard.

I check my GTN 650 tonight. After the 6.41 upgrade what was ADSB+ was changed to ADSB+ Format 1.

A question for g3xexpert is my assumption that Format 1 the same as the original ADSB+? Then what is different with Format 2 and what requires that setting?
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
  #144  
Old 01-04-2018, 11:06 AM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default

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
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
  #145  
Old 01-06-2018, 05:55 AM
ecurington ecurington is offline
 
Join Date: Nov 2007
Location: Melbourne Florida
Posts: 111
Default UAT Console 4.1.0

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
Reply With Quote
  #146  
Old 01-06-2018, 06:18 AM
rleffler's Avatar
rleffler rleffler is offline
 
Join Date: Jun 2006
Location: Delaware, OH (KDLZ)
Posts: 4,196
Default

Quote:
Originally Posted by ecurington View Post
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.
__________________
Bob Leffler
N410BL - RV10 Flying
http://mykitlog.com/rleffler
Reply With Quote
  #147  
Old 01-06-2018, 10:44 AM
ecurington ecurington is offline
 
Join Date: Nov 2007
Location: Melbourne Florida
Posts: 111
Default Email Sent

Quote:
Originally Posted by rleffler View Post
Send me an email, do NOT PM me. If you click on my userid, you?ll find a link to email me.
Thanks Bob
Reply With Quote
  #148  
Old 01-06-2018, 12:29 PM
CharlieWaffles's Avatar
CharlieWaffles CharlieWaffles is offline
 
Join Date: Nov 2010
Location: West Linn, Oregon
Posts: 1,351
Default

Quote:
Originally Posted by rleffler View Post
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
I can confirm that this indeed works with the ADS-B+ Format 1. Just wired up my unit and this format worked as intended.
__________________
CharlieWaffles - But you can call me "Mark"
RV-10
N928MT
Flying - AKA Still Tinkering
Build Project Site
Reply With Quote
  #149  
Old 01-19-2018, 07:12 AM
cardmarc cardmarc is offline
 
Join Date: Jan 2018
Location: tx
Posts: 6
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
  #150  
Old 01-19-2018, 07:13 AM
cardmarc cardmarc is offline
 
Join Date: Jan 2018
Location: tx
Posts: 6
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
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 01:38 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.