Bug #3974
open
Added by Mariusz Ch. over 8 years ago.
Updated about 8 years ago.
Found in version:
4.1-2216~gfd7806a-dirty
Description
I use TVheadend version 4.1-2216~gfd7806a-dirty and Oscam version "1.20-unstable_svn Build: r0 Compiler: arm-mv5sft-linux-gnueabi"
on TBS MOI+ IPTV streamer. My MOI+ has dual TBS 6281 DVB-C card and TBS 3102 card reader.
ISSUE:
occasionally (once every few hours) scrambled channel freeze.
The log appears the error "ECM - key late" of the large late time.
It helps to temporarily switch to another channel.
I attach the debug log from TVHeadend, Oscam and CA Configuration in the screenshot.
Files
Jaroslav Kysela wrote:
Provide the full oscam log for 'dvbapi' (debug level 128) for oscam and enable '--trace descrambler,capmt' in tvh. https://tvheadend.org/projects/tvheadend/wiki/Traces
OK, but I have problem with '--trace descrambler,capmt' option in my tvheadend. This option is totally ignored in startup script or web interface. Works only 'all' parameter, but this produce probably a GBits log after a few hours...
Mariusz Ch. wrote:
OK, but I have problem with '--trace descrambler,capmt' option in my tvheadend. This option is totally ignored in startup script or web interface. Works only 'all' parameter, but this produce probably a GBits log after a few hours...
I have 11GB log - '-- debug all --trace all' after 10 night hours. The error "ECM late" occurred after 4 hours...
I have no idea what to do with this file.
OK, attached tvheadend.log cut with scripts:
- the occurrence of the ECM error
- removed from the lines included TRACE: tbl-eit, timeshift, parser, tsfix, htsp-sub, upnp, tbl-base
Additionally full oscam.log with debug level 128.
An answer? Plan? Something I can complement? Problems constantly repeated ...
Could you try to add your CAID (0B00) to "const_cw" section in data/conf/descrambler ?
I added this section:
{
"name" : "Stansat",
"caid" : "0B00"
}
I'll come back with the observations
The error "descrambler: ECM - key late" still occurs.
It's very unlikely. Do you see "adding CAID 0B00 as constant crypto-word" line when you start tvh? Also, provide another traces.
I'm not sure what you're asking. I changed file /tvheadend/data/conf/descrambler adding the section:
{
"name" : "Stansat",
"caid" : "0B00"
}
then restart tvheadend done. What more can I do?
but I had something else earlier in this section and added a new entry as the second. Is that good?
Check tvh log for line in comment 9 .
OK, I understand now.
After allowing only one entry in the "const_cw" section of descrambler file, tvheadend starts with "adding CAID 0B00 as constant crypto-word" option and the ECM key too late problem is resolved.
I have another question what are the options "adding CAID XXXX as quick ECM"?
Hi,
I have same problem with ECM too late with another caid, when add to "const_cw" section in data/conf/descrambler problem resolved, but my question is to every problematic caid i must add and every new version i must add my problematic caid, can make something to maid code and not make this on every new version ?
Thanks
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 