loved this video. shows people that everyone faces issues, thanks @uavisuals for keeping it in!
@beaurosario8358 Жыл бұрын
I have had nothing but trouble with the i3 and the RTK-2... Setting it up in the exact location over different days often results in ellipsoidal height differences up to 10m. The engineers keep telling me this is normal. But, the results are often so severely varied that the footage is not salvageable for "long-term timelapses" (the phrase they use in advertisements, etc.) Have you had similar issues?
@UAVISUALS Жыл бұрын
There definitely are a few key things to keep in mind when ensuring accurate repeatable missions over time with the RTK functionality: First ensure that the D-RTK 2 station is always setup in the EXACT same position every time you return to a location. Second ensure the RTK mode is set to Broadcast (Mode 5). Lastely ensure the base station is turned on first, and allow up to 15 minutes for it to calibrate it's location BEFORE turning on the drone & connecting it to RTK. That said, it is true that whilst the relative accuracy will be 1 - 2 cm, there still can be large errors for the absolute accuracy, From DJI's own communications, there can be a horizontal error of at least 1.5m horizontally and 3m vertically. The 10m ellipsoidal height difference you're is well above that so perhaps try the above suggestions if you haven't been to see if the accuracy get better? Please keep us updated!
@Colinfichman Жыл бұрын
Why not just use network RTK? It's so much easier and more consistent for me. I'm lucky there is a free network in my area.@@UAVISUALS
@IanAveryLeaf11 ай бұрын
I have been getting the same severe elevation differences (everything besides elevation stays the same between repeated flights) using repeatable routes w/ and w/out the RTK-2. RTK is always deployed in the exact same height/spot using mode 5, or I skip the RTK entirely but the problem remains. It's not only very annoying but borders on unsafe when the elevation change brings obstacles into the path. I haven't figured out a fix yet