Focus Sat Setup Guide: CCcam & OScam Configuration 2026

Getting focus sat channels working on an Enigma2 box sounds straightforward — point the dish, scan, configure the server line, done. In practice, most people hit a wall at the config stage because the scattered documentation online either shows the wrong CAID, skips the provider ID entirely, or just says "check your settings" without telling you which file and which line. This guide covers the actual parameters you need, the config syntax that works, and how to read your logs when things go wrong.

What Is Focus Sat and Which Satellite Carries It

Focus Sat is a Romanian DTH (direct-to-home) satellite platform, one of the largest pay-TV operators in Romania. The service broadcasts on the Thor satellite cluster operated by Telenor, positioned at 0.8°W / 1.0°W. If you're in Central or Eastern Europe, this position is accessible with a modest dish. If you're further west or southwest, you'll need a larger dish and clear sky conditions.

Satellite Orbital Position and Footprint Coverage

The Thor satellites — Thor 5, 6, and 7 — are co-located at roughly 0.8°W to 1.0°W. They are not identical in terms of transponder assignments and beam patterns. Thor 6 (1.0°W) carries the main Focus Sat transponders. For a motorized dish with USALS, use 1.0°W as your primary target position. Enter this exactly, because entering 0.8°W vs 1.0°W produces a slightly different motor position that can cost you 1-2dB on weaker transponders.

The core footprint covers Romania, Moldova, parts of Bulgaria, Hungary, and Serbia. Signal strength peaks over Romania — Bucharest sits almost in the center of the beam. At the fringe: Poland, Western Germany, Greece, and Turkey can receive the signal, but margins are tighter.

Channel Lineup Overview and Language Packages

Focus Sat carries Romanian general entertainment, news, sports, kids, and cinema channels. There are also international channels in the package — Discovery, National Geographic, Eurosport — redistributed under Romanian licenses. The platform runs both SD and HD services, with an increasing number of HEVC/H.265 encoded HD channels. That last point matters for older receivers, which I'll get to in the troubleshooting section.

Encryption System Used (CAID Identification)

Focus Sat uses Conax conditional access. The primary CAID is 0B00. On some transponders and service groups you'll also see 0B01 — this is also Conax, a slightly different variant. For your sharing server config, 0B00 is what you need to target first. If certain channels remain scrambled after getting 0B00 working, add 0B01 as well.

This is the detail most guides skip: "Conax encryption" tells you almost nothing useful. The actual CAID value is what your CCcam or OScam config must reference. Without it in the right place, the server either doesn't request ECMs for the channel at all, or requests them under the wrong encryption system.

Dish Size Requirements by Region

In Romania and immediate neighboring countries: a 60cm offset dish is the minimum, and it works fine in good weather. In fringe areas (Western Poland, Austria, Eastern Germany, Northern Greece), go to 80-90cm. Rain fade is the main practical issue — Thor at 1°W is a relatively weak signal compared to Astra 19.2°E, and a small dish loses 2-3dB during heavy rain, which can drop you below the decoding threshold on weaker transponders even when signal looks fine on screen.

Transponder Frequencies and Channel Scanning

The Focus Sat multiplex on Thor runs across several Ku-band transponders. Here's a working set as of early 2026 — these do occasionally change, so run a blind scan afterwards to catch anything new.

Full Transponder List with Frequency, Polarization, Symbol Rate, FEC

LNB local oscillator frequencies: 9750 MHz (low band, below 11700 MHz) and 10600 MHz (high band, above 11700 MHz). Any standard Universal Ku-band LNB covers this. The 22kHz tone switches automatically between bands on Enigma2 receivers.

Blind Scan vs Manual Transponder Entry

Blind scan is slower but catches everything — including transponders that were added after any guide was written. On OpenATV or OpenPLi, go to Menu > Setup > Service Searching > Blind Scan, select the Thor 1.0°W satellite, and let it run. It typically takes 4-8 minutes per satellite position. The downside: blind scan sometimes produces duplicate or misnamed channel entries that you'll need to clean up.

Manual entry is faster when you just need to add one or two specific transponders. Use the table above as your source.

Adding Transponders Manually on Enigma2

On OpenATV/OpenPLi: Menu > Setup > Service Searching > Manual Scan. Select satellite position, enter frequency (11258 for example), set polarization (H), symbol rate (27500), FEC (3/4), and hit Scan. The receiver will lock and add found services. Some images have this under Menu > Setup > Service Searching > Transponder Edit instead — the path varies between image versions.

Verifying Signal Quality (SNR, BER Thresholds)

Target SNR of at least 10dB for reliable decoding. Anything below 8dB is marginal — you'll get picture but rain will knock it out. For BER (bit error rate), keep it below 1×10⁻⁷. Values above 1×10⁻⁶ mean you're getting uncorrectable errors and the picture will break up even with good "signal strength" shown on screen. Check both SNR and BER — the signal strength bar many receivers show is nearly useless for fine-tuning. Use the SNR value.

LNB skew is frequently overlooked on Thor. Because 1.0°W is almost due south for users in Central Europe, the polarization angle can be slightly off, costing 1-2dB. On a motorized setup, adjust the LNB rotational position (skew) while watching a weak transponder's SNR in real time.

Configuring CCcam for Focus Sat Channels

CCcam config file location depends on the receiver image. Common paths:

• /var/etc/CCcam.cfg — OpenATV, OpenPLi, most mainstream images
• /usr/keys/CCcam.cfg — older Gemini images and some OE 2.0 builds
• /etc/CCcam.cfg — some Vu+ specific images

Check which path your image uses before editing. On OpenATV: find / -name "CCcam.cfg" 2>/dev/null will find it immediately.

CCcam.cfg Syntax for Adding a Remote Server Line

The C: line connects your box to a remote sharing server:

C: hostname.example.com 12000 myusername mypassword

Format is: C: <host> <port> <username> <password>. The port is whatever your server provider gives you — common ports are 12000, 12001, 12010, and 15000. Some servers use non-standard ports to avoid firewall issues. Use the exact credentials provided — CCcam is case-sensitive on both username and password.

Optional keepalive setting (add near the top of the config):

CWS_KEEPALIVE = 1

This prevents the TCP connection from being dropped by NAT firewalls during quiet periods.

F: Line vs C: Line Format Explained

The C: line connects to a remote CCcam server over the CCcam protocol. The F: line is for Newcamd protocol connections (different protocol, different port range). Focus Sat servers typically use CCcam protocol (C: lines). If your server gave you credentials with a port in the 10000-11000 range and mentions "Newcamd", use the F: line format instead:

F: hostname.example.com 10000 myusername mypassword 01 02 03 04 05 06 07 08 09 10 11 12 13 14

The 14 pairs at the end are the Newcamd key — your server provider supplies this. If you mix up C: and F: lines (wrong protocol for the server type), CCcam will show the connection as "handshake failed" in the log.

CAID and Provider ID Filters (I: and B: Lines)

To tell CCcam to only request ECMs for Conax (focus sat CAID), add an I: line:

IGNORE: 0000:000000PROVIDE: 0B00:000000

Or using the shorter syntax some CCcam versions support:

I: 0B00

The B: line blocks specific CAIDs. If you're on a multi-provider server and only want Focus Sat traffic, this cuts noise and speeds up ECM routing. Provider ID filtering (the six hex digits after the colon) is where many setups fail — if your server filters by provider ident and you leave it as 000000 (wildcard), it should still work, but some server configs require the exact ident. The correct Focus Sat provider ident under CAID 0B00 is typically in the range 020810 — verify this in your CCcam web info page against what the server actually reports.

Reading the CCcam Web Info Page to Confirm Card Availability

Open a browser and navigate to http://<receiver-ip>:16001. The info page shows connected servers, cards available, and — this is the critical part — the entitlement list for each card.

What you're looking for: under the server you added, expand the card list. You should see a CAID entry for 0B00 with provider IDs listed below it. If the server shows as connected but there's no 0B00 in the card list, the server doesn't carry Focus Sat. The channel will stay scrambled even though the connection status looks green. This is the most common misdiagnosis — "connected" does not mean "has the right card."

Restarting CCcam After Config Changes

On OpenATV/OpenPLi using the standard softcam init script:

/etc/init.d/softcam restart

Or force-kill and restart:

killall -9 CCcam && sleep 2 && CCcam -d

CCcam takes about 10-15 seconds to reconnect to remote servers after restart. Wait before declaring that your config change didn't work.

Configuring OScam for Focus Sat Channels

OScam is split across multiple config files, which is both its strength (granular control) and the reason it frustrates people on first setup. The main files you'll touch: /etc/oscam/oscam.server, /etc/oscam/oscam.user, and /etc/oscam/oscam.dvbapi. Some images store these under /usr/etc/oscam/ or /etc/tuxbox/config/.

oscam.server Entry for a CCcam or Newcamd Reader

For a CCcam protocol reader connecting to a remote server:

[reader]label = focus_sat_cccamprotocol = cccamdevice = hostname.example.com,12000user = myusernamepassword = mypasswordcaid = 0B00ident = 0B00:020810group = 1inactivitytimeout = 30reconnecttimeout = 10

The ident line restricts this reader to only handle ECMs for CAID 0B00 with provider ident 020810 (Focus Sat). Without this restriction, OScam might route ECMs to the wrong reader and you'll get slow response times or failures. The group = 1 ties the reader to user accounts that also specify group = 1.

For Newcamd protocol:

[reader]label = focus_sat_newcamdprotocol = newcamddevice = hostname.example.com,10000user = myusernamepassword = mypasswordkey = 0102030405060708091011121314caid = 0B00group = 1

oscam.user File Permissions and AU Settings

The dvbapi user (what your receiver uses to request decryption) lives in oscam.user:

[account]user = local_dvbapipassword = group = 1au = 1caid = 0B00

Set au = 1 only if you need entitlement updates (EMM processing). For straightforward ECM-only operation, au = 0 is cleaner and reduces server load. Many users set au = 1 automatically without understanding what it does — it tells OScam to forward EMMs from the server to your local config, which is only useful if you have a physical card locally.

oscam.dvbapi Priority Lines for Forcing CAID/Provider

This is the file most guides completely skip, and it causes problems when multiple CAIDs are present on the same SID. Add a priority line for Conax:

P: 0B00:000000

Or with the specific provider ident:

P: 0B00:020810

Without a priority line, OScam picks a CAID based on internal ordering, which may not be Conax. On focus sat transponders where both Conax and another CA system show up in the PMT, this priority line ensures OScam always tries 0B00 first. Less guessing, faster ECMs.

Cache Exchange (CSP/CWC) Considerations

OScam supports CW (control word) caching via the cache3 protocol and CWC (control word cache) exchange between OScam instances. If your server supports cache push, add to oscam.conf:

[cache]cachex_mode = clientcachex_host = <server-ip>cachex_port = 14000

Cache exchange can reduce ECM time to near-zero for popular channels because the CW has already been decrypted by someone else. But if your server doesn't offer this, leave the cache section out entirely — misconfigured cache settings cause spurious errors in the log.

Reading OScam Status via Web Interface on Port 8888

OScam's web interface is at http://<receiver-ip>:8888. The "Readers" tab shows your configured readers, their status (connected/offline), and current ECM time. The "Services" tab shows active decryptions with real-time ECM times. Watch the ECM time column — anything consistently above 400ms is a problem. Under 250ms is excellent. If you see values jumping between 50ms and 900ms erratically, that's network jitter, not a server issue per se.

Troubleshooting Black Screen, Freezing, and Scrambled Channels

Most problems fall into one of five categories. Here's how to actually diagnose each one instead of guessing.

Channel Scrambled but Signal Is Fine — CAID Mismatch

Symptom: good SNR (12dB+), channel found, but picture shows "scrambled" or "conditional access error."

Diagnosis: Open CCcam web info (port 16001) or OScam status (port 8888). Look for CAID 0B00 in the reader's entitlement list. If it's missing, the server literally doesn't have the right card — no config change on your end will fix this. You need a server that carries 0B00.

If 0B00 is present but the channel is still scrambled: check the provider ident. Some servers carry Focus Sat but with provider ident filtering that excludes certain channel packages. In OScam log: tail -f /tmp/oscam.log | grep "0B00" — look for "wrong provider" or "filtered" messages.

Freezing Every Few Seconds — High ECM Time or Network Jitter

Symptom: picture works but freezes for 1-2 seconds every 10-30 seconds.

Diagnosis: tail -f /tmp/oscam.log and watch for ECM response times. Lines look like:

2026/05/15 14:23:01 r focus_sat_cccam (0B00&020810/0D2B/XXXX): found (375 ms)

If you're seeing 800ms+ regularly, the freeze is from late CW delivery — the receiver runs out of valid CW before the next one arrives. Fix: either switch to a geographically closer server (lower RTT), or investigate if the freezing correlates with a specific transponder (signal issue) vs happening across all channels (network/server issue).

Also check concurrent connection limits. If the same account is used on two boxes simultaneously, the server may throttle ECMs, causing one box to freeze intermittently while the other works fine.

Some Channels Work, Others Don't — Provider ID Filtering

Symptom: sports channels work, cinema channels scrambled. Or the reverse.

This is almost always a provider ident mismatch. Focus Sat packages different channel groups under different provider IDs, all under CAID 0B00. Some sharing servers carry the base package ident but not the premium cinema ident. Check OScam log for the specific SID of the failing channel:

tail -f /tmp/oscam.log | grep "DENIED\|rejected\|wrong"

If you see "rejected by server" for specific SIDs, the server simply doesn't have entitlement for those channels — regardless of how your config is set up.

Black Screen with Audio — HD Codec or PID Issue, Not Encryption

This one trips up a lot of people. If you have audio but no video on HD channels, the decryption is almost certainly working fine. The receiver is decoding the audio PID but can't handle the video PID because it's HEVC/H.265 and the receiver hardware doesn't support it.

Focus Sat moved several HD channels to HEVC encoding in 2024-2025. Any receiver older than roughly 2018 without hardware HEVC support will show this symptom. Dreambox DM900/DM920, Vu+ Duo 4K, Octagon SF8008 — these handle HEVC. Older Vu+ Duo2, DM800, DM8000 — they don't. You can verify by checking the stream info: if the video codec shows "HEVC" or "H.265" and your box can't play it, that's the end of the diagnosis.

Reading CCcam/OScam Logs to Pinpoint the Failure

CCcam log location: /tmp/CCcam.log or /tmp/log/CCcam.log depending on image. Key patterns to grep for:

grep -i "0B00\|error\|rejected\|denied\|timeout" /tmp/CCcam.log | tail -50

OScam log: /tmp/oscam.log by default. Same grep pattern. Look at timestamps — if errors cluster at a specific time of day (say, 18:00-22:00), the server is overloaded during peak hours, not broken.

How to Choose a Reliable Sharing Server for Focus Sat

The technical criteria matter more than marketing claims. Here's what actually correlates with a working setup.

What Technical Criteria Actually Matter

First: does the server carry CAID 0B00 with Focus Sat provider idents? This is non-negotiable. Ask for a test line and verify this in CCcam web info before paying anything. A server that shows CAID 0B00 in the entitlement list with the correct provider ident will work. One that doesn't, won't — simple as that.

Second: the CCcam protocol version compatibility. OScam and newer CCcam builds use protocol version 2.3. Some older server setups run 2.1 or 2.2. Mismatched versions cause connection failures that look like credential errors. Ask what protocol version the server runs if you're having handshake issues.

Server Uptime and ECM Response Time Benchmarks

Real-world uptime for a well-run server is 98-99.5%. Anyone claiming 100% uptime is lying — hardware fails, networks blip, maintenance windows happen. What matters is how fast they recover from outages and whether they have redundancy.

ECM response time benchmarks to use as your quality bar:

• Under 150ms: excellent, fast enough for instant zapping
• 150-400ms: acceptable, occasional slight delay on channel change
• 400-800ms: marginal, visible freeze on channel change
• Above 800ms: consistently causes picture freezing during key rotation

Measure ECM times during peak viewing hours (19:00-23:00 local time), not at 3am. Peak load is when server quality shows.

Geographic Proximity and Network Latency

A server in Romania or Central Europe will serve Focus Sat ECMs faster than a server in the US or Asia, simply due to network round-trip time. RTT adds directly to ECM time. A server with 20ms RTT vs one with 150ms RTT is 130ms advantage on every single ECM request. For a stream that rotates CW every 10 seconds, this compounds quickly when the server is also under load.

Run a simple ping test to a server's IP before subscribing. Under 30ms is great. 30-80ms is fine. Above 150ms will likely give you marginal ECM times during peak hours.

Red Flags to Avoid When Evaluating Providers

Avoid any setup claiming "unlimited reshares" — this means your ECM request travels through a chain of intermediary servers before reaching an actual card. Every hop adds latency and a failure point. Unlimited reshare setups routinely produce 600ms+ ECM times and cascade failures when one node in the chain drops.

Other red flags: prepayment required for 6-12 months with no trial or test line. A provider confident in their service offers a test line — 24-48 hours is standard. No test line means no accountability. Also avoid providers who don't disclose which CAIDs their server carries — this is a basic technical detail, and if they're vague about it, they're likely overselling capacity they don't have.

Hardware and Network Requirements

Receiver Compatibility (Enigma2, Dreambox, Vu+, Octagon)

Enigma2 is the operating system you want — it's what CCcam and OScam are built for. Compatible receiver families:

• Dreambox: DM900 UHD, DM920, DM7080 — all run OScam natively on OpenATV/DreamOS. Older DM800 and DM8000 work but lack HEVC support.
• Vu+: Duo 4K, Uno 4K, Zero 4K, Ultimo 4K — all supported. OpenATV and VTi images both ship with OScam.
• Octagon: SF8008, SF8008 4K, SX888 — solid Enigma2 boxes, good OScam support on OpenATV and OpenPLi.
• GigaBlue: Quad 4K, UHD Trio — work well with OpenATV.

Images that ship with pre-configured softcam support: OpenATV 7.x, OpenPLi 8.x/9.x, VTi 14.x and newer. On these images, softcam management is through the Plugins menu > Softcam Setup.

Internet Connection Stability and Latency

Raw bandwidth is almost irrelevant — each ECM is a tiny packet exchange. What kills sharing setups is jitter. A 2 Mbps DSL connection with stable 15ms latency works better for cardsharing than a 100 Mbps cable connection with 80ms jitter spikes.

Test your connection quality: ping -i 0.2 -c 100 <server-ip> and look at the min/avg/max values. If max is more than 3× the average, you have jitter. During picture freezing, run this ping test and correlate spikes with freezes — if they match, it's your connection, not the server or config.

Dish, LNB, and DiSEqC Switch Considerations for Thor Satellite

For a multi-satellite setup combining Thor 1°W with other positions, you'll need a DiSEqC switch. Standard committed switch port assignments for a common 4-port setup:

• Port A: Astra 19.2°E (highest-priority, most channels)
• Port B: Hotbird 13.0°E
• Port C: Thor 1.0°W / 0.8°W
• Port D: Spare or Astra 28.2°E

DiSEqC 1.0 switches on certain receiver models (notably some older Dreambox configurations) occasionally lose their port assignments after a power cut. If Thor channels suddenly stop working after a power outage, check the DiSEqC settings before diagnosing anything else. Menu > Setup > Service Searching > Tuner Configuration on Enigma2.

For motorized dish users (DiSEqC 1.2 or USALS), the USALS coordinates for Thor 1.0°W vary by location. For Warsaw, Poland: approximately 174.5° azimuth, 26.5° elevation. For Vienna: approximately 176° azimuth, 33° elevation. Enter your exact longitude/latitude in the USALS setup and the receiver calculates the motor position automatically.

Multi-Satellite Setups: Combining Focus Sat with Hotbird/Astra

Focus Sat on Thor 1.0°W, combined with Hotbird 13.0°E and Astra 19.2°E, is a common setup in Central Europe. With a fixed multi-LNB setup: space the LNBs on the dish arm at angular separations matching the satellite positions relative to your location. Thor to Hotbird spans about 12° of sky, Hotbird to Astra spans another 6.2°. On a 90cm dish this is achievable with standard multi-LNB brackets.

In oscam.server, each satellite position typically maps to a separate reader. You can combine them all on the same server line if the sharing server carries all CAIDs, but keeping them as separate readers with CAID filters per reader makes troubleshooting much cleaner.