Mike Draper wrote:
@Bruce, thanks for sharing your findings. We may be on to something. I had a 2-hour flight scheduled for this weekend and connected my iPhone and 740 to the Echo UAT. ~60 minutes into the flight I got the networking error. Not sure why it took ~60 minutes or what may trigger this. @Brolin, any updates from discussions with Walter and David @ Uavionix?
Mike, I think your "Not sure why it took ~60 minutes or what may trigger this" is the critical point here. I always take off with the 740 and the iPhone both "Receiving" (in the ADSB instrument), and both display other ADSB traffic simultaneously. On some flights, they continue until I land and switch everything off. But on some other flights I get the networking error on the 74. If I'm not too busy I dismiss it, and sometimes the 740 resumes to displaying traffic, sometimes it doesn't. The iPhone, once it's "Receiving" almost always keps on receiving--but sometimes it stops. Sometimes neither device is "Receiving" and displaying.
So in other words, most of the time there's no problem--meaning that the Ping router CAN handle more than one device. Last week I also had an iPad connected, along with the 740 and the iPhone, and all three worked fine for a while, until the networking error popped up, and then (if I remember correctly) both iOS devices gave up. but the 740 reconnected eventually.
The uAvionix tech I spoke with on the phone a few weeks ago had written a patch and sent me instuctions for downloading and installing it. Unfortunately, it didn't fix my version of the problem--and then I got busy and haven't gotten around to calling him again. Because I'm waiting for the new iPad 6 mini with the cell and GPS stuff to be released (maybe late January), I sort of lost interest in this problem. But if it isn't fixed by then, I'll just rely on the iPad instead of the 740, as it will have better resolution. All the same, it's a problem that needs to be fixed.