Inconsistent absolute positions for Osmo Mobile
I developed an iOS app for with DJI Mobile SDK 4.16.2.
However, every time I turn on the gimbal and then set the position to
let rotation = DJIGimbalRotation(
pitchValue: 0,
rollValue: 0,
yawValue: 0,
time: 2,
mode: .absoluteAngle,
ignore: true
)
The position is different and not aligned with the initial position that the device was as soon as it was turned on.
I also tried to use
DJIGimbalState.yawRelativeToAircraftHeading
to correct the angle, but this value is always 0.
-
The reference frame used by absoluteAngle on different devices is different. Can you tell me what the orientation of the OSMO gimbal is when it just starts up? And then, what is the orientation of the gimbal that you get after calling the gimbal rotation interface? I assume that absoluteAngle represents the angle in the geodetic coordinate system at this time, meaning it represents the angle between the gimbal and true north. -
When the OSMO gimbal starts up, it is centred at the expected center (the one recalled with double press of the trigger button).
Your assumption seems legit, but it looks like at every start of the gimbal, the angle (0,0,0) represent a different point in the real world, so a different angle in the geodetic coordinate system.
You can find a video that shows the issue at https://youtu.be/Ud31_6sK5GY (https://www.bilibili.tv/en/video/4791202754985984). Every time I click the button "HOME" on the tablet, I callDJIGimbal.rotate(with:completion:)
with the rotation as above, requesting a rotation to the absoluteAngle (0,0,0). As you can see, what this angle means for the gimbal changes at every power on the device or I exit standby mode. -
Thank you for providing the video. It allows me to visually see the issue you are facing. However, I have noticed that the OSMO device used in this video does not seem to be a device that is compatible with the IOS Mobile SDK. For devices that are not compatible with the SDK, we cannot guarantee the effectiveness of using the SDK interface. There should be a relative mode for gimbal movement. Have you tried using this mode? -
I tried implementing the feature with the relative mode for the gimbal movement, but this solution does not work for what I want to accomplish: I want to store the attitude of the gimbal and then mode the device back to that orientation at a later point. Calculating saved position - current position gives the same result as setting the absolute position directly, that does not work as explained above.
-
I am very disappointed to hear that the Osmo Mobile 3 is not supported by the iOS Mobile SDK (even though most of the other functions works fine). This leaves no alternative to the developers than integrating with other gimbal brands, and the user will have chose those devices over DJI's one to use the mobile application.
Stopping updating and SDK completely as announced https://sdk-forum.dji.net/hc/en-us/articles/25786229596057-Part-of-DJI-SDK-stops-updating-announcement takes away value from your product that can now be used in less creative way with third-party integrations. You suggest to develop mobile applications based on the Android SDK, but this is sometimes, like in my case a viable alternative - for me and for the users.
I really hope you reconsider your decision, that I cannot fully understand, knowing that you still support all the new devices in your first-party apps. -
Mobile SDK is currently focusing on adapting enterprise series drones, while also adapting some consumer-grade drones that can be used in fields such as inspections. We have not received any plans to officially adapt the new OSMO devices. The official app is not based on the SDK implementation; the SDK needs to be adapted to the product before it can be used stably. The decision to stop updating the iOS SDK was made by the team after careful consideration. We apologize for any inconvenience this may have caused you.
请先登录再写评论。
评论
6 条评论