FangsCPO said:
RiNkY said:
During the upgrade, make sure you also import the Phantom Configuration Perimeters from:
http://www.dji.com/download/phantom-downloads/
Then import them in the 'Tools' tab. The only way I could get my Phantom into Calibration mode was to actually put a magnet nearby so the Compass Mod value was high enough to clear the Error [27] Error, after which I was able to toggle the switch and get into Compass Calibration mode.
Not flown yet after the upgrade.
So if you haven't flown it since the upgrade how can you feel confortable providing advice. You don't even know if its actually going to work. Not a risk I would be willing to take with someone else's Phantom. Not a good practice if you ask me.
The only 'advice' RiNkY offered was to import the parameter file, which is DJI's recommendation as well. I for one appreciated the info and the inclusion of the all-important caveat "Not flown yet after the upgrade." No one is asking anyone to take risks, we're each the pilots of our own craft.
I would suggest that before putting magnets by the compass, one should carefully watch DJI's video on resetting the Phantom compass using an external magnet when compass calibration fails (
http://www.youtube.com/watch?v=Vo7Kf3uo93I). As I recall, it involves exposing the compass to successive semi random external magnet movements while monitoring the compass Mod values on the Assistant SW. The goal is to get the compass Mod value from 1400-1800 so that the error can then be compensated by the normal compass calibration process. This is different from just holding a magnet nearby to pass the initial error check, but perhaps not reducing the actual compass error. From reports on adverse consequences of potential or actual compass errors, I would be certainly advise making sure compass calibration is successful before flight testing.
At the risk of contributing more 'not yet flown' information, I completed the install of the Phantom upgrade board for the Zenmuse H3-2D. Some observations that might be of some interest:
The board upgrade procedure is fairly straight-forward and the result is much cleaner in 'appearance' than the previous option with PMU v2 and separate GCU. The upgrade board weighs less than 10 g more than the original (33 g vs. 24 g), so the overall savings in wt is non-trivial since the metal-encased PMU and CGU are not needed (maybe 60-70 g savings, can't remember for sure).
Some observations that might be of some interest: The board I received is actually slightly different in layout than the one pictured in DJI's manual. Specifically, the 'left' edge (as viewed from the front of the craft) by the battery leads has been trimmed several mm providing more clearance from the Phantom shell. The cable lengths are 'exactly right' so pay careful attention to layout. I added some extra solder to the V (VCC) and G (GRND) pads for the ESC wires before attaching the wires. Removing the NAZA from the original board required some persuasion, that 3M adhesive works quite well.
Can't personally comment yet on functionality, except to say the NAZA booted, the new LED board displayed normally and got to GPS lock with no issues.
Steve
PS: Remember the number one rule of multirotor flight - YMMV...
