SkyTrax FAQ's

Simpson,

What concerns me about the chart there is MLX products list a RS232 & A429 Display port. I assume this is in reference to FIS-B data only?

As I understand it the MLB-100 uses A429 for the traffic information (TIS-B) and RS232 for FIS-B data.

Maybe I'm missing something obvious when I look a the table (i.e. Is display port some odd protocol I've never heard of?).  Either way that table could be cleared up a bit.

AviSimpson wrote: roltman wrote: As I understand it the MLB-100 uses A429 for the traffic information (TIS-B) and RS232 for FIS-B data. This is correct all of the "ML" (MLB100 & MLX200/210) products use Arinc 429 to display traffic and RS232 for weather.

Interesting. I wasn't aware ADS-B In required a GPS.  Is that RS-232 or Arinc 429?

AviSimpson wrote: flybikeski wrote: Interesting. I wasn't aware ADS-B In required a GPS.  Is that RS-232 or Arinc 429? ADS-B IN does not, however, the MLX210 has an internal WAAS GPS for ADS-B OUT.

OK, thanks.  I think your chart is confusing on that point as it says "Requires External GPS" for the MLB100 which I interpreted as needing to connect to one.

The MLX200 looks like the ADSB- in/out solution for my IFD540 KT76A, since I don't fly in the flight levels. Have any idea of the availability and price?

May, 2015 is almost over.  Sure wish these deadlines meant something.

MLB100 received today for (pre-wired) install!   

Edited by n7ifr - 10 Jun 2015 at 3:05pm

I didn't realize the MLB100 was shipping.  Thought that was on hold pending 10.1.0.0 software cert?  

No experimental here.  Confirmed by phone, MLB (x2) in his hands.  My installer is high volume Avidyne, and a squeaky wheel too.

tony wrote: Simpson, referring your response to flybikeski, I don't think the chart is wrong:  doesn't the ADSB-in receiver need to know the current aircraft position so it can center the display and orient the data with respect tot the position of the aircraft?

In this scenario, when the TAS-A is operational, the MLB100 will serve as a ADS-B source for Wx, displayed on the 540. 

Edited by n7ifr - 13 Jun 2015 at 12:16am

oskrypuch wrote: If you have an MLB100 and 605A, only the MLB100's weather output will be of any use to you. The one exception might be to feed 605A traffic to one device, say the 540, and then for some reason to feed ADS-B (TIS-B) only traffic from the MLB100 to the ASPEN, for example. That would be kind of an odd ball setup. * Orest

That oddball setup would not be good.  The ADS-B transponder tells the ground stations what ADS-B in capabilities you have.  The choices are none, 1090, UAT, and both.  Both means that traffic information can be received on either frequency, not that it must be received on both frequencies.  So at least one of the ADS-B receivers would not see all traffic.

Well, my early bird MLB100 is installed/configured, but here's a NEWS FLASH!

n7ifr wrote: .... Very dissappointing (again) timing on Avidyne's part - releasing costly hardware, not functional at all until free software upgrade 10.1 is released at some undisclosed future time!

n7ifr wrote: Well, being optimistic as well... I plan on doing my own upgrade to v10.1 via thumb-drive on 540, to avoid the extra trip.   Will the software upgrade need an A&P signed log entry though? Tom

Edited by oskrypuch - 15 Jun 2015 at 6:11pm

Orest Said: "It is my understanding that you need an A&P (although not necessarily an avionics shop) for a sign off. I'm lucky, my shop is right on the field. They slip over to my hanger and do the work so I don't have to worry about it."

Not sure how the A&P would work, but if it is an installation via STC it needs to have a 337 filed and that can be done by a mechanic who holds an IA.

I am installing an IFD-540 in my Cessna 172 and at the same time I am installing wire provisions for an MLX200.  The installation part is done and the airplane is mostly closed up, but I just learned something that I didn't know.

I thought that all of the data from the MLX200 would go to the IFD as serial data.

If I am reading this thread correctly, only the weather (FIS-B) data will flow as serial data (at least initially), and the traffic (TIS-B) data must flow over a 429 bus.

So the problem is that I did not provision 429 wiring, since I thought it would all be on the single serial data port.  It's my mistake, and if it means I have to wait for the traffic data until a future software release, then I am okay with that.

Please tell me that Avidyne at least intends to process all of the data through the serial port at some point?  I understand waiting, and I don't have a problem with that.

I am expecting my IFP440 soon (supposedly this month) to replace my Garmin 430W.  I also have a Garmin GMX200 display and an Aspen Evolution unit.  The question is, can I get an MLB100 or MLX200 to display on any devices besides the Avidyne IPF440? 

I had my Archer pre-wired for the MLB100 when my IFD540 was installed in April.  Checking with my avionics shop, my MLB is in, but he indicates it is not STC'd. 

Can anyone from Avidyne confirm this?  I want to make one stop for the 10.x upgrade and MLB install since the shop is not local.

Thanks in advance for any input you have.

wbennett3 wrote: I had my Archer pre-wired for the MLB100 when my IFD540 was installed in April.  Checking with my avionics shop, my MLB is in, but he indicates it is not STC'd.  Can anyone from Avidyne confirm this?  I want to make one stop for the 10.x upgrade and MLB install since the shop is not local. Thanks in advance for any input you have.

Does the MLB100 provide aural traffic alerts?

If so, what are they like?

E.g., "Traffic, 12 o'clock, 3 miles"?

Or?

I have been told that I will get aural alerts from my MLB100 and AMX240 com panel in my IFD540 system with the next version of updated software. I have 10.1.1 now.  I did have to have a wire installed between the comm panel and IFD 540. FWIW my bluetooth phone stopped working with that last software update.  I know it wasn't supposed to be working yet, but mine did without any attempt to pair it.  It just connected the first time I tried it.

Correct, we don't yet supply aural alerts for the MLB100 Traffic. It's currently slated for 10.2.

flybikeski wrote: AviSimpson wrote: Correct, we don't yet supply aural alerts for the MLB100 Traffic. It's currently slated for 10.2. The previous poster said "an additional wire was run" to get ready for that.  Just to confirm, that would be normal audio output from the 540, not the TAWS traffic aural output? Thanks!

I have just had my MLB-100 connected to the IFD-540 with 10.1.1 and 4.09 (MLB-100) software updates. Initial flight has ghosting right under the aircraft which keeps the Aux button yellow since this other(ghost) aircraft is so  close. I see the same thing on my IPAD with Foreflight. 

I've been chasing an issue which I just traced to the MLB100. I have dual 540s, MLB100 and also an Aera 560 GPS in the right side panel inside an AirGizmo doc... quite cool how the 540 outputs the flight plan to the 560.

However recently the 560 stopped working. I use it for XM weather, flight logging and airport data, so it is sorely missed. I chased several potential reasons, but just today sorted out the issue.

Turns out it stopped working when the MLB100 was installed. The GPS signal strength bars now die when the MLB100 is turned on. Pull that breaker and it works fine. The MLB100 is mounted about 3-4 inches from the back of the Aera, which is using its internal GPS antenna, otherwise successfully.

Have there been any studies of spurious emissions from the MLB100? Any other indications of GPS signal blocking? This could become an issue for other in-cabin portable units.

I'm planning to experiment with a remote antenna but would appreciate any thoughts on why the MLB100 has this effect.