tracernz raemin You can use the telemetry scheduler to slow down update rates and disable objects you're not interested in. In this way you can control the bandwidth requirements. By default things are reasonably aggressive and you need quite a bit.
For every entry in [settings] and [data objects] I can see the following pattern
A few questions:
1/ GCSTelemetry vs FlightTelemetry : is this USB telemetry versus Serial telemetry or Ground>Aircraft(TX) versus Aircraft>Ground(RX) ?
2/ ???UpdatePeriod=1000 : Does it mean, a message is sent at least every second regardless of the fact that the value has changed or not? What is the maximum delay? Does UpdatePeriod=0 mean no message sent unless specifically requested?
3/ ???TelemetryAcked boolean value : the online doc (http://rdu.im/dronin-dev-guide/software/uavtalk_protocol/) suggests that this indicator lists the "messages" that should be acknowledged by the recipient. Given that I am looking to update waypoint, maybe that waypoint proceeding from the GCS should be acknowledged by the Aircraft. On a similar vein, GPS position should be sent by the Aircraft and acknowledged by GCS. These are roughly the only messages I want to be acknowledged, as I don't mind loosing other telemetry packets (such as voltage, amps, etc...).
4/ Assuming 3/ is correct, in case the proof of receipt is requested, will the telemetry module re-submit the message until it is acknowledged, and submit all other messages as "fire and forget"?
5/ Can these settings be selectively applied to "USBTelemetry"? in other words if I aggressively remove object from the serial telemetry feed is there a possibility to keep a full connection in USB?
As an initial step I'll try to connect through an FTDI adapter. Will see later I can manage the added complexity of bluetooth, wifi or LRS...