Big Issue with uAvionix when using a G430W for GPS position
The uAvionix echo UAT can only accept the G430W GPS position on its COM2 In Port, and the G430W only outputs at 9600 Baud. The echoUAT can then only TX on COM2 at 9600 Baud. COM2 TX is the only serial port that can output Serial TFC & WX (to an EFIS) so it then can only send out TFC & WX at 9600 Baud,
COM1 cannot be used for sending out TFC or WX, only UAT control.
So if you plan on using your G430W for GPS position this UAT will only be usable over WIFI for TFC & WX since 38400 Baud is the bare minimum for usable TFC & WX for ADSB, and preferred is 115200 Baud and neither are possible when using the G430W.
I just learned this integration lesson the hard way.
For example NAVWORX in its setup SW can limit the number/sec of TFC & WX messages that are sent to the EFIS so if you are using 38400 Baud you can make sure your COM Port is not overloaded. No such option exists in the uAvionix SW, and 9600 Buad is so slow as to be out of the question.
If you get a stand alone approved WAAS GPS that can output its Serial data at 115200 Baud then there should not be any echoUAT COM issues for a wired EFIS.
*** Update, I just got a call from uAvionix and they are looking to see if they can fix this issue in their software. So standby..
RV-8 Under Construction
Flying RV-6A with Son Chris
IO-360, MGL-EFIS, G430W, ADSB
2018 Dues Paid, Home Field 18FD
Last edited by hpmicrowave : 05-10-2017 at 04:56 PM.
Reason: Update on the post