Recent content by motigchelaar

Did you not actually read the thread? So far nobody has figured out how to increase the Control signal. So the patch you see described is for the video link on 2.4Ghz only.

That is indeed all it takes to introduce the "watchdog.sh" on the drone as well. This is described in the instructions somewhere in this very long thread - but the Windows patch tool currently does not yet patch the drone for you. At least, it looks like it does not.

I think that when you look carefully in the log of your remote (/var/log/messages) you will find that the remote DID change back to CE-mode but the "watchlog.sh" script quickly changed it into FCC mode again... That is the purpose of the whole patch you applied with the Windows tool. I have the...

Correct. I have the drone on 1.5.7 and the remote on 1.6.8... This may mean that with a drone on firmware 1.6.8 it may be required to have the "watchlog.sh" script on the drone as well. I have not tried this yet and the Windows tool does not currently patch the drone. It only patches the remote.

Yep. Good catch. My typo. I have corrected my posts. Do you mean it changes back for the drone or for the remote? Or both? The Windows app made by PappaTita handles the remote. I have not seen my drone change back to CE mode yet. Could be a firmware thing. I have my remote on the latest...

I don't know (yet). You obviously managed to get telnet enabled. So, you can execute the required commands manually whilst in a telnet session: Connect to the drone using telnet execute "iwinfo" to confirm the drone is using 17dbm execute "iw dev wlan0 set tx power limit 2700" to set the drone...

Here is what I did on the DRONE-side using a WINDOWS system: Turn on the Remote Control Turn on the Drone Connect your Windows device to the WiFi signal of the Remote Control Open a Windows command prompt (Start -> Run -> "cmd") Make note of the current directory for your Command Prompt window...

You clearly need to learn to read properly. Here is what gvsukids said: "I had it lose connection while trying to orbit in tracking. It just hovered. I had it come back to me in a waypoint mission after disconnecting from controller." He is describing his experience with two different flying...

You can download the file(s) you want to edit using FTP. If you're using Windows command-line FTP make sure to enable "type binary" (!) when transferring file. When you have downloaded the file(s) onto Windows you should use a text editor like Notepad++ to edit the file(s). But really - all...

Stupidity rules. It's not an issue. It's in the Litchi documentation. There is different behavior depending on the type of mission / mode the drone is flying in when it loses control signal...

You can also prepare some type of missions online using the Litchi Mission Hub: Mission Hub - Litchi

That is correct because the Windows software appears to only patch the Remote Control and not the drone. At current you will have to patch the drone manually following the instructions that can be found in this thread. The good news is that when the drone has been patched it does not appear to...

If you had taken my previous post a bit more serious you would have known why it fails. There is an error in your code. It is not setting the correct permissions of 755 for the "watchlog.sh" script: I guess you tested your Windows tool against a remote control that had already been patched.

There is at least one typo in your code. At least in the wording that is displayed. If you made the same typo in the actual commands that are being executed then the "watchlog.sh" will not have the correct permissions :-) "07:15 hmod 775 /sbin/watchlog.sh" should read "07:15 chmod 775...