HDZ ain't leaving. It's the only system with a consistent latency and has some sort of feedback as to when the signal might drop. WS will suddenly drop without warning, and there's times where DJI isn't much better. I'm hoping that this is something that can be worked into this system. It does look promising and the fact that it's open source, like HDZ, is nice.

The receiver is true diversity, if a packet is missed from one of the channels it is taken from the other, if available.

@@tipoman9317 Is this system capable of recalling the lost frame (with a little latency increase) like Dji do? Thx!

@@PistiBala You mean request it from the transmitter? No, it can't do that.

How did you configure your VENC + VDEC ? Or are you using Majestic + VDEC ?

@@douglaskoo2354I do not use VDEC. I use laptop with qOpenHD on the ground.

i see@@tipoman9317

I use ELRS for control and basic telemetry and OpenIPC for video and advanced telemetry. Read the wiki about the latter.

There are many more compatible SoC+ sensors, it is explained in the OpenIPC wiki

No, it is not a bug. It is а very useful feature Video bandwidth alone is a useless metric, since it is constant all of the time. I show TOTAL amount of data received by BOTH channels. This is much more important value, since when this value starts to drop, I know that one of the channels starts losing packets. That is how true diversity + Forward Error Correction work - if a packet is missed by one of the channels, it is taken from the other. If it can't be found there, FEC tries to recover it. This value is a good indicator that you are close to the range limit of the link

@@tipoman9317 Ah so it's total data rate of diversity, overhead, plus whatever else is in the link. Cool.

Here I deliberately flew below the horizon ukposts.info/have/v-deo/hKl3an1-jqajp58.html