Moderator Control Panel ]

ISDB-T under linux - TBS6814 not working properly

ISDB-T under linux - TBS6814 not working properly

Postby nrm » Tue Nov 22, 2016 2:11 am

Hi ,

I've been trying to lock ISDB-T signal but so far I'm only able to lock DVB-T. I'm using dvblast 3.1. All I get is a DVB: lock status is 00.
I remember using a x8227 board from geniatech and changing nothing at all to make the ISDB work. Plain DVB-T settings would work.

I suppose there's something missing in dvblast to set ISDB-T under the 6522 board. Does anyone have any clue?

Thank you
Last edited by nrm on Sat Nov 26, 2016 1:58 am, edited 1 time in total.
nrm
 
Posts: 34
Joined: Tue Jan 29, 2013 3:39 am

Re: ISDB-T under linux

Postby nrm » Tue Nov 22, 2016 3:02 am

I always get ahead of myself....

ISDB-T Working flawlessly

./dvblast -a 0 -n 0 -f 497000000 -r /tmp/adapter4.sock -5 ISDBT -b 6 -m qam_64 -G 16 -r /tmp/adapter1.sock
DVBlast 3.1 (git-3.0-15-g12a1eb9-dirty)
warning: restarting
debug: compiled with DVB API version 5.10
debug: using DVB API version 5.10
debug: Frontend "TurboSight TBS 6522 DVB-S/S2/DVB-T/T2/C " supports:
debug: frequency min: 42000000, max: 870000000, stepsize: 0, tolerance: 0
debug: symbolrate min: 1000000, max: 45000000, tolerance: 0
debug: capabilities:
debug: INVERSION_AUTO
debug: FEC_1_2
debug: FEC_2_3
debug: FEC_3_4
debug: FEC_5_6
debug: FEC_7_8
debug: FEC_AUTO
debug: QPSK
debug: QAM_16
debug: QAM_32
debug: QAM_64
debug: QAM_128
debug: QAM_256
debug: QAM_AUTO
debug: TRANSMISSION_MODE_AUTO
debug: GUARD_INTERVAL_AUTO
debug: HIERARCHY_AUTO
debug: 2G_MODULATION
debug: MULTISTREAM
debug: FE_CAN_MUTE_TS
debug: delivery systems:
debug: DVBT
debug: DVBT2
debug: DVBC_ANNEX_A
debug: ISDBT
debug: DVBC_ANNEX_B
debug: ISDB stuff
debug: tuning ISDB-T frontend to f=497000000 bandwidth=6 inversion=-1 fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_64 guard=16 transmission=-1
warning: failed opening CAM device /dev/dvb/adapter0/ca0 (No such file or directory)
debug: setting filter on PID 0
debug: setting filter on PID 16
debug: setting filter on PID 17
debug: setting filter on PID 18
debug: setting filter on PID 19
debug: setting filter on PID 20
error: no config file
debug: frontend has acquired signal
debug: frontend has acquired carrier
debug: frontend has acquired stable FEC
debug: frontend has acquired sync
info: frontend has acquired lock
lock status: 1
debug: - Bit error rate: 0
debug: - Signal strength: 0
debug: - SNR: 42968
debug: new PAT tsid=32736 version=14
debug: * NIT pid=16
debug: * program number=1024 pid=496
debug: * program number=1025 pid=1008
debug: * program number=1408 pid=8136
debug: * program number=65520 pid=7408
debug: end PAT
debug: new NIT actual networkid=32736 version=3
debug: - desc 40 networkname="4XEl9-0h#0"
debug: - desc fe unknown length=2 value=0301
debug: * ts tsid=32736 onid=32736
debug: - desc 41 service_list sid=1024 type=0x01
debug: - desc 41 service_list sid=1025 type=0x01
debug: - desc 41 service_list sid=1408 type=0xc0
debug: - desc 41 service_list sid=65520 type=0xa4
debug: - desc fa unknown length=4 value=5a5a0f3c
debug: - desc fb unknown length=2 value=0580
debug: - desc cd unknown length=30 value=0142234e2348234b416d39672126456c357e0f0304000401fff0af010580
debug: end NIT
debug: new SDT actual tsid=32736 version=0 onid=32736
debug: * service sid=1024 eit_schedule eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0x1 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=84
debug: - desc cf unknown length=7 value=01fe00f0000400
debug: * service sid=1025 eit_schedule eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0x1 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=84
debug: - desc cf unknown length=3 value=02fe00
debug: * service sid=1408 eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0xc0 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=88
debug: - desc cf unknown length=10 value=030e4e484b0f215d0e47
debug: end SDT
^Cinfo: Shutdown was requested.

./dvblastctl -r /tmp/adapter1.sock fe_status
type: OFDM
name: TurboSight TBS 6522 DVB-S/S2/DVB-T/T2/C
frequency_min: 42000000
frequency_max: 870000000
frequency_stepsize: 0
frequency_tolerance: 0
symbol_rate_min: 1000000
symbol_rate_max: 45000000
symbol_rate_tolerance: 0
notifier_delay: 0

capability list:
CAN_INVERSION_AUTO
CAN_FEC_1_2
CAN_FEC_2_3
CAN_FEC_3_4
CAN_FEC_5_6
CAN_FEC_7_8
CAN_FEC_AUTO
CAN_QPSK
CAN_QAM_16
CAN_QAM_32
CAN_QAM_64
CAN_QAM_128
CAN_QAM_256
CAN_QAM_AUTO
CAN_TRANSMISSION_MODE_AUTO
CAN_GUARD_INTERVAL_AUTO
CAN_HIERARCHY_AUTO
CAN_MUTE_TS
CAN_2G_MODULATION
CAN_MULTISTREAM

status:
HAS_SIGNAL
HAS_CARRIER
HAS_VITERBI
HAS_SYNC
HAS_LOCK

Bit error rate: 0
Signal strength: 61008
SNR: 41000
nrm
 
Posts: 34
Joined: Tue Jan 29, 2013 3:39 am

Re: ISDB-T under linux

Postby nrm » Tue Nov 22, 2016 3:07 am

I also have a TBS6814 in the same setup, but that one doesn't work properly. It happens both with the TBS drivers and the Open source drivers.
A lot of discontinuities and errors trying to lock the same frequency.

Crazycat can you help me? In this example I'm using a Ubuntu 16.04 with latest upstream TBS open source drivers.

./dvblast -a 5 -n 0 -f 497000000 -r /tmp/adapter4.sock -5 ISDBT -b 6 -m qam_64 -G 16 -r /tmp/adapter1.sock
DVBlast 3.1 (git-3.0-15-g12a1eb9-dirty)
warning: restarting
debug: compiled with DVB API version 5.10
debug: using DVB API version 5.10
debug: Frontend "Turbosight TBS 6814 (Quad ISDB-T)" supports:
debug: frequency min: 76000000, max: 858000000, stepsize: 166667, tolerance: 0
debug: symbolrate min: 0, max: 0, tolerance: 0
debug: capabilities:
debug: INVERSION_AUTO
debug: FEC_1_2
debug: FEC_2_3
debug: FEC_3_4
debug: FEC_5_6
debug: FEC_7_8
debug: FEC_AUTO
debug: QPSK
debug: QAM_16
debug: QAM_64
debug: QAM_AUTO
debug: TRANSMISSION_MODE_AUTO
debug: GUARD_INTERVAL_AUTO
debug: HIERARCHY_AUTO
debug: FE_CAN_RECOVER
debug: FE_CAN_MUTE_TS
debug: delivery systems:
debug: ISDBT
debug: ISDB stuff
debug: tuning ISDB-T frontend to f=497000000 bandwidth=6 inversion=-1 fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_64 guard=16 transmission=-1
warning: failed opening CAM device /dev/dvb/adapter5/ca0 (No such file or directory)
debug: setting filter on PID 0
debug: setting filter on PID 16
debug: setting filter on PID 17
debug: setting filter on PID 18
debug: setting filter on PID 19
debug: setting filter on PID 20
error: no config file
warning: transport_error_indicator on pid 17 (SDT, sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: TS discontinuity on pid 17 expected_cc 13 got 11 (SDT, sid 0)
warning: transport_error_indicator on pid 17 (SDT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 9 got 1 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 7 got 11 (EPG, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
debug: new PAT tsid=32736 version=14
debug: * NIT pid=16
debug: * program number=1024 pid=496
debug: * program number=1025 pid=1008
debug: * program number=1408 pid=8136
debug: * program number=65520 pid=7408
debug: end PAT
debug: new NIT actual networkid=32736 version=3
debug: - desc 40 networkname="4XEl9-0h#0"
debug: - desc fe unknown length=2 value=0301
debug: * ts tsid=32736 onid=32736
debug: - desc 41 service_list sid=1024 type=0x01
debug: - desc 41 service_list sid=1025 type=0x01
debug: - desc 41 service_list sid=1408 type=0xc0
debug: - desc 41 service_list sid=65520 type=0xa4
debug: - desc fa unknown length=4 value=5a5a0f3c
debug: - desc fb unknown length=2 value=0580
debug: - desc cd unknown length=30 value=0142234e2348234b416d39672126456c357e0f0304000401fff0af010580
debug: end NIT
warning: TS discontinuity on pid 0 expected_cc 10 got 2 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 15 got 10 (EPG, sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: TS discontinuity on pid 18 expected_cc 11 got 1 (EPG, sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: TS discontinuity on pid 18 expected_cc 2 got 12 (EPG, sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: TS discontinuity on pid 0 expected_cc 3 got 14 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 13 got 9 (EPG, sid 0)
warning: TS discontinuity on pid 0 expected_cc 7 got 11 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 12 got 4 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 13 got 15 (EPG, sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 5 got 6 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 8 got 11 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 0 got 10 (EPG, sid 0)
warning: TS discontinuity on pid 17 expected_cc 12 got 15 (SDT, sid 0)
debug: new SDT actual tsid=32736 version=0 onid=32736
debug: * service sid=1024 eit_schedule eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0x1 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=84
debug: - desc cf unknown length=7 value=01fe00f0000400
debug: * service sid=1025 eit_schedule eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0x1 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=84
debug: - desc cf unknown length=3 value=02fe00
debug: * service sid=1408 eit_pf running=0
warning: couldn't convert from to UTF-8 (Invalid or incomplete multibyte or wide character)
debug: - desc 48 service type=0xc0 provider="" service="▒El5~"
debug: - desc c1 unknown length=1 value=88
debug: - desc cf unknown length=10 value=030e4e484b0f215d0e47
debug: end SDT
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: invalid EIT section received on PID 18
error type: invalid_eit_section pid: 18
warning: TS discontinuity on pid 16 expected_cc 6 got 7 (NIT, sid 0)
warning: transport_error_indicator on pid 16 (NIT, sid 0)
warning: transport_error_indicator on pid 20 (TDT/TOT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 4 got 1 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: transport_error_indicator on pid 19 (..., sid 0)
warning: transport_error_indicator on pid 18 (EPG, sid 0)
warning: TS discontinuity on pid 0 expected_cc 2 got 8 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 9 got 0 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 0 expected_cc 2 got 12 (PAT, sid 0)
warning: transport_error_indicator on pid 0 (PAT, sid 0)
warning: TS discontinuity on pid 18 expected_cc 13 got 0 (EPG, sid 0)

Also...no status
./dvblastctl -r /tmp/adapter1.sock fe_status
type: OFDM
name: Turbosight TBS 6814 (Quad ISDB-T)
frequency_min: 76000000
frequency_max: 858000000
frequency_stepsize: 166667
frequency_tolerance: 0
symbol_rate_min: 0
symbol_rate_max: 0
symbol_rate_tolerance: 0
notifier_delay: 0

capability list:
CAN_INVERSION_AUTO
CAN_FEC_1_2
CAN_FEC_2_3
CAN_FEC_3_4
CAN_FEC_5_6
CAN_FEC_7_8
CAN_FEC_AUTO
CAN_QPSK
CAN_QAM_16
CAN_QAM_64
CAN_QAM_AUTO
CAN_TRANSMISSION_MODE_AUTO
CAN_GUARD_INTERVAL_AUTO
CAN_HIERARCHY_AUTO
CAN_MUTE_TS
CAN_RECOVER

status:
nrm
 
Posts: 34
Joined: Tue Jan 29, 2013 3:39 am

Re: ISDB-T under linux - TBS6814 not working properly

Postby PortalNET » Tue May 29, 2018 10:26 pm

Problem seems to be its detecting TBS6814 isdbt AS OFDM and OFDM is standar DVB v3 for DVB-T and T2

i am facing the same issues here for ISDBT front end type code needs to be changed as its specified on the ISDBT standards not shure if the linux drivers are correct will need to check.
PortalNET
 
Posts: 13
Joined: Sat May 19, 2018 6:57 am


Return to TBS6522 Multi-standard Dual Tuner PCI-e Card

Who is online

Users browsing this forum: No registered users and 4 guests

cron