radio

A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

What happened?

While testing https://github.com/gnuradio/gnuradio/blob/main/gr-digital/examples/packet/example_corr_est_and_clock_sync.grc I found that there are no signals on the QT GUI Time traces. They are set for tag trigger on corr_est and corr_start tags, but there don't seem to be any tags. If I change to Auto trigger, the data can be seen, but no tags at all.

A similar problem

It would be nice to be able to select which entries in the playout history are included when the list is exported. The checkout boxes are already there, but need plumbing into the export buttons.

This is the telemetry screen on my X10(s) Express with OTX 2.3.14

and this is with EDGE v2.5

We are using a MPX HF modules with a MPX to FrSky convert