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
12/22/2020 10:53 PM
 
Walter wrote:

It s some sort of compatibility issue between some iFlys and some Echos.  It is usually benign, if you hit OK it should reconnect to the echo and keep working. This doesn't happen for all users, and we've been unable to duplicate it in the office, so really not sure what is causing this.  It doesn't seem to happen with a tablet or phone connected to the device.  

Walter, my 740 has put up WinCE dialogs (usually Networking) about a dozen times in the past 8 or 10 months--including my most recent two flights. Both of those times I was on short final for a land landing. (Probably not relevant, but I had done a water landing about 5. to 1.0 hrs earlier, with no dialog appearing.)

It's very hard to get a finger on the OK button--or the X button, either--when you're on short final, so I've learned to just ignore the dialog and land the airplane instead. The point is, it's really hard to press that tiny button.

 
New Post
12/23/2020 8:44 PM
 

This seems like a problem.  Is it possible for iFly to determine when we're landing, or at least maneuvering at low level, and not present messages that are not critical to that phase of flight?  Simply being distracted on short final could be a hazardous.

 
New Post
12/24/2020 7:06 AM
 

WinCE is the operating system, and that's what's popping the messages.  The iFly application has no way to know that the operating system is doing that, and certainly no way to stop it from doing that.

 
New Post
8/15/2021 7:11 PM
 
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 ?
 
New Post
8/15/2021 9:08 PM
 

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

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