I reverted my hostasp.conf. Couldn't connect to solo after that. Ended up having to do a factory reset and re-pair. Everything is good now.
>>>AS OF THE UPCOMING FIRMWARE THIS MOD IS NO LONGER NECESSARY<<<
Also note that modding any file in the SoloLink system means that it won't update when you update the copter. To revert to using the defaults, SSH into both Solo and Controller and do: sololink_config --settings reset
You will need to re-pair after the settings reset.
Note: @Judicator has automated this process too, the Windows program can be downloaded from here: Solo Tweaker
I've just finished this video today, it's relevant to the latest firmware as well. Amongst other things this allows the Solo to use any pair of channels from 1 to 12, whereas before the mod it is limited to using only channels 6 and 11.
This has increased my range in both congested and non-congested Wi-Fi areas. The cost of doing this mod is exactly $0.00.
The software to download to perform this mod is:
A hackable text editor for the 21st Century
Bitvise SSH Client Download
The IP address of the Solo controller is: 10.1.1.1
The IP address of the Solo is: 10.1.1.10
The username is: root
The password is: TjSDBkAu
The changes to make to the hostapd.conf file are:
acs_num_scans=8
#chanlist=6 11
beacon_int=999
wmm_ac_vi_cwmin=2
wmm_ac_vi_txop_limit=136
wmm_ac_vo_txop_limit=1
disassoc_low_ack=0
The command to run to update the MD5 is:
md5sum /etc/hostapd.conf > /etc/hostapd.conf.md5[/QUOTE
Will this reset work on Mac?
Apparently yes, you must use the command line or the tool (which executes the command line) as the file will still appear as modified and the new update will not overwrite the file to give you the new changes.Thanks for pointing that out. Didn't go back and read the updated note
So I reverted by changing the values back to stock setting in the hostasp. Is the settings reset command line that Ian mentions needed then?
>>>AS OF THE UPCOMING FIRMWARE THIS MOD IS NO LONGER NECESSARY<<<
Also note that modding any file in the SoloLink system means that it won't update when you update the copter. To revert to using the defaults, SSH into both Solo and Controller and do: sololink_config --settings reset
You will need to re-pair after the settings reset.
So i run this "sololink_config --settings-reset" on both controller & Solo with the command: "md5sum /etc/hostapd.conf > /etc/hostapd.conf.md5" correct?Ian -- Actual command is "sololink_config --settings-reset" (with the hyphen between "settings" and "reset". You may want to edit that in your first post on this thread.
Thanks!
I reverted my hostasp.conf. Couldn't connect to solo after that. Ended up having to do a factory reset and re-pair. Everything is good now.
As you did a reset I'd expect you'd be fine. Did you run the command on the Solo first then the controller? I'm not sure it matters, but I'd have run it on the Solo, then the controller, then power cycled both.I also had to do a factory reset! For some reason while doing the Conf reset the controller froze. I could not ssh back into the controller. It kept telling me the link to the controller had changed. Even tried the default password with no success. So total reset and repair. Then updated to current firmware. Is this going to give me any problems that I'm not aware of?
As you did a reset I'd expect you'd be fine. Did you run the command on the Solo first then the controller? I'm not sure it matters, but I'd have run it on the Solo, then the controller, then power cycled both.
No, I made changes on the controller 1st. Afterwards I had thought the solo should had been done first. Seems to me that if a total reset works that would be a better way then modifying the conf files. Anyway the final result seems to have worked. Thanks!As you did a reset I'd expect you'd be fine. Did you run the command on the Solo first then the controller? I'm not sure it matters, but I'd have run it on the Solo, then the controller, then power cycled both.
Didn't have time to root through and change all the numbers in the config file. I just ran solo tweaker and reverted changes. It was supposed to update the solo and controller. It obviously failed so a quick factory reset and good to go.
Same here...needed a factory reset and re-pair.
I went in and did a quick check on the etc directory. After running the reset command and updating firmware, the firmware seems to have deleted all my old backup files.As you did a reset I'd expect you'd be fine. Did you run the command on the Solo first then the controller? I'm not sure it matters, but I'd have run it on the Solo, then the controller, then power cycled both.
The new hostapd.conf enables more channels but starts the channel availability at channel 4, despite giving channel 1 a selection advantage (0.8). I didn't comb through to see what all the other changes were to compare them to the original mod but clearly it's not an exact copy.
I left the modified hostapd.conf as is and did the update. It was a bit troublesome as it changed the Solo link password back to the default. Then I had to re-pair the controller and Solo.That's correct, not sure why the channels start at 4, but I'm assuming there's a reason 3DR have done that, so I'm going to see how well it works before modding it back to all channels.
We use essential cookies to make this site work, and optional cookies to enhance your experience.