FAQ
TL;DR: 2 channels were dark — "apart from Polsat 2 and Historia, all channels are working" — fix dark NC+ Cameleon on OSCam by enabling logs, verifying reader settings, and preparing for pairing requirements. [Elektroda, John121212, post #18890412]
Why it matters: This FAQ helps Dreambox/OSCam users with NC+ Cameleon cards diagnose dark channels and understand pairing-driven changes.
Quick Facts
- Receiver/build seen here: Dreambox 7080 HD with OSCam r11577 (11.577). [Elektroda, John121212, post #18892282]
- Typical reader slot setup: protocol=internal, device=/dev/sci0, CAIDs=0100,0B01, mhz=450, cardmhz=2700. [Elektroda, John121212, post #18892088]
- Operator is sealing the system; channels will gradually disappear without pairing ("parka"). [Elektroda, charlee, post #18892316]
- Meaningful diagnostics require OSCam logs; verify card inquiries and matching reader. [Elektroda, n6210, post #18889814]
Why are my NC+ Cameleon channels going dark on OSCam?
The operator is tightening access controls, and channels are being phased to pairing-only. As one expert noted, "you need a special oscam and the so-called 'parka'" configured correctly. Without pairing, affected services stop clearing progressively. Plan for pairing-capable OSCam and proper setup. [Elektroda, charlee, post #18892316]
Which receiver and OSCam version does this thread use as a reference?
The case discussed uses a Dreambox 7080 HD with OSCam 11.577 (r11577). Knowing the exact box and build helps align configs and logs. If your environment differs, note it when asking for help. [Elektroda, John121212, post #18892282]
What base OSCam reader settings were shown for a Cameleon in the internal slot?
Example settings: protocol=internal, device=/dev/sci0, caid=0100,0B01, mhz=450, cardmhz=2700, plus EMM handling entries. These are configuration lines, not logs. Wrong CAIDs or clocking can block ECMs. Confirm your slot path and CAIDs match your card. [Elektroda, John121212, post #18892088]
How do I capture useful OSCam logs when a channel is dark?
Enable logging and reproduce the issue for at least 60 seconds. Include ECM/EMM lines and note the exact channel and time. Share logs with sensitive data redacted so others can see card inquiries and reader matches.
- Enable OSCam webif logging.
- Tune the failing channel 60–120 seconds.
- Copy ECM/EMM lines and channel/time info. [Elektroda, n6210, post #18889814]
Are configuration snippets the same as logs?
No. Config snippets show how OSCam is set, but logs show what happens at runtime. Helpers need logs to see ECM requests, EMMs, and reader matching. As noted, “to nie są logi” when only configs were posted. [Elektroda, vito007, post #18892305]
Why did Polsat go dark today on my setup?
A user reported, “today they also switched off Polsat,” indicating the ongoing rollout reached that service. Expect additional channels to follow as pairing requirements expand. Prepare your pairing-ready setup to maintain access. [Elektroda, John121212, post #18892088]
Only two channels failed at first—what does that tell me?
Initially, two channels (Polsat 2 and Historia) failed while others worked. That pattern suggests a staged migration, not a total outage. Track which services fail and when, then compare against your logs for trends. [Elektroda, John121212, post #18890412]
Do I need “parka” (pairing data) and a specific OSCam build?
Yes. With the system being sealed, you need a pairing-capable OSCam and to enter the required “parka” correctly. “You need a special oscam and the so-called 'parka'” to keep channels clearing. [Elektroda, charlee, post #18892316]
Where can I read more background on the NC+/Canal+ changes?
See the thread linked by a contributor for details on the changeover and implications. It provides context for pairing and OSCam requirements as channels transition. [Elektroda, vito007, post #18889857]
What should I include when asking for help on dark channels?
Provide OSCam logs from the failing channel, plus the channel name and time. Helpers explicitly asked for logs to verify card inquiries and reader matches. Without them, you may just “wait until the other channels disappear.” [Elektroda, n6210, post #18891298]
Will a single setting unlock all NC+ channels in OSCam?
No. There isn’t a universal toggle. The operator’s sealing requires pairing and a suitable OSCam. Without that, more channels will stop clearing over time, regardless of reader tweaks. [Elektroda, charlee, post #18892316]
How do I know if the card is being queried and matched by OSCam?
Check your logs for ECM requests reaching the reader and a matching CAID. If there’s no inquiry or no matching reader, channels stay dark. Confirm CAIDs, device path, and reader assignment. [Elektroda, n6210, post #18889814]
How are EMMs handled in the shared example config?
The example blocks unknown and global EMMs and saves unique and shared EMMs: blockemm-unknown=1, blockemm-g=1, saveemm-u=1, saveemm-s=1. Review your EMM handling so necessary updates aren’t unintentionally filtered. [Elektroda, John121212, post #18892088]
Can I get one-on-one guidance to set this up?
A helper offered to direct the user via private message. If you need individualized steps, request guidance similarly and share your exact box, OSCam build, and logs. [Elektroda, charlee, post #18892428]
