OK, so what settings on the new app do you use to make the drone act in the same way. The drone want to keep itās heading on the nearest POI, not the next one, or the one you set in the waypoint settings.
Myself and a couple others have had the same issue with a POI and reported it. You canāt set all the waypoints to follow course because it then stops the drone from focusing on the POI even though the waypoint is set to POI 1. The only way is to set the POI and then batch edit all the other waypoints and set them to custom and adjust every one which can be time consuming. This is the only way I can get it to focus on a POI and then back to following the paths course.
Iām sure the SDK is different, but I donāt understand how it can be that much different from before. In my mind Litchi has gone backwards, not improvedā¦the old interpolate worked flawlessly, this new transition does not work at all, or if it does, someone PLEASE let us know how to make it work like before!!!
Is it the drones that wonāt allow it to function as before? If that is the case, then I apologize to Litchi, and am wondering why DJI would change something so basic.
The Ltichi Mission Hub is the same for any drone. Itās the new Beta Mission Hub which is still being tested and updated so hopefully they get some more done. For now you can use the original Litchi Mission Hub and as long as you save them those same plans are saved in the Beta Hub as well. You donāt need to use the Beta unless you need mapping or another component which it has.
Mike, I realize the difference between the two hubs. I have made a mission in the old hub using the interpolate function, but it does not work with the newer drones, which makes me think it is a DJI problem, not Litchi, but if the Litchi guys would weigh in, that would be helpful.
If you want to interpolate between angles (heading and/or gimbal pitch):
Set Heading Mode & Gimbal Pitch Mode to āTransitionā.
If you want to āinterpolateā between POI:
Set Heading Mode & Gimbal Pitch Mode to āPoint of Interestā.
Heading and Gimbal Pitch have always been two separate and independent settings.
You can set the gimbal pitch to focus at a POI and at the same time the heading in opposite direction (a specified angle), and vice versa.
Can you explain exactly what you are trying to do as itās not clear?
If I understand correctly, what you want is the gimbal/heading angles to be automatically calculated when switching from POI to Transition rather than it being initialized to 0?
Is there any reason for using Transition rather than Focus POI if you want to focus on a POI?
I get new projects (water treatment plants etc..) all of the time that require multiple POIās over a rather large area. With the old system, you would do a āCustomā heading to each POI and then the gimbal as āInterpolateā between the POIās. This would make a more cinematic flight, especially when capturing it on video. This was all done using the mission HUB
Now, I canāt seem to figure out which settings will give me the same flight characteristics as before. When I use the pilot hub, all of that has changed. I can reproduce the same project in Pilot Hub with transitioning for the heading and gimbal, and the drone will want to stay fixed on the closest POI till it reaches the next waypoint when it swings to the next POI. While this will work if youāre taking photos, it does not work if you are taking video.
I have done some testing at my home with every imaginable combination of the internal/onboard, POI/Transition setting there is, but I canāt seem to replicate the old smooth cinematic āInterpolateā.
In Litchi Pilot Interpolate is now called Transition which is a transition from one angle to another (same as what Interpolate did before). All you need to do is set the angle for each waypoint.
POIs are meant to be used with the āPoint of Interestā mode where the drone will focus on the POI. One exception is if 2 consecutive waypoints have different POIs and are both set to āPoint of Interestā mode then the drone will transition from one POI to the other (internally it does a Transition).
What you are describing is not the expected result. Would you share this mission so that we can have a look? The only way to accomplish what you are describing is to use waypoint actions to set the yaw of the drone but I doubt that is what you are doing. Either your waypoint mission will show us something or perhaps you have uncovered a bug.
You mentioned that you are flying an M3E. I donāt have an M3E but I have used DJIās Flight Hub 2 to design flights for enterprise drones. Unless Iām mistaken, Flight Hub 2 does not provide the POI feature. Have you used DJIās Flight Hub 2? Can you confirm whether or not it supports POIs?