
-----------------------------------------------------------------------
ph3pns.zip

Hi old post I know but hoping to get an answer.If the camera has been sitting for quite a while, the P3P gimbal board has a history of loosing the memory in the nand chip. It will need to be re-flashed.
hi, your problem is too common on this thread if u have the skills and a solder iron an ftr32 so guys here will help u help your self , if u dont have any technical knowledge then u need direct help from dji repair shopHi old post I know but hoping to get an answer.
I lost video feed followed a stalled firmware update, no cooling fan used. Was advised I likely damaged the gimbal board.
I don’t see a replacement around to buy is anybody repairing or flashing the boards ?
Thanks
Barry
You need to look earlier, at kernel boot. You will notice there are two copies of kernel. The primary kernel did not booted - only recovery kernel was able to boot.The console log file shows a strange error which I couldn't find on any of the forums. Here is the log: DaVinci Start GetFPGAStatus Err! - Pastebin
The strange error for me is this:
GetFPGAstatus err! FPGA[1,0,1,0]-1.000000:0 hdmi status is 1 ARM Load: 6% Video fps: 7 fps Video bit rate: 0 kbps PHY Bandwidth: 0 kbps Time: 00:00:10 Resolution: 1280x720
Consegui resolver amigo ?sim, várias vezes, parece estar vinculado ok, apenas sem exibição ao vivo e a mensagem NITS
help please? help please, I don't know what to doNovos links
yadisk
https://yadi.sk/d/KncyzdaO3N2X5B
gdrive
PH3P_NoSignal - Google Drive
Dropbox
Dropbox - ph3pns.zip
help pleaseBem, SunsetCatcher devo muito obrigado a você! Eu tinha uma placa-mãe gimbal P3 Pro antiga com o temido "Dispositivo 08 e 15 não encontrado" mensagem de erro e decidi tentar este método. Soldei meu módulo FTDI de acordo com suas instruções (Boot0 e Boot1 no Gimbal para 3,3V no Gimbal; 5V no FTDI para 5V no Gimbal; Ground no Gimbal para Ground no FTDI; TX no FTDI para 368_U0_RXP no Gimbal; RX no FTDI para 368_U0_TXP no Gimbal; defina o jumper FTDI para lógica de 3,3V). Confirmei que 3,3 V estava presente no cardan com um multímetro e depois conectei-o ao computador. Defina o diretório CMD como C:\ph3pns e siga o tutorial e tudo correu bem. Reconectei a placa-mãe ao drone e pronto! Transmissão de imagem restaurada! OBRIGADO!
como você fez isso?Sim, isso era necessário, fiz isso ontem e agora posso ligar os motores, mas ainda não há transmissão ao vivo e a mensagem NITS
i hope u can help in this "> help please? help please, I don't know what to do
I think every instruction mentions this problem. I even updated mine to make it more clear:
![]()
dji-technical-stuff/davinci-manual-flash-firmware-in-gl300-rc.md at main · quaddama9e/dji-technical-stuff
Technical details and howtos about DJI drones. Contribute to quaddama9e/dji-technical-stuff development by creating an account on GitHub.github.com
For the future, if the issue you're having seem linked to a specific message on screen, it may be a good idea to ask your favorite search engine that message.
my objective is to remove the drone id of the phantom3 that it sends to dji aeroscope .
what is the fw that is considered old???Just use the old firmware which does not send any additional packets.
Ph3 was not originally designed with Aeroscope in mind, that was added via one of last FW updates.
On old FW, Aeroscope will be able to tell only that there's Ph3 class drone in range somewhere.
We use essential cookies to make this site work, and optional cookies to enhance your experience.