Focus SAT on Cardsharing: Setup Guide & Troubleshooting

If you're trying to decode focus sat channels through a cardsharing line and getting nothing but a black screen, you're probably missing one or two specific config details that most guides skip entirely. I've seen people chase signal issues for hours when the real problem was a wrong provider ID in oscam.server. This guide covers the full chain — satellite position, encryption details, OScam and CCcam config, and a proper diagnostic flow so you can actually tell what's broken.

What Focus SAT Is and How It Is Encrypted

Focus SAT is a Romanian pay-TV DTH platform. It's been operating for years on Eutelsat 16°E, offering a mix of general entertainment, news, and premium channels aimed at Romanian-speaking audiences. Some legacy content historically appeared on Hot Bird 13°E as well, but 16°E is the primary position you need to lock in 2026.

The platform uses a Nagravision-class conditional access system (CAS). If you're looking at it in a channel scan, you'll see it flagged as Nagra or NDS-adjacent depending on your receiver firmware. The key point: it is not FTA, and it does rotate encryption material — which means EMM forwarding is not optional if you want stable long-term decoding.

Satellite Position and Footprint

Primary position: Eutelsat 16°E. The footprint covers central and eastern Europe well — Romania, Moldova, Bulgaria, Hungary, Serbia. If you're further west (Germany, France), signal levels drop and you'll need a larger dish. South of the footprint (North Africa) you're borderline even with an oversized dish.

The 13°E position (Hot Bird) carries some older or simulcast content but is not the main platform. Don't assume your 13°E setup gives you access to the full Focus SAT package — it doesn't.

Encryption System and CAID

Focus SAT runs on Nagravision 3 (sometimes listed as Nagra 3). The CAID range you're looking for falls in the 1830–183F hex range (Nagra 3 family). When you scan a live channel in OScam logs, you'll see ECM packets tagged with one of these CAIDs. The exact CAID active on a given transponder can shift with platform updates, so always confirm by reading your /tmp/ecm.info on a channel that's currently on air.

Do not confuse Nagra 2 (CAID range 1800–181F) with Nagra 3. They look similar in some UIs but the emulation profile and key handling are different. Wrong CAID = the ECM request goes nowhere.

Provider IDs and Card Type

Focus SAT uses specific provider IDs under the Nagra 3 CAS umbrella. These are 3-byte hex values that identify the operator. You'll need to match these exactly in your OScam ident field and in your CCcam line's filter block. The card type is a standard Nagra 3 smart card — not a CAM-only setup, which is why CAM modules from other platforms don't help here. Cardsharing requires the actual card to be present somewhere in the chain and the ECMs routed correctly.

Because Nagra 3 rotates ECM keys and issues EMMs to update card state, any reader in the chain that strips EMMs will eventually cause the card to fall behind on key material. After a key change, you'll see roughly 10–30 seconds of decoding followed by a freeze — classic EMM-not-propagated symptom.

Required Hardware, LNB and Transponder Setup

Before touching config files, confirm you're actually receiving signal from 16°E. Half the "cardsharing doesn't work" reports I've seen are actually "dish isn't pointed right" problems.

Dish Size and LNB Skew for 16°E

Minimum 80 cm offset dish for reliable reception in Romania, Bulgaria, or Hungary. If you're in Germany or Austria — go 90 cm or larger. A universal Ku-band LNB works fine; no special LNB needed for Focus SAT.

LNB skew matters more than most people realize. At 16°E, skew is typically positive (clockwise when viewed from the front) across most of eastern Europe. Check a skew calculator with your exact coordinates — being 15° off skew can cost you 3–4 dB, which is the difference between a stable lock and rain-fade dropouts.

Key Transponders and SR/FEC Values

I won't list specific frequencies here because transponder plans change and I'm not going to have you type in stale data. Get the current TP list from a satellite chart database like KingOfSat or lyngsat, search for Eutelsat 16°E, and find the Focus SAT cluster. You're looking for DVB-S2 transponders, typically 8PSK or QPSK, with symbol rates in the 27500–30000 range and 3/4 or 5/6 FEC. Always do a fresh scan rather than entering manual TPs unless you've verified the values are current.

After scanning, open your signal meter on one of the Focus SAT transponders before you do anything else. You want SNR above 10 dB (ideally 12+ dB) and BER under 1e-5. If you're not hitting those numbers, the cardsharing config is irrelevant — fix the dish first.

DiSEqC and Motorized Setups

If you're combining 16°E with 13°E (Hot Bird) using a multifeed bracket, you'll need DiSEqC 1.0 to switch between LNBs. Configure port A for your primary position and port B for the secondary. On Enigma2, this is in Menu → Setup → Service Searching → Tuner Configuration.

One practical problem with multifeed setups: the bracket skew is a compromise. You can't optimize skew for both 16°E and 13°E simultaneously. In practice, Focus SAT on 16°E works fine in clear weather on a multifeed, but during moderate rain fade the 1–2 dB skew penalty can push you below threshold. A dedicated dish for 16°E is the cleaner solution if Focus SAT is your main target.

Motorized setups (DiSEqC 1.2 / USALS) don't have this problem — the dish tracks to the correct position and skew. But motor positioning takes a few seconds, which is annoying if you're switching between 13°E and 16°E frequently.

OScam Configuration for Focus SAT

OScam is the right tool for this. It gives you logging, CAID filtering, EMM control, and dvbapi priorities that CCcam simply doesn't expose in the same way. If you're getting intermittent decoding with CCcam and want to actually diagnose it, switching to OScam is the first step.

oscam.server Reader Block

Here's the structure you need in /etc/oscam/oscam.server:

[reader]label = focus_sat_lineprotocol = cccamdevice = your.provider.host,12000user = your_usernamepassword = your_passwordgroup = 1caid = 1830,1831,1833ident = 1830:PPPPPP,1831:PPPPPPaudisabled = 0emmcache = 1,3,21ecmcache = 0reconnect = 30connectoninit = 1

Replace PPPPPP with the actual provider ID hex values for Focus SAT. The ident field is the one most people get wrong — if you put the wrong provider ID here, OScam will find no matching reader for Focus SAT ECMs even if the line is perfectly healthy. The ECM request just falls through silently.

Keep caid narrow. Don't set it to 1800-18FF just to be safe — that catches everything Nagra-related and slows ECM routing. Specify only the CAIDs you've confirmed are active on Focus SAT transponders.

oscam.user and Group Mapping

In /etc/oscam/oscam.user, your local receiver user needs to be in the same group as the reader above:

[account]user = receiver_userpwd = receiver_passgroup = 1caid = 1830,1831,1833au = focus_sat_line

The au line tells OScam which reader should forward EMMs for this user. Without it, EMMs don't propagate and your decoding fails after the next key change. This is probably the single most commonly misconfigured field for Focus SAT.

oscam.dvbapi CAID/ProvID Priorities

This is the part most guides completely ignore. Your receiver's dvbapi needs to know to route Focus SAT channels to the cardsharing reader, not to an internal CI module or software CAM. In /etc/oscam/oscam.dvbapi:

P: 1830:PPPPPPP: 1831:PPPPPPP: 1833:PPPPPP

The P: priority lines force OScam to try these CAID:ProvID combinations first. Without explicit priorities, if your receiver has an internal CI slot with any card in it, dvbapi may route the ECM to the CI first, get no answer, and only then fall back to cardsharing — or just give up. The result looks like "no decoding" even though your cardsharing line is fine.

If you're on a VU+ or Dreambox and you've installed a software CI module (like a Softcam), make sure it's not also claiming Nagra 3 CAIDs. They'll conflict with your cardsharing reader.

Enabling EMM and AU

In oscam.server on the reader, audisabled = 0 enables EMM forwarding. Pair it with emmcache = 1,3,21 — this caches EMMs (value 1), with a minimum cache count of 3, and a 21-hour expiry. Don't disable emmcache thinking it saves resources; without it, repeated EMM lookups hit the card harder and decoding becomes less stable during key transitions.

Restart OScam after any change to these files: systemctl restart oscam or /etc/init.d/oscam restart depending on your image. Then watch /var/log/oscam/oscam.log in real time with tail -f while switching to a Focus SAT channel.

CCcam.cfg Setup for Focus SAT

If you're running pure CCcam rather than OScam, configuration is simpler but you lose a lot of diagnostic capability. Still, it works for straightforward setups.

CLine Syntax and Slot Order

In /etc/CCcam.cfg, your CLine looks like this:

C: your.provider.host 12000 username password

Some providers send you a line with a fifth parameter — a reshare block like { 0 0 0 0:0:1 }. Include it exactly as provided. That block controls resharing behaviour on your local CCcam server. The values matter — 0 0 0 means no local resharing, which is what you want if you're just a client.

Slot order in the config file matters when you have multiple CLines. CCcam tries them in order. Put your best line (lowest latency, most reliable) first. If your Focus SAT line is second or third, and the first line is timing out, you'll see 1–2 second gaps before decoding kicks in.

SID Assign / SID Block

CCcam lets you force specific channels to specific lines using SID assignments:

SID ASSIGN ON: 1234 5678

This is useful when you have multiple lines and one of them doesn't have rights for Focus SAT but CCcam keeps trying it anyway. Block it explicitly:

SID BLOCK ON: 1234

Use the actual SID (service ID) values from your channel list. In Enigma2, you can find these in the service info screen (typically accessible via the Info button while a channel is selected).

Cache and Hop Limits

CCcam's built-in cache can mask problems. If a key is cached from a previous decrypt session and has since changed (EMM key rotation), CCcam serves the stale key and you get 5–10 seconds of video then a freeze. If you're debugging, temporarily set cache size to 0 to rule this out.

Hop count is the other thing to watch. Most provider lines are hop 1 (direct card) or hop 2 (one reseller). If your line is hop 2 or higher, EMMs are often stripped at the intermediate node — the line will decode initially but fail after a key change because the card never receives the EMM update. If your provider can't tell you the hop count, treat it as suspicious.

Troubleshooting: Black Screen, Freezes and 'No Signal' on Focus SAT

Here's how to actually diagnose focus sat decoding problems instead of randomly changing settings. Work through this in order.

Step 1: Confirm Signal Quality First

On your Enigma2 box, open the signal meter (usually Menu → Information → Signal) while tuned to a Focus SAT transponder. If SNR is below 9 dB or BER is above 1e-4, you have a signal problem — not a cardsharing problem. No amount of OScam tweaking fixes a bad dish alignment. Sort the RF side first.

ECM Time > 2000 ms — What to Do

Read /tmp/ecm.info while tuned to a Focus SAT channel. You'll see something like:

Reader: focus_sat_lineCAID: 1830ProvID: PPPPPPECMtime: 1840ms

ECM times above 1500 ms cause visible freezes and audio dropouts. Above 2000 ms is garbage — you'll see maybe 2 seconds of video, then a freeze, then 2 seconds, etc. The causes are: geographic distance to the server (high base latency), server overload (latency spikes), or network jitter on your ISP.

Latency vs. load: if your ping to the server is 80 ms but ECM time is 1800 ms, the card is under load — the queue is backed up. If ping is 220 ms, the geographic distance is the problem. Different solutions: for load, get a different line; for distance, ask if the provider has a node closer to you.

One edge case that's a pain to diagnose: ISPs with high jitter. Average ECM time might show 400 ms but the 99th percentile is 2200 ms. Your log will show mostly fast ECMs with occasional 2000 ms spikes — and those spikes cause freezes every few minutes. Run ping -c 200 your.provider.host and look at the max value, not the average.

Channel Decodes Briefly Then Freezes

This is almost always the EMM/AU problem described above. The sequence: card has the current key → ECM decodes → key rotates → EMM is not forwarded to update card → card is now behind → ECM answers with old key → decoder shows garbage → freeze.

Fix: confirm audisabled = 0 in oscam.server, confirm the au field in oscam.user points to the right reader label, confirm your provider line actually forwards EMMs (hop 1 direct lines do; some hop 2 reseller lines strip them). If you can't confirm EMM forwarding with your provider, you can watch OScam logs for lines starting with EMM — you should see them periodically on active channels.

Wrong CAID Picked by dvbapi

Symptom: channel shows 'encrypted', OScam log shows no ECM activity at all, but your signal is fine. This means dvbapi isn't routing the ECM to OScam — something else is intercepting it first (CI module, software CAM, or dvbapi is just ignoring the channel's CAID).

Check /etc/oscam/oscam.dvbapi — make sure the P: priority lines for the Focus SAT CAID:ProvID are present. Then check that the dvbapi port in oscam.conf matches what Enigma2's software emulator is connecting to (default is 9001, but it varies by image). Restart both OScam and the enigma2 process after changes.

EMM Rejected / Card Not Updating

OScam logs EMM outcomes. Look for lines like EMM rejected by reader or EMM written. If you see consistent rejections, either the provider ID in the EMM doesn't match what the reader expects, or the upstream card genuinely doesn't receive EMMs (stripped at a reseller hop). This is a provider-side problem — you can't fix it in your local config. Either get a line with EMM support confirmed, or accept that decoding will fail after each key rotation.

Signal Quality vs. Card Sharing Issue

This distinction trips up a lot of people. If channels freeze regardless of which channel you tune to, and it happens on FTA channels too — it's a signal or receiver problem. If freezes happen only on encrypted channels, only on specific CAIDs, or only on Focus SAT specifically — it's the cardsharing config. And if FTA channels are perfect but Focus SAT freezes after 10–15 seconds of initial decoding — that's the EMM key rotation issue, not signal.

One more edge case: if you're on an IPv6-only connection and your provider's server is IPv4-only, and your ISP's NAT64 gateway is flaky, you'll see intermittent ECM timeouts even though pings look fine. Test by forcing IPv4 on your receiver's network config if possible, or connect the receiver directly to a dual-stack segment.

Receiver Firmware Resets dvbapi Priorities

This is an actual bug in some Enigma2 images. After a reboot, the dvbapi config reverts to defaults, losing your P: priority lines. The fix is to make your oscam.dvbapi read-only after configuring it correctly — or to script a restore on boot. Check your image's release notes; some VU+ and Octagon firmware versions from 2024–2025 have this issue. The workaround is to put the dvbapi file in a location that your update script doesn't overwrite.

How to Evaluate a Cardsharing Provider for Focus SAT (Generic Criteria)

Finding a good line for focus sat specifically requires asking the right questions before you hand over any money. Here's what actually matters.

Server Stability and Uptime Metrics

A provider that doesn't publish uptime data is hiding something. Look for a status page or monitoring dashboard — any serious operation runs one. You want to see 99.5%+ uptime over a rolling 30-day window. Below that, you're looking at consistent outages during peak hours. Ask specifically about downtime history for the Nagra 3 CAID — some servers are stable for Viaccess and terrible for Nagra.

ECM Response Time and Geographic Latency

Under 300 ms ECM time is comfortable viewing with no noticeable issues. 300–800 ms causes occasional brief freezes when zapping between channels but is generally watchable. Above 800 ms you'll notice quality issues; above 1500 ms is not usable for live TV. Ask the provider what their ECM response time SLA is, and whether they have nodes geographically distributed. A server in the Netherlands has lower latency to Romania than a server in Singapore does — obvious, but worth stating.

Card Origin Transparency

Direct card means the provider has an actual physical card receiving EMMs from the satellite. Reseller means they're buying a line from someone else. Resellers add hop count and often strip EMMs. Ask directly: "Is this a direct card or a reseller line?" If they can't or won't answer, assume it's a reseller. For focus sat specifically, where EMM propagation is important, a direct card makes a real difference.

Multi-CAID Support and EMM Handling

A competent provider explicitly lists which CAIDs they support and confirms whether EMMs are forwarded for each. For Nagra 3 platforms, EMM forwarding is non-negotiable for stable long-term decoding. If the provider's FAQ doesn't mention EMMs at all, that's a yellow flag. Ask specifically: "Does your line forward EMMs for CAID 183x?" and expect a direct yes/no with an explanation.

Refund and Trial Policy

A 24–48 hour trial before payment is normal for reputable providers. It lets you test ECM times, EMM propagation, and channel coverage for Focus SAT before committing. No trial = take the risk yourself. Some providers offer a 24-hour money-back window — that's also reasonable. Anything that requires full payment upfront with no testing option is a red flag, especially for niche platforms like Focus SAT that not every line covers.