neumoDVB

[satesco]

12604H SR34284 looks interesting, that SR is used for NS3?

Symbol rate 34284 Ks/s is mainly used for the S2X extension. But this mux(12604 H) is definitely not for NS3.

 

[deeptho]

Tom55,

webro wf100 is supposed to be one of the best types of cable. I have very long runs of them (ten years ago) and did not experience problems. It is of course a bit stiff, making it (slightly) less suitable for the small pieces of cables needed in switches, where some flexibility is helpful.

It could be interference (e.g., switched power supply?).

 

[Llew]

deeptho, latest pull of neumodvb works fine for the dropping 11262H mux. Been up tor 15min. Thanks.

Just need to sort my 11227H phantom mux. A cable problem I think.

 

[satesco]

deeptho, latest pull of neumodvb works fine for the dropping 11262H mux. Been up tor 15min. Thanks.
...

It is probably a Generalised packetised stream

I updated neumoDVB for tbs 6903x with git pull, after which 11221 H was fixed. But the problem is now with 11262 H, which crashes after a manual search. In the log, it shows an error again.
In screenshot 11262 H before the crash:

Added: The same problem with the 6902 cards also on 11220 H/11262 H(?) when the neumoDVB crashes before it finishes scanning.

 

[Llew]

I updated neumoDVB for tbs 6903x with git pull, after which 11221 H was fixed. But the problem is now with 11262 H, which crashes after a manual search. In the log, it shows an error again.
In screenshot 11262 H before the crash:

Added: The same problem with the 6902 cards also on 11220 H/11262 H(?) when the neumoDVB crashes before it finishes scanning.

11262H is still OK with me, no dropouts. I'll try to route a different cable to my PC's TBS6903X to see if that solves my missing 11221H mux.
I have half a reel of WF100 in the shed, might be long enough to reach the Gibby.

 

[satesco]

I tried the tbs6590 card also on the two muxes(11220 H/11260 H), and the scan is ok now. There is no crash with this card.

 

[deeptho]

I updated neumoDVB for tbs 6903x with git pull, after which 11221 H was fixed. But the problem is now with 11262 H, which crashes after a manual search. In the log, it shows an error again.
In screenshot 11262 H before the crash:

Added: The same problem with the 6902 cards also on 11220 H/11262 H(?) when the neumoDVB crashes before it finishes scanning.

Satesco,

There are just debug messages and they shed no light on the error, but they show that you are not running the last
version at 17:47. Also for me, these muxes scan without any problem.

In general I need the complete log file to fix problems.

 

[satesco]

Deeptho.

I think I've updated my app.
I'm providing you with the log, and I hope you'll find out where the problem is.

 

[tom55]

Tom55,

webro wf100 is supposed to be one of the best types of cable. I have very long runs of them (ten years ago) and did not experience problems. It is of course a bit stiff, making it (slightly) less suitable for the small pieces of cables needed in switches, where some flexibility is helpful.

It could be interference (e.g., switched power supply?).

I don't say wf100 is necessarily the cause of distortions, however, @Llew is using it and have this problem as well. It is unclear on which dish installation he use mix of cables so best to wait until he sorts it out.
As i understand you both have same card, but only he has these spikes in spectrum.
At the moment i have 2 pieces of approx 15m, some noname cheap bought 15y ago and axing. Both have same issue. I think the noname cable could also be a mixture of steel and copper.

Switched power supply, it is possible. Especially since i used both my laptop and card on battery supplies when the test was carried out with card directly attached to the LNB.

 

[deeptho]

Deeptho.

I think I've updated my app.
I'm providing you with the log, and I hope you'll find out where the problem is.

It is what I suspected: you are still running the old version

 

[deeptho]

I don't say wf100 is necessarily the cause of distortions, however, @Llew is using it and have this problem as well. It is unclear on which dish installation he use mix of cables so best to wait until he sorts it out.
As i understand you both have same card, but only he has these spikes in spectrum.
At the moment i have 2 pieces of approx 15m, some noname cheap bought 15y ago and axing. Both have same issue. I think the noname cable could also be a mixture of steel and copper.

Switched power supply, it is possible. Especially since i used both my laptop and card on battery supplies when the test was carried out with card directly attached to the LNB.

The dips and peaks seem to be every 10Mhz or so and across the complete spectrum, which is less than 1% of the frequency transmitted
over the cable. So that would be difficult to explain by reflections on the cable. This is why it may be some source of interference.

If you have diseqc, you could check if they also appear on all or only on some satellites. This could shed some light on the process.

 

[Llew]

I don't say wf100 is necessarily the cause of distortions, however, @Llew is using it and have this problem as well. It is unclear on which dish installation he use mix of cables so best to wait until he sorts it out.

Without going outside with a torch to confirm, I have two cables of WF100 from the KaKU Inverto LNB on a Gibertini dish, the Ka and Ka/Ku outputs going to ports 1 and 2 of a 4-way DiSEqC switch in the shed. Five metres each max (the section I know for sure).

The output of the switch is 22 metres WF100 from the shed (just paced it down the garden), up to the extension roof and along to an f-socket junction box in the spare bedroom. A thicker cable than WF100 (can't remember its type, it's that stuff that's hard to find f-plugs to fit) goes into the loft and down to a bedroom where my PC is. A small section of WF100 goes to an A/B switch and thence to the TBS6903 and 6903X cards.

I haven't checked cable and connector losses with the Promax HD Ranger meter recently, but I had no reason to suspect any major issues with the runs as my other programs and devices (Crazyscan, EBSPro and the Linux updateDVB etc.) showed nothing unusual, taking into account the expected losses through the run.

 

[tom55]

The dips and peaks seem to be every 10Mhz or so and across the complete spectrum, which is less than 1% of the frequency transmitted
over the cable. So that would be difficult to explain by reflections on the cable. This is why it may be some source of interference.

If you have diseqc, you could check if they also appear on all or only on some satellites. This could shed some light on the process.

It is not satellite related. I had the scan in db several months old when i was testing LNB and cable in my room. Only part of the spectrum range looks free of distortion as you can see on screenshot (range 300-2350mhz).
Not sure if i have the same indoor test result of card directly attached to the LNB, even if i do, hard to find that one in thousands of db samples...
Either way the screens in neumoDVB are proving enough

 

[tom55]

Managed to find more spectrum backups
In blue - card directly to LNB with something similar to this https://m.media-amazon.com/images/I/41lTSGoiy0L._AC_SY580_.jpg and other with 15m axing

Also, its not a switching power supply problem

 

[Llew]

I decided to try an LNB (Inverto Premium PLL) on the Triax TD88 with its shorter cable run to see if there was any improvement on the false mux appearance with neumoDVB on 16E H polarity spectrum scan.

Initially, there was still the same problem, 11227H showing instead of 11221H, as shown in my previous posts. I then did a V polarity scan, which also showed a non-existent mux on 11235H, the adjacent mux on 11282V locking OK :-



I then decided to do a combined H and V polarity scan, which to my surprise showed the correct muxes, with no sign of the 'phantom' muxes :-



I then re-did an H Pol only scan. It now gave me the correct muxes! ( A scan of V Pol also gives a correct spectrum result).

It all seems very odd to me that doing the H and V scan 'seemed' to correct the spectrums. I will do subsequent tests occasionally to see if there's any repeat of the anomaly.

 

[deeptho]

I decided to try an LNB (Inverto Premium PLL) on the Triax TD88 with its shorter cable run to see if there was any improvement on the false mux appearance with neumoDVB on 16E H polarity spectrum scan.

Initially, there was still the same problem, 11227H showing instead of 11221H, as shown in my previous posts. I then did a V polarity scan, which also showed a non-existent mux on 11235H, the adjacent mux on 11282V locking OK :-

View attachment 146275

I then decided to do a combined H and V polarity scan, which to my surprise showed the correct muxes, with no sign of the 'phantom' muxes :-

View attachment 146277

I then re-did an H Pol only scan. It now gave me the correct muxes! ( A scan of V Pol also gives a correct spectrum result).

It all seems very odd to me that doing the H and V scan 'seemed' to correct the spectrums. I will do subsequent tests occasionally to see if there's any repeat of the anomaly.

View attachment 146278

If by "phantom mux" you mean "a mux that really does not exist" and not "a mux which has a wrong frequency due to the ripple:
Perhaps you are running outdated drivers? I do fix problems from time to time (like in August) but of course, none of that helps if
it is not installed.

However, the ripple on top of the spectrum is an unrelated problem. Because of your tests, it sounds like an interference problem inside the PC or on the card.

 

[Llew]

If by "phantom mux" you mean "a mux that really does not exist" and not "a mux which has a wrong frequency due to the ripple:
Perhaps you are running outdated drivers? I do fix problems from time to time (like in August) but of course, none of that helps if
it is not installed.

However, the ripple on top of the spectrum is an unrelated problem. Because of your tests, it sounds like an interference problem inside the PC or on the card.

I'm sure I'm up-to-date on the drivers, but I'll check anyway.

Your neumoDVB is obviously far too sensitive for my old equipment ( but in a good way - it keeps us on our toes )

 

[tom55]

I decided to try an LNB (Inverto Premium PLL) on the Triax TD88 with its shorter cable run to see if there was any improvement on the false mux appearance with neumoDVB on 16E H polarity spectrum scan.

Initially, there was still the same problem, 11227H showing instead of 11221H, as shown in my previous posts. I then did a V polarity scan, which also showed a non-existent mux on 11235H, the adjacent mux on 11282V locking OK :-

View attachment 146275

I then decided to do a combined H and V polarity scan, which to my surprise showed the correct muxes, with no sign of the 'phantom' muxes :-

View attachment 146277

I then re-did an H Pol only scan. It now gave me the correct muxes! ( A scan of V Pol also gives a correct spectrum result).

It all seems very odd to me that doing the H and V scan 'seemed' to correct the spectrums. I will do subsequent tests occasionally to see if there's any repeat of the anomaly.

View attachment 146278

See these very narrow small peaks at 11300, 11200 and the other 3 left of 11169 in your 3rd screenshot.

I also had these appearing with the premium PLL. I guess it's the same cheap 5euro LNB you used here.

 

[Llew]

There are no spikes showing using my Promax spectrum analyser within that spectrum range . There's a very small peak on 11200, but that also shows using the Inverto Ka/Ku LNB (DRO LO). Maybe a neumodvb issue (or not).

 

[tom55]

11200 might be a beacon. What is the promax scan resolution?