Windows CE Networking error message - iFly Owners Q&A - iFly EFB

iFly GPS Forum

We have a new Forum!  Go here to get started: https://adventurepilot.community.forum.  
The new forum is easier to use and much more capable than the old, we hope you will join our community! 

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.
HomeHomeDiscussionsDiscussionsiFly Owners Q&AiFly Owners Q&AWindows CE Networking error messageWindows CE Networking error message
Previous
 
Next
New Post
8/16/2021 10:43 AM
 
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.

 
New Post
8/16/2021 10:45 AM
 
N854HC wrote:

Just another point for reference: I'm also running the Echo and a 740b and I have never seen CE pop a message. Have you verified that you are running the latest system and wifi firmware on the Echo?

Good Luck,

John

No, I haven't (yet), but only because it seems like probably a big P.I.A.

 
New Post
10/31/2021 4:57 PM
 

I got this error for the first time on 10/31/21.  I was 6 miles out from landing and using my IFLY740 to set up entry on the 45 to downwind.  As others noted, it was very distracting.  After a gazillion attempts to hit  ok or X, I got the dialog box to close.

I have an EchoUAT with the skyFYX-EXt GPS installed.   FWIW, last weekend I adjusted the transponder threshold down by 50 because I recently received a PAPR report with some missing baro alt elements.  

I'll enable ADBS logging the next time I go flying.

 
New Post
11/2/2021 10:38 AM
 

I'm three for three.  Flew twice today and got the error on both legs of the trip, on approach.  I don't consider this to be a benign issue.  It's distracting, adds to the workload, and impacts situational awareness.  Imagine this popping up on approach to ripon/fisk/airventure?   My 740 is panel mounted.  I did have ADSB logging enabled and am willing to help troubleshoot.  Let me know how I can help.

 
 Widows CE Network Error 2NOV21.jpg
 Windows CE Networking Error 02Nov21b.jpg
New Post
11/2/2021 11:19 AM
 
Mike Draper wrote:

I'm three for three.  Flew twice today and got the error on both legs of the trip, on approach.  I don't consider this to be a benign issue.  It's distracting, adds to the workload, and impacts situational awareness.  Imagine this popping up on approach to ripon/fisk/airventure?   My 740 is panel mounted.  I did have ADSB logging enabled and am willing to help troubleshoot.  Let me know how I can help.

I had a client mention that uAvionix had some kind of an internal fix for this - i don't recall who it was but it was about a month ago. Might want to check w/ them. i'll check my resources here bc i remember there was something about how they had to distribute it themselves. 

 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly Owners Q&AiFly Owners Q&AWindows CE Networking error messageWindows CE Networking error message