Thanks Patrick,
your tip was very helpful

I played a bit with the timedPosHold and SetHeading. I wanted to make the copter turn 360° on a spot. So I defined 6x the same timedWP and 6x setHeading varying 60° each.
The result was diassapointing, instead of hovering at the same place, the copter went all over the flying field and the heading never seemed to be "under control".
The copter is well trimmed and infinite PosHold works much better.
Looks like the NAV Software doesn't like WPs that are too close to each other ( or even match the old WP )
Maybe a new command would be helpful here: PosHold in combination with a SweepHeading command.
The heading inaccuracy is also visible when I define a circle and setPOI at the center of the circle. I hoped, the copter would always aim to the center, but between WPs the heading is wrong.
For later NAV versions I would like to have a "camera-trigger" command implemented in the mission planner and also a PosHold command that loiters until a definable switch or other event happens. That would be more flexible than the timedPosHold..
But beside this, the NAV feature is my favoured toy ATM

<edit> BTW: wouldn't it be better to rename the
PosHoldtimed and
PosHoldInfinite into
timedPH and
InfPH? That would make it easier to read the mission.