Karma works, eventually, but I'd rather rely on actions that address such ignorant and/or deceiptive bussiness practices. The very least I would do is make a comment to the local BBB on their behalf and then tell them I did so.
You RTN issue is the same that many have been having. I have as well occasionally.The real problem is that RTN is in one of the crummiest places to be in the grand scheme of satellite channels. It is too close to a neighboring signal that is much stronger, and that signal is taking over your receiver, blocking out the RTN transmission.
Solutions have been to move the target channel parameters (freq and symbol rate) away from the intruding signal's values.
From a users perspective the receiving side of this mode of transmission is not absolute. In an analog (NTSC, your am/fm radio etc) you select channel xyz you will get xyz if it is there, or nothing if it is not. Not the case here. When you input the RTNs data, you are telling the receiver, (your dvb computer card) "I want to see a signal at around 11735mhz with a symbol rate of about 4444". The receiver begins hunting for such a signal withing a few units of what you told it. It must receive enough error free data to id it as a valid signal before it will 'lock on to' and display what it finds. If a neighboring broadcast signal is within the few units of "capture range", and the receiver gets sufficient valid data to id it as a valid signal first, it calculates that this is the on you actually want, locks to it and ignores the weaker signal, even though the ignored signal was actually closer to the 'desired' freq data you entered.
It's just the nature of the beast. This issue reflects very poor engineering and transponder utilization AFAIC. Even switching the uplink to the opposite polarity would yield quite a bit of isolation, probably enough to eliminate the issue.
For now the best workaround has been to input values that are further from the undesired freq/sr and still within capture range of the desired one.
I use 11739 and 4500 and get a lock most of the time. It may be slow to act as well, as it is looking for enough error free data to id as a valid transmission. If your still cant get it with those values, by all means experiment with others.
Something else I've noticed is that the consistancy of the offending signal varies at different points during the day and night.
You RTN issue is the same that many have been having. I have as well occasionally.The real problem is that RTN is in one of the crummiest places to be in the grand scheme of satellite channels. It is too close to a neighboring signal that is much stronger, and that signal is taking over your receiver, blocking out the RTN transmission.
Solutions have been to move the target channel parameters (freq and symbol rate) away from the intruding signal's values.
From a users perspective the receiving side of this mode of transmission is not absolute. In an analog (NTSC, your am/fm radio etc) you select channel xyz you will get xyz if it is there, or nothing if it is not. Not the case here. When you input the RTNs data, you are telling the receiver, (your dvb computer card) "I want to see a signal at around 11735mhz with a symbol rate of about 4444". The receiver begins hunting for such a signal withing a few units of what you told it. It must receive enough error free data to id it as a valid signal before it will 'lock on to' and display what it finds. If a neighboring broadcast signal is within the few units of "capture range", and the receiver gets sufficient valid data to id it as a valid signal first, it calculates that this is the on you actually want, locks to it and ignores the weaker signal, even though the ignored signal was actually closer to the 'desired' freq data you entered.
It's just the nature of the beast. This issue reflects very poor engineering and transponder utilization AFAIC. Even switching the uplink to the opposite polarity would yield quite a bit of isolation, probably enough to eliminate the issue.
For now the best workaround has been to input values that are further from the undesired freq/sr and still within capture range of the desired one.
I use 11739 and 4500 and get a lock most of the time. It may be slow to act as well, as it is looking for enough error free data to id as a valid transmission. If your still cant get it with those values, by all means experiment with others.
Something else I've noticed is that the consistancy of the offending signal varies at different points during the day and night.
