-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semi-permanent FCC mode #4
Comments
Hello. How do you measure? |
By my homemade RF power meter. (In order:: TX antenna RC - gap 14cm - RX antenna of power meter.) |
Dear edyno |
I think the problem is persistence. The FS looks writable but changes are not persisted across restarts. If you |
Any progress to this? |
Yeah. On russian 4pda this permanent hack confirmed, seems. |
Does someone has checked real output power? Thanks. |
Hello friend.
I have an idea how to make semi-pernament FCC mode. However, since I have very little Linux knowledge, maybe you can help me.
I found by measuring the TX power and testing the RC that if I change the "country = ??" to "country = US" in the "/etc/amt/wifi.conf" file, RC always switches AC to FCC mode. Of course, if I connect the apk before turning on the engines, the apk will change FCC mode back to CE mode.
The solution would be to write the code :: "sed -i 's/country=../country=US/' /etc/amt/wifi.conf" somewhere in the code after the RC is booting.
This cause that each time the RC is switched on, it always switches to FCC mode. And if we connect the apk after starting the engines, the FCC mode does not change back to CE mode.
Note: Using the "disable_country=1" switch will permanently switch to FCC mode, but with a lower TX power than using "country = US" or fake gps.
Measured TX power (not totally exact) ::
CE mode ~ 2 dB (country = SK)
FCC mode ~ 18 dB (country = US)
disable_country=1 ~ 10 dB (country = ZZ)
Mavic Mini FCC, firmware:: .300, apk DJI fly version 1.1.2
The text was updated successfully, but these errors were encountered: