How to Update Tx-Power with Magic Power v5.0

[AngryBird]

Thanks for this mod, PapaTita.
One question, does this mod still works with DJI GO ? Or I should use Litchi?

 

[ciro italy]

it work with both

Sent from my SM-T113 using PhantomPilots mobile app

 

[Tirex]

Hello. And why you set the value of 27 dbm? Why is the value of 27 ?? I saw somewhere that puts people 33dbm and too set when the firmware was 1.5.7. I want to try to put the same 3300 value. And why the region BO, and not US? In BO, the channel width has to manage the 5.8 Gz

 

[Philltayl]

Hello. And why you set the value of 27 dbm? Why is the value of 27 ?? I saw somewhere that puts people 33dbm and too set when the firmware was 1.5.7. I want to try to put the same 3300 value. And why the region BO, and not US? In BO, the channel width has to manage the 5.8 Gz

What are you smoking??????. This mod has nothing to do with 5.8Ghz!!!!!

 

[Tirex]

What are you smoking??????. This mod has nothing to do with 5.8Ghz!!!!!

What is found, then the smoke)) Each region has its own frequency. It can be seen from the log. The CE (Europe) its frequency in the US (America), the BO (Japan) on your own. If you look at your logs, you will see clearly. What frequencies are different at 5.8 Gz. Value TX no relation to the frequency of 2.4 Gz has not, but the choice is in the region.

 

[Tirex]

US

Jan 1 00:00:04 (none) kern.info kernel: [ 3.840000] cfg80211: Regulatory domain changed to country: US
Jan 1 00:00:04 (none) kern.info kernel: [ 3.850000] cfg80211: DFS Master region: FCC
Jan 1 00:00:04 (none) kern.info kernel: [ 3.850000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jan 1 00:00:04 (none) kern.info kernel: [ 3.860000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 00:00:04 (none) kern.info kernel: [ 3.870000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
Jan 1 00:00:04 (none) kern.info kernel: [ 3.880000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (0 s)
Jan 1 00:00:04 (none) kern.info kernel: [ 3.890000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 00:00:04 (none) kern.info kernel: [ 3.900000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
BO

Aug 20 05:20:14 (none) kern.info kernel: [ 295.750000] cfg80211: Regulatory domain changed to country: BO
Aug 20 05:20:14 (none) kern.info kernel: [ 295.760000] cfg80211: DFS Master region: JP
Aug 20 05:20:14 (none) kern.info kernel: [ 295.760000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 20 05:20:14 (none) kern.info kernel: [ 295.770000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Aug 20 05:20:14 (none) kern.info kernel: [ 295.780000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
RU

Aug 20 05:20:02 (none) kern.info kernel: [ 283.840000] cfg80211: Regulatory domain changed to country: RU
Aug 20 05:20:02 (none) kern.info kernel: [ 283.840000] cfg80211: DFS Master region: ETSI
Aug 20 05:20:02 (none) kern.info kernel: [ 283.850000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 20 05:20:02 (none) kern.info kernel: [ 283.860000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Aug 20 05:20:02 (none) kern.info kernel: [ 283.860000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Aug 20 05:20:02 (none) kern.info kernel: [ 283.870000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
Aug 20 05:20:02 (none) kern.info kernel: [ 283.880000] cfg80211: (5650000 KHz - 5730000 KHz @ 80000 KHz), (N/A, 3000 mBm), (0 s)
Aug 20 05:20:02 (none) kern.info kernel: [ 283.890000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
GB

Aug 20 05:19:48 (none) kern.info kernel: [ 269.840000] cfg80211: Calling CRDA for country: GB
Aug 20 05:19:48 (none) kern.info kernel: [ 269.840000] cfg80211: Regulatory domain changed to country: GB
Aug 20 05:19:48 (none) kern.info kernel: [ 269.850000] cfg80211: DFS Master region: ETSI
Aug 20 05:19:48 (none) kern.info kernel: [ 269.850000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 20 05:19:48 (none) kern.info kernel: [ 269.860000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 1700 mBm), (N/A)
Aug 20 05:19:48 (none) kern.info kernel: [ 269.870000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Aug 20 05:19:48 (none) kern.info kernel: [ 269.880000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
Aug 20 05:19:48 (none) kern.info kernel: [ 269.890000] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm), (0 s)
Aug 20 05:19:48 (none) kern.info kernel: [ 269.900000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)

We are interested only channel
5.8 Ghz


You understand that in the REGON us, transmitter power 5.8 Gz, more than BO. By this, I would put the US in the region of the program that actually going to try to change the script. Let's see what happens. This is with regards to 5.8Gz, about 2.4. there is no question at all. The only question is why 27 dBm, and not 33?


More'll tell you, I installed antenna itelite, replaced in the remote
amplifier transmitter 5.8 Gz is more powerful now that my 3 Standart flies 3km without problems

 

[Philltayl]

What is found, then the smoke)) Each region has its own frequency. It can be seen from the log. The CE (Europe) its frequency in the US (America), the BO (Japan) on your own. If you look at your logs, you will see clearly. What frequencies are different at 5.8 Gz. Znachanie TX no relation to the frequency of 2.4 Gz has not, but the choice is in the region.

Again, what are you on............this mod is to do with the 2.4Gz ....ie. the 'wi-fi' comms

 

[Tirex]

Again, what are you on............this mod is to do with the 2.4Gz ....ie. the 'wi-fi' comms

You carefully look at all what you are doing, or just press the button? You can see right into the program, the program changes the region at the BO? Do you live in Japan ??? BO is a region of Japan, which you change. You can put scripts in any of the above. The question is about 27 dBm program was the author, and do not understand why you left in the question about 5,8 Gz?

REG="BO"
LIMIT=2700
DRONELIMIT=2700
DRONE="192.168.1.2"

 

[Tirex]

Again, what are you on............this mod is to do with the 2.4Gz ....ie. the 'wi-fi' comms

You about something that's talking about?

/ # iw reg get
country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)
/ # iw reg set US
/ # iw reg get
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
/ # tail -f /var/log/messages
Sep 23 11:14:15 (none) kern.info kernel: [ 1084.660000] cfg80211: DFS Master region: JP
Sep 23 11:14:15 (none) kern.info kernel: [ 1084.670000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Sep 23 11:14:15 (none) kern.info kernel: [ 1084.680000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Sep 23 11:14:15 (none) kern.info kernel: [ 1084.690000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)

As the logs show that the choice of the region is very important. Since we are talking about a program that changes the mode, and it also changes the region. So if you make the choice of the region is still in the program, it will be all super. Further, it is visible that in the BO region power management on the drone 30 dbm, and regional US 40 dbm. Then the question that you smoke, if you do not understand what makes this program. I obviously did not live in Japan ...

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)

country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

 

[Mac_flyfr]

Again, what are you on............this mod is to do with the 2.4Gz ....ie. the 'wi-fi' comms

Remember i told you exactly the same a few post ago...
This mod changes the region so it changes 5.8ghz power configuration too ! (it's interesting only for CE area's people...CE area is ultra restrictive on 5.8ghz tx power so we have a very bad range )
I'm in CE area and i told many times i see a range difference on 5.8ghz too.
First i didn't understand why, so i did the telnet command "iw reg get" --> BO: JP, before mod i was in CE... so it's exactly what Tirex said... i'm in CE area so it explains why my 5.8ghz range is improved too after papatita mod...

 

[toegema]

I thought Japan region transmitted somewhere in the 900 MHz area?


Sent from my iPhone using PhantomPilots

 

[Tirex]

I thought Japan region transmitted somewhere in the 900 MHz area?


Sent from my iPhone using PhantomPilots

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A) Telematic, Video
(5735 - 5835 @ 80), (N/A, 30), (N/A) Radio Control

MHz

 

[toegema]

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A) Telematic, Video
(5735 - 5835 @ 80), (N/A, 30), (N/A) Radio Control

MHz

Sent from my iPhone using PhantomPilots
Look at operating freq

 

[Tirex]

Sent from my iPhone using PhantomPilots
Look at operating freq

I do not know what they write in the description, and for whom. But the logs to give back drone and 900 MHz in them no where. Description, and the reality is different.

 

[Tirex]

In general, under this program, which replaces files scripts their Magic Power v5.2. Nowhere today I did not go to fly, because last night decided to fix the BO region, in the US. Fixed so that had to fluster the USB console - UART and telnet right handle, then he changed his well-handled.In general, I report, so that those who will follow in my footsteps, so did not. First, I changed in watchlog.sh files, watchlog2.sh that lie in the directory, BO in the US, the author of a program offered the same. And then began dancing with a tambourine include copter includes control 3-4 seconds and the connection is lost and no longer broadcast wifi on the remote. I found a pattern that if you include only the control, not to include the drone, the wifi not lost. As soon as the copter, all communication is lost. I have sinned in the script of the curve, it has decided to correct, corrected so that generally all went out. In general, I found that in the new version worked FCC US mode, it works, but with a 13 channel generally not friendly. If you put a scan from 1 to 13, then reaching the 13th, the relationship falls off. If forced to put 13 the same. The solution was found. Fixed file scan13.sh channel 11 and it worked. I found a pattern that if you include only the control, not to include the drone, the wifi not lost. As soon as the copter, all communication is lost. I have sinned in the script of the curve, it has decided to correct, corrected so that generally all went out. In general, I found that in the new version worked FCC US mode, it works, but with a 13 channel generally not friendly. If you put a scan from 1 to 13, then reaching the 13th, the relationship falls off. If forced to put 13 the same. The solution was found. Fixed file scan13.sh channel 11 and it worked. Bottom line, it works fine with 1.7.9 But downloading 5.2, go to File 2 watchlog.sh expose in the REG = "US" save in file scan13.sh, watchlog.sh -ch13, put -ch11. And you can use the prog. But do not use Auto Scan channels or place anything on the channel change or check the channel, only 13 (he turns 11), so then do not sit with a tambourine, like me. Good luck to all.

 

[sunkyu]

In general, under this program, which replaces files scripts their Magic Power v5.2. Nowhere today I did not go to fly, because last night decided to fix the BO region, in the US. Fixed so that had to fluster the USB console - UART and telnet right handle, then he changed his well-handled.In general, I report, so that those who will follow in my footsteps, so did not. First, I changed in watchlog.sh files, watchlog2.sh that lie in the directory, BO in the US, the author of a program offered the same. And then began dancing with a tambourine include copter includes control 3-4 seconds and the connection is lost and no longer broadcast wifi on the remote. I found a pattern that if you include only the control, not to include the drone, the wifi not lost. As soon as the copter, all communication is lost. I have sinned in the script of the curve, it has decided to correct, corrected so that generally all went out. In general, I found that in the new version worked FCC US mode, it works, but with a 13 channel generally not friendly. If you put a scan from 1 to 13, then reaching the 13th, the relationship falls off. If forced to put 13 the same. The solution was found. Fixed file scan13.sh channel 11 and it worked. I found a pattern that if you include only the control, not to include the drone, the wifi not lost. As soon as the copter, all communication is lost. I have sinned in the script of the curve, it has decided to correct, corrected so that generally all went out. In general, I found that in the new version worked FCC US mode, it works, but with a 13 channel generally not friendly. If you put a scan from 1 to 13, then reaching the 13th, the relationship falls off. If forced to put 13 the same. The solution was found. Fixed file scan13.sh channel 11 and it worked. Bottom line, it works fine with 1.7.9 But downloading 5.2, go to File 2 watchlog.sh expose in the REG = "US" save in file scan13.sh, watchlog.sh -ch13, put -ch11. And you can use the prog. But do not use Auto Scan channels or place anything on the channel change or check the channel, only 13 (he turns 11), so then do not sit with a tambourine, like me. Good luck to all.

US use 1~12 wifi channel. So, If you set reg US, you have trouble in connecting 13 wifi channel. It is reason that we set reg BO( BO use all wifi channel 1~13)

 

[Tirex]

US use 1~12 wifi channel. So, If you set reg US, you have trouble in connecting 13 wifi channel. It is reason that we set reg BO( BO use all wifi channel 1~13)

This is all great, but for some reason it is important which channel 2.4., And the range is not important in terms of interference. If you have a technical
education, you need to understand. what a narrow bandwidth. In the BO, at 5.8 Ghz, it is narrow, that if any interference, control will be lost and the range correspondingly decrease.

I suggest the author to the program in the interface of choice in the region and 5.3 that if choose US, then it is impossible to set channel scan and channel only 13. But it is possible to put any other channel by entering the number in the space provided okoshoke. And then the program will be Super

 

[PapaTita]

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)

country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

I do not see any difference.
1. RC Operating frequency is 5735 - 5835 with maximum allowed transmission power (EIRP) in this country is 30 dBm, this value does not mean in RC must be that.
2. Its in bold in the US Country, is that the 60 GHz band?

 

[Tirex]

I do not see any difference.
1. RC Operating frequency is 5735 - 5835 with maximum allowed transmission power (EIRP) in this country is 30 dBm, this value does not mean in RC must be that.
2. Its in bold in the US Country, is that the 60 GHz band?

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)


The frequency range for control in Japan 5735 - 5835 Mhz with the channel width 80 Mhz is 30 dBm

country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

The frequency range for control in US 5170 - 5250 Mhz, with the channel width 80 Mhz, 17 dBm.
The frequency range for control in US 5250 - 5330 Mhz, with the channel width 80 Mhz, 23 dBm
The frequency range for control in US 5735 - 5835 Mhz, with the channel width 80 Mhz, 30 dBm

There are strange in my opinion group.

Why does he need not clear to me, because with increasing frequency, the wavelength is divided by 2, the signal range distance decreases. 57240 - 63720 Mhz with the channel width 2160 Mhz.

But the difference is visible between Japan and America in frequency and channel width. I quency amplifier 1w in the remote at 5.8 Ghz, and Antennas Itelite, this to me is not very important power of the transmitter in the remote, and the important frequency and width of the channel, because if this control frequency with a narrow channel would be a hindrance, then lost control. I tested one and the same BO and US conditions. Us, proved to be a stable.

 

[sunkyu]

country BO: DFS-JP
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)


The frequency range for control in Japan 5735 - 5835 Mhz with the channel width 80 Mhz is 30 dBm

country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

The frequency range for control in US 5170 - 5250 Mhz, with the channel width 80 Mhz, 17 dBm.
The frequency range for control in US 5250 - 5330 Mhz, with the channel width 80 Mhz, 23 dBm
The frequency range for control in US 5735 - 5835 Mhz, with the channel width 80 Mhz, 30 dBm

There are strange in my opinion group.

Why does he need not clear to me, because with increasing frequency, the wavelength is divided by 2, the signal range distance decreases. 57240 - 63720 Mhz with the channel width 2160 Mhz.

But the difference is visible between Japan and America in frequency and channel width. I quency amplifier 1w in the remote at 5.8 Ghz, and Antennas Itelite, this to me is not very important power of the transmitter in the remote, and the important frequency and width of the channel, because if this control frequency with a narrow channel would be a hindrance, then lost control. I tested one and the same BO and US conditions. Us, proved to be a stable.

I know that P3S only use 2.4g wifi(not 5.8g wifi) frequency for video. RC 5.8 ghz don't use wifi module chip. There is another chip for modulation of RC 5.8ghz. RC 5.8 didn't depend on wifi module.