Wicardd Newcamd Reader Setup: Config Guide 2026
If you're diving into the Wicardd newcamd reader setup configuration, you've likely already installed Wicardd and have your server access details at hand. This guide will help you configure the newcamd reader properly so that it connects to a remote newcamd server and decrypts channels reliably. I’ll cover the syntax, port settings, DES key format, and troubleshooting tips to ensure your setup runs smoothly.
What the Newcamd Reader Does in Wicardd
The newcamd reader acts as a client connection to a remote newcamd-serving CAS (Conditional Access System). This protocol is designed to securely transmit control words for decrypting satellite channels. It uses a 14-byte (28 hex character) DES key for the login handshake. Typically, the default TCP ports for newcamd are in the range of 15000 to 15009.
Newcamd protocol basics
Newcamd protocol operates over TCP and transmits encrypted control words using DES. The server sends ECM (Entitlement Control Message) requests, and the reader responds with the corresponding control words. It's essential to ensure that the port and DES key are correctly configured to establish a successful connection.
Where Wicardd fits: emulator vs full softcam
Wicardd functions as an emulator rather than a full-fledged softcam. It does not handle card sharing itself but acts as a bridge to other servers. This distinction is crucial, especially if you're coming from a CCcam or camd35 background, where the roles might seem similar but operate differently.
Reader vs server role — which side you are configuring
It's important to clarify that you're configuring the client-side reader in Wicardd. The reader initiates the connection to the server, requesting access to the control words that allow decryption of the channels. Understanding this role will help you set up the configuration correctly.
Wicardd Newcamd Reader Config: Exact Syntax
The configuration for a newcamd reader in Wicardd follows a specific syntax that you must adhere to for successful operation. The structure of a newcamd reader block in wicardd.conf typically looks like this:
[reader]protocol = newcamd525device = host,portkey = <28 hex DES key>user = your_usernamepassword = your_passwordCAID = your_caidLocating and editing wicardd.conf
Finding your wicardd.conf file is the first step. Depending on your setup, it is usually located at /var/etc/wicardd.conf or within the plugin folder on your Enigma2/DVB receiver. Open the file using a text editor like nano or vi to make your changes.
The [reader] / newcamd block fields explained
Each field in the reader block serves a specific purpose:
- protocol: This specifies the version of the newcamd protocol. Use
newcamd525for most cases, whilenewcamd524is a fallback for some older servers. - device: Here you will input the host and port as
your.host.com,port. - key: The DES key must be a 14-byte key formatted as 28 hexadecimal characters. Ensure it matches exactly with what your server provides.
- user: The username for your newcamd server.
- password: The password associated with your username.
- CAID: The CAID is the identifier for the channel or service you want to access.
DES key, user, password, host, port line by line
When entering the DES key, user, and password, pay attention to detail. Even a single wrong character can cause the connection to fail. Ensure that your host and port correspond to the server settings.
Assigning CAID and provider IDs to the reader
After you've filled in the basic fields, you can assign the CAID and provider IDs. This step ensures that the reader can access the correct channels. If your server supports multiple CAIDs, list them separated by commas in the CAID line.
Verifying the Reader Is Online
Once you've configured the Wicardd newcamd reader setup configuration, it's time to verify whether your reader is online. Enabling verbose logging is a great first step to troubleshoot any issues.
Reading the Wicardd log for handshake success
Check the Wicardd logs for entries indicating a successful DES handshake. Look for messages like "CARD INIT", which shows the reader is communicating with the server properly. If you see these lines, your reader is making progress.
Confirming ECM requests and control word replies
After establishing a handshake, check if ECM requests are being sent and if control words are being received. A healthy newcamd reply typically returns well under 500 ms. If your decode times are significantly higher, you may need to troubleshoot further.
Checking decode time (ms) as a health signal
Monitoring the decode time can help you gauge the health of your connection. If you notice times exceeding 500 ms consistently, it may hint at network issues or server responsiveness problems.
Troubleshooting Common Newcamd Reader Failures
When things go wrong, it's essential to know how to troubleshoot effectively. Here’s a breakdown of common issues and their potential causes.
Reader stuck offline / connection refused
If your reader shows as offline, you may be facing a connection refused error. This typically points to a wrong host or port configuration, or a firewall blocking the connection. Double-check these settings and ensure the port is open on any routers or firewalls in between.
Login OK but channels stay black (CAID mismatch)
When your reader connects but you see black screens, the login was successful, but the decoding is failing. This usually indicates a CAID or provider filter mismatch. Verify that the CAID assigned to your reader corresponds with the channels you are trying to access.
Intermittent freezing and high decode times
If streaming is choppy, you might be experiencing network latency or possibly ECM rate limiting from the server. High jitter or packet loss can result in frustrating freezes. Consider checking your network's performance and making adjustments if necessary.
DES key length and format errors
Be cautious with the DES key; it must be exactly 28 hexadecimal characters. Some servers provide a key with a leading 01 03 00 header, which can lead to confusion. Ensure you format the key as per the server’s instructions.
Choosing a Reliable Newcamd Source (Generic Criteria)
Selecting the right newcamd server is critical for a stable setup. Here are some criteria to consider without naming any specific providers.
Uptime and low-latency ECM response
A good server should have high uptime and low latency in ECM responses. Look for reviews or community feedback that highlights server reliability and responsiveness.
Local vs shared/reshared cards
Understand whether the server uses local or shared cards. Local cards typically offer better performance, while reshared cards may lead to additional latency and potential issues.
Support for the CAIDs you actually need
Make sure the server supports the CAIDs necessary for the channels you want. You can often request a test line to verify if the server meets your needs before committing.
What port does a Wicardd newcamd reader use by default?
Newcamd typically uses TCP ports in the 15000–15009 range; the exact port is defined by the server and must match the device line. Confirm the port is open through any firewall or router.
Why does my newcamd reader show online but channels stay black?
Login succeeded but ECM decoding is failing — usually a CAID/provider filter mismatch, the card not carrying that package, or ECM not being forwarded. Verify the CAID assigned to the reader matches the channel.
What format must the newcamd DES key be in?
It is a 14-byte DES key expressed as 28 hexadecimal characters. Some servers publish it with a leading 01 03 00 header; enter it exactly as the server specifies or the handshake fails.
What is the difference between newcamd524 and newcamd525?
They are protocol revision variants; 525 is the more common modern version. The reader must use the same variant the server expects, otherwise the connection negotiates incorrectly or drops.
Where is the Wicardd config file located?
Path depends on the image/receiver but is commonly under /var/etc/wicardd.conf or the plugin/config directory. Edit the reader block there and restart the Wicardd daemon to apply changes.
Why does my reader connect then immediately disconnect?
Almost always a wrong DES key, username, or password — the DES handshake completes but authentication is rejected. Re-check the key length and credentials character by character.