Punchbuggy
Second Officer
Flight distance : 483166 ft
Australia
Offline
|
UltraDan Posted at 2017-3-16 14:43
This gimball tilt issue is awful. Surely a class a ton lawsuit is on the cards? I mean they are selling products by the truckload that are faulty beyond repair?
Well, I don't have this issue to the extent the op has reported, so let's not be tempted to over-generalise. And I haven't noted a horizon leveling issue on my P4P since the latest update. My P4 still has the issue, but I've found if I do a 360 degree yaw left and let it hover for a couple of seconds, the gimbal will decide to correct itself - or you can correct the horizon level using C2 or the 'Adjust Gimbal roll' function in GO, of course.
The real question is why are the craft so variable? Some don't have this issue, some have it slightly, but others have it like the op. Why? With the P4P we did have an issue with some, where gimbal initialisation couldn't complete if the camera was caught on something (grass, ribbon cable, etc), and then perhaps any amount of gimbal correction after that would be ineffective? So many variables.
My best suggestion is to:
Place the P4P on a clean, flat surface next to PC;
Use Assistant 2 V1.1.0 to refresh the craft firmware to the latest level (but do that while the craft is cool - power up while app is waiting to connect, and start refresh immediately once the craft has finished initialising);
Do a VPS calibration; and then
Use GO to perform a gimbal calibration.
Prior to doing the latter, you could also reset to factory settings to be sure (although I need to remind myself how to do that). Oh, and I always update via PC, and not via app and RC, as with the PC it's a direct connection, while the RC and wifi introduces another link in the process.
[Edit] and I only do an IMU and/or compass calibration after upgrade if the app says it needs it. If it doesn't ask for it, I leave them alone (but I will check the sensor indicators are green in GO).
|
|