Bruce Yarbro wrote:
The answer to question (1) is definately yes! I also use an ECHO UAT ADSB in-out.
I am also getting the Windows CE Networking error messages. I got two during cruise flight last week and was able to close them by hitting OK or the X. Not sure which I hit as I agree they are too small.
Today they came up immedately after takeoff and would not close. Traffic seemed to still be displayed around the edges, and I could pan to find them. It is very disconcerting to have the screen blocked and not be able to see the airport or traffic. The first one was:
"DHCP was unable to obtain an IP address. If the netcard is removable, then you can remove/reinsert it to have DHCP make another attempt to obtain an IP address for it. Otherwise, you can statically assign an address."
I turned the ify 740 off and restarted. When it came back on the same message you had came up:
"The system has detected a conflict for statically assigned address 192.168.4.100 and with the system having hardware address A8:5C:2C:7C:D5:1A.The local interface has been disabled."
Walter, Has ANYONE been able to answer questions 2 and 3 ?
Bruce, the most recent response I've had from AP (Walter, I think, via Brolin) had me do a factory reset of the 740 box. I've done that, but haven't had a chance to test it in flight yet. I'll do that as soon as the WX clears up a bit here. I think they think that the problem is in the box's connection to the uAvionix Ping wifi router (They've also suggested using a fixed IP address, but i don't want to do that because then it would be hard to connect to other wifi routers.) I never had the problem before installing the ADS-B, and have had it fairly often ever since, so that seems like a useful lead. I'll let you all know as soon as I can.