Moderator Control Panel ]

TBS6590 and Cam module on Dutch encrypted services

TBS6590 and Cam module on Dutch encrypted services

Postby BlueSkyThinking » Mon Sep 09, 2019 3:47 pm

Hi,

Can I please get some help with TBS6590 and cam module.
I cannot get the encrypted channels to work on 23.5 east Canal Digitaal.
I have the appropriate Cam module and card.

I am also the proud and very satisfied owner of a TBS6991, but that card is no longer supported in the more recent Ubuntu versions, so it is time to move on.

End goal is to use TBS6590 with MythTV, but for the speed of testing this card I am currently using mumudvb and dvblast.
Both seem to be very quick when making small configuration changes which hopefully helps in eliminating the issue I have

I have a desktop computer, with more than 2 partitions, 1 partition is on a virgin Ubuntu 18.04.3 LTS kernel 5.0.0-27-generic, to test the TBS6590 card and another on Virgin Ubuntu 14.04
kernel 4.4.0-142-generic for the TBS6991 card. Then I have installed the applications and drivers required for test.
For the TBS6590 I use the opensource driver download from 9 September 2019. The compile process does generate a number of warnings,
but seems to end OK.
The adapters are created after reboot, dmesg lists the frontend and reports that the cam is initialised.
dmesg output here:
[ 18.820578] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6590 DVB-S/S2 + 2xCI )...
[ 18.820609] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 0 frontend 1 (Silicon Labs Si2183)...
[ 18.947720] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6590 DVB-S/S2 + 2xCI )...
[ 18.947766] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 1 frontend 1 (Silicon Labs Si2183)...

[ 29.210010] TBSECP3 driver 0000:01:00.0: CA slot enabled for adapter1
[ 29.210011] dvb_ca_en50221: dvb_ca adapter 1: DVB CAM detected and initialised successfully

I therefore presume this is all OK, but given that I struggle getting the card to work this might contain a clue to the problem.

With TBS6991 on Ubuntu 14.04 -using the drivers from tbs-linux-drivers_v170330.zip- everything still works, which makes the problem more intriguing.

Swapping from one card to the another is done by physically swapping the cards after powerdown in the exact same PCIe slot, and reboot the appropriate OS

So what works on the TBS6590:
Cam is in inserted for all trials, green (TBS6590) led is lit, and dmesg reports successful initialisation of cam, and creation of frontends as mentioned above.

I can swing the dish with motor from 28.2 east to 23.5 east and vice versa using satmap.
I can with gnutv get to the cam data with: gnutv -adapter 1 -caslotnum 0 -cammenu
And I even believe to have seen that the expiry data has been updated whilst in the TBS6590

For 28.2 East FTA channels
I can receive and watch BBC Oxford as a DVBS channel with success
I can receive and watch BBC ONE HD as a DVBS-2 channel with success

For 23.5 East
I can receive and watch OCKO TV (FTA) as a DVBS channel with success.

The above successes are both done with a mumudvb and dvblast.
For mumdvb config in include the OCKO one as an example:

Start file contents of Ocko_single.mumudvb_v2.conf top
Code: Select all
#DVB Card specifics
#Ensure that demux and the dvr are symbolic linked to 1 e.g a demux1 and dvr1 must exist.
card=1
tuner=1
#cam_support=1
#this is weird, cam0 seems to at least respond to a certain degree
#cam_number=0

#Streaming specifics
#disable multicast  THIS PARAMETER HAS CHANGED NAME FROM multicast TO multicast_ipv4
multicast_ipv4=0
#enable unicast
unicast=1
#listen at all addresses
ip_http=192.168.1.189
#default port 4242
port_http=4242

#Transponder specifics
freq=12168
pol=v
srate=27500
delivery_system=DVBS
modulation=QPSK
#coderate=3/4
#rolloff=35

#channel specifics
new_channel
name=PQ2
unicast_port=8001
pids=54 53 257
#pids=261  #video pid, audio pid, pmt pid
#pmt_pid=xxx   #only for scrambled channels

#new_channel if more then one

End file contents of Ocko_single.mumudvb_v2.conf bottom

And the Command line for Mumudvb looks then like this:
/usr/local/bin/mumudvb -d -c "./Ocko_single.mumudvb_v2.conf"

I can play the channel on VLC using this:
vlc -> playlists -> right click -> open media -> open network -> http://192.168.1.189:4242/playlist_port.m3u -> ENTER

Or as an alternative with a DVBlast config file like the one below. OCKO one as an example

Start file contents of ocko_dvblast.conf top
Code: Select all
239.255.0.1:8001 1 5201

End file contents of ocko_dvblast.conf bottom


The Command line for DVBlast look like this:
dvblast -a 1 -n 1 -f 12168000 -s 27500000 -v 13 -C -c "./ocko_dvblast.conf"

I can play channel on VLC using this :
vlc -> playlists -> right click -> open media -> open network -> rtp://239.255.0.1:8001 -> ENTER

Two things that I have noticed are:
1: using the old femon application from dvbtools. there is a significant repeatable drop in signal strength.
(The cable and devices between LNB and card have not changed at all, and are almost undisturbed, reconnecting one f-connector when swapping the cards)
TBS6991 indicates signal stength of B4** to C5** in hex values and a SNR of F0** to FF**
TBS6590 gives noticeable lower signal strength. 82** to 8c** in hex values and a SNR of b6** to c0** in hex values.

This could well be that the values are obtained in a different way and hence this is not a real issue

2:It feels that the TBS6991 is more solid in its performance and behaviour. Could well be subjective.

What does not work on TBS6590

Mumudvb config file looks like this for the SBS6 encrypted channel
Start file contents of SBS6_single.mumudvb_v3.conf top
Code: Select all
#DVB Card specifics
card=1
tuner=1
cam_support=1
#this is weird, cam0 seems to atleast respond to a certain degree
cam_number=0

#Streaming specifics
#disable multicast  THIS PARAMETER HAS CHANGED NAME FROM multicast TO multicast_ipv4
multicast_ipv4=0
#enable unicast
unicast=1
#listen at all addresses
ip_http=192.168.1.189
#default port 4242
port_http=4242

#Transponder specifics
freq=11739
pol=v
srate=29900
delivery_system=DVBS2
modulation=8PSK
coderate=2/3
rolloff=35

#channel specifics
new_channel
name=PQ3
unicast_port=8001
pids=2490 526 106
pmt_pid=2490
#only for scrambled channels
cam_ask=1

#new_channel if more then one

End file contents of SBS6_single.mumudvb_v3.conf bottom

command line for mumudvb looks like this:
/usr/local/bin/mumudvb -d -c "./SBS6_single.mumudvb_v3.conf"

DVBlast config file looks like this for the SBS6 channel.

Start file contents of SBS6_dvblast.conf top
Code: Select all
239.255.0.1:8001 1 6090

End file contents of SBS6_dvblast.conf bottom

command line used for dvblast:
dvblast -a 1 -n 1 -f 11739000 -s 29900000 -m psk_8 -F 23 -v 13 -C -c "./SBS6_dvblast.conf"


Using dvblast whilst the TBS6590 is inplay.
Gives a constant stream of discontinuity errors on the Dvblast terminal screen.
warning: TS discontinuity on pid 526 expected_cc 1 got 2 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)
warning: TS discontinuity on pid 526 expected_cc 5 got 6 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)
warning: TS discontinuity on pid 106 expected_cc 6 got 7 (13818-3 audio (MPEG-2), sid 6090)
warning: TS discontinuity on pid 526 expected_cc 5 got 6 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)
warning: TS discontinuity on pid 526 expected_cc 7 got 8 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)
warning: TS discontinuity on pid 42 expected_cc 13 got 14 (H.222.0/13818-1 PES private data, sid 6090)
warning: TS discontinuity on pid 526 expected_cc 7 got 8 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)
warning: TS discontinuity on pid 526 expected_cc 12 got 13 (H.264/14496-10 video (MPEG-4/AVC), sid 6090)


With Mumudvb it starts and does report that the channel is fully de-crypted, but when trying to play the stream
Looking at the messages in VLC I see a constant stream of discontinuity error messages,

ts error: libdvbpsi (PSI decoder): TS discontinuity (received 3, expected 2) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 7, expected 6) for PID 18

warnings and debug gives even more messages.

The video output itself looks blotched and a large part of the screen is grey blocks.
The top of the screen the first 5% has the least distortion.

signal strength with femon looks like this:
rpq@rpq-OptiPlex-960:~$ femon -a 1 -f 1
FE: Silicon Labs Si2183 (DVBS)
status SCVYL | signal 8cf0 | snr b02c | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal 8cf0 | snr b02c | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal 8cf0 | snr b02c | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal 8cf0 | snr b02c | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal 8cf0 | snr b02c | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal 8cf0 | snr acf8 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

I can, if beneficial, provide similar information for NPO1, different frequency, and polarisation. The result is the same.

I can receive and watch SBS6, NPO1 and others on the TBS6991.
One thing to note is that for the TBS6991 card I have to set Ask-cam in Mumudvb config file, which seems to indicate
that the channels - although scrambled - are advertised in the stream as FTA. That is how I read the mumudvb manual, on that specific option.

I apologise for the extensive explanation of what I have done. I hope that the comparison helps to indicate
what I am missing in the set up to get the TBS6590 to work as well or better than the TBS6991 does.

I fully expect and hope that you would require more specific detail, and you can get access to this box if that would help
in diagnosing the problem.

Your help and further analyses is very much appreciated, because I am at a dead end at this moment.
BlueSkyThinking
 
Posts: 5
Joined: Sun Nov 11, 2018 8:59 pm

Re: TBS6590 and Cam module on Dutch encrypted services

Postby xiaocao » Mon Sep 16, 2019 5:20 pm

hi ,

please set this pids and test

pmt_pid =
service_id =
pids = pcr_pid video_pid audio_pid
xiaocao
 
Posts: 64
Joined: Tue Jun 25, 2013 5:48 pm

Re: TBS6590 and Cam module on Dutch encrypted services

Postby BlueSkyThinking » Tue Sep 17, 2019 5:52 pm

Hi,

Thanks for responding to the issue that I raised.

Going on the suggestion I presumed you were referring to the mumudvb config file.
I implemented your suggestion, adding service_id=6090 to the mumu configuaration file.

this section
Code: Select all
#channel specifics
new_channel
name=PQ3
unicast_port=8001
pids=2490 526 106
pmt_pid=2490
#only for scrambled channels
cam_ask=1

becomes this
Code: Select all
#channel specifics
new_channel
name=PQ3
unicast_port=8001
service_id=6090
pids=2490 526 106
pmt_pid=2490
#only for scrambled channels
cam_ask=1

Unfortunately that did not resolve the issue.

Starting mumdvb lists this. Indicating succesfull descramble
Code: Select all
Deb1:  TS:  GOOD service_id for PMT 2490 and channel "PQ3"
Info:  CAM:  Received new PMT - sending to CAM...
Info:  CAM:  CA PMT (ADDED) sent for channel 0 : "PQ3"
Info:  Main:  Channel "PQ3" is now partially unscrambled (43% of scrambled packets). Card 1
Info:  Main:  Channel "PQ3" is now fully unscrambled (0% of scrambled packets). Card 1

Opening VLC to watch the stream, I get the same top of 5% of the screen best visible, not perfect, the rest grey-ish blocks.

On the message screen of VLC there are the same type of errors listed at a constant high rate.
Snippet of the sort of errors below
Code: Select all
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 7, expected 6) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 3, expected 2) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 9, expected 8) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 14, expected 13) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 12, expected 11) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 4, expected 3) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 7, expected 6) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 12, expected 11) for PID 18
ts error: libdvbpsi (PSI decoder): TS discontinuity (received 0, expected 15) for PID 18


Compiling the open source driver is challenging, it fails a lot on the make step for me.
I am most likely to be successful in compiling over the weekend in a strange way.
I managed to catch some of the warnings I get.

The last successful compile with warnings from scratch - that is including a complete new download from git - was from Saturday September 14th 2019
I moved from Ubuntu 18.04 to 19.04 in the hope that it could resolve the issue. Unfortunately it did not.
These are the modules that raise a warning during the make step.
Going on the names, some seem to relate to TBS drivers or driver components.
    tbs_priv.c
    tbsecp3-dvb.c
    tbsecp3-asi.c
    tbs_pcie.c
    tbs_pcie-sdi.c
    tbsmod.c
and a few others.
I don't know which modules I need for the TBS6590 card, so this might well be unimportant.
I can list the warnings if you believe this would be helpful.

I hope you will give further assistance to determine the cause of the issue.
Please let me know if you need more specific information.
Thanks.
BlueSkyThinking
 
Posts: 5
Joined: Sun Nov 11, 2018 8:59 pm


Return to TBS6590 Multi Standard Dual Tuner Dual CI PCI-e Card

Who is online

Users browsing this forum: No registered users and 1 guest