Duplicate Sololink network after v1.2 upgrade,

Posted by G McCollam on October 12, 2015 at 4:08pm

I just performed the update to v1.2 and now have two Sololink networks in my settings tab (iOS) - one being the original - Sololink-xxx - the other being a newer Sololink network with the default password. The app seems to recognize only the newer one while the controller and Solo seem to prefer the original. 

The update ran to completion, it didn't end prematurely at least as far as I can tell. I've performed updates before without issue so wondering what I did wrong and how to fix. I can't connect the controller to Solo. Perhaps I can simply delete the newer network?

Has anyone seen a similar issue after updating to v1.2? 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • Chip Luck October 12, 2015 at 4:47pm

    I had to re-pair Solo to the Controller.  Is the controller seeing Solo when both are powered on?  Anyway, this is how I fixed mine after the update:

    • EVERYTHING off, turn off Wi-Fi on your tablet/phone device
    • power up Solo
    • power up Controller
    • wait a few minutes (my Controller just sat there, indicating "looking for Solo")
    • Turn Solo over and hit the Pair button for little more than 1 second
    • Controller should now say "searching for GPS" or other message indication communication with Solo is established
    • Turn on your Wi-Fi on your tablet phone
    • 'Forget' or delete all SoloLink Wi-Fi connections on your device
    • Re-search for SoloLink Wi-Fi on your device
    • Re-enter 'sololink' for default password on your device (it did get reset on mine)
    • Change SoloLink network password to your choice
    • Test fly!

    Hope this works, did for me.  Let us know.

    Cheers

    • G McCollam > Chip Luck October 18, 2015 at 3:29pm

      No, the controller doesn't see Solo when the two are powered on.  When I turn the controller off and power up the Solo I see one SSID; when I turn Solo off and turn on the Controller I see another (older) SSID. When both are on I see two, the older SSID being the one I had before attempting the update. That might explain why the two devices can't see one another. This is consistent across reboots of app, controller and Solo. Forgetting networks or rebooting the iPad makes no difference. 

      This afternoon I contacted a friend who also owns a Solo. She attempted the upgrade herself over the weekend and got the same result. I don't know what's at root but based on this and on conversation with 3DR, it's a problem that hasn't been fixed yet (as of 10/18). 3DR support mentioned an issue with their update server, possibly a firmware upgrade gone awry. Whatever, it's clear something's wrong.  

      The most recent recommendation from 3DR calls for a factory-reset, which I'm not happy about until they offer more info on root cause. Honestly, the last few days have made me question 3DR. I was patient throughout summer, now not so sure. 

    • Chip Luck > G McCollam October 19, 2015 at 6:30am

      @G McCollam

      From my limited knowledge of Solo and firmware, however experienced at software, UNIX, Linux, etc. I have a couple of questions for you.  First off, I do not have an iOS device and run android on the Application side, the software that runs on the Controller and Solo is the same, no matter what flavor is on the App side.  It just appears as you stated that you have had an issue with the Software Update which was applied using your iOS based App. You stated it's and issue verified by 3DR, however with years of software and hardware integration and configuration, I have a few questions for you.  NOTE: I'm not a support person for 3DR, just a home grown integrator and just plain curious.

      You stated: "When I turn the controller off and power up the Solo I see one SSID; when I turn Solo off and turn on the Controller I see another (older) SSID"  Can you tell me what name of the SSID's were on each device?  I have an idea for you to try.

      Also, are you familiar with performing a access to the files on the Controller and Solo using a SSH program?

      Cheers

    • G McCollam > Chip Luck October 24, 2015 at 6:43am

      Thanks Chip. This turned out to be a problem which I can't fix on my end. 3DR will replace the unit. For a short while there was an issue with 3DR's upgrade server that resulted in firmware being written to the wrong device. Only a handful of people worldwide were effected, apparently. Next time I'll wait a bit before upgrading :)

    • G McCollam > Chip Luck October 13, 2015 at 3:43pm

      Thanks Chip, Unfortunately that doesn't work. The controller won't respond to the pair button (tried your sequence several times). I've been in conversation with 3DR support and it looks like it may be an issue related to this release, perhaps specific to iOS. I'd suggest that other iOS app users who've not applied 1.2 hold off a bit until we hear more from the company.

      As of today 3DR support has received 5 similar cases of duplicate WIFI, all running on iOS. I'm told they're working on a resolution and I expect to hear more from them by tomorrow. If others have the problem (and you happen to have an Android device handy) one possible solution is do a factory reset on the Solo then try applying the upgrade using an Android device. I've not tried this myself (for lack of an Android device).

      Have any iOS users applied the upgrade without issue? 

    • Erik Graham > G McCollam October 15, 2015 at 9:44pm
      Upgraded without an issue. Initially the iPad did show both networks, but after cycling the wifi on/off on iPad it "healed" itself. I think your iPad is just trying to hang onto the wifi connection, but your Solo is NOT actually creating 2 wifi networks. You could power cycle the iPad, or in wifi settings on the iPad, click the little "i" next to the old network and then select "Forget this network" on the screen that comes up.
    • G McCollam > Erik Graham October 16, 2015 at 1:06pm

      Thanks Erik,

      In fact this is/was an issue with 3DR. There was a bug where the update was installing a controller firmware to the Solo. In my case there are in fact two networks with the Solo and the controller using separate network configs. Turning one off and the other on show the two different networks.

      At this point I haven't had time to revisit and fix. I can't ssh to the Solo though I can to controller. I suspect that Solo's network config got over-written during the errant firmware install and perhaps the process didn't complete.

      3DR has acknowledged that their server caused this, I suspect it depends on when you did the upgrade whether it effected you. It's definitely an issue on their end and frustrating as I've lost two days of planned work because of it. I'm not going to slam the company, they recognized the problem and have been good about trying to provide support. But it should never have happened in the first place. 

This reply was deleted.