While this is generally a positive post (for a short time I appeared to have a working SkyRadar / iFly combo! Yippee!), it comes with three caveats: (1) I don't know for sure what changed to make it work, (2) in 30 minutes I got only one Nexrad frame (with no echoes in the area) and never saw an update or received any TAFs/METARs, and (3) I have so far been unable to duplicate my brief success!
Note also that after 30 minutes with no updates, I unplugged the USB cable from the iFly, and 10 minutes later it still indicates "ADSB live weather" mode and that port 0 is connected to a SkyRadar, so that tells me that you can lose the connection and not know it.
Since then I have tried multiple reboots of the iFly and SkyRadar and reconnection attempts, and have been unable to again see the two devices connected.
Here are the detalis of what's happened since my last post:
I talked to Ed on the phone this afternoon, and he suggested a test (that Shane has posted elsewhere on this forum today): Plug the USB cable from the SkyRadar into a Win7 machine and see if Win7 recognizes the device and loads the correct driver (it should recognize the SkyRadar as a FT232R UART, which is the USB-to-serial port interface the SR uses).
I performed this test, and it worked: That means the SkyRadar's USB port is functional.
I then tried to plug the SkyRadar back into the iFly. The last time I tried this (see Update 3), the iFly seemed to find multiple serial ports trying to connect, and eventually had 15 virtual serial ports established, with none of them talking to anything.
When I tried it this time, it was different: The iFly detected a single port (port 0), but said nothing was connected to it. I tried connecting the SkyRadar with two different USB cables, but from what I could see they were both of the 5-pin variety that is required. I got the same results after at least four or five attempts: The iFly recognized a single port 0, but there was no communication happening.
So I put it down and walked away for a while. Next came the one thing that changed that could have had an effect.
I have been using an external battery pack with a cigaretta adapter to drive the SkyRadar. Two of the rechargeable AA batteries out of the 12 used in the battpack are "flaky" and don't hold a charge very well. While the two LEDs on the SkyRadar both behaved as expected, that was my only insight into the SkyRadar unit...which isn't much!
So I took all the batteries out and recharged them for several hours. I then put them back into the battery pack and tried connecting the SkyRadar to the iFly, and that's when I had success.
I also notice that the SkyRadar is broadcasting an ad-hoc wifi network signal that I can see on my laptop that I could not see before (it is called "skyradar0001" in my list of available networks). (This ad-hoc network name is NOT visible via my Android phone, btw.)
After playing around with the SkyRadar and the iFly for about 45 minutes, I'm again having trouble getting the iFly and SkyRadar to talk to each other, and I noticed that the "skyradar0001" network no longer appears on my laptop. Suspecting a power problem, I just pulled the batteries our of my battpack and stuck them in the charger, and they're showing a lower charge than I would have expected. I'm going to top them off again before doing any futher testing.
I wish I had a stable power source for the SkyRadar for testing, but I'll have to get by with my battpack...