TBSDTV Community Forum

by **xfileslv** » Tue Sep 18, 2012 1:06 am

Hello.

Why is Symbol Rate is 44950 all channels from this transporder get many CC errors ?
Please help.

My tests in software astra and getstream a84.

Code: Select All Code: OS : Linux Slackware 13.37 x86 Kernel : 2.6.34.12 TBS drivers : last current version.. Motherboard : Intel DP67BG Bios last version.

Test 1 :
Topology :
Input D (adapter0) connected to satellite 53E 11044:V:44950 (max is 45k)
Input C (adapter1) connected to satellite 53E 11161:V:5785
Input B (adapter2) connected to satellite 13E 10815:H:27500
Input A (adapter3) connected to satellite 13E 11566:H:27500

if i take all channels from 4 inputs (A-3,B-2,C-1,D-0) - i get many CC in input D (adapter0)
if i take only channels from only 1 input (D-0) - no CC, all works perfect no problem (adapter0)
if i take channels from 2 inputs (D-0,C-1) - no errors, all works perfect no problem (adapter0 and adapter1)
if i take channels from 3 inputs (D-0, C-1, B-2) - no errors, all works perfect (adapter 0, adapter 1 and adapter 2)
if i take channels from 3 inputs (D-0, C-1, D-3) - no errors, all works perfect (adapter 0, adapter 1 and adapter 3)
if i take channels from 3 inputs (D-0, B-2, D-3) - i get many CC in input D (adapter0), others inputs work without CC (adapter 0, adapter 2 and adapter 3)
if i take channels from 3 inputs (C-1, B-2, D-3) - no errors, all works perfect (adapter 1, adapter 2 and adapter 3)

Result : problem in input D (adapter0) where Symbol Rate is 44950.

Test 2 :
I change topology :
*Input D (adapter0) connected to satellite 13E 11566:H:27500
Input C (adapter1) connected to satellite 53E 11161:V:5785
Input B (adapter2) connected to satellite 13E 10815:H:27500
*Input A (adapter3) connected to satellite 53E 11044:V:44950

this same CC errors but in input A (adapter3) where Symbol Rate is 44950.

Test 3:
I change topology :
Input D (adapter0) connected to satellite 13E 11566:H:27500
Input C (adapter1) connected to satellite 53E 11161:V:5785
Input B (adapter2) connected to satellite 13E 10815:H:27500
*Input A (adapter3) connected to satellite 4,8E 11843:H:27500

Result: NO CC!!!

Code: Select All Code: # femon -H -a 0 status 1f | signal 74% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK # femon -H -a 1 status 1f | signal 74% | snr 78% | ber 0 | unc 0 | FE_HAS_LOCK # femon -H -a 2 status 1f | signal 49% | snr 65% | ber 0 | unc 0 | FE_HAS_LOCK # femon -H -a 3 status 1f | signal 49% | snr 92% | ber 0 | unc 0 | FE_HAS_LOCK

Code: Select All Code: tbs6982fe: module license 'TurboSight Proprietary: www.tbsdtv.com' taints kernel. Disabling lock debugging due to kernel taint SAA716x TBS 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 SAA716x TBS 0000:07:00.0: setting latency timer to 64 IR NEC protocol handler initialized IR RC5(x) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized Registered IR keymap rc-tbs-nec input: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.4/0000:07:00.0/rc/rc0/input1 rc0: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.4/0000:07:00.0/rc/rc0 DVB: registering new adapter (SAA716x dvb adapter) input: MCE IR Keyboard/Mouse (saa716x) as /devices/virtual/input/input2 IR MCE Keyboard/mouse protocol handler initialized lirc_dev: IR Remote Control driver registered, major 253 TurboSight TBS 6984 Frontend 0 Attaching... rc rc0: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 0 IR LIRC bridge handler initialized TurboSight TBS6984 DVB-S2 card port0 MAC=00:22:ab:90:1a:d4 DVB: registering adapter 0 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 1 Attaching... TurboSight TBS6984 DVB-S2 card port1 MAC=00:22:ab:90:1a:d5 DVB: registering adapter 1 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 2 Attaching... TurboSight TBS6984 DVB-S2 card port2 MAC=00:22:ab:90:1a:d6 DVB: registering adapter 2 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 3 Attaching... TurboSight TBS6984 DVB-S2 card port3 MAC=00:22:ab:90:1a:d7 DVB: registering adapter 3 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... SAA716x TBS 0000:08:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 SAA716x TBS 0000:08:00.0: setting latency timer to 64 Registered IR keymap rc-tbs-nec input: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.5/0000:08:00.0/rc/rc1/input3 rc1: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.5/0000:08:00.0/rc/rc1 input: MCE IR Keyboard/Mouse (saa716x) as /devices/virtual/input/input4 rc rc1: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 1 DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 0 Attaching... TurboSight TBS6984 DVB-S2 card port0 MAC=00:22:ab:90:1a:d0 DVB: registering adapter 4 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 1 Attaching... TurboSight TBS6984 DVB-S2 card port1 MAC=00:22:ab:90:1a:d1 DVB: registering adapter 5 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 2 Attaching... TurboSight TBS6984 DVB-S2 card port2 MAC=00:22:ab:90:1a:d2 DVB: registering adapter 6 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 3 Attaching... TurboSight TBS6984 DVB-S2 card port3 MAC=00:22:ab:90:1a:d3 DVB: registering adapter 7 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... SAA716x TBS 0000:09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 SAA716x TBS 0000:09:00.0: setting latency timer to 64 Registered IR keymap rc-tbs-nec input: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.6/0000:09:00.0/rc/rc2/input5 rc2: saa716x IR (TurboSight TBS 6984) as /devices/pci0000:00/0000:00:1c.6/0000:09:00.0/rc/rc2 input: MCE IR Keyboard/Mouse (saa716x) as /devices/virtual/input/input6 rc rc2: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 2 DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 0 Attaching... TurboSight TBS6984 DVB-S2 card port0 MAC=00:22:ab:90:1a:dc DVB: registering adapter 8 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 1 Attaching... TurboSight TBS6984 DVB-S2 card port1 MAC=00:22:ab:90:1a:dd DVB: registering adapter 9 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 2 Attaching... TurboSight TBS6984 DVB-S2 card port2 MAC=00:22:ab:90:1a:de DVB: registering adapter 10 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)... DVB: registering new adapter (SAA716x dvb adapter) TurboSight TBS 6984 Frontend 3 Attaching... TurboSight TBS6984 DVB-S2 card port3 MAC=00:22:ab:90:1a:df DVB: registering adapter 11 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...

Code: Select All Code: # lsmod Module Size Used by tbsfe 681 12 isl6423 1855 0 ir_lirc_codec 3623 0 tbs6984fe 67655 12 lirc_dev 7659 1 ir_lirc_codec ir_mce_kbd_decoder 3642 0 ir_sony_decoder 1735 0 ir_jvc_decoder 1861 0 rc_tbs_nec 872 0 ir_rc6_decoder 2213 0 ir_rc5_decoder 1733 0 ir_nec_decoder 2213 0 saa716x_tbs_dvb 34897 0 tbs6928fe 9036 1 saa716x_tbs_dvb tbs6922fe 10696 1 saa716x_tbs_dvb rc_core 12679 12 ir_lirc_codec,ir_mce_kbd_decoder,ir_sony_decoder,ir_jvc_decoder,rc_tbs_nec,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder,saa716x_tbs_dvb saa716x_core 34095 35 saa716x_tbs_dvb dvb_core 73024 2 saa716x_tbs_dvb,saa716x_core i2c_algo_bit 4239 1 saa716x_tbs_dvb tbs6618fe 7277 1 saa716x_tbs_dvb tbs6991fe 9548 1 saa716x_tbs_dvb stv090x 53457 1 saa716x_tbs_dvb tbs6680fe 7277 1 saa716x_tbs_dvb tbs6982fe 11143 1 saa716x_tbs_dvb i2c_core 13875 12 isl6423,tbs6984fe,saa716x_tbs_dvb,tbs6928fe,tbs6922fe,saa716x_core,i2c_algo_bit,tbs6618fe,tbs6991fe,stv090x,tbs6680fe,tbs6982fe

by **xfileslv** » Tue Sep 18, 2012 1:09 am

Code: Select All Code: 07:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 02) Subsystem: Device 6984:0013 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f3400000 (64-bit, non-prefetchable) [size=1M] Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [50] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [74] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Vendor Specific Information: Len=50 <?> Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=088 <?> Kernel driver in use: SAA716x TBS Kernel modules: saa716x_tbs-dvb 08:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 02) Subsystem: Device 6984:0013 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at f3300000 (64-bit, non-prefetchable) [size=1M] Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [50] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [74] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Vendor Specific Information: Len=50 <?> Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=088 <?> Kernel driver in use: SAA716x TBS Kernel modules: saa716x_tbs-dvb 09:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 02) Subsystem: Device 6984:0013 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at f3200000 (64-bit, non-prefetchable) [size=1M] Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [50] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [74] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Vendor Specific Information: Len=50 <?> Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=088 <?> Kernel driver in use: SAA716x TBS Kernel modules: saa716x_tbs-dvb

Code: Select All Code: BIOS Information Vendor: Intel Corp. Version: BGP6710J.86A.2209.2012.0717.2302 Release Date: 07/17/2012 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 0.0 Firmware Revision: 0.0 Handle 0x0007, DMI type 2, 20 bytes Base Board Information Manufacturer: Intel Corporation Product Name: DP67BG Version: AAG10491-401 Serial Number: _______________ Asset Tag: Base Board Asset Tag Features: Board is a hosting board Board is replaceable Location In Chassis: Base Board Chassis Location Chassis Handle: 0x0008 Type: Unknown Contained Object Handles: 0

by **cody** » Tue Sep 18, 2012 1:58 am

it's hard to tell the exact reason for the issue - i myself have tested 6984 with 4 x 90 Mbps input without any issues and that's why it's not related to the data-rate, i.e. it's not capacity issue with the card. so, i have possible few ideas:

* more data rate at the same time means more power consumption from the card. so, one possibility is that power performance of your computer goes down in your tests scenario and that adds some noise to the tuners due to bad power supply and in such case the highest data-rate signal is affected, because it's most fragile to noise

* the other option - again, in your scenario the interference between 4 tuners could cause noise that affects the 11044:V:44950 frequency, which maybe could be avoided if the signal on that frequency is stronger. however, that idea i see as less feasible, because you provided signal statistics in Linux on your logs.

so, one thing i suggest to try that might work is in your test scenario try to lock 11044 with few MHz offset, i.e. +/- few MHz, example 11042, 11046, etc just some close frequencies around 11044 and see if that improves the performance in case the issue is related to your LNB. also, you can try the same idea with the symbol rate: instead 44950 use 44948, 44952, etc again just some close values around 44950 and check if that gives better performance. that's the only ideas i have at the moment.

by **xfileslv** » Tue Sep 18, 2012 2:49 am

Hello cody, thanks for reply.

cody Wrote:* more data rate at the same time means more power consumption from the card. so, one possibility is that power performance of your computer goes down in your tests scenario and that adds some noise to the tuners due to bad power supply and in such case the highest data-rate signal is affected, because it's most fragile to noise

power supply 600W is ok ? maybe you can recommended ?

cody Wrote:so, one thing i suggest to try that might work is in your test scenario try to lock 11044 with few MHz offset, i.e. +/- few MHz, example 11042, 11046, etc just some close frequencies around 11044 and see if that improves the performance in case the issue is related to your LNB. also, you can try the same idea with the symbol rate: instead 44950 use 44948, 44952, etc again just some close values around 44950 and check if that gives better performance. that's the only ideas i have at the moment.

ok, i try check it.

by **cody** » Wed Sep 19, 2012 1:09 am

600W seems OK to me, but another thing except what i already suggested: you shows the CC errors in Windows with TSReader and all the rest of your logs are from Linux. so, do you have the same problem in Linux or you observed it only in Windows?

by **xfileslv** » Wed Sep 19, 2012 2:22 am

Hi.
i checked, power is 650W so for test i replace to 750W - tomorrow start test .. (maybe bad power supply in 600w)
About CC, yes, in linux this same errors in logs, getstream or astra software have output http, my PC where TSreader is connected to this PC in protocol http for get fully detail TS ( you can see in screenshot "Source : HTTP" )

by **xfileslv** » Wed Sep 19, 2012 9:17 pm

cody Wrote:it's hard to tell the exact reason for the issue - i myself have tested 6984 with 4 x 90 Mbps input without any issues and that's why it's not related to the data-rate, i.e. it's not capacity issue with the card. so, i have possible few ideas:

cody Wrote:* more data rate at the same time means more power consumption from the card. so, one possibility is that power performance of your computer goes down in your tests scenario and that adds some noise to the tuners due to bad power supply and in such case the highest data-rate signal is affected, because it's most fragile to noise

Replace power supply to 750W - not help, this same cc errors

cody Wrote:* the other option - again, in your scenario the interference between 4 tuners could cause noise that affects the 11044:V:44950 frequency, which maybe could be avoided if the signal on that frequency is stronger. however, that idea i see as less feasible, because you provided signal statistics in Linux on your logs.

yes, signal is good and no ber.

Code: Select All Code: status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 84% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 86% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 86% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 86% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 86% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 84% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 83% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 83% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 84% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 83% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 83% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 83% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 85% | ber 0 | unc 0 | FE_HAS_LOCK status 1f | signal 74% | snr 84% | ber 0 | unc 0 | FE_HAS_LOCK

cody Wrote:so, one thing i suggest to try that might work is in your test scenario try to lock 11044 with few MHz offset, i.e. +/- few MHz, example 11042, 11046, etc just some close frequencies around 11044 and see if that improves the performance in case the issue is related to your LNB. also, you can try the same idea with the symbol rate: instead 44950 use 44948, 44952, etc again just some close values around 44950 and check if that gives better performance. that's the only ideas i have at the moment.

checked, not help, this same cc errors.

log from astra software

Code: Select All Code: Sep 19 16:09:46: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:09:51: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:09:56: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:01: INFO: ready:true bitrate:61936Kbit/s Sep 19 16:10:06: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:11: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:16: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:21: WARNING: [CC error] 181:2 47:3 Sep 19 16:10:26: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:10:31: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:10:36: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:41: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:46: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:10:51: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:10:56: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:01: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:06: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:06: WARNING: [CC error] 47:4 Sep 19 16:11:11: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:11:16: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:16: WARNING: [CC error] 44:3 Sep 19 16:11:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:21: WARNING: [CC error] 38:5 181:3 191:2 Sep 19 16:11:26: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:31: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:36: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:11:41: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:11:46: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:11:51: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:11:56: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:12:01: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:12:06: INFO: ready:true bitrate:61767Kbit/s Sep 19 16:12:06: WARNING: [CC error] 35:2 55:3 Sep 19 16:12:11: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:12:16: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:12:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:12:21: WARNING: [CC error] 171:2 44:4 Sep 19 16:12:26: INFO: ready:true bitrate:61767Kbit/s Sep 19 16:12:31: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:12:36: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:12:41: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:12:46: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:12:51: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:12:56: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:01: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:06: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:11: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:13:11: WARNING: [CC error] 41:3 171:3 181:5 55:4 Sep 19 16:13:16: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:13:16: WARNING: [CC error] 41:4 44:6 Sep 19 16:13:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:26: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:13:31: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:36: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:41: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:46: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:13:51: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:13:56: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:01: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:06: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:11: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:14:16: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:16: WARNING: [CC error] 48:2 Sep 19 16:14:16: INFO: [analyze TS] CC: ERROR Sep 19 16:14:17: INFO: [analyze TS] CC: OK Sep 19 16:14:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:21: WARNING: [CC error] 36:3 48:3 Sep 19 16:14:26: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:14:31: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:36: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:14:36: WARNING: [CC error] 44:7 55:6 Sep 19 16:14:41: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:46: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:51: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:14:56: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:01: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:15:06: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:15:11: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:15:15: INFO: [analyze TS] CC: ERROR Sep 19 16:15:16: INFO: [analyze TS] CC: OK Sep 19 16:15:16: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:15:16: WARNING: [CC error] 201:3 202:3 Sep 19 16:15:21: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:21: WARNING: [CC error] 41:5 44:9 201:4 Sep 19 16:15:26: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:15:31: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:36: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:41: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:46: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:15:51: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:15:56: INFO: ready:true bitrate:62273Kbit/s Sep 19 16:15:56: WARNING: [CC error] 41:6 47:6 Sep 19 16:16:01: INFO: ready:true bitrate:62294Kbit/s Sep 19 16:16:06: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:16:11: INFO: ready:true bitrate:61757Kbit/s Sep 19 16:16:16: INFO: ready:true bitrate:62283Kbit/s Sep 19 16:16:21: INFO: ready:true bitrate:62283Kbit/s

I for test change to other motherboard model intel, this same errors in previous motherboard.
For test i removed disecq - works directly : this same errors in CC.

Maybe you have others idea ?

I take harmonic preview 7000 for test, connect to this transponder, no errors, no cc.

by **crazycat** » Wed Sep 19, 2012 9:45 pm

This common problem for dual demod IC's (6984 use 2x dual demod CX24117). If you want good performance at high bitrates (SR>30000Ks) - need use only one demod path.

by **xfileslv** » Thu Sep 20, 2012 12:21 am

crazycat Wrote:This common problem for dual demod IC's (6984 use 2x dual demod CX24117). If you want good performance at high bitrates (SR>30000Ks) - need use only one demod path.

hmm. but in @cody work 4 inputs and one input is 90Mbps, so this is not problem in demod CX24117, totaly 1 dual demod CX24117 (2 inputs) get 180Mbps

cody Wrote:it's hard to tell the exact reason for the issue - i myself have tested 6984 with 4 x 90 Mbps input without any issues and that's why it's not related to the data-rate, i.e. it's not capacity issue with the card. so, i have possible few ideas:

@Added :

xfileslv Wrote:if i take channels from 3 inputs (D-0, B-2, D-3) - i get many CC in input D (adapter0), others inputs work without CC (adapter 0, adapter 2 and adapter 3)
if i take channels from 3 inputs (C-1, B-2, D-3) - no errors, all works perfect (adapter 1, adapter 2 and adapter 3)

if i correct understand adapter0 and adapter1 this is one dual demon CX24117.
so, if correct, you can see my first post where i test inputs...

by **xfileslv** » Fri Sep 21, 2012 2:25 pm

any idea ?

TBSDTV Community Forum

Problem in DVB-S QPSK

Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Re: Problem in DVB-S QPSK

Who is online