Horizons 85E Setup Guide: CCcam/OScam Reception 2026

Setting up the Horizons 85E satellite reception setup for cardsharing can be a bit tricky, especially when you want to nail down specifics for CCcam and OScam. With a solid understanding of your dish alignment, LNB settings, and configuration paths, you’ll be well on your way to achieving a clean lock. I’ve been through this process several times, and I can assure you, there are some key details you don’t want to overlook.

Dish and LNB Requirements for Horizons 2 at 85.2E

To get started, let’s talk about the dish and LNB setup. The orbital slot you’re targeting is 85.2E, where Horizons 2 is co-located with Intelsat. The coverage for this satellite can vary quite a bit, especially if you’re on the edge of the footprint, which can dictate the size of your dish.

Minimum dish size by region and footprint edge

If you’re located toward the center of the footprint, a 90cm dish should suffice. However, if you’re on the fringes of the coverage area, you’ll want to consider going for a 1.2m or larger dish. I’ve seen users struggle with weak signals using smaller dishes on the edge of the coverage. Always check a footprint map for your specific area to see what’s recommended.

Choosing a universal Ku-band LNB and polarization skew

Look, when it comes to LNBs, a universal Ku-band LNB with a low noise figure is essential. You’ll typically want one that operates at LO frequencies of 9750/10600 MHz. Don't forget about the 22kHz tone for band switching. Additionally, the polarization skew is crucial due to the satellite's inclination — I’ve seen setups fail simply because the skew wasn’t set correctly. A motorized mount can help if you need to adjust for orbital drift.

Setting azimuth, elevation, and LNB skew for 85E

Setting up your dish entails getting the azimuth, elevation, and skew dialed in properly. The azimuth for 85E is approximately 82° to 90° depending on your location. Elevation will vary, but it’s typically between 25° to 35°. Make sure to adjust the LNB skew to match the satellite’s polarization, which may involve some trial and error until you find the sweet spot.

Scanning Transponders and Confirming a Clean Lock

Once your dish is set up, the next step is scanning transponders to confirm you have a solid lock on Horizons 2. You can manually add transponders to ensure your dish is pointed correctly, which is crucial for the Horizons 85E satellite reception setup for cardsharing.

Reference transponders for verifying alignment

For verifying alignment, you can use transponders like 12615 V 30000 3/4 or 12661 H 30000 3/4. Enter these manually into your receiver to see if you can pick them up. If you’re getting a lock on these, you’re most likely aligned correctly.

Reading SNR, AGC, and BER on Enigma2 receivers

When checking signal quality, focus on the SNR (Signal to Noise Ratio), AGC (Automatic Gain Control), and BER (Bit Error Rate). Aim for an SNR above 8 dB for stability, with BER ideally at zero or close to it. If your signal quality is fluctuating, it may indicate misalignment or interference.

Blind scan vs manual transponder entry

I’ve found blind scanning can sometimes lead to picking up adjacent satellites if you’re not careful. It’s often better to enter a known transponder manually first, confirm you have a lock, and then proceed with a blind scan if needed.

Configuring CCcam for 85E Channels

Now, let’s get into CCcam configuration. This part is crucial for the Horizons 85E satellite reception setup for cardsharing. You’ll need to edit your CCcam configuration file, typically found at /etc/CCcam.cfg or /var/etc/CCcam.cfg, depending on your image.

CCcam.cfg client line syntax and fields

Your C: line in the CCcam.cfg should look something like this: C: hostname port username password. Make sure you include the two DES key fields, even if they’re left as default for initial setups. CCcam listens on port 12000 for the web interface, which is handy for monitoring.

F-lines, C-lines, and reader priority

F-lines and C-lines are essential for configuring clients. Ensure your priority is set correctly, especially if you have multiple readers. The web info page will show you the status of your connections, so keep an eye on it to ensure everything's working smoothly.

Verifying ECM/EMM flow and share reception

Once you’ve set up your CCcam, check the ECM (Entitlement Control Message) flow. Low ECM time is key to avoiding freezes. If your channels are freezing, it’s often a result of high ECM decode times or network saturation. Use the web interface to check these values regularly.

Configuring OScam for 85E Channels

Next up is OScam configuration, which is equally important for ensuring a stable reception setup. The config directory is usually found at /etc/tuxbox/config/oscam/ or /var/etc/oscam.server depending on your image.

oscam.server, oscam.conf, and oscam.user layout

Your oscam.server file will need the [reader] block setup with protocol=cccam, device=hostname:port, user, and password. The oscam.conf file will define your global settings, while oscam.user will manage your users and access levels.

Adding a cccam-protocol reader and CAID/ident filters

When adding a CCcam-protocol reader, be sure to include CAID and ident filters to route only the relevant channels to the correct reader. This can help mitigate any unnecessary load on your server.

Reading the OScam web interface log for ECM status

The OScam web interface is invaluable for monitoring your ECM status. Here, you can see how quickly ECM messages are being processed and identify any issues that arise. If you notice high decode times, it may indicate a problem with your connection or the share itself.

Troubleshooting No Lock, Freezing, and ECM Errors

Finally, if you're experiencing issues like no lock or freezing, it’s time to troubleshoot. Start with checking your cabling and LNB power. I can’t stress enough how often these simple checks fix the problem. After that, confirm your 22kHz/DiSEqC settings if you're using a multi-satellite setup.

Signal present but no lock — polarization and LO issues

If you’re getting a signal but no lock, this could be due to incorrect polarization or local oscillator settings. Verify that your LNB is correctly skewed. I’ve had issues in the past where a minor adjustment made all the difference.

Channel opens then freezes — ECM timeout and network latency

If channels open but then freeze, look at your ECM timeout settings. High latency or jitter in your network can cause these issues, especially if you’re sharing with multiple peers. Check the load on your share and make sure it’s not overloaded.

Reader connects but no decode — CAID/provider mismatch

If your reader connects but there’s no decode, ensure that the CAID and provider identifiers match what the share is carrying. Often, the specific package or tier for a channel might not be included in your share, leading to frustration when trying to access certain content.