Phantom 3 Standard range mod , let's do it together...

@ PapaTita

just update again with '27 dbm rc only" with or without "scan channel', individual options (rc & drone) should not be used.

Was it a bug in version 3.3 that is fixed in v3.4 or it is still unsafe to use "Patch to FCC - RC and Drone" in your updated v3.4?

And thank you for this nice tool.
 
Ok "can use the power up to 27 and channel 13"
can i choose 27dBm manually or is it just 27? and channel 13 is also automatic selection
Sorry for my english
No, there are only two choices: 27 dBm or 20 dBm, unless you change watchlog.sh file
Scan channel automatically selects an empty channel (start number 13 to 1).

@ PapaTita
Was it a bug in version 3.3 that is fixed in v3.4 or it is still unsafe to use "Patch to FCC - RC and Drone" in your updated v3.4?

And thank you for this nice tool.
Still not safe and i have not had time to test fly again.
 
No, there are only two choices: 27 dBm or 20 dBm, unless you change watchlog.sh file
Scan channel automatically selects an empty channel (start number 13 to 1).


Still not safe and i have not had time to test fly again.

OMG still not safe?
the working patch only the RECOMMENDED setting? am i right?
 
No risks of bricks with the last update and the recommended way ?
 
Sorry for off topic but how can i check my Tx-Power is it 17or 27 because i get 1400m in EU without any mods with lichi app.
 
Sorry for off topic but how can i check my Tx-Power is it 17or 27 because i get 1400m in EU without any mods with lichi app.
You can the FTP method to enable telnet in /etc/init.d/rcS file.
There is a "telnetd" line with # upfront, remove the #.
After reboot you can telnet, check your power with iwinfo command.
 
You can the FTP method to enable telnet in /etc/init.d/rcS file.
There is a "telnetd" line with # upfront, remove the #.
After reboot you can telnet, check your power with iwinfo command.

Or you can check /tmp/var/log to see whether you are in FCC or ETSI (CE)
This will not give you exact power however.
 
You can the FTP method to enable telnet in /etc/init.d/rcS file.
There is a "telnetd" line with # upfront, remove the #.
After reboot you can telnet, check your power with iwinfo command.

I believe adding the telnet line into /sbin/djileds.sh is safer as if you get modifying the rcS file wrong then you can brick your device.


Sent from my iPad using Tapatalk
 
Hi PapaTita, is the revert back to 17dbm now safe? Thank you!
Revert to CE is safe.

No risks of bricks with the last update and the recommended way ?
Many are using this application and there are no reports of brick.

On the "Patch to FCC RC & Drone" script watchlog.sh work independently.
Not recomended, because when test last week happen "lost connection", remote can no longer connect to the drone until it restarted (live streaming off), I think this may be a different regulatory domain between the remote and drones.

This just my assumption, this weekend I try to change the script and test again.

You can the FTP method to enable telnet in /etc/init.d/rcS file.
There is a "telnetd" line with # upfront, remove the #.
After reboot you can telnet, check your power with iwinfo command.
Hope you (+Donis) do this correctly (don't use notepad!!)
 
Last edited:
  • Like
Reactions: Andi HaK
i did, they scramble the traffic

#appologies wrong reply..someone inbox asking can apsvr tobe sniffing but why i'm typing here :lol

That's not scrambled. It's a protocol.
You have a start byte of 55 followed by message lenght then 04 and the message and 2 byte checksum at the end.
If you look at it in hexeditor and tidy up a bit then you'll get something that will start make sense :

551a 04 b10e02 f50e 0006 0500040004000400040004000700 2baf
551a 04 b10e02 f60e 0006 0500040004000400040004000001 92f2
551a 04 b10e02 f70e 0006 0500040004000400040004000001 750a
5512 04 c70e02 f80e 0006 1e6210000064 cfc0
551a 04 b10e02 f90e 0006 0500040004000400040004000700 cbab
551a 04 b10e02 fa0e 0006 0500040004000400040004000001 72f6
551a 04 b10e02 fb0e 0006 0500040004000400040004000001 950e
551a 04 b10e02 fc0e 0006 0500040004000400040004000001 02f4

Byte 7 in each message is the message counter, notice how it goes up from F5 to FC in these few lines

BTW these two messages/commands set the drone and remote to FCC mode :
550f 04 a20e02 5300 c006360000 b85e
550f 04 a20e02 5400 c006340032 893e
 
Last edited:
Ojcze Nasz, is there a way to explane me, WHY the patching only gives 70/70 on 2.4ghz ?

dont we need 5.8ghz to gain?? i did all the progress and all are fine. but i newer see 5.8ghz that shows a better performance.

i think 5.8ghz needs to be tweaked on full capacity. do you know how ?

Thanks.

5.8Ghz is a separate circuit. I recently got all necessary info including specs for power amp.
All I need is some help gettting the meter. It would really speed up things : Help buy RF meter
Thanks
 
  • Like
Reactions: jeganx
Hi Everyone,

I am looking for urgent help as I am travelling with my Phantom 3 through Australia. Initially I had the problem that I had a very weak signal which lead me to the hack above. Unfortunately I rebooted the remote control (RC) before applying the change to the drone as well. After rebooting the RC the wifi doesn't appear anymore.

Is there anyway to flash the firmware of the RC (P3 Standard not Professional!) or maybe get access via USB the filesystem of the RC so that I can change the /etc/init.d./rcS file?

Thanks for your help in advanced.

Marcel

#!/bin/sh

# This script runs when init it run during the boot process.
# Mounts everything in the fstab

mount -o remount +w /
mount -t tmpfs mdev /dev
mkdir -p /dev/pts
mount -t devpts devpts /dev/pts
mount -t sysfs sysfs /sys
mount -t proc proc /proc
mount -t tmpfs tmpfs /tmp
echo /sbin/mdev > /proc/sys/kernel/hotplug
mdev -s

mknod /dev/caldata b 31 6
mount -t debugfs none /sys/kernel/debug
mkdir /var/run
mkdir /var/lock
mkdir /var/log
/sbin/klogd
/sbin/syslogd

insmod /lib/modules/3.10.49/compat.ko
insmod /lib/modules/3.10.49/crypto_blkcipher.ko
insmod /lib/modules/3.10.49/crc-ccitt.ko
insmod /lib/modules/3.10.49/arc4.ko
insmod /lib/modules/3.10.49/cfg80211.ko
insmod /lib/modules/3.10.49/mac80211.ko
insmod /lib/modules/3.10.49/ath.ko
country=`fw_printenv -n country`
if [ $country = “OK” ];then
insmod /lib/modules/3.10.49/ath9k_hw.ko cert_country=1
else
insmod /lib/modules/3.10.49/ath9k_hw.ko
fi
insmod /lib/modules/3.10.49/ath9k_common.ko
insmod /lib/modules/3.10.49/ath9k.ko

echo dji > /proc/sys/kernel/hostname
/etc/init.d/sysfixtime boot

iw dev wlan0 del
#iw phy phy0 set antenna all all
iw phy phy0 set antenna_gain 0
iw phy phy0 set distance 0
iw phy phy0 interface add wlan0 type managed

ifconfig wlan0 up

brctl addbr br-lan
ifconfig br-lan 192.168.1.1 netmask 255.255.255.0 up
dwifi ap start
apsrv &

ifconfig usb0 hw ether 60:60:1f:ff:ff:ff up
brctl addif br-lan usb0
brctl addif br-lan wlan0

ifconfig lo 127.0.0.1 up
/usr/sbin/udhcpd -S /etc/udhcpd.conf &
#telnetd -l /bin/ash &
mkdir -m 0755 -p /var/run/vsftpd
/usr/sbin/vsftpd &
djiled.sh &

iw phy phy0 set retry short 1 long 1
iw phy phy0 set rts off
iw phy phy0 set frag 256
iw dev wlan0 set noack_map 0x00c0

iw reg set US
iw dev wlan0 set txpower limit 2700
 
Guys, I highly recommend you don't try this as it looks like my remote is buggered. I followed the tutorial step by step. When I saved the file back to the remote I lost the PHANTOM_XXXX wifi network. Its not showing up on any device in my house. I have tried the gimble/s2 button combination to reset the wifi but no good.
If anyone has a way to access the remote via the cable you use the charge the remote it would be great.
Any other suggestions would be much appreciated.

Hi Shrek,

I have done the same. Any luck so far to get your remote back to life?

Cheers,
Marcel
 

Members online

No members online now.

Forum statistics

Threads
143,099
Messages
1,467,631
Members
104,984
Latest member
akinproplumbing