MLB100 Traffic

DavidBunin wrote: Does your shop have experience with NavWorx installations? In other words they have "done a couple" of NavWorx installations or Avidyne installations?

Both.  I know they were familiar with the NavWorx and it's console, but they knew not to mess with the Avidyne using the console.

The shop purchased some external piece of ADS-B equipment that can transmit UAT/1090 targets and that's what they've used, so they know it kinda works with those targets, but they were concerned there was some piece of programming they were missing (i.e. aircraft ID or hex code, etc.) for it to function correctly.

I was just told today the IFDs and the MLB's can't be powered up simultaneously due to some issue with the A429 bus or A735B data.  Like the MLB100 falsely putting out incorrect SSMs on the labels and never working correctly after that point (this is my assumption based on the info provided).  I'll let Avidyne comment since it is a known issue to them and I'm just putting together 3rd hand info I was told today.

tony wrote: On my airplane when my shop installed my 340, they asked me what frequency my ADSB in was going to be.  I told them I was 978.  They had to submit some paper work telling the FAA that I need the 1090 rebroadcasted.  I have no idea what that paperwork was, but I remember the discussion.

That's a setting on the 340 to broadcast what "In" you have.  I have it setup correctly and it was confirmed by the FAA. 

Spoke with my shop this morning, apparently there's some known ARINC issues and how power's applied.  I'll let Avidyne elaborate as I'd be repeating 3rd hand info.

The shop also had some questions about how the MLB100 is programmed as they've done a couple now it and it shows traffic correctly with their ground test equipment which throws out some false targets, but I'm not seeing any traffic in flight.

Took a 3200nm flight this last week with the MLB100 and traffic turned on.  I only saw one target the entire trip (numerous traffic calls by ATC though) with the traffic set to "unrestricted".

I'm going to talk to my shop, but I was at 15,000 over Kansas City class B yesterday where I saw the one target and it was shown at my altitude at less than 1nm.  I asked ATC and the only traffic there was a airliner on approach at ~3000' or ~12,000' below me.

Not 100% sure how the altitude is determined for display.  I know the IFDs have proper altitude from the encoder and my AXP340 does too.  It has ADS-B out turned on and FAA report came back with a "gold star".

The MLB100 was supposed to use the "parroted"AXP340 pressure altitude values.

Also sporadically I would get a "Traffic Sensor Fault" message on the IFD540 about every say hour or two and they'd last only a few seconds.  I assume it was just a issue with a ground station? 

I also noted that the traffic data tab looked normal under this fault state until a brief flicker to a "Red X" when unit returned to normal ops.  Wondering if it shouldn't be a "Red X" the entire time the IFD540 has a yellow traffic sensor fault?