Posting

3 pengikut Ikuti
0
Avatar

Linear Mission - Image Orientation

 I'm capturing about 45km of pipeline for a client using MP and seems to be working pretty well. One issue I noticed this morning when reviewing a section of images is that the image orientation doesn't appear to be at 90 degrees to the track of the drone, more like 45 degrees. Any ides why this would be? M210 and X4S Nadir?

 

Aaron Emmett

Komentar resmi

Avatar

The gimbal should be pointing nadir regardless of the aircraft speed or wind. That is its job. Now, if you accidentally hit the dial and it went up some it would stay there for the rest of the flight. You can look at the values in your log file. If they say 90 for the camera tilt and the images say otherwise you likely have a hardware issue on your hands. 

There is an issue in 2.8.3 with the M210 and X4S camera with the gimbal. We have addressed the issue and submitted version 2.8.4 that has the fix. That could also be the issue. 

Zane
Tindakan komentar Permalink

Harap masuk untuk memberikan komentar.

6 komentar

0
Avatar

The software does not account for wind.  It will fly the track as best as it can but depending on the wind, it may be in a crab (skewed into the wind).

Dave Pitman 0 suara
Tindakan komentar Permalink
0
Avatar

Yep so I’m on site now and just ran another couple of kms. The issue isn’t the nadir orientation, it’s the image footprint that is skewed somewhere between landscape and portrait each flight. My work around is to now pause it at the start, manually correct image orientation by slewing the gimbal until it’s near landscape and continue.

Aaron Emmett 0 suara
Tindakan komentar Permalink
0
Avatar

Another user pointed out that if you rotate the aircraft to fly the entire path backwards it apparently doesn't do it. We haven't verified that this is the case. Also, we don't recommend mixing data that was taken while flying forwards and backwards.

Another alternative would be to purchase the Business version of the app which has not gotten the latest DJI SDK update and will work as previous versions did because it is still on version 2.8.1. Just a thought.

Zane 0 suara
Tindakan komentar Permalink
0
Avatar

Thanks Zane, not too critical as I’m only mapping the linear corridor for a 375mm pipeline and only for an ortho so elevation and other data are not an issue, have had good success stitching even with just a single run and high fwd overlap. The workaround is fine now I know about and hopefully once the new version is approved it’s sorts this. Thanks for the quick reply

Aaron Emmett 0 suara
Tindakan komentar Permalink