|
Next revision
|
Previous revision
|
howto:fcc32ch [2017/09/09 11:55]
czokie created |
howto:fcc32ch [2017/09/11 05:12] (current)
czokie [The results...] |
| 00000020 45 54 45 21 00 00 00 01 11 11 11 11 11 11 11 11 |ETE!............| | 00000020 45 54 45 21 00 00 00 01 11 11 11 11 11 11 11 11 |ETE!............| |
| 00000030 | 00000030 |
| </file> | |
| ==== dji.configs_force_boost ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 22 |..............."| | |
| 00000030 22 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |""..............| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| </file> | |
| ==== dji.configs_force_boost_and_23 ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 66 |...............f| | |
| 00000030 66 66 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |ff..............| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| |
| </file> | |
| ==== dji.configs_force_boost_and_25 ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 aa |...............?| | |
| 00000030 aa aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |??..............| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| 00000047 | |
| </file> | |
| ==== dji.configs_force_ce ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 44 |...............D| | |
| 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| 00000047 | |
| </file> | |
| ==== dji.configs_force_ce_23 ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 44 |...............D| | |
| 00000030 44 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |DD..............| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| 00000047 | |
| </file> | |
| ==== dji.configs_force_ce_25 ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 88 |................| | |
| 00000030 88 88 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| | |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| 00000047 | |
| </file> | </file> |
| ==== dji.configs_force_fcc ==== | ==== dji.configs_force_fcc ==== |
| 00000047 | 00000047 |
| </file> | </file> |
| ==== dji.configs_force_fcc_and_23 ==== | |
| | Now. If we look at those two files, it appears that the first 36 bytes at least are header data that is not used. Beyond that, we can see that the 32ch file as a bunch of 11's next. Comparing that to the force_fcc file, it has a few 11's in different positions and some extra nulls at the end. |
| | |
| | Why not combine the two files and try it? |
| | |
| | ==== dji.configs_force_fcc_32-ch_mod ==== |
| <file> | <file> |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | 00000000 44 4a 49 20 53 4f 46 54 57 41 52 45 20 43 4f 4e |DJI SOFTWARE CON| |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | 00000010 46 49 47 20 3a 20 44 4f 20 4e 4f 54 20 44 45 4c |FIG : DO NOT DEL| |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 55 |...............U| | 00000020 45 54 45 21 00 00 00 01 11 11 11 11 11 11 11 11 |ETE!............| |
| 00000030 55 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |UU..............| | 00000030 11 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| |
| 00000040 00 00 00 00 00 00 00 |.......| | |
| 00000047</file> | |
| ==== dji.configs_force_fcc_and_25 ==== | |
| <file> | |
| 00000000 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000010 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 |................| | |
| 00000020 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 99 |................| | |
| 00000030 99 99 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| | |
| 00000040 00 00 00 00 00 00 00 |.......| | 00000040 00 00 00 00 00 00 00 |.......| |
| 00000047 | 00000047 |
| |
| |
| ===== Credits ===== | ==== The theory... ==== |
| * credit to vk2fro for starting this FAQ | |
| * The config files here were sourced from a file Mavic FCC configs.zip - However, the source of this is lost in the mist of time. Anyone who wants to claim authorship - please let us know on slack. I found here http://forum.rcdesign.ru/attachment.php?attachmentid=1341758&d=1499227235 | Theoretically, we are just merging two files. The suggested combined file also align with the code below, which is believed to be the parser for this file. There are some offsets for which byte to look at in various places in the parser. However the parser is not looking at a structure of the same size as our files since the bytes do not clearly align to the correct position in our file. The original authors of these config files also were guessing a bit, since they repeat the same values in multiple places. Even 1 "1" gets written as "11" to account for different encoding standards. It doesn't hurt to do both. Either way, the original files work... So, theoretically, our composite file will work also. The only reason it would not work is if the SDR in the P4P does not support higher TX power levels. But, lets give it a test fly.... Stay tuned for more. |
| * Found some stuff on a Russian forum. Two interesting things: | |
| * I found a version of these files published by SaNX at http://forum.rcdesign.ru/f132/thread500402-6.html | ==== The Results ... ==== |
| * SaNX also provided a block of code at http://forum.rcdesign.ru/f132/thread500402-4.html that I will quote below for archival purposes | * Previous State: |
| | * On 2.4 32ch mod, I got some pretty decent range. however, I was unable to descend to a lower altitude. I maintained 120m to avoid obstructions. |
| | * For 5.8 - I had not tried all that much before. The 32ch mod for 2.4 gave me what I needed. I know that I regularly had range issues on 5.8. In testing today, I was able to go the same range as the 2.4 32ch test. |
| | * Conclusion: Overall, due to interference, 32ch doubles my range. Due to higher output, I believe the FCC part of the custom file gives me increased range on 5.8g. |
| | * But: Need to do something more scientific to validate before releasing a new config file to the masses. |
| | * WANTED: Need someone with some test gear. |
| | ==== The Code ==== |
| |
| <file c> | <file c> |
