Integrated EFIS Network / Serial to Ethernet Converter

Recently I've been thinking of possible workarounds to the single serial port limitation of the EFIS Sport, and some of the threads about networked EFIS Lites got me thinking...

It seems to me that since all the units (EFIS 1, Sport, Lite) use similar hardware and the same OS, they should be designed to talk to one another over a LAN and share data. It seems a waste to use the ethernet port only to talk to the autopilot and make software updates. The example brought up in another thread was only setting the altimeter once and having any other BMA units on a network automatically use the new setting. Taking that a step or two further, why shouldn't multiple units be able to share flight plans, nav signals, Wx, Traffic, engine instruments, checklists, etc. over the LAN?

As an example (and assuming all the up & coming wx, traffic, etc. interfaces were available): say I have a dual BMA system (EFIS One/Sport with an EFIS Sport/Lite as backup) and I want to connect to an SL-30 & GNS 480, plus FADEC, weather, and traffic. Depending on the two units I have, I may or may not have enough serial ports to go around. Furthermore, even if I do, it's all segregated--if weather is hooked up to the serial port on one unit, I can't view it on the other.

If I'm not mistaken, the bandwidth/throughput available on a 10/100 Mbps network far exceeds that of standard serial ports. Why not use that already existing capability to turn a collection of separate EFIS units into an integrated suite? If my SL-30 is connected to my EFIS Sport, but I want to view its nav data on my EFIS Lite HSI page, that data should be pumped across the network from one unit to the other. If I have an s-band transponder connected to my EFIS Lite, but I want to view the traffic data on my Sport or One, the data is on the network. You can see where I'm going with this...

Each BMA unit is self-contained and able to function independently, but the versatility & functionality of multiple units is increased by integrating them across a network--synergism and all that.

In the case of a dual EFIS Sport system, there would still be only two serial ports. What about a serial to ethernet converter? Make a new box to install behind the panel--it could have multiple serial ports and the required electronics/software to send that data across the LAN to every BMA unit. The upcoming engine pod could have a similar function and connect to the Sport via ethernet instead of serial port...

There are probably issues such as data lag across the network (am I looking at "now" nav data, or "5 seconds ago" nav data), etc.

I don't think this would be difficult from a hardware perspective, but it would require a significant change to the software in every BMA product--probably not something Greg & company would welcome right now.

Thoughts, anyone?

IMO the last thing you said, says it all; "probably not something Greg & company would welcome right now." They have a pretty full plate, with everything else, weather included. They can't re-design their products for every "light bulb" idea. But, who knows. Sounds neat, but the work to do it, looks like a pretty long list.

Bryan

I'd love to comment on what we're doing, but the delays in bringing the new Lites out has taught me to remain silent until I have machine IN BOXES. Things can happen, and in succcession ...

Suffice it to say I like the network idea rather a lot.

It will plug in very nicely to my in panel Mac Mini. On board CD/DVD/iTunes/Wireless keyboard/all my files away from home, in a 6.5 x 2 box. : )