Testing TBS6903X and TBS6522 in neumoDVB

[Llew]

Some observations of the blindscan differencies/similarities with the TBS6903X (stid135) and TBS6522 (si2183) using the neumoDVB program.

Satellite chosen is 34.5W.

On the whole, times taken for blindscanning the spectrum range chosen (11.000 - 11.600 GHz) compares favourably between the two cards, with the TBS6522 locking 5 out of 24 found scanning in the horizontal polarity. The TBS6903 locks 2 extra, but this is over 40 in total scanned in.

In the vertical plane,The TBS6522 seems to do better locking 12 out of the 20 scanned in, but there seems to have been something odd happening with 11.525 GHz, with three appearances of the frequency over the scan. I'll check that one again in due course.

TBS6522 -





TBS6903X -




This is just a preliminary comparison of the two cards with neumoDVB, more to come.

 

[deeptho]

Some observations of the blindscan differencies/similarities with the TBS6903X (stid135) and TBS6522 (si2183) using the neumoDVB program.

Satellite chosen is 34.5W.

On the whole, times taken for blindscanning the spectrum range chosen (11.000 - 11.600 GHz) compares favourably between the two cards, with the TBS6522 locking 5 out of 24 found scanning in the horizontal polarity. The TBS6903 locks 2 extra, but this is over 40 in total scanned in.

In the vertical plane,The TBS6522 seems to do better locking 12 out of the 20 scanned in, but there seems to have been something odd happening with 11.525 GHz, with three appearances of the frequency over the scan. I'll check that one again in due course.

TBS6522 -

View attachment 149668 View attachment 149669

View attachment 149674 View attachment 149675

TBS6903X -

View attachment 149670 View attachment 149671

View attachment 149672 View attachment 149673
This is just a preliminary comparison of the two cards with neumoDVB, more to come.

LLew,

That is weird indeed. Are you running the most recent drivers? I suspect that the card perhaps
cannot lock to some peaks for some reason (poor signal?) and then uses a broad search range to find something that locks
and it then ends up at the same mux for the three starting peaks. What happens if you do a non-blind tune
on the 6522 with the mux 11542V or 11558V? Does it lock?


By the way: I made some changes yesterday to the drivers. The only new thing is that it is now possible to
compile for newer kernels in the 6.1 and 6.2 range.

 

[Llew]

What happens if you do a non-blind tune
on the 6522 with the mux 11542V or 11558V? Does it lock?

No problem locking 11542V deeptho, but those spikes or whatever they are spaced 50 MHz between 11200V and 11450V are interesting. They don't appear every time I scan this spectrum range with the 6522, as my previous spectrum shows. Doesn't worry the 6903X scans any time.

 

[Llew]

By the way: I made some changes yesterday to the drivers. The only new thing is that it is now possible to
compile for newer kernels in the 6.1 and 6.2 range.

Thanks, I wanted to use Fedora 37, but I couldn't find a working kernel below 6.1 or 2 to be able to use the program.