diff options
| author | Nick Piggott <nickpiggott@LINUX-DESKTOP-2.piggott.eu> | 2022-03-13 16:50:11 +0000 |
|---|---|---|
| committer | Matthias P. Braendli <matthias.braendli@mpb.li> | 2022-03-17 16:54:18 +0100 |
| commit | fb4bcbebcb890dc48b21f38126fb8818c0ec8a49 (patch) | |
| tree | 2fee90b7734946ff2b3e626ca924abb772ea8634 /src/zmq2edi/zmq2edi.cpp | |
| parent | 88d35427608d7c342509c5f9169cfc78984d3d7f (diff) | |
| download | dabmux-fb4bcbebcb890dc48b21f38126fb8818c0ec8a49.tar.gz dabmux-fb4bcbebcb890dc48b21f38126fb8818c0ec8a49.tar.bz2 dabmux-fb4bcbebcb890dc48b21f38126fb8818c0ec8a49.zip | |
Added FIG 0/14 for FEC scheme defintion, when a packet model channel is using FEC error correction (enhancedpacket)
Needs another pair of eyes to check it.
FIG0_14.cpp, line 37 - the data field is a single byte, top 6 bits are SubChanID, bottom 2 bits are FEC type; is this how you organise the bits in the right order?
FIG0_14.cpp, line 78 - there needs to be a test here if the packet channel is enhanced or not, but it looks like that attribute is only held on the file input, and not easily readable from the services configuration?
FIG0_14.cpp, lines 101-106 - is this writing the entire FIC into the stack correctly? The usual preamble bytes for the service identifier followed by the 1 byte data field
Diffstat (limited to 'src/zmq2edi/zmq2edi.cpp')
0 files changed, 0 insertions, 0 deletions