- Joined
- Jan 1, 2017
- Messages
- 191
- Reaction score
- 17
- Age
- 57
I am experiencing some painful issues with the Wifi functionality:
I have a Stock Solo running latest release of opensolo on the vehicle and the controller.
When I fly the Solo near an area that has many access points in range I lose connectivity from the controller to the Solo at closer range than if out in the middle of nowhere.
This is at about 400FT. range from the controller with the stock antennas. (this is expected normal)
The Solo immediately starts to return home (of course) as it is designed to do this.
However the Solo takes AT LEAST 1 minute to reconnect to the controller (Wifi Access Point)
Sometimes over TWO minutes (by that time it has already landed and is 20 feet from me.
And sometimes it *NEVER* reconnects to the controller.
I've waited 30 minutes after it has landed and have stood 5 10 20 30 and 50 feet from it waiting.
Something is braindead and it won't reconnect.
The ONLY way to get it to connect again is to power cycle the SOLO vehicle.
And then it instantly connects.
Power cycling the controller while in this state had no affect. it never reconnects once in this state from just power cycling or rebooting the controller (access point).
I come here posting with a very good understanding of Wifi how it works interference and such so please keep that in mind and realize I know how this works and what
could be going on here and also what is not.
On the ground we can see maybe 4 or 5 2.4GHz Wifi access points from distant houses/buildings.
We do not have congestion or connectivity issues on the ground or connectivity issues at all on initial connect and flying at short range (several hundred feet away from controller)
The connectivity and reliability is fine here.
At 400ft. altitude we can see hundreds of Accesspoints and at some point (not weak signal) but under heavy congestion I see the connectivity just drop (Around -65 or -67 dBm signal strength).
At this point the craft goes into RTL and starts getting closer to the controller.
1-2 minutes later it reconnects and most of the time after it has already landed or is very very close.
Sometimes it NEVER reconnects EVER.
The bug I am reporting or wish to pursue investigation is on Craft to controller Wifi re-association after lost connection.
I am 100% sure it is not working like it should be.
The craft Wifi should be very aggressively trying to re-associate back to the controller (access point) after a lost association for any reason and clearly is not happening.
Just In case it could be a contributing factor I should also mention that I am running openSolo (latest release and up to date) on my Samsung Galaxy Phone in the combination.
The phone does not ever lose association to the controller (AP) or experience connectivity issues to the controller.
I can provide any logs or do further testing please let me know what I should do next.
I definitely would like to see this get resolved and would like to be helpful as possible with this.
Thanks.
Steve
I have a Stock Solo running latest release of opensolo on the vehicle and the controller.
When I fly the Solo near an area that has many access points in range I lose connectivity from the controller to the Solo at closer range than if out in the middle of nowhere.
This is at about 400FT. range from the controller with the stock antennas. (this is expected normal)
The Solo immediately starts to return home (of course) as it is designed to do this.
However the Solo takes AT LEAST 1 minute to reconnect to the controller (Wifi Access Point)
Sometimes over TWO minutes (by that time it has already landed and is 20 feet from me.
And sometimes it *NEVER* reconnects to the controller.
I've waited 30 minutes after it has landed and have stood 5 10 20 30 and 50 feet from it waiting.
Something is braindead and it won't reconnect.
The ONLY way to get it to connect again is to power cycle the SOLO vehicle.
And then it instantly connects.
Power cycling the controller while in this state had no affect. it never reconnects once in this state from just power cycling or rebooting the controller (access point).
I come here posting with a very good understanding of Wifi how it works interference and such so please keep that in mind and realize I know how this works and what
could be going on here and also what is not.
On the ground we can see maybe 4 or 5 2.4GHz Wifi access points from distant houses/buildings.
We do not have congestion or connectivity issues on the ground or connectivity issues at all on initial connect and flying at short range (several hundred feet away from controller)
The connectivity and reliability is fine here.
At 400ft. altitude we can see hundreds of Accesspoints and at some point (not weak signal) but under heavy congestion I see the connectivity just drop (Around -65 or -67 dBm signal strength).
At this point the craft goes into RTL and starts getting closer to the controller.
1-2 minutes later it reconnects and most of the time after it has already landed or is very very close.
Sometimes it NEVER reconnects EVER.
The bug I am reporting or wish to pursue investigation is on Craft to controller Wifi re-association after lost connection.
I am 100% sure it is not working like it should be.
The craft Wifi should be very aggressively trying to re-associate back to the controller (access point) after a lost association for any reason and clearly is not happening.
Just In case it could be a contributing factor I should also mention that I am running openSolo (latest release and up to date) on my Samsung Galaxy Phone in the combination.
The phone does not ever lose association to the controller (AP) or experience connectivity issues to the controller.
I can provide any logs or do further testing please let me know what I should do next.
I definitely would like to see this get resolved and would like to be helpful as possible with this.
Thanks.
Steve
Last edited: