at 1920x1080, you are cropping the image from it's native 4K. Less effective pixels allow for the higher frame rateDid anyone notice the 120FPS video option in 1920x1080? I did a quick test and it looked good but does crop the image.
at 1920x1080, you are cropping the image from it's native 4K. Less effective pixels allow for the higher frame rateDid anyone notice the 120FPS video option in 1920x1080? I did a quick test and it looked good but does crop the image.
What are your Mod values for the compass, if they are within the acceptable range, then you can rule that out. Recalibrating won't assure you are calibrated... Only actually checking the values being in rangeFlown about 6 times and do a compass recalibrate every time at the pre-flight check because of the problem!
Is there anything else with regards to compass i can do? To get this sorted?
I think you are on the right track with your comment, but your language isn't specific enough for my tastes.at 1920x1080, you are cropping the image from it's native 4K. Less effective pixels allow for the higher frame rate
Can you point me to what they "should" be?What are your Mod values for the compass, if they are within the acceptable range, then you can rule that out. Recalibrating won't assure you are calibrated... Only actually checking the values being in range
I think you are on the right track with your comment, but your language isn't specific enough for my tastes.
First, let's look at the GH4 sensor, which has the same dimensions as the X5:
Note the magenta rectangle; this is the part of the sensor that the X5 uses when filming 1,920 x 1,080 at 24, 25, and 30 frames/second. It is 4,608 pixels by 2,592 pixels. The video processor samples this area of the sensor, combines the pixels into a 1,920 x 1,080 image (this is called "pixel-binning"), then sends that image to the H.264 compressor.
That works fine up to 30 frames/second, but the video processor simply can't do all of that at 120 frames/second. It doesn't have enough bandwidth to read that much data from the sensor 120 times/second, then pixel-bin the images into a 1,920 x 1,080 image, then compress that frame.
So instead, when filming at 120 frames/second, the camera does not sample the entire magenta (4,608 x 2,592) area of the sensor. Instead, it samples a much smaller area, 1,920 by 1,080 pixels, at the center of the sensor. It then does not have to do any pixel-binning, as the image is already the final size; it just sends the data to the H.264 compressor.
Two bad things happen as a result:
So while 120 frames/second is a nice feature, it's not very useful. And the compromises made in order to provide it are yet another example of how the underpowered video processor on the X5 is undermining what could and should be an incredible camera.
- Because fewer pixels on the sensor are used, the quality of the image is decreased significantly
- The field of view is narrowed dramatically.
So let me get this straight! We can't fly in P mode to get home in very windy days now? Not enough power?I would caution flying the new FW (1.6.0.40) in strong wind conditions. I was struggling to control mine today in 9-10m/s winds and almost experienced a flyaway. Despite turning into wind and applying full right stick forward I was not able to counter the wind drift in P-GPS mode. I had to reduce height and switch to ATTI to regain control. PS. Air temp was 9C.
I wonder if using FPV camera and Auto Flight Logic will bypass the new DJI restrictions such as reduced power and Cold batteries.
I wonder if using FPV camera and Auto Flight Logic will bypass the new DJI restrictions such as reduced power and Cold batteries.
If I set a new mission in Mission Zplanner for instance, will the Inspire have an issue in windy conditions now?
Funny thing is, I updated the cold weather update while vacationing in the hot tropical air of Cairns, Australia.I think it's Flight Controller-based, which would mean SDK or not, it's part of the new behavior.
For the record, I guess I'd rather be forced to land in a non-home position than have battery protection kick in and shutdown the aircraft mid flight.
After weighing those options, I've updated to 1.6. Sigh. Need to see what happens on cold weather flight testing now that winter is in the way in New England.
Ed & KilrahAs Kilrah says - DO NOT do a compass calibration before every flight. It is totally unnecessary and runs the risk of introducing errors.
Far more important is to check your mod values at rest immediately before each take off.
What are/were your mod values at this location?
1500ish seems low.. at least for the past couple of updates.. I remember earlier this year that 1400-1500 was spot on, but the last two, the sweet spot was 1600-1650.
ps.. I have not updated.
I always get between 1400 and 1600. Most times its about 1500. That's been true since I have owned my craft, and after all the updates. And unlike the Editor's suggestions, I always do a compass calibration. But that is a whole other issue that has been discussed in this forum at great length for months. And one last point, I always do an IMU calibration after every firmware update.