jliltd
Well Known Member
The G5 has one RS232 bi-directional interface with one receive pin and one transmit pin (RX1, TX1). Each of these can be configured under different formats. For example TX1 can be used to send pressure altitude to a transponder while RX1 can take data navigation input from a GPS.
I have this very configuration currently using an aera 660 to feed the G5. However, I just added a GNC 355 WAAS navigator to the panel to replace the aera. So the 355 will now talk to the G5 via the RS232 input channel. Now the GNC 355 manual has me set RX1 to "MapMx" instead of NEMA or the like. But that's where things get wonky. When I change the G5 RX1 input to MapMx it causes the TX1 output to gray out and no longer provide for altitude encoding out. On any other input mode other than MapMx the output pin can be used for altitude.
Is this a limitation of the MapMx data format? If so I guess I will have to buy a stand-alone altitude encoder, something unexpected and not described in the marketing.
Jim
I have this very configuration currently using an aera 660 to feed the G5. However, I just added a GNC 355 WAAS navigator to the panel to replace the aera. So the 355 will now talk to the G5 via the RS232 input channel. Now the GNC 355 manual has me set RX1 to "MapMx" instead of NEMA or the like. But that's where things get wonky. When I change the G5 RX1 input to MapMx it causes the TX1 output to gray out and no longer provide for altitude encoding out. On any other input mode other than MapMx the output pin can be used for altitude.
Is this a limitation of the MapMx data format? If so I guess I will have to buy a stand-alone altitude encoder, something unexpected and not described in the marketing.
Jim