New NS2000 (NS3 / NS4) thread

[moonbase]

Six channel golf mux in NS3.
It looks like this weeks event in the USA Korn Ferry Championship tour if the ID's in the mux are correct?

There are four FTA channels and two encrypted channels in the mux.
The vlc stream showing the test card was from the first of the four FTA channels (VPID = 402).

.

 

[satesco]

Forgive me, @moonbase, and I may become obnoxious if I insist that all transmission parameters be reported, especially symbol rates. Here on the right side, these parameters in your report are not shown; it is hidden, which is exactly what is more important (I think). And to be in the dark about everything, the satellite used is not reported.
Try to put yourself in my position or others who don't have this device and read these reports. What's to understand?...
What is this secrecy?
I want to think that's not why the old thread about the NS3/4 was dropped.
Regards

 

[moonbase]

Forgive me, @moonbase, and I may become obnoxious if I insist that all transmission parameters be reported, especially symbol rates. Here on the right side, these parameters in your report are not shown; it is hidden, which is exactly what is more important (I think). And to be in the dark about everything, the satellite used is not reported.
Try to put yourself in my position or others who don't have this device and read these reports. What's to understand?...
What is this secrecy?
I want to think that's not why the old thread about the NS3/4 was dropped.
Regards

@satesco

To the best of my knowledge the old topic was removed from the main forum at the request of the person who started the topic.
I do not think it was removed from the main forum due to any issues with publication of frequency parameters.

Please note that in reply 7 of this topic, one of the forum senior admin members indicated that he thought it did not really matter if the exact frequency parameters were not included in a contribution.
I read that as guidance that it was up to the contributor to decide if they wished to include frequency parameters.

As I said earlier in my first post in this new topic (reply 3), I am happy to share satellite and frequency parameters of the signals if other members do the same.
Apart from @tom55 who has uploaded some really nice spectra, there have been no other members who have uploaded screenshots of NS2000 settings or streams and channels received.

I realise that very few members have access to the equipment but if you read the old topic it is obvious that there are some who do.

 

[7mdish]

So, where is golf feed? We don't know......

 

[moonbase]

So, where is golf feed? We don't know......

When you start sharing screenshots from the NS2000 unit you have access to I will start including frequency parameters in my screenshots.
Until then...

 

[moonbase]

NS3 on 07.0 East using frequency of 10973V.

.

 

[satesco]

NS3 on 07.0 East using frequency of 10973V.

...

I believe 10973 V is not in NS3/4, but only with the S2X extension. The signal reaches 5 dB, but that's not enough to lock it.
I hope I'm not wrong, but I say this because the standard S2X extension doesn't see an ns3/4 signal even if they use the same extension(?).

 

[tom55]

I think it is NS3. Look at screen by moonbase, he get 12.24db SNR, while yours is about 4-5db which is also what my card shows (sometimes 7.8db).
There appears to be difference in SNR calculation algorithm between NS and DVBS

 

[moonbase]

I think it is NS3. Look at screen by moonbase, he get 12.24db SNR, while yours is about 4-5db which is also what my card shows (sometimes 7.8db).
There appears to be difference in SNR calculation algorithm between NS and DVBS

As the NS2000 demodulator also handles S2X mode I set it for that. The frequency of 10973V fails to lock and has reduced signal level compared to NS3 mode, see attached picture below.
When the NS2000 is returned to NS3 mode the frequency locks and returns to the high signal level.

I am reasonably confident that the frequency is using NS3 mode.

.

 

[moonbase]

I think it is NS3. Look at screen by moonbase, he get 12.24db SNR, while yours is about 4-5db which is also what my card shows (sometimes 7.8db).
There appears to be difference in SNR calculation algorithm between NS and DVBS

@tom55

What did your card and blind scan register for the two frequencies slightly higher than the 10973V signal please?
I estimated them to be at about 10996V and 11004V.

 

[Analoguesat]

Hey guys. Frustrating as it might be, its up to the contributor to decide exactly how much information to provide in any screen grabs or text post. No bitching if stuff is omitted - if you dont like it then you are totally free to get a decoder, set it up & post full transmission criteria.

It was my decision alone to remove the other thread, and I am not willing to go into the reasons any further.

 

[tom55]

@tom55

What did your card and blind scan register for the two frequencies slightly higher than the 10973V signal please?
I estimated them to be at about 10996V and 11004V.

Blindscan didn't work.
Manually discovered 10996 tries to lock at 8000ks/s.

 

[7mdish]

I confirm that 10973v is NS3, SR 34285, SNR around 12.7dB.
It could be F1 from Mexico but no ASI out here so I don't know.
Maybe some upgrade in that decoder could be possible in the future, we will see.
No permission by the decoder owner to post screenshots, sorry.

 

[satesco]

I think it is NS3. Look at screen by moonbase, he get 12.24db SNR, while yours is about 4-5db which is also what my card shows (sometimes 7.8db).
There appears to be difference in SNR calculation algorithm between NS and DVBS

I don't know what to think, it's probably as you say, but after checking 10973 V with IQmonitor, a DVBs application, this mux seems to be only in S2X. Such an app would not be able to process an ns3 signal, and despite the weak signal, it has managed to lock.
Still, I will consider your valuable observation when I find another mux with the same characteristics.
Here's what the signal looks like and the parameters of 10973 V, obtained with the 6903x card, the same as those reported by moonbase.
Unfortunately, scanning this mux took so long that I didn't get a chance to scan the close ones.

 

[tom55]

Looks like tbs6903x used with IQmonitor can also detect NS transmissions. Although it is possible there is difference between S2X and NS even at hardware level, that difference is small, and a lot of other factors are pretty much the same.
That's the reason this is possible. For example you get incorrect rolloff 0.35, while it is 0.05 and can even be 0.02 (are there S2X cards supporting 0.02?)
Sometimes it does not work, like with the above transponders, other times they are scanned even with quite a lower SR (set 30000, obtained 34288).

 

[satesco]

I checked 10973 V with neumoDVB, and as you can see from the screenshot, the app sees the signal but doesn't lock it. This makes me think you are right that this mux is in ns3.
It remains to check if IQmonitor can detect other NS3 muxes.
Have you tried working with neumoDVB on mux NS3, and if so, with what results? Thanks

 

[tom55]

Try to enter 34286 manually and lock in 3 ways.
1. Blind tune
2. Disable blind tune, choose DVBS2
3. Disabled blind tune choose DVBS

to see if it will try to do anything. run abort between tune attempts

 

[satesco]

You should know that I tried all three options you recommended on other occasions, but didn't have the desired result.
I'll try tomorrow, it's too late now.
Regards

 

[tom55]

Maybe for your card windows drivers are better for this than linux drivers.
All 3 muxxes gone within few minutes

 

[7mdish]

As the mux was gone just aftet 1am CET (12am UK time), I think more and more it was Formula 1 from Mexico City.
Again, I'm sure it was NS3. Our decoder has no DVB-S2X, and it perfectly locked in NS3 mode.