neumoDVB

[Llew]

DVB-T/T2 muxes found now thanks to @deeptho finding the problem in my Fedora OS during a Teamviewer session.

That was with the Sony USB stick. At present, I'm having trouble finding the muxes with the TBS6522 DVB-T/T2, so still work to do.

 

[Llew]

DVB-T/T2 muxes found now thanks to @deeptho finding the problem in my Fedora OS during a Teamviewer session.

That was with the Sony USB stick. At present, I'm having trouble finding the muxes with the TBS6522 DVB-T/T2, so still work to do.

OK now with the latest version from GitHub.

 

[Butacas]

Is media_build necessary/required?

I will do a clean install of fedora 37 and connect the card directly. I will follow your installation instructions.

 

[Llew]

A bonkers scan result with my particular TBS6522 card on 7E Ka.

Ignoring the ever-present 50MHz - spaced spikes that run through the spectrum with my card, the 2STV channel at 21619H is actually one of the 21595H "locked" channels in the scan

 

[deeptho]

A bonkers scan result with my particular TBS6522 card on 7E Ka.

Ignoring the ever-present 50MHz - spaced spikes that run through the spectrum with my card, the 2STV channel at 21619H is actually one of the 21595H "locked" channels in the scan


View attachment 150451

Easy to explain: the spectral peaks are used as the intial frequency to search for a mux. In your case they are just random starting points but for some reason the search range is large enough to reach the same peak from multiple starting frequencies. It would be nicer to only colour the correct peak. It is also not clear why the search range is so large, but the driver lacks documentation

 

[Llew]

Regarding the 50 MHz spikes. Checking an earlier scan I did a few weeks ago, they were absent in both polarities, so it doesn't seem to be a permanent problem. So perhaps not irreversible.

 

[EnoSat]

maybe bad condenser filtration (loss of capacity)

 

[Llew]

maybe bad condenser filtration (loss of capacity)

Perhaps a decoupling capacitor across one of the chips? Domodulator section?

 

[satesco]

Regarding the 50 MHz spikes. Checking an earlier scan I did a few weeks ago, they were absent in both polarities, so it doesn't seem to be a permanent problem. So perhaps not irreversible.

View attachment 150458View attachment 150459

The results with neumoDVB at 34.5W in Ku-band, between what you received and what I got, highlight that the 6522 card doesn't have excellent support on Linux. You can see this from the fact that the card found and locked two muxes that should not be between 11200-11400 MGz, because the satellite does not work in this range, and on the other hand, the demod only works between 1000-45000 Ks. Or the symbol rate of over 100000 that I got on Intelsat 35e is fictitious, to be more polite.
On the other hand, I notice that both on your spectrum and mine, there are many muxes with low symbol rates, which is not ok for this card.
It is not @deeptho's fault that such errors or bugs occur in cards that, even on Windows, are problematic reliable, and good receptions.
I don't insist on this problem because I might be wrong.
Posting my results with the 6522 cards on this satellite is best. For comparisons, I added blindscan with the 6903x card,
However, being a multi-standard card, the tests were excellent on cable and terrestrial muxes reception. I have not encountered any problem receiving in one try both standards.
I've added some files for @deeptho. It may help: tbs6522-tests.zip

 

[Llew]

The results with neumoDVB at 34.5W in Ku-band, between what you received and what I got, highlight that the 6522 card doesn't have excellent support on Linux.

I could never get the TBS6522 to do a spectrum scan with Linux. That's with Ubuntu 22.04. So I went back to Fedora.

I sstill get spikes at 50 MHz intervals in my scans, so think I have a hardware problem with my card.

However, being a multi-standard card, the tests were excellent on cable and terrestrial muxes reception.

No problem using the terrestrial tuner.

I'll return to 34.5W to recheck and compare with your results in due course.

 

[deeptho]

Could be a hardware fault. According to TBS the chips are the same between 6522 and 6504 and the
main difference is 4 instead of 2 tuners.

What you could also try is connect the cable to the other input (and use the corresponding adapter or
rf input)

 

[Llew]

What you could also try is connect the cable to the other input (and use the corresponding adapter or
rf input)

Tried both inputs deeptho; post #824 scan is using rf input 1, showing the same result as using the first input rf0.

I don't know the tuners and demodulator arrangement - do both tuners share the same demodulator? (You've probably explained the layout somewhere).

 

[deeptho]

Tried both inputs deeptho; post #824 scan is using rf input 1, showing the same result as using the first input rf0.

I don't know the tuners and demodulator arrangement - do both tuners share the same demodulator? (You've probably explained the layout somewhere).

As far as a I know all are separate. The best thing right now would be to have some confirmation from other users
of the same card: do they have the problem or not.

It is of course very strange that you suddenly started having problems

 

[Llew]

The best thing right now would be to have some confirmation from other users

It seems the TBS6522 @satesco uses is free of the problem, at least there's no sign of it in the screenshot in post #829 above.

I'll swap its pci slot with the TBS6903X - it's right under the video card at present, maybe there's some EMI being picked up from there or thereabouts.

 

[satesco]

It seems the TBS6522 @satesco uses is free of the problem, at least there's no sign of it in the screenshot in post #829 above.

I'll swap its pci slot with the TBS6903X - it's right under the video card at present, maybe there's some EMI being picked up from there or thereabouts.

Indeed I have no problems with the 6522 card with neumoDVB.
After you pointed out that you have problems using the two tuners, I tested them on Ubuntu and Windows. On both systems, the card works fine with both tuners simultaneously.
On neumoDVB, I chose one output for cable and the other for satellite reception, as shown in the screenshots.
I assume you are not working with 6522 only on Linux but also on Windows. That's why I would say to test first on Windows and then on the other system.
On Windows, as you already know, before working on cable or satellite, you must use the TBS6522ChangeModeTool utility, which allows you to choose the outputs for satellite and/or cable as you wish. Once you have done this, you can use players or apps, as in the example below.

 

[Llew]

Indeed I have no problems with the 6522 card with neumoDVB.
After you pointed out that you have problems using the two tuners, I tested them on Ubuntu and Windows. On both systems, the card works fine with both tuners simultaneously.

I don't have problems using either the satellite or terrestrial tuners in neumodvb or Windows satesco, it's just the 'spikes' showing an neumodvb's spectrum that are the problem.

However, I haven't thoroughly checked for any appearances of the spikes doing a satellite scan in Windows using the 6522. I would assume there would be some showing over the scan. I will do another check when I have rearranged my cards' pci slot positionings.

 

[satesco]

... it's just the 'spikes' showing an neumodvb's spectrum that are the problem.

...

Do you have spikes in Ku or Ka-band?
If you have problems in Ka, I will test neumoDVB on Ubuntu 22.04.

 

[Llew]

Do you have spikes in Ku or Ka-band?
If you have problems in Ka, I will test neumoDVB on Ubuntu 22.04.

Same in Ka satesco.

neumoDVB

DVB-T/T2 muxes found now thanks to @deeptho finding the problem in my Fedora OS during a Teamviewer session. That was with the Sony USB stick. At present, I'm having trouble finding the muxes with the TBS6522 DVB-T/T2, so still work to do.

www.satellites.co.uk

 

[deeptho]

I don't have problems using either the satellite or terrestrial tuners in neumodvb or Windows satesco, it's just the 'spikes' showing an neumodvb's spectrum that are the problem.

However, I haven't thoroughly checked for any appearances of the spikes doing a satellite scan in Windows using the 6522. I would assume there would be some showing over the scan. I will do another check when I have rearranged my cards' pci slot positionings.

The methods for the spectrum are different in windows (no fft scan) and linux, so for this problem comparing is not possible.

 

[Llew]

The methods for the spectrum are different in windows (no fft scan) and linux, so for this problem comparing is not possible.

Yes, should've thought that through before checking. Still, here's my Windows spectrum check for what it's worth.