- Jan 1, 2017
- Reaction score
Logging in the /log directory on Solo and Controller are rotated in different ways so you don't need to worry about how much the device holds, and etc. Just grab all the logs found in the log directory.I'll get to work on those logs.
I don't at all believe that I am the only one having the problem.
I'm just now aware of the problem and know how to bring it out consistently.
I'm also in the process of seeing if I can get it to fail without even having to fly the Solo.
By simply walking out the TX (controller) in a residential area (no props on the solo)
until the connection is lost then walking back.
If it fails just as much or as easily without having to risk it up in the air each time people may be more
inclined to test their own and test them more extensively.
I also have a friend who owns a Solo completely stock that I may be able to run similar tests on swap wifi cards etc.
Yep it can be a lot of work.
I very much appreciate any/all help that is being offered!
And I will get you those logs made available here soon.
How much logging does the device hold?
Minutes hours? is there a reboot or rollover policy?
I'm unclear if I should provide ALL logs since I started flying it (or how long they are stored.
Or if they must be grabbed before rebooting etc.
If by 'the way it should be' you mean a completely non-standard, custom, proprietary protocol and signal stack then yes.Just keeping an eye on this.
I've not flown it since my last post.
It's been cold and crappy out.
And I got a Mavic Pro.
Which implements 2.4GHz wireless the way it was meant to be.
The range and reliability are insanely good.
The way it should be.