|
We've only had our new MRX (firmware 2.6) for a few weeks, since Aviation Consumer gave it a good review. About 15 flights so far. By way of contrast, we have five years and about 1000 hours using, and still using, a Monroy ATD-200 in the plane. The MRX is much better.
Still, the MRX could be even better with some minor firmware changes. (Minor - easy for me to say!) So some requests. But know that my airplane partner dropped our unit on the kitchen table from 4 inches, breaking the 5 way navigator button, also jamming that function, so we've been without ability to change range and stuff. Perhaps some of these ideas are moot if I had a working 5 way nav button. (The factory has graciously offered to fix the unit under warranty, and it goes in the mail tomorrow.)
- I would like a timed MUTE function.
When on the ground, the unit is constantly beeping ALERTS from traffic in the pattern. If I activate the MUTE button, I know I’ll never remember to un-mute in flight, even with the flashing dot, which I never notice. A ten minute timer on the MUTE would be better. (Else a more obvious annunciation of Mute.)
- I would like the MRX to show ADVISORY for any target within a couple hundred feet of us, even if at 5 miles. The problem is two fold:
First, the "catch up" problem, per p 34 of the v 1.4 manual. We've had a few cases with traffic close to our altitude that started out at 5 miles, but within seconds was at 1 mile. I'd rather know about these targets sooner in case they "catch up."
Second, in a Glasair and other fast homebuilts, closure rates can be phenomenal. Again, I'd rather be alerted to someone at or near my altitude sooner, even if his range doesn't appear to be a threat now. At 6 miles per minute closing speed for two Glasairs, distances close very quickly, not to mentioning reaction time, thinking whether I should pull up or push down.
Perhaps if I had a working RANGE switch, I could address this by going to higher range than default?
- I would like the MRX to have an "unsquelch" or "Show ANY" button. (This might take a rethink of the whole 5 way multifunction button, which I think can be eliminated and made cheaper/easier with standard buttons.) Often, our ATD-200 will call traffic when the MRX is silent. It's hard to know for sure that the MRX hasn't heat soaked in the hot Phoenix sun, that it's working okay, etc. I mean, just because you see 4 dashes, doesn’t mean the unit is operational, does it? (Because my partner broke the 5 way, I can’t hit the LOCAL button, which I suppose is a pseudo operational check I would be doing a lot.) So in the same way we confirm our comm radios are working, by pulling the squelch off, listening for static, I would like to be able to make the MRX display whoever is out there that it can see, regardless of range/alt settings.
Sometimes too, we will see traffic that is apparently out of range on the MRX for advisories. I’d like to be able to do a failsafe check to confirm the unit is operational and check out that traffic for myself anyway.
- I would like the unit to change it's blank display when it's in GROUND mode. Two things here.
I've had to change the batteries in flight, when my flying partner reminded me about the 200 foot bump needed. Not very practical in IFR or in a TCA.
-- So how about a way to force the unit out of GROUND mode in flight without having to do the roller coaster?
-- Also, an annunciator telling you when the unit is in, and more importantly, out of GROUND mode would be nice. How about only two dashes in ground, and all 4 in flight? (Or it could flash GND every so often.)
- Can there be an up/down trend arrow on RANGE more than 2 miles? Things happen fast in these fast homebuilts, and staring at someone at my altitude at 3 miles without trend, waiting to see if he goes 2, 4 or stays at 3 makes me anxious.
- Instead of flashing NEW, eating up precious seconds, per p10, how about if the unit simply flashes the range and altitude information for new targest the same short time?
- Is there any way for the beeps to be different frequencies for traffic above / traffic below? (Am guessing would require two piezo units.)
Hope this helps.
|