Phantom 2 Vision+ Camera startup advice

Joined
Feb 8, 2022
Messages
9
Reaction score
0
Age
49
First time posting so Hi everyone and new owner here

I bought a second hand Phantom 2 Vision+ to teach myself to fly a drone, and the drone has problems with it's camera where it refuses to connect from the Vision + app (even though I can bind with the MAC address of the WiFi board) and doesn't do the correct camera startup-up centring pattern on startup

I've attached a video below, but as you can see it does move the camera part of the assembly, but the top rotation board doesn't move and it seems to fail initialisation and then give up

In the box came two spare top rotation boards (the big circuit board with the silver case and gimbal shock mounts on it) so I wonder if first advice would be to try replacing that and see if it initialises any better?

Any thoughts welcome and thanks in advance

Judder

 
Joined
Feb 8, 2022
Messages
9
Reaction score
0
Age
49
And a bit more information - when I tested the two top gimbal motor boards on their own connected to the drone they both came on with a solid red light, and the motor ran continuously

They look like this :)

Out of interest what does the small silver button do - reset button?

IMG20220208154943.jpg
 
Joined
Jun 2, 2014
Messages
240
Reaction score
74
Age
76
If the drone has been in storage for awhile, the P2V+ has an inharent issue with the wfi module, (inside the drone body). The NAND chip kernels quit booting up. This creates a loss of wifi signal & thus video. There are several sources for "reflashing" the wifi module. BTW, I don't recommend connecting the upper main board all by itself to see if the yaw motors work. There is way more to it than just having the motor spin. The button on the plate is a "capture" button for taking stills. The gimbal issue at start-up is more than likely bad gimbal motor(s).
 
Joined
Feb 8, 2022
Messages
9
Reaction score
0
Age
49
Thanks - good tips there and much appreciated!

FYI the first thing I did was disassemble the WiFi board and soldered on a USB serial connector and reflashed that - so that's one net positive job done 👍

On the gimbal boot-up issues, one other suggestion I got from another member was to replace the ribbon cable that joins it all together, but it does sound easier to get a couple of spare motors and try those first.

Ribbon cable changing if I have to do it doesn't look too daunting, and I might, as a first step, try opening the existing gimbal motherboard, disconnecting the gimbal cable and ball-bearing and try swapping in one of the other motherboards just to see if the gimbal boot up sequence is the same

Does that sensible or would you go with the motors first?

Many thanks Alex
 
Joined
Oct 25, 2021
Messages
5
Reaction score
1
Age
64
If the drone has been in storage for awhile, the P2V+ has an inharent issue with the wfi module, (inside the drone body). The NAND chip kernels quit booting up. This creates a loss of wifi signal & thus video. There are several sources for "reflashing" the wifi module. BTW, I don't recommend connecting the upper main board all by itself to see if the yaw motors work. There is way more to it than just having the motor spin. The button on the plate is a "capture" button for taking stills. The gimbal issue at start-up is more than likely bad gimbal motor(s).
 
  • Like
Reactions: jiminyfixit
Joined
Oct 25, 2021
Messages
5
Reaction score
1
Age
64
I have a P2vt
If the drone has been in storage for awhile, the P2V+ has an inharent issue with the wfi module, (inside the drone body). The NAND chip kernels quit booting up. This creates a loss of wifi signal & thus video. There are several sources for "reflashing" the wifi module. BTW, I don't recommend connecting the upper main board all by itself to see if the yaw motors work. There is way more to it than just having the motor spin. The button on the plate is a "capture" button for taking stills. The gimbal issue at start-up is more than likely bad gimbal motor(s).
 
Joined
Oct 25, 2021
Messages
5
Reaction score
1
Age
64
I have a P2V+ I have control of the camera up down turn but no video or still I flashed the board as the guy from Flymy phantom shows in his video. I can't get it to bind Any Suggestions. Thank You Robert from Canada Email me please tr[email protected]
 
Joined
Feb 8, 2022
Messages
9
Reaction score
0
Age
49
I have a P2V+ I have control of the camera up down turn but no video or still I flashed the board as the guy from Flymy phantom shows in his video. I can't get it to bind Any Suggestions. Thank You Robert from Canada Email me please [email protected]
If you have the WiFi board now booting correctly then it should bind OK when powered up if everything is connected correctly. Binding is pretty hit and miss but if you reboot everything (phone included) then this seems to be the most likely way for it to work from my tests

I've included below the output when the NAND chip kernels fail, as well as what it should look like when it is successfully reflashed, just so you can compare if you have any logs of your output

Also as I was flashing a couple of PV2+ drones I bought some test probes from China via AliExpress which are 2.54mm pitch and perfect for touching the text pads so you don't need to solder wires there every time you do this


IMG20220307185032.jpg


IMG20220307185730.jpg



Not working:

Code:
····ˇ····ˇ···DM36x initialization passed!
UBL Product Vesion : DJI-UBL-1.0-rc2
Dji UBL Version: 1.51(Jan 24 2014 - 04:27:19)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Valid magicnum, 0xA1ACED66, found in block 0x0000001B.
Valid magicnum, 0xA1ACED66, found in block 0x0000001D.
Valid magicnum, 0xA1ACED66, found in block 0x0000001F.
No valid boot image found!
NAND Boot failed.
Aborting...

Working:

Code:
DM36x initialization passed!
UBL Product Vesion : DJI-GSP-UBL-1.0-rc10(2014-08-15)
Dji UBL Version: 1.51(Aug 15 2014 - 17:05:12)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Uboot Checksum:0x7E25B44B
Actua Checksum:0x7E25B44B

U-Boot Product Vesion : DJI-GSP-Uboot-1.0-rc4(2014-07-23)
U-Boot 2010.12-rc2-svn-Dji (Jul 23 2014 - 11:14:40)
Cores: ARM 432 MHz
DDR:   297 MHz
I2C:   ready
DRAM:  128 MiB
NAND:  128 MiB
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000000140000
*** Warning - bad CRC, using default environment

1½Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2014-04-09  12:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3823424 Bytes = 3.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Kernel Product Vesion : DJI-Kernel-1.0-rc2
[    0.000000] Linux version 2.6.32.17-davinci1 ([email protected]) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #6 PREEMPT Wed Apr 9 05:21:55 PDT 2014
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: DaVinci DM36x EVM
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] DaVinci dm36x_rev1.2 variant 0x8
[    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 12192
[    0.000000] Kernel command line: console=ttyS0,115200n8 rw dm365_imp.oper_mode=0 video=davincifb:vid0=0,10K:vid1=0,10K:osd0=1920x1080X16,8100K mem=48MB davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs ip=off lpj=1077248
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 48MB = 48MB total
[    0.000000] Memory: 44784KB available (3456K code, 310K data, 112K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:245
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop (skipped) preset value.. 215.44 BogoMIPS (lpj=1077248)
[    0.000000] Mount-cache hash table entries: 512
[    0.000000] CPU: Testing write buffer coherency: ok
[    0.000000] DaVinci: 8 gpio irqs
[    0.000000] NET: Registered protocol family 16
[    0.070000] EVM: tvp5146 SD video input
[    0.130000] bio: create slab <bio-0> at 0
[    0.130000] DM365 IPIPE initialized in Continuous mode
[    0.140000] usbcore: registered new interface driver usbfs
[    0.140000] usbcore: registered new interface driver hub
[    0.140000] usbcore: registered new device driver usb
[    0.140000] vpss vpss: dm365_vpss vpss probed
[    0.140000] vpss vpss: dm365_vpss vpss probe success
[    0.140000] dm365_afew_hw_init
[    0.150000] ch0 default output "COMPOSITE", mode "PAL"
[    0.150000] VPBE Encoder Initialized
[    0.150000] cfg80211: Using static regulatory domain info
[    0.150000] cfg80211: Regulatory domain: US
[    0.150000]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    0.150000]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[    0.150000]     (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.150000]     (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.150000]     (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.150000]     (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.150000]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    0.150000] cfg80211: Calling CRDA for country: US
[    0.150000] LogicPD encoder initialized
[    0.150000] Switching to clocksource timer0_1
[    0.160000] musb_hdrc: version 6.0, cppi-dma, host, debug=0
[    0.180000] musb_hdrc: USB Host mode controller at fec64000 using DMA, IRQ 12
[    0.180000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[    0.180000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[    0.180000] usb usb1: configuration #1 chosen from 1 choice
[    0.180000] hub 1-0:1.0: USB hub found
[    0.180000] hub 1-0:1.0: 1 port detected
[    0.180000] NET: Registered protocol family 2
[    0.180000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.180000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.180000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.180000] TCP: Hash tables configured (established 2048 bind 2048)
[    0.180000] TCP reno registered
[    0.180000] NET: Registered protocol family 1
[    0.180000] RPC: Registered udp transport module.
[    0.180000] RPC: Registered tcp transport module.
[    0.180000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.190000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.190000] msgmni has been set to 87
[    0.200000] alg: No test for stdrng (krng)
[    0.200000] io scheduler noop registered (default)
[    0.240000] davincifb davincifb.0: dm_osd0_fb: Initial window configuration is invalid.
[    0.320000] Console: switching to colour frame buffer device 240x67
[    0.410000] davincifb davincifb.0: dm_osd0_fb: [email protected],0 with framebuffer size 8100KB
[    0.410000] davincifb davincifb.0: dm_vid0_fb: [email protected],0 with framebuffer size 10KB
[    0.410000] davincifb davincifb.0: dm_osd1_fb: [email protected],0 with framebuffer size 810KB
[    0.420000] davincifb davincifb.0: dm_vid1_fb: [email protected],0 with framebuffer size 10KB
[    0.480000] DM365 IPIPEIF probed
[    0.480000] imp serializer initialized
[    0.480000] davinci_previewer initialized
[    0.490000] davinci_resizer initialized
[    0.490000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.490000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[    0.950000] console [ttyS0] enabled
[    0.950000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[    0.960000] brd: module loaded
[    0.970000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[    0.980000] Creating 4 MTD partitions on "davinci_nand.0":
[    0.980000] 0x000000000000-0x0000004a0000 : "bootloader"
[    0.990000] 0x0000004a0000-0x000000e00000 : "kernel"
[    1.000000] 0x000000e00000-0x000007f00000 : "filesystem"
[    1.010000] 0x000000000000-0x000008000000 : "all"
[    1.020000] davinci_nand davinci_nand.0: controller rev. 2.3
 

New Threads

Members online

No members online now.

Forum statistics

Threads
141,961
Messages
1,459,596
Members
103,743
Latest member
Miatakoss