![]() ![]() This is what Jeff DeFouw at GRT responded to my question about proper set up: Long story short, even tho I’m using the Safefly as GPS1 and not the internal GPS in the SX, it still needs to be designated as internal flight plan source. The other challenge I’ve had is figuring out how to enter a flight plan. Still have to test fly, so will report the results. I’ve since changed over to Aviation data and there is no “no gps” warning on the Trio. I had the Trio on port 1 at 9600 baud, but set to receive NMEA0183 data. I had sent my Trio in for repair of the display a couple years ago, at which time they upgraded it to receive data ether from NMEA, at 4800 baud, or via Aviation data at 9600 baud. But the Trio was not receiving GPS data from the SX. In the original panel/installation, I was getting a very slight but persistent oscillation when it was engaged. really avionics challenged!Ī test of the Trio EZ pilot autopilot showed that the wing leveler function was rock solid. Some squawks still are challenging me, mostly because I am slightly avionics-challenged. I can see that it will be some time before I am utilizing all it’s functions. The 8.4” screen seems to be a good fit for me. I’ve flown the airplane and really like the presentation of the GRT Sport SX. They’re probably going to say, “Oh jeeze. I have an email, again, into GRT and should hear back tomorrow to see if that is a possibility before I take things apart. Out from the Safefly/EchoUAT going to the out from the Sport SX. Not that I’ve ever done anything stupid or anything like that, but I’m wondering if I could have switched the in/out wires. One is for Ads-b data, which I have going to port 5 at 115200 baud, and two are for GPS in and out, which I have on port 3. There are 3 wires coming from the Safefly/EchoUAT (other than power and ground). I’ve checked all other settings to the best of my feeble ability, but I can’t figure it out. The serial in data counter for serial port 3 is ticking over, but the data isn’t making it to the display. Still, after correcting the baud rate, no joy. The setup instructions say to set the baud rate at 115200, but after emailing GRT, the apparent correct rate is 38400. I’ve configured it to communicate on serial port 3 and have the baud rate configured per consult with GRT. The current hurtle I am experiencing is that my Safefly GPS that is coupled with the Echo is not playing nice with the EFIS. I’ve also configured the Echo UAT, but I will need to update the firmware as has been discussed elsewhere. ![]() Got the magnetometer calibration completed, and have the EIS engine monitor limits set up. ![]()
0 Comments
Leave a Reply. |