This read-write object sets the receive FEC type to one of uncoded(0), viterbi(1), viterbiReedSolomon(2), tcmReedSolomon(5), turbo(6), or tpcLdpc(7), again noting hardware-dependent availability. Like its transmit-side counterpart, this selection is gated by which optional FEC hardware this specific unit has installed, and it must match the FEC type actually applied at the far-end transmitter, since receiving a Turbo-coded carrier while configured for plain Viterbi decoding will produce no valid lock regardless of signal strength. If a remote unit's Turbo option reports none(0), that unit is hard-capped to Viterbi-based FEC types on receive, meaning it cannot be part of a network segment whose hub has standardized on Turbo coding without a hardware upgrade.