P3S - Maybe a paperweight?

Last edited:
  • Like
Reactions: amrth
Still wonder if the motors would start, I'm guessing yes?

That linked help me understand you quite clearly.. Now how can think I could get the motors to start?
I tried the manual way listed in the user manual.. it did not work..

All these conversion makes me take off from work and get the drone in front of me and ask more questions.. really appreciate all your support to get me through this..
 
Another item that I didn't think of at the time and from what @RodPad mentioned, the disconnect could also very well be a firmware mismatch between the RC and AC. You never mentioned anything about updating the RC. The versions must match. Not necessarily by number but by version. If what has been suggested does not correct your issue you may want to look in to that as well.
 
That linked help me understand you quite clearly.. Now how can think I could get the motors to start?
I tried the manual way listed in the user manual.. it did not work..

All these conversion makes me take off from work and get the drone in front of me and ask more questions.. really appreciate all your support to get me through this..
No, I was must be wrong, I don't have any answers, but I would like to know if the Phantom is red with remote turned off, otherwise that would really be weird. As you can tell now, changing firmware before you got it work, throws another twist of the what if's.

Is what it is,

Rod
 
Thanks @RodPad .......LOL

Holy Moley.gif
 
I just got home .. Getting all the data that might help.. At first here are the 2 screenshots of the application on the phone .. Will get the log file in a minute..
Screenshot_20180112-163111.png
Screenshot_20180112-163144.png
Screenshot_20180112-163111.png
 
Here is the log file ..
[00140217]========== remo-con disconnect. boot(15) ============
[00140344]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0x94f61056].
[00140382]Packet upgrade start...

[00140638]Packet checking...
[00140678]Packet vlink 01.09.0200 <-> 00.00.0000.
[00140767]Done.

[00140807]Version checking[1]...
[00140856][04 00][00] v1.51.0.0 -> v1.51.0.0
[00140974][11 00][00] v1.8.0.0 -> v1.8.0.0
[00141092][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00141129][11 01][00] v1.8.0.0 -> v2.0.0.33
[00141174][01 00][00] v1.14.4920 -> v1.14.4920
[00141213][01 01][00] v1.14.4920 -> v1.14.4920
[00141295][03 05][00] v34.2.0.9 -> v34.2.0.9
[00141393][03 06][00] v2.4.20.22 -> v2.4.20.50 need upgrade.
[00153936][07 00][00] device not detected.
[00153996][09 00][00] v0.1.0.9 -> v0.1.1.1 need upgrade.
[00154084][12 00][00] v5.9.0.0 -> v5.9.0.0
[00154185][12 01][00] v5.9.0.0 -> v5.9.0.0
[00154294][12 02][00] v5.9.0.0 -> v5.9.0.0
[00154401][12 03][00] v5.9.0.0 -> v5.9.0.0
[00154444]Done.

[00156483]Waiting for user confirm...
[00166521]Timeout, start upgrade automatically.

[00166600]Firmware upgrading[1]...
[00166870][03 06] Firmware upgrade start...
[00566346][03 06] Firmware upgrade finished successfully.
[00566402][09 00] Firmware upgrade start...
[00592261][09 00] Firmware upgrade finish without reboot.
[00622297][09 00] Firmware upgrade finished successfully.
[00622337]Done.

[00622376]Version checking[2]...
[00622420][04 00][00] v1.51.0.0 -> v1.51.0.0
[00622555][11 00][00] v1.8.0.0 -> v1.8.0.0
[00622675][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00622713][11 01][00] v1.8.0.0 -> v2.0.0.33
[00622752][01 00][00] v1.14.4920 -> v1.14.4920
[00622792][01 01][00] v1.14.4920 -> v1.14.4920
[00622870][03 05][00] v34.2.0.9 -> v34.2.0.9
[00622954][03 06][05] v2.4.20.50 -> v2.4.20.50
[00635499][07 00][00] device not detected.
[00635575][09 00][05] v0.1.1.1 -> v0.1.1.1
[00635655][12 00][00] v5.9.0.0 -> v5.9.0.0
[00635843][12 01][00] v5.9.0.0 -> v5.9.0.0
[00635920][12 02][00] v5.9.0.0 -> v5.9.0.0
[00636046][12 03][00] v5.9.0.0 -> v5.9.0.0
[00636086]Packet upgrade failed at version checking.



[00014156]========== remo-con disconnect. boot(15) ============
[00014197]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0x94f61056].
[00014238]Packet upgrade start...

[00014283]Packet checking...
[00014321]Packet vlink 01.09.0200 <-> 00.00.0000.
[00014397]Done.

[00014443]Version checking[1]...
[00014493][04 00][00] v1.51.0.0 -> v1.51.0.0
[00014621][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014740][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014780][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014821][01 00][00] v1.14.4920 -> v1.14.4920
[00014870][01 01][00] v1.14.4920 -> v1.14.4920
[00014942][03 05][00] v34.2.0.9 -> v34.2.0.9
[00015019][03 06][00] v2.4.20.50 -> v2.4.20.50
[00027559][07 00][00] device not detected.
[00027622][09 00][00] v0.1.1.1 -> v0.1.1.1
[00027705][12 00][00] v5.9.0.0 -> v5.9.0.0
[00027801][12 01][00] v5.9.0.0 -> v5.9.0.0
[00027890][12 02][00] v5.9.0.0 -> v5.9.0.0
[00027990][12 03][00] v5.9.0.0 -> v5.9.0.0
[00028029]Packet upgrade failed at version checking.



[00044161]========== remo-con disconnect. boot(15) ============
[00044202]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0x94f61056].
[00044245]Packet upgrade start...

[00044288]Packet checking...
[00044332]Packet vlink 01.09.0200 <-> 00.00.0000.
[00044412]Done.

[00044454]Version checking[1]...
[00044501][04 00][00] v1.51.0.0 -> v1.51.0.0
[00044733][11 00][00] v1.8.0.0 -> v1.8.0.0
[00044852][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00044892][11 01][00] v1.8.0.0 -> v2.0.0.33
[00044935][01 00][00] v1.14.4920 -> v1.14.4920
[00044978][01 01][00] v1.14.4920 -> v1.14.4920
[00045069][03 05][00] v34.2.0.9 -> v34.2.0.9
[00045153][03 06][00] v2.4.20.50 -> v2.4.20.50
[00057696][07 00][00] device not detected.
[00057770][09 00][00] v0.1.1.1 -> v0.1.1.1
[00057937][12 00][00] v5.9.0.0 -> v5.9.0.0
[00058033][12 01][00] v5.9.0.0 -> v5.9.0.0
[00058126][12 02][00] v5.9.0.0 -> v5.9.0.0
[00058222][12 03][00] v5.9.0.0 -> v5.9.0.0
[00058270]Packet upgrade failed at version checking.



[00014160]========== remo-con disconnect. boot(15) ============
[00014201]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0x94f61056].
[00014243]Packet upgrade start...

[00014289]Packet checking...
[00014329]Packet vlink 01.09.0200 <-> 00.00.0000.
[00014404]Done.

[00014452]Version checking[1]...
[00014500][04 00][00] v1.51.0.0 -> v1.51.0.0
[00014628][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014748][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014789][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014831][01 00][00] v1.14.4920 -> v1.14.4920
[00014879][01 01][00] v1.14.4920 -> v1.14.4920
[00014974][03 05][00] v34.2.0.9 -> v34.2.0.9
[00015056][03 06][00] v2.4.20.50 -> v2.4.20.50
[00027597][07 00][00] device not detected.
[00027659][09 00][00] v0.1.1.1 -> v0.1.1.1
[00027756][12 00][00] v5.9.0.0 -> v5.9.0.0
[00027840][12 01][00] v5.9.0.0 -> v5.9.0.0
[00027942][12 02][00] v5.9.0.0 -> v5.9.0.0
[00028037][12 03][00] v5.9.0.0 -> v5.9.0.0
[00028080]Packet upgrade failed at version checking.



[00062181]========== remo-con disconnect. boot(15) ============
[00062222]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0x94f61056].
[00062265]Packet upgrade start...

[00062312]Packet checking...
[00062357]Packet vlink 01.09.0200 <-> 00.00.0000.
[00062430]Done.

[00062468]Version checking[1]...
[00062516][04 00][00] v1.51.0.0 -> v1.51.0.0
[00062662][11 00][00] v1.8.0.0 -> v1.8.0.0
[00062785][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00062875][11 01][00] v1.8.0.0 -> v2.0.0.33
[00062917][01 00][00] v1.14.4920 -> v1.14.4920
[00062970][01 01][00] v1.14.4920 -> v1.14.4920
[00063039][03 05][00] v34.2.0.9 -> v34.2.0.9
[00063122][03 06][00] v2.4.20.50 -> v2.4.20.50
[00075760][07 00][00] device not detected.
[00075822][09 00][00] v0.1.1.1 -> v0.1.1.1
[00075906][12 00][00] v5.9.0.0 -> v5.9.0.0
[00076034][12 01][00] v5.9.0.0 -> v5.9.0.0
[00076131][12 02][00] v5.9.0.0 -> v5.9.0.0
[00076209][12 03][00] v5.9.0.0 -> v5.9.0.0
[00076249]Packet upgrade failed at version checking.
 
Not fare I'm still at work.
You also have Weak remote control signal in the middle top, but that might just be a generic message because you don't have telemetry.

You normaly have live feed, correct?

Sorry I don't have any knowledge of the log file on a P3S, I gave up on firmware updates when me bird got cooked the second time.

Rod
 
I'm stupidly trying to figure out where somebody stated that Telemetry and Live video is on two different WiFi channels, I just found where I stated it so it must have been before. Aug 10th 2016.

Phantom 3 Standard Range Issue is a Common Problem
Post #152

Rod
 
  • Like
Reactions: amrth
  • Like
Reactions: amrth
@Oso, @sar104,

Was one you guys good on these firmware log files, if not can you point him to who does?

Thanks..

Rod
 
  • Like
Reactions: amrth
[00027597][07 00][00] device not detected.
This is an issue. Not being fully confident on Module configurations, someone should know which this is.
 
This is an issue. Not being fully confident on Module configurations, someone should know which this is.
Thanks.. Even that's hit me when I saw this log.. But it's all alien to me..
I'm thinking is it the remote that might at fault.. Just wondering.. Tried a lot of combination last night to get it link.. Not successful..
 
I'm going to take a wag, and suggest that module [7] is on the gimbal. I have a partial listing of P3A/P modules, and I do not see a module 7 listed on those. However, being the fact that module [8] is on the gimbal on the P3A/P, and the fact that you had a gimbal issue to start with, I would suggest that you take a really close look at the ribbon cables, both inside and out. You could have a loose connection, severed wire, or an actual board problem. Checking the cables would be first.
 
  • Like
Reactions: amrth
I'm going to take a wag, and suggest that module [7] is on the gimbal. I have a partial listing of P3A/P modules, and I do not see a module 7 listed on those. However, being the fact that module [8] is on the gimbal on the P3A/P, and the fact that you had a gimbal issue to start with, I would suggest that you take a really close look at the ribbon cables, both inside and out. You could have a loose connection, severed wire, or an actual board problem. Checking the cables would be first.
That's a good guess and a good suggestion.

Several of the modules on the P3S match the P3A/P, but of course some don't for obvious reasons. For some reason, I seem to recall reading somewhere that module 7 on a P3S is the WIFI module as noted in this post. I admit however that I am not certain on that one as I only recently started reading the P3S forum. On the other hand, when I check this popular github site it skips module 7 as if it doesn't even exist.

FYI Dawg - here is a list of the P3A/P modules that I post and reference often on the forum.
 
  • Like
Reactions: JoBe and amrth
Hi all...

Friend, I've seen it happen with a Phantom 3 S and it may be your case. At the bottom of the motherboard there is an SD Card in a slot. This card is stuck in the slot Well glued right! To avoid being released during the flight, etc. Check if this card has not left the slot or if it is loose ... Or even it may have burned needing to be replaced.
 
  • Like
Reactions: amrth and RodPad
@renamaf
Welcome to the Forum!
I have know idea about your post, but I do think there is something intresting if the Phantom has to save / connect / wright to what I call the SD_BB.

Thanks for your thoughts.

Rod
 
  • Like
Reactions: amrth

Members online

No members online now.

Forum statistics

Threads
143,092
Messages
1,467,578
Members
104,976
Latest member
cgarner1