New NS2000 (NS3 / NS4) thread

[satesco]

Yes, I should have mentioned you as an exception to a rule that tacitly manifests itself on the forum by those who own this device. I'm glad you broke who knows what rules imposed by the manufacturer(?).
In fact that's my idea too, that manufacturers don't dictate what should be discussed on the forums. Their administrators know when users cross the red line between what is allowed and what is not on their forums.
Why create more frustration for users who don't have the financial means to buy these devices. And even if they did, there's no telling if the manufacturer would sell their product. It is clear that such manufacturers avoid discussion of their product on a forum of users who have technical/intellectual curiosities.
Regards

 

[7mdish]

It is quite old, not been updated for a couple of years.
What version is installed in the unit you have access to?

I suspect that mine (not mine unfortunately) is older than yours, surely they got it more than two years ago.
Firmware version is 5.7.0.

 

[moonbase]

I suspect that mine (not mine unfortunately) is older than yours, surely they got it more than two years ago.
Firmware version is 5.7.0.

Firmware version 6.05.00
Probably could do with an update.

 

[tom55]

Although you changed the frequency range to 11090-11095 in a later post, I found something at 10995V on 07.0E with narrow bandwidth.

There is something around 10994V to 10995V that fails to lock in a DVB-S2X receiver (Octagon SF8008) and fails to lock on both EBSPro and CrazyScan.

CrazyScan registers the signal but fails to lock it.
At the moment I dont know for sure that the frequency has NovelSat modulation, just guessing based on the fact that it "Syncs" using NS3 mode.

I have attached below the screen grabs from NS2000 demodulator, Promax Ranger meter and CrazyScan.
The frequency will "Sync" in an NS2000 demodulator but it fails to lock, possibly due to incorrect SR. I could try stepping the SR in small increments to see if I can get it to lock.
However, if @tom55 is around and can scan an accurate SR for the frequency I would be grateful as it would probably speed up the process.

.
View attachment 145618 View attachment 145619 View attachment 145620

It's still present at 10995v, SR 5710.
11066v 17144 (s2x?)
11093v 34286 NS3

 

[moonbase]

It's still present at 10995v, SR 5710.
11066v 17144 (s2x?)
11093v 34286 NS3

@tom55
Many thanks.

I was reasonably close to the SR with my stepping technique, I had it as 5709.9
I will have a look at the other two that you have listed later today (11066V and 11093V) with an NS2000 demodulator.

 

[7mdish]

As I know, if NS2000 state is "sync" it means that symbol rate is correct.
If SR is wrong the carrier can not be "synced".
Lock is a different story. A signal can be synced but not locked.
Lock depends mainly by signal strength and licenses installed in the box. Both are clearly visible from the box web interface.

 

[7mdish]

Firmware version 6.05.00
Probably could do with an update.

I try to tell them.... not so optimistic because it could be expensive I'm afraid.

 

[moonbase]

It's still present at 10995v, SR 5710.
11066v 17144 (s2x?)
11093v 34286 NS3

11066V is DVB-S2x, lockable with both an NS2000 demodulator and an Octagon SF8008 or any S2X capable satellite receiver.

.

 

[7mdish]

I try to post again a question that had no reply in the old discussion.
Since my good old Alitronika ASI to USB interface does not work anymore (main problem is that I must use a virtual machine now), I would like to connect Novelsat IP out to my computer network connection and analyze TS streams in TSReader in the same way like from the ASI out.
I'm totally stuck with right settings and configurations.
In the NS2000 menu there is no significant settings, and I don't know if TSReader must be configured in Multicast or Unicast and which IP address to use. Just tried with Novelsat main IP address but it does not work.
Could anyone please address me in the right way? Thanks.

 

[moonbase]

It's still present at 10995v, SR 5710.
11066v 17144 (s2x?)
11093v 34286 NS3

Slightly off topic but involving the use of an NS2000 demodulator and a follow up to earlier discussions.

The feed on 11066V from 07.0 East is an unencrypted DVB-S2x feed for the Celtic vs Shatkar Donesk Champions League match.

It scans and locks in an Octagon SF8008 receiver but does not display a picture. The Octagon is DVB-S2x and 16APSK capable so might be expected to render a picture but fails to do so, possibly due to the high FEC of 28/45?
There might also be an issue with the DVB-S2x frame rate that the Octagon tuner can cope with. I dont think the Octagon tuner is both "long and short frame rate" capable. If this feed is in the frame rate that the Octagon cannot cope with it could also be the reason for no picture, just guessing however?

The NS2000 demodulator in DVB-S2x mode has no problems with the feed, it sends it via ASI to a capture card and can be displayed in vlc via a signal analyser.
Picture attached below.

.

 

[7mdish]

Possible 4:2:2 feed?

 

[tom55]

Probably 422 feed, and receiver cant deal with it

 

[satesco]

7.0E_11066 V,17142,3/45,S2X/16APSK,0.05-Feed A UHD_FTA(locked with tbs6903X)

 

[moonbase]

Probably 422 feed, and receiver cant deal with it

I completely forgot about 4:2:2. However looking at the stream analyser preview of the VPID in the ts stream there is no evidence of 4:2:2.
It probably needs looking at with something like Media Info Pro that has a more in depth analysis to determine if it is 4:2:2

 

[ozumo]

In VLC going Tools > Codec Information will list the video format.

 

[satesco]

It can be seen on TSReader that the broadcast of this match is in 422, and as we already know, VLC can run such a stream.

 

[moonbase]

Confirmed as 4:2:2.
The SF8008 WebIf can stream the video to vlc and MediaInfo Pro also shows it as 4:2:2.

Oh well, on to the next...

.

 

[satesco]

7.0E_11083 V,17141,28/45,16apsk- FL/ASI/GEN1(card test)
Same operator(BT Media) but on a different frequency with the same parameters in S2X.
Probably later they will switch to H.265, maybe again in 4:2:2(?).

added later: No test card now

 

[EnoSat]

The topic is about NS3/NS4, not about DVB-S2X

 

[moonbase]

The topic is about NS3/NS4, not about DVB-S2X

When 11066V was first reported yesterday there might have been a small chance that it was NS3/NS4.
That was the reason for the discussion about it.

As it turns out, I locked the frequency in an NS2000 demodulator and the thread title is "New NS2000 (NS3 / NS4) thread"
At the time yesterday I thought that it was valid to include the screenshots of the frequency.

I look forward to your contributions to this topic.