Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
howto:fcc32ch [2017/09/09 12:07]
czokie |
howto:fcc32ch [2017/09/11 05:12] (current)
czokie [The results...] |
| |
| 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. | 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. |
| | |
| | ==== The Results ... ==== |
| | * 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> |
