I was thinking about this too a couple of months ago, and came to the conclusion that it’s fine the way things are now, and it shouldn’t be screwed with.
The stormscope needs to be controlled as well as the output displayed. In my SR22, the stormscope is operated and displayed via the ICDS2000 only.
While the GNS430s, Sandel, and ICDS2000 all have the capability to talk to the WX500, they aren’t all wired to the Stormscope. It’s highly unlikely that the WX500 was designed to have multiple master control units, and even if it was, I don’t see much of an advantage to switching them or displaying the information in 4 places. What happens if I have the Sandel tell the WX500 to work in strike mode and the ICDS2000 tells it to work in cell mode? Ditto display ranges…?
If you’re going to have to pick one of them, the ICDS2000 is the right place to put it. It’s big and easy to glance at at occasion, but not in the primary scan area. The whole concept of a sterile cockpit dictates simplifying things, not making them more complex. More complexity = more to go wrong.
If the ICDS2000 breaks on a dark and stormy night, and I needed the strikefinder, I’ll land, thank you very much. That’s the weather god’s message that “tonight is a better time to be drinking a single malt on the ground than be fighting thunderstorms in little piece of plastic.”
I have the moving maps all set up on my Sandel. If I ever want or need them, they are one keypress away (e.g. a graphical version of the nearest field display from the garmins). However 90% of the time, I run my Sandel as a HSI+RMI in 360 degree view. Why? Because we have a whole bunch of other avionics that do the rest as good or better than the Sandel does.
Don’t take this as a knock against Sandel, I think their HSI display is a godsend and until we graduate to full EFIS, all of my future aircraft will be equipped with one.
Note to Sandel: If you started making EFISs, I would be glad to make my plane a test subject of yours based upon how impressed I have been with the operation and UI of your HSI display.
However, to paraphrase the old saying, “Just because you have a hammer doesn’t turn everything into a nail.”
Actually, one piece of information I think I’d like displayed on the Sandel (but I’m not sure) instead of the ICDS2000 or the Garmins would be TCAS. I think that might be the best place to display it, although I am not firm in that conviction, just thinking about it.
One problem is that that 10.4" MFD is actually going to seem really small by the time it has been divided up into a TCAS display area, an engine monitoring display area, and the moving map. These three things are NOT pages that I’m willing to swap between.
Note to ARNAV: If you really want to do the engine monitoring intelligently, what I’d really like is something like the F22 and Airbus displays. Keep the engine display hidden or small until any parameter has exceeded a user-defined threshold. If that occurs, then zoom in on the engine monitor display. I don’t need to keep an eye on the engine monitor when everything is perfect, but I do need to know when things start to move.
While the same thing could also be done for TCAS (no contacts = small display, distant contacts = medium display, alerts = large display), I suspect that users would become very annoyed with the constantly changing size of the TCAS display.