The other response explained what LO stood for, but I think it needs to be explained further that it is the Local Oscillating frequency of the LNB. Ie these frequencies are not used in the receivers at all, they are the frequency that the LNB mixes with the downlink frequency to downconvert a band from C or Ku band down to the L band intermediate frequency that the receiver actually uses. Basically the software uses the LO freq to know what freq to tune to. Some receiver software does't even use LO freq at all, but just uses the IF freq. Ie on one receiver I have, if I want to receive a transponder at say 11800 MHz, I have to input 1050 MHz, ie since I use an LNB with a LO freq of 10750 on Ku, 11800-10750=1050). And even on some software written for the
Twinhan, you can just use zero for the LO freq, and enter the IF freq directly. These receivers where you enter LO freq do so just so you don't have to do the calculation yourself.
But back to your post, while I understand that it is confusing, it is still correct that we refer to LO freq, because that is in fact the parameter that you are selecting, whether or not the Twinhan software actually calls it or not. Ie it is the Twinhan software or documentation that is misleading, not the people on this list. Perhaps we could use another sentence to explain the Twinhan software, but personally I don't even recommend using the Twinhan software. Personally I use TSREADER with either VLC or a Roku, and virtually never use the Twinhan software, so I don't keep up with what Twinhan is calling things in their current software.
But use of the term LO is correct, and I don't think there should be a problem with using terminology which is correct. The worst thing that can happen is for people to learn what the parameters actually refer to.