MLB FIS-B Wx "Unavailable"

When you look at the AUX page for the weather features (the legend) what does it say for service level at the bottom of the first section? Mine says "ADS-B Wx" or something like that. What service level (or subscription) does your IFD expect?

I don't have a screen shot, but it's the page that shows you how old each piece of data is.

That is the page, but I'm not asking about the age of any particular data.  (I am trying to attach an image here, but it isn't working again.  Grrr.)

Look at the Datalink Status Page in the Pilot's Guide (page 4-54 in my 'Change 2' copy).  The Service Level is shown at the bottom right of the Age-in-Minutes block.  In their example, the Service Level is "Professional".

In my airplane, the Service Level is "ADS-B Wx".

I can't recall specifically if this indication is available to me on the ground.  I think it is, but not sure.

Step #1 for you is to determine if the IFD is getting the service.  Then we can work on troubleshooting  the features within that service.

n7ifr wrote: As an aside, in your referenced manual page (4-54) I notice it shows "Aviator Pro"... I assume XM Satellite Wx.

I would make the same assumption.  I don't think they had an ADS-B product available when they first wrote (and made screen shots for) the pilot's guide for the IFD.

At this point we may need Jake to chime in with what the indication should be for our planes while on the ground.  I think that mine says "ADS-B Wx" even on the ground.  (I know it says that in the air.)  Since yours doesn't, my guess is that the serial port configuration is not correct.

I know you're frustrated, and for good reason, but I would tell you to hang in there.  This system can work in your airplane, because it works in mine.  It's just a matter of getting everything set up right.

In your airplane, which IFD serial data port is receiving the weather data?  Which 429 port is receiving the traffic data?  Are the two IFDs wired the same, or differently?

David Bunin

David,

Curious:

I thought that unless the ADS-B ground station was located on your airport, you generally need 3000ft AGL to receive the ADS-B products.

Gring wrote: I thought that unless the ADS-B ground station was located on your airport, you generally need 3000ft AGL to receive the ADS-B products.

It's a function of altitude and distance.  Most pilots near a city will have coverage well before 3000 feet.  I am 30 miles from the nearest station and I have signal just above pattern altitude.

But anybody should certainly have good signal upon reaching 3000'.

David Bunin

Tom, I did the 10.1.1.0 upgrade on my IFD today, and I confirmed that I get "ADS-B Wx" as the subscription type, even inside the hangar.  (Each individual data type says "Not Recvd" naturally, but the subscription type is there.)

If your replacement MLB doesn't solve the problem, then it has to be a configuration issue in your MLB software.  The good news is that it can be reconfigured without removal, if that's the problem.

My pleasure, Tom.  I want to see this thing work for you.

I haven't loaded the 4.0.9 software yet.  4.0.8 was working fine for me (pressure altitudes are rarely below sea level around here) so I wasn't in any hurry to load the .9 software.  I'll get to it eventually.

I don't have the AXP240 audio panel.  As far as I can tell, I never experienced the problem with the standby volume.  I expect I might need to adjust my volumes (in my audio panel or in the IFD) now that I have the new software loaded.

The NavWorx ADS600-B and the Avidyne MLB100 both make use of a "Maintenance Console" software that runs on a PC (usually a laptop, but I suppose a desk top with a long cable would do it too).  The MC software looks about the same (the graphic user interface is the same) between the two.  My guess is that a shop that has experience with the NavWorx products tries to use that version of the console, and in the process wipes out the Avidyne software resident in the MLB100 from the factory.  (Please note that this is all my own theory, I don't have any proof or evidence.)  So it is very important to "read the fine print" and make sure you're using the MLB console and not the ADS console.  There is a relatively easy indication to see on the screen, but it is subtle if you're not looking for it.

Once an MLB100 unit is corrupted by the ADS600 Maintenance Console software, I do not know if it has to go back to the factory, or if an MLB console is able to restore it to functionality.  Haven't tried that experiment.  Your best bet is to receive an MLB100 unit and only connect the MLB console to it.  (And while you're at it, make sure the console is version 4.0.9.)

I am okay (not great) at using the Maintenance Console software.  My unit was configured for me by the factory, so I never had to do that for myself.  I have done several software updates, and I have observed the configuration on the screen, but I don't know it well enough to talk you through it without seeing it in front of me.

David

One interesting thing in the image above are the time stamps.  I can't say for sure, but I strongly suspect that the MLB was removed from the equation (disconnected) in a single moment.  But each message was presented at a different time, based on the duration of each. The "429 Data Not Rcvd" predates the "Traffic Sensor Fault" by three minutes.  (I guess the loss of 429 data is more 'obvious' to the IFD than the lack of a traffic device.)  Conversely, the loss of the MLB (Datalink Receiver Fault) predates the loss of weather data by 25 minutes.  Possibly this was the time when the last piece of weather data toggled from valid to invalid (when the METARs/TAFs expired).

Just curious stuff.

David