QAM256 channels give errors

[Mark]

Hello,

I'm using a Sundtek MediaTV Digital Home III (EU) with DVB-C (Ziggo, Netherlands) and TVHeadend. With this combination I can watch channels which use QAM64 with no problems, but I cannot watch channels with QAM256.

When I open QAM256 channels I get Continuity counter errors and Transport error indicators in the TVHeadend log file.

May 10 08:51:19 E6410 tvheadend[2568]: TS: Sundtek DVB-C (III)/Ziggo Venlo: 372,000 kHz/Canvas: Transport error indicator, 2939576 duplicate log lines suppressed
May 10 08:51:19 E6410 tvheadend[2568]: TS: Sundtek DVB-C (III)/Ziggo Venlo: 372,000 kHz/Canvas: CA @ #5004: Continuity counter error, 418 duplicate log lines suppressed
May 10 08:51:20 E6410 tvheadend[2568]: TS: Sundtek DVB-C (III)/Ziggo Venlo: 372,000 kHz/Canvas: Transport error indicator, 2946250 duplicate log lines suppressed
May 10 08:51:20 E6410 tvheadend[2568]: TS: Sundtek DVB-C (III)/Ziggo Venlo: 372,000 kHz/Canvas: CA @ #5004: Continuity counter error, 419 duplicate log lines suppressed


When I check the signal level of the MediaTV it looks okay, no errors there:

root@E6410:~# /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [.................................] ( 99%)  BER:      0 FREQ: 372000000  Hz LOCKED: YES SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:      0 FREQ: 372000000  Hz LOCKED: YES SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:      0 FREQ: 372000000  Hz LOCKED: YES SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:      0 FREQ: 372000000  Hz LOCKED: YES SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:      0 FREQ: 372000000  Hz LOCKED: YES SYM: 6875000 MOD: QAM256

Maybe you can tell me if this is a issue with the Sundtek DVC-C stick or do I need to dive into TVHeadend for this problem ?

Mark

[Sundtek]

Can you try to use 6900 as symbolrate? We already opened a ticket at the chip desing house to doublecheck whats best to do here in the future (either Firmwareupdate or just treat 6875 as 6900 in the driver)

[Mark]

Can you try to use 6900 as symbolrate? We already opened a ticket at the chip desing house to doublecheck whats best to do here in the future (either Firmwareupdate or just treat 6875 as 6900 in the driver)

Thanks, that was the solution. I always thought that i wouldn't receive anything when using a wrong symbol rate. But when it's working you don't hear me complain

[Sundtek]

This 6875 -> 6900 Symbolrate issue is currently on our todo list we will definitely update it once it's clarified with the chip manufacturer.
There's no side-effect on the sensitivity but having to set this manually is just not nice, so we have to handle this in order to work correctly.