After that it is no longer a Q500, and you are not running Yuneec software to allow waypoints and POI. You should start a new thread with the topic of modding a Q500 to become something else. Dredging ancient topics is not the method to do that. What you are bringing up is totally different than the subject of that thread which was Yuneec adding that functionality to the stock Q500
My My are we sensitive ! and it seems ALL topics on this forum are 2+ yrs old, so hard to know what is 'safe from your criticism' and what is not !
and the topic is/was/ and forever will be WAYPOINTS on a Q500, & how to get them, no ?
besides, according to your definition, likely Q500's are NOT Q500's as they likely have diff internal components from that of the original, see how that shortsigted view works ?
and yes, the st10+ does not support waypoints (i ASSuME), so do not understand how vid guy ran waypoints for claimed 8km.
but waypoints on the st10+/Q500 should have been very possible if they had the rom space & as said before, if needed more rom space, an upgrade of components (now not a Q500 according to you) would have allowed.
that assumes that the st10+/st16 just spews out gps locations and orchestrates the copter as it flies, comparing current location to next waypoint (called interpelation of interim values), of course doing housework all the while of keeping track which waypoints having been reached and which are still pending, but how is this DIFFERENT FROM 'GO HOME' method in actual execution ?????
but i do not have a clue how it is really done by H/st16, just how it could be done, will look up how H does it.
Thanks for your very helpful criticism, we all learned oh so much from it. moderator !
ps: every forum i ever see has ppl commenting on older posts, some 6 yrs old, AND it is often helpful, jsut as often not.