black screen whit cccam 2.3.0

[BlueIsMyColor]

Re: black screen whit cccam 2.3.0

In older receivers (e.g. old DBOX2) it is recommended to use Vers. 2.011. The other (newer) versions don't really work there.
In newer receivers many online updates only offer 2.30 or 2.21. On my new receiver I downgraded from 2.30 to 2.21 and have better results (less wrong answers, which are declared as correct answers in webinterface).

How do you check these things?

regards

[Satphoenix]

Re: black screen whit cccam 2.3.0

How do you check these things?

regards

I was watching a football match and perhaps every 3-4 minutes I had a freeze for 6-7 seconds. This means a cw-failure, or the server didn't answer or a short disconnect and cccam connets to another server...
But when I checked the result in cccam-webinterface, it said: 420 (420)

Then I downgraded to 2.21 and the freezes in the second half went nearly to zero.

Then again upgrade to 2.30 (same server, next match) and the freezes came back, downgrade again and better result.

[aplok]

Re: black screen whit cccam 2.3.0

... freezing ...
But when I checked the result in cccam-webinterface, it said: 420 (420)

do you known the meaning of 420 (420) ?

Then I downgraded to 2.21 and the freezes in the second half went nearly to zero.
Then again upgrade to 2.30 (same server, next match) and the freezes came back, downgrade again and better result.

experienced user -> empirical method, trail and test method -> factual conclusions

[Satphoenix]

Re: black screen whit cccam 2.3.0

do you known the meaning of 420 (420) ?

experienced user -> empirical method, trail and test method -> factual conclusions

420 (420) means 420 ecm-request to server and (420) answered ecm = correct controlword for descrambling.
But if only one bit of the 48bit cw is wrong, everything is wrong in the descamblimg algorythm (because of the diffusion-rule in descrambling).
And as it seems I had a wrong answer or wrong descrambling every 3 or 4 minutes. Very disturbing when you watch a film or a high-tension-scene in a football match...

[sjamesamuel]

Re: black screen whit cccam 2.3.0

420 (420) means 420 ecm-request to server and (420) answered ecm = correct controlword for descrambling.
But if only one bit of the 48bit cw is wrong, everything is wrong in the descamblimg algorythm (because of the diffusion-rule in descrambling).
And as it seems I had a wrong answer or wrong descrambling every 3 or 4 minutes. Very disturbing when you watch a film or a high-tension-scene in a football match...

But freezes could be also caused by the delay of receiving the key (eg sky), I wonder if this counts within the answered ecms.

Also some cards may give keys which don't decrypt channels, in which case the receiver stays with this key until a new key from a good card is received.

[gianni253]

Re: black screen whit cccam 2.3.0

But freezes could be also caused by the delay of receiving the key (eg sky), I wonder if this counts within the answered ecms.

You can easily tell if your freeze is due to a wrong cw or a delay:
- in case of delay you will have a temporary glitch
- in case of a wrong cw you will have a freeze that will last until next (good) cw is received (i.e. a freeze lasting at least 10 seconds)

[aplok]

Re: black screen whit cccam 2.3.0

420 (420) means 420 ecm-request to server and (420) answered ecm = correct controlword for descrambling.

... so if i read, after let's say 2 min of initialisation, this:

local 0500:032830 4(0)

that means, 4 requests, 0 answer , and this server.card gains a I: ticket for cccam.prio:

I: 0500:032830

? correct ?

may i say this server is a fake ?
or a so-called fake is a relay server (hop >1) ?
or this server has the card at home (hop=0), but a bad card ?

---

... But if only one bit of the 48bit cw is wrong, everything is wrong

but as the data is tcp protocolled -> data can not be corrupted
... only the connection is udp ...

---
so about your freezing,
i suggest you to monitor

/tmp/ecm.info

along your football match, into a log file

... may be the kids take all the bandwidth at that time ...

[gianni253]

Re: black screen whit cccam 2.3.0

... may be the kids take all the bandwidth at that time ...

420 (420) makes your case quite clear: freezes are only due to cw delays, i.e. cw that is received is good but was received too late.
If you want to double check, put on screen an infobar with ecm time and crypto info ... when freezes occur you should only see a long ecm time but crypto decoding should be always ok (green color or whatever).

[sjamesamuel]

Re: black screen whit cccam 2.3.0

... so if i read, after let's say 2 min of initialisation, this:

local 0500:032830 4(0)

that means, 4 requests, 0 answer , and this server.card gains a I: ticket for cccam.prio:

I: 0500:032830

? correct ?

may i say this server is a fake ?
or a so-called fake is a relay server (hop >1) ?
or this server has the card at home (hop=0), but a bad card ?
...

Not necessarily fake. Sometimes expired cards give this result. Also some providers share the same caid (eg 604), this will give zero as well.