Differences

This shows you the differences between two versions of the page.

--- documentation:nld:start [2021/12/20 10:10] – gregk
+++ documentation:nld:start [2022/04/20 01:19] (current) – gregk
@@ Line 1: / Line 1: @@
-**WORK IN PROGRESS**: This is a new page and not yet complete. Please be patient.
 ====== No Limit Dronez ======
 Thank you for your purchase or interest in NoLimitDronez, or NLD for short. How do I use NLD, where do I start? Is using NLD legal, and will it void my warranty?
@@ Line 76: / Line 74: @@
   * No-fly zone limits removed
   * Galileo satellites enabled (where supported by your hardware)
+{{:documentation:nld:cfc.png?600|}}
 The installation is a simple process. Just click the install button, and wait for the chains to fall off your bird. You can uninstall the custom flight controller later if you wish to do so.
@@ Line 112: / Line 112: @@
   * Boost mode will look the same as FCC mode in the app and cannot be verified any other way.
-{{:documentation:nld:fcc-check.jpg?600|}}
+**FCC mode**
+{{:documentation:nld:fcc-mode.jpg?600|}}
+**CE mode**
+{{:documentation:nld:ce-mode.jpg?600|}}
 FCC has a higher output for RC power than CE mode. You can change your RC to a higher level here. You must have a supported bird and be on compatible firmware. Connect your bird and Enable FCC Mode to change from CE to FCC. Once changed, you can leave it, or if you want even more power, you can Enable Signal Boost, along with FCC mode, for the highest power output possible.
@@ Line 133: / Line 137: @@
 **NOTE**: As stated above, the decrypted app used to build this application is ancient. It does not work, for example, with a Mavic 2 series bird. If the NLD mod tools support the features you require, you are encouraged to use the stock DJI app and leave your data turned off during flight. We no longer provide support for the Android APK patcher, but it is still available for those that require it.
-FIXME: HereMaps versus GoogleMaps
+=== HereMaps versus GoogleMaps ===
+There are two map options in NLD GO. Go to internal storage and look for the /DJI/og_settings folder.
+Unzip {{ :documentation:nld:usegooglemap.zip |}} and copy the useGoogleMap file into the /DJI/og_settings folder, or you can make a file named useGoogleMap and place it there. It should NOT be called useGoogleMap.txt - that will not work. You need to remove the .txt and save it only as useGoogleMap. Run GO and Google Maps will be working.
+If you want to switch back to HERE maps, rename that file. As a suggestion, you could name it HuseGoogleMap.
 ==== 3.9 NFZ Removal ====
-The NFZ removal tab will only be available for Mavic 2 series equipment. If you have other equipment, the installation of a custom flight controller will also bypass NFZ restrictions.
+The NFZ removal tab will only be available for Mavic 2 series equipment. If you have other equipment, installing a custom flight controller will also bypass NFZ restrictions.
 FIXME: Details of what to click
-We have one big tip for NFZ bypass. We recommend you to start your flight in this order.
-Turn on your remote control
-Turn on your bird and let it connect to your remote control
-Connect your RC to the device running GO
-The above will minimise the chances of NFZ updates flowing to your aircraft during startup.
 ==== 3.10 DJI GO 4 Custom Patcher ====
-To patch a version of GO that we support, click on the drop-down box on the left side of the screen and select the GO version you want to patch.
+Click on the drop-down box and select the GO version you want to patch to patch DJI GO. Click on download and save this file. Click "APPLY PATCH" at the bottom of the screen, and our software will patch the DJI App into the modified NLD-DJI-GO4 App. Be patient. Depending on your internet connection, this may take a while.
-Click on download and save this file to your desktop, or to the NLD folder you created. Click on the box on the right side of the screen and select an output folder where you want the new NLD DJI GO4 App to be stored. Use the same location as where you downloaded the unpatched GO file. Once that is done, click APPLY PATCH at the bottom of the screen and the DJI App will now be patched and converted into the modified NLD-DJI-GO4 App. Be patient. Depending on your internet connection, this may take a while. Once that is done, transfer that file to your device via a USB cable hooked between the phone & the computer. Use the "My Files" app on the phone to locate the APK file and click on it to install it in the phone. Note you have to allow unknown apps to be installed in the settings on your device. If you have issues with the .apk not wanting to install, download ES file explorer from the Google play store and use that. Current Mavic 2 owners will use Stock GO, either iOS or Android for their birds. We recommend flying in airplane mode, and caching your maps before you fly. Either download offline HERE maps, or open GO on your device, go to the map and scroll around your flying area before you fly.
-Why is the NLD GO Patcher not available for the M2? It's greyed out.
+After patching is complete, transfer the file to your device via a USB cable. Use the "My Files" app on the phone to locate the APK file and click on it to install it on your phone. You need to enable settings on your device to allow the installation of unknown apps. If you have issues installing the .apk, download ES file explorer from the Google play store and use that.
-This is due to our NLD GO app not being compatible with the M2. You will use the same GO (stock version) you are using now with the M2. Either Android or iOS version.
-==== NLD FCC mode and other options ====
+Current Mavic 2 owners cannot use the patched app and must use the current standard version of DJI GO4 for iOS or Android. For privacy, we recommend flying in aeroplane mode and caching your maps before you fly.
+You can obtain a raw unpatched version of the apk's from the links below. You may need to Right Click and select 'Save Link As' to download these APK's.
-.1.22 link for patching with NLD: http://www.openpilotlegacy.org/dji.go.v4-4.1.22-3028592-noseceo.apk
+^Go4 4.1.22|http://dji-rev.com:8080/APK/DJI_Go_v4%204.1.22_NoSecNeo.apk|
+^Go4 4.1.14|http://dji-rev.com:8080/APK/DJI_Go_v4%204.1.14_NoSecNeo.apk|
+^Go4 4.1.15|http://dji-rev.com:8080/APK/DJI_Go_v4%204.1.15_NoSecNeo.apk|
+=== 32 Channel Mode for P4 ===
+There is a datalink.settings.json file on your device after installing NLD GO. This file allows enabling boost mode on Mavic Pro devices or enabling 32 channel mode for P4 devices. However, boost mode mods are now available even without the GO4 app, so the Mavic boost mod for GO4 is now out of date but still useful for P4 users.
+Edit the datalink.settings.json file with a text editor, find the variable 32Channels and change false to true. Save the file.
+Or, you can extract an already patched file from {{ :documentation:nld:datalink.settings.zip |}}. Extract the JSON file and save this to /DJI/og_settings/ on your device.
-==== Switch between Google Maps and HERE maps ====
-Here is what you need to do on your device:
-Go to internal storage and look for the /DJI/og_settings folder.
-Unzip useGoogleMap.zip and copy the useGoogleMap file into /DJI/og_settings folder, or you can make your own file named useGoogleMap and place it there. DO NOT make useGoogleMap.txt file and use that. It will not work. You need to remove the .txt and save it only as useGoogleMap. Run GO. You should have Google Maps working.
-If you want to switch back to HERE maps, just rename that file. As a suggestion, you could name it HuseGoogleMap.
-Here is how to enable boosted RC for Mavic (1.5w output) and 32 channel mode for P4.
-It's configured from the /DJI/og_settings/datalink.settings.json on your device with NLD GO 4.1.22 installed.
-Edit the datalink.settings.json file with a text editor, find the variable called "boost" and change this from false to true to enable the 1.5W boost feature to get even more range than FCC mode. Do the same for the 32Channels and change false to true. Save the file. Boost has been tested and working on Mavic, and 32 channel tested and working on P4P. NOTE! This feature runs the RF chips at their max voltages and as such generates a LOT more heat. It isn't advisable to use this mode in very hot climates as the small internal cooling fan may not be able to cope with the extra heat. Run this boost mode at your own risk! You could burn out your RF chips if the chips overheat.
-  * the file attached has boost mode enabled. Save this to /DJI/og_settings/ on your device
 Watch this great video on how to patch your own NLD GO 4.1.22:
 https://youtu.be/PDI9NgHFNmk
-====  User Supplied Firmware ====
+====  3.11 User Supplied Firmware (ModuleMix) ====
-Using a user-supplied firmware file? Why would you want to do this? DJI always is changing firmware, adding new features - but mostly adding security and patching holes to stop you from modding your birds. NLD is always figuring out ways to get around these security patches, so you CAN mod your bird.
+DJI constantly changes firmware, adding new features and patching security holes to stop you from modding your birds. NLD supports user-supplied firmware flashing. You can now use mixed module firmware to flash your drone and still use NLD!
-NLD now supports user-supplied firmware flashing.
+What exactly is mixed module firmware or cherry-picked firmware? Go here and read: https://wiki.dji-rev.com/howto/modulemix
-This means you can now use mixed module firmware to flash your drone and still use NLD!
-What exactly is mixed module firmware or cherry-picked firmware? Go here and read: https://dji.retroroms.info/howto/modulemix
+DJI packages firmware with multiple modules for the various hardware components on your bird, such as Camera module, ESC modules, sensor modules etc. DJI then combines these modules into one firmware file. When you upgrade or downgrade your firmware, the flashing code on the drone will check each module and flash it to match the firmware you are trying to install.
-The DJI firmware is made up of individual firmware modules for the various hardware components on your bird, such as Camera module, ESC modules, sensor modules etc. This is combined into one single firmware file. When you upgrade or downgrade your firmware, the flashing code on the drone will check each module and flash it to match the firmware you are trying to flash to.
+Not all modules have version changes in each subcomponent, and sometimes they may be the same version. If this is the case, OR if the module is not in the firmware file, the flashing code will SKIP that module and not throw any error.
-Not all modules have version changes in each firmware-flashing module. Sometimes they may be the same version. If this is the case, OR if the module is not in the firmware file, the flashing code will SKIP that module and not throw any error. Cool huh?!
+DJI firmware is like a big zip type file. (actually a .tar file). You can use a program like 7-zip to open it and see all the modules. All the parameter/Mod changes are in the Flight Controller modules, #305 and #306. You can delete any modules, save the firmware file and flash it, but you need to keep the cfg.sig file intact. **Warning**. If you do not know what you are doing, don't mess with this, it is possible to brick your drone.
-What does this really mean? The DJI firmware is really a big zip type file, actually a .tar file. You can use a program like 7-zip to open it and see all the modules. All the parameter/Mod changes are in the Flight Controller modules and they are #305 and #306. You can delete any modules, save the firmware file and flash it, but you need to keep the cfg.sig file intact...but like any flashing of your drone, if you do not know what you are doing, don't mess with this, it is possible to brick your drone.
+Why would you want to do this? Sometimes, one module gets updated with changes that block NLD features, with other enhancements in other modules. Using this technique, you can include the good bits and exclude other parts that cause problems.
-Why would you want to do this? Let's take for example the Mavic Pro/Platinum and the Spark birds. For the Mavic Pro, the last firmware before DJI really started locking it down was 01.03.0700. On that firmware all mods can be done, with the two most popular being NFZ and Altitude disable. The Spark was firmware 01.00.0300 to do the same. The difference with the Spark firmware is that DJI FORCED a firmware update to the Sparks on that firmware and DJI will LOCK your SPARK if you do not upgrade from that firmware to a higher one. To avoid this, you use NLD GO, or you can use mixed firmware.
+While you gain the modding ability of the earlier flight controller version, you may lose some functions in the more recent flight controller version. You will have to determine if modding is worth the trade-off.
-As new firmware came out, DJI added more fixes to the firmware modules and more features, like panorama mode etc. If you upgrade to 01.04.0300 for the Mavic or 01.00.0900 for the Spark, you lose the ability to disable NFZ and Altitude. But if you are using NLD, you can use our NLD NFZ removal patch, and that is a different way to deal with NFZ, but the NFZ detection is still active and could be overridden by the GO app IF you are using a stock app, Android or iOS. If you are using the NLD GO app for Android, we have removed the NFZ data from that, so the app has nothing to override because it has no NFZ data.
+However, there have been no recent examples where mixed firmware modules are required for our mods to work. We keep this capability in NLD to defeat future DJI changes that would otherwise block our mods.
-How does mixed modules come into play? Since we know that the firmware file is made up of modules, and we know in the example of the Mavic and Spark that 01.03.0700 and 01.00.0300 can do all mods, why don't we take out these modules from the more recent firmware, like 01.04.0300 and 01.00.0900, so that the firmware flashing SKIPS the already flashed flight controller module, but updates all the rest? Do you see it? What you end up with is all the firmware modules are upgraded on your bird, EXCEPT the flight controller module, (since you deleted it from the .bin file, AND the bird already has the older version) so that you can continue to mod your bird, just like you were still on 01.03.0700 or 01.00.0300!
-NLD now supports you uploading your own firmware, so this is now possible. Make 100% sure you know what you are doing. If not done right, you can brick your bird. This means ONLY getting firmware that you have made yourself and know what you are doing, or from a trusted source.
-So for example...If your Mavic is on V01.04.0300: flash custom firmware that ONLY CONTAINS module 305/306 and the cfg.sig file from 01.03.0700 firmware, with the result of now having all up to date modules, except you now have flight controller modules from 01.03.0700 and can do all mods!
-You could also go the opposite way...if your bird is on 01.03.0700, you would flash 01.04.0300 firmware with all modules intact except you would remove 305/306 from this firmware and end up with the same result!! All modules are on 01.04.0300 firmware except for the flight controller module. The same goes for the Spark using the spark firmware versions.
-What about NLD, will it now detect that I have mixed firmware and make all the options available for the flight controller version that is actually on the bird? Yes and No. Your firmware version will be detected as the LAST version you flashed with.
-For example. Your bird is on firmware 01.03.0700 and you flash to mixed module 01.04.0300. Your firmware will be detected as 01.04.0300. Let's say you go the opposite route, and are already on 01.04.0300 Stock, but want to have all mods available, so you flash mixed module 01.03.0700. Your firmware will be detected as 01.03.0700 version.
-What are the down sides to doing this?
-While you gain the modding ability of the earlier flight controller version, you may lose some functions in the more recent flight controller version. You will have to determine if modding is worth the trade-off.