TBS6903X Pixelating and Freezing

[crazycat]

This is just a sample of all of the errors from Frequencies 3800 to 4200 both H & V polarities on all CBand satellites. There are no issues with KU Band.

Signal quality (SNR * 5) is bad for 8PSK,3/4. Look like some issues with FBC tuner in STiD135.

P.S. Can you make spectrum scan with CrazyScan on selected range 3800-4200 H/V ?

[DVB]

Weird if the issue is not present on Ku-band because the card does not receive Ku-band or C-band, but L-band, no matter what comes from the satellites. LNB always makes downconversion of any signal to L-band (so Ku-band LNB converts received Ku-band signals to L-band signals and C-band LNB converts received C-band signals to L-band; between 950 and 2150 MHz - it's the basic rule of satellite reception). It's always L-band, what comes into the tuner. So there should be no difference.

I would rather bet on 5G interferences which are amplified by a weak shielding of STiD135 in 6903x. But who knows...

[Babadem]

Signal quality (SNR * 5) is bad for 8PSK,3/4. Look like some issues with FBC tuner in STiD135.

P.S. Can you make spectrum scan with CrazyScan on selected range 3800-4200 H/V ?

I hope these Screenshots capture what you requested? Thanks!

[Babadem]

Weird if the issue is not present on Ku-band because the card does not receive Ku-band or C-band, but L-band, no matter what comes from the satellites. LNB always makes downconversion of any signal to L-band (so Ku-band LNB converts received Ku-band signals to L-band signals and C-band LNB converts received C-band signals to L-band; between 950 and 2150 MHz - it's the basic rule of satellite reception). It's always L-band, what comes into the tuner. So there should be no difference.

I would rather bet on 5G interferences which are amplified by a weak shielding of STiD135 in 6903x. But who knows...

I hope there's a quick resolution on the issue one way or the other. This is an expensive card, and it's supposed to be a "Professional Card", but so far the performance has been nothing but that.

[crazycat]

Strange - 4120, 4140 transponders received with SNR 10-12dB
Maybe need update streamreader.dll for SmartDVB ?

[DVB]

A lot of weird patterns visible on the screenshots from CrazyScan.
E.g. RF on vertical:
Between 3800 and 3950 - copied to 3950-4100.
Reported transponders have got no reflection to the graph, e.g. the middle of 4120H (high SR) is marked at the end of increased RF Level graph. 4140V (again high SR) is marked in the middle of small RF Level peaks.

Basically graph shows garbages, not related to the real situation.

@Babadem Did you set up LNB LOF correctly, exactly as your C-band LNB says? Because data from RF Level has got nothing to do with real situation and it looks like a misconfiguration.

Please switch to L-band and re-do graph/blindscan - RF Level must correspond to detected carriers and now it does not.
Do you have a correct, latest test StreamReader.dll from here? https://sourceforge.net/projects/crazyscan/files/test/

[Babadem]

Strange - 4120, 4140 transponders received with SNR 10-12dB
Maybe need update streamreader.dll for SmartDVB ?

I get the same errors with DVBViewer Latest version, DVB Dream Latest Version, and EBSpro (using the Release version of StreamReader Ver.1.2.5.191). On CrazyScan I used Release version of StreamReader Ver.1.2.5.191. I will post screenshot using "Test version" of StreamReader Ver.1.2.5.194 later.

[Babadem]

A lot of weird patterns visible on the screenshots from CrazyScan.
E.g. RF on vertical:
Between 3800 and 3950 - copied to 3950-4100.
Reported transponders have got no reflection to the graph, e.g. the middle of 4120H (high SR) is marked at the end of increased RF Level graph. 4140V (again high SR) is marked in the middle of small RF Level peaks.

Basically graph shows garbages, not related to the real situation.

@Babadem Did you set up LNB LOF correctly, exactly as your C-band LNB says? Because data from RF Level has got nothing to do with real situation and it looks like a misconfiguration.

Please switch to L-band and re-do graph/blindscan - RF Level must correspond to detected carriers and now it does not.
Do you have a correct, latest test StreamReader.dll from here? https://sourceforge.net/projects/crazyscan/files/test/

Below are ScreenShots of LBand Scans as requested. By the way LOF is set to 5150 and using the "Test" StreamReader ver. 1.2.5.194

[DVB]

Thanks, still looking very weird, but that's not a LOF issue - by using L-band we took away any calculations and this should represent exactly what tuner gets from the LNB.
E.g. 1070H - high SR, so a wideband signal - detected in the middle of nowhere on the graph (red is V).
Only 950-1350 scanned, but all signals looks very narrow on the graph, which would carry rather a low-SR broadcasts.
Something fishy going on here...

And if we're moving into fish-related topics - @crazycat - what do you think about this?

[Babadem]

Below, I have posted KU-Band Lband Screenshots of my scans for Analysis. As I indicated before, it should be noted; I have no errors on KU_Band frequencies.