How To Install Omnikey Reader On Dreambox

**B16MCC** · 26-08-2009

OK guys since writing the tutorial 'How To Setup A Linux PC Card Server' I've been asked a lot if the Omnikey reader was compatible with the Dreambox. Well its seems now it is ! Massive thanks to Jakey !

A pack of drivers / dependency files has surfaced to install the Omnikey to a Mipsel Dreambox. If you don't know a Mipsel dreambox is basically the Enigma2 boxes, DM7025, 800 & 8000. This method is not applicable for the older E1 boxes.
Basically the pack consists of 4 *.ipk installer files which will add the required components to the Dreambox to run the Omnikey USB reader.
Your image will most likely have the ability to install these via your manual install option in the addon panel, however to make sure everything is correct I recommend you install via Telnet and follow this guide below.

FTP the 4 IPK files to your /tmp folder on the dreambox. Then start a telnet session.

1. ipkg install /tmp/libusb_0.1.12-r0_mipsel.ipk

Code:

Installing libusb (0.1.12-r0) to root...
Configuring libusb

2. ipkg install /tmp/pcsc-lite_1.5.5-r0_mipsel.ipk

Code:

Installing pcsc-lite (1.5.5-r0) to root...
Configuring pcsc-lite
 Adding system startup for /etc/init.d/pcscd ...
  /etc/rc2.d/S20pcscd -> ../init.d/pcscd
  /etc/rc3.d/S20pcscd -> ../init.d/pcscd
Starting PCSC Daemon: pcscd.
  /etc/rc4.d/S20pcscd -> ../init.d/pcscd
  /etc/rc5.d/S20pcscd -> ../init.d/pcscd
  /etc/rc0.d/K20pcscd -> ../init.d/pcscd
  /etc/rc1.d/K20pcscd -> ../init.d/pcscd
  /etc/rc6.d/K20pcscd -> ../init.d/pcscd

3. ipkg install /tmp/libpcsclite1_1.5.5-r0_mipsel.ipk

Code:

Installing libpcsclite1 (1.5.5-r0) to root...
Configuring libpcsclite1

4. ipkg install /tmp/ccid_1.3.11-r0_mipsel.ipk

Code:

Installing ccid (1.3.11-r0) to root...
Configuring ccid

So, once all this is in place, connect the USB reader and set it up in NewCS as normal. The reader type is
<type>pcsc</type>

The node address will be simply
<node>0</node>

If you add a second reader it will be
<node>1</node>

I don't want to take my server offline to test this as its the only Omnikey I have at the moment. I have 2 more coming. If you can test before I do then please do post your comments / findings.

**andel** · 26-08-2009

This is great news.... if it works! Unfortunately im in the same boat as you and am awaiting a reader, will post back as soon as i get the chance to test it

Edit:- installed all the drivers exactly as you stated though

**B16MCC** · 28-08-2009

I took delivery of 2 Omnikey 3121 readers this morning. Having installed everything as stated I plugged in the reader.

The dmesg command via telnet reports the following.

Code:

hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002
ohci_hcd 0000:00:14.2: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS
hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
ohci_hcd 0000:00:14.2: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS
usb 1-1: new full speed USB device using ohci_hcd and address 2
ohci_hcd 0000:00:14.2: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS
usb 1-1: ep0 maxpacket = 8
usb 1-1: skipped 1 descriptor after interface
usb 1-1: default language 0x0409
usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: Smart Card Reader USB
usb 1-1: Manufacturer: OMNIKEY AG
usb 1-1: hotplug
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
usb 1-1:1.0: hotplug
usbserial_generic 1-1:1.0: usb_probe_interface
usbserial_generic 1-1:1.0: usb_probe_interface - got id
hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002

This seems good. Now to setup NewCS and test some cards.

Ok at this point I need to mention something very important !
These readers WILL NOT WORK with the NewCS that you install from your images addon panel. You must use the file named newcs.mips.pcsc

I FTP'd this file to /usr/bin where all the others live, renamed it to newcs_1.67.pcsc and started it via telnet with the following command.

Code:

./newcs_1.67.pcsc -C /var/tuxbox/config/newcs.xml

It works a treat. I've tested the old and new sly cards and an old Conax card I had all working great.

**andel** · 30-08-2009

ok i just got back from a weekend away to find my new reader has arrived. gonna set it up tommorow but can you link me please to the newcs.mips.pcsc file i need?

**andel** · 01-09-2009

i got hold of the file and followed your instructions.
if i type dmesg from telnet I dont get anything refering to USB like you do. Its almost as if its not detecting it. Any thoughts?

Update:- if i use the other usb port i get the following.....

Code:

hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0002
brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [0] = 0x00030100 PESC
C PPS
hub 2-0:1.0: port 1, status 0100, change 0003, 12 Mb/s
usb 2-1: USB disconnect, address 2
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
usb 2-1:1.0: hotplug
usb 2-1: unregistering device
usb 2-1: hotplug
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002
brcm-ehci brcm-ehci.0: GetStatus port 1 status 001002 POWER sig=se0  CSC
hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0004
brcm-ehci brcm-ehci.0: GetStatus port 2 status 001803 POWER sig=j  CSC CONNEC
hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501
brcm-ehci brcm-ehci.0: port 2 full speed --> companion
brcm-ehci brcm-ehci.0: GetStatus port 2 status 003801 POWER OWNER sig=j  CONN
hub 1-0:1.0: port_wait_reset: err = -134
hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0004
brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00010101 CSC
 CCS
hub 2-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101
brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC
S PES CCS
usb 2-2: new full speed USB device using brcm-ohci-0 and address 3
brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC
S PES CCS
usb 2-2: ep0 maxpacket = 8
usb 2-2: skipped 1 descriptor after interface
usb 2-2: default language 0x0409
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: Smart Card Reader USB
usb 2-2: Manufacturer: OMNIKEY AG
usb 2-2: hotplug
usb 2-2: adding 2-2:1.0 (config #1, interface 0)
usb 2-2:1.0: hotplug
hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0004

after this i started using /usr/bin/newcs_1.67.pcsc -C /var/tuxbox/config/newcs.xml

Code:

Reading Config file from /var/tuxbox/config/newcs.xml
NewCS is trying to bind to IP: 192.168.1.64
TCP-log password is enabled, set to: NewCSpwd
TCP-log set to simple mode
level: normal
type: init
output: console,tcp
logger config: level 1 type 3 output 5
Console log options: level 1 type 3
TCP log options: level 1 type 3
[ 17:27:05 ] [ Box detect ] Box type 7 (Dream Multimedia (MIPS) HD Box)
[ 17:27:05 ] [ Config ] Option <Seca-PPV> for device 0 (USB) not present, defaul
ting to NO
[ 17:27:05 ] [ Config ] 1 ECM priority: round
[ 17:27:05 ] [ httpd ] httpd-user: admin, password: admin, accesslevel: admin
[ 17:27:05 ] [ EMM Cache ] Initialising dynamic Cache
[ 17:27:05 ] [ ECM Cache ] Initialising dynamic Cache
[ NewCS ] Process ID is: 1636
[ 17:27:05 ] [ Loader ] Starting Telnet on port 3001
[ 17:27:05 ] [ Loader ] Started HTTP-server on port: 8080
[ 17:27:05 ] [ Loader ] Reader type 9 on node 1

but now i cant connect to the web interface

any ideas?

**B16MCC** · 01-09-2009

Using a different port shouldn't matter of course, but anyway that looks good now.

Make up your newcs.xml and run it. Don't forget the <type> and <node> settings to suite.

**andel** · 01-09-2009

well i have my newcs reader setup as below but that dosnt explain why i cant connect to the web interface, dos it?

Code:

  <readers name="Card Readers">
    <device>
      <name>USB</name>
      <type>pcsc</type>
      <node>1</node>
      <mhz>357</mhz>
      <export>yes</export>
      <enabled>yes</enabled>
      <blocksa>no</blocksa>
      <blockua>no</blockua>
      <blockga>yes</blockga>
      <blockc0>yes</blockc0>
      <boxkey>******</boxkey>
      <PTShandshake>no</PTShandshake>
      <crypto-special>no</crypto-special>
      <carddetect>yes</carddetect>
      <newcamd_port>12678</newcamd_port>
      <priority>round</priority>
    </device>

**B16MCC** · 01-09-2009

andel, that device config looks ok, pretty standard stuff, but you are correct, it has nothing to do with the NewCS web interface setup. You need to check the section of config labeled <httpd>

This is where your web interface is configured.
Also I find a commonly omitted line can stop the web interface working sometimes. Make your newcs.xml start as shown below...

Code:

<newCSconfig>
	<globals>
		<!-- valid value for listening-ip are:
				IPv4 adress of local interface.  -->
		<listening-ip>192.168.1.10</listening-ip>
	</globals>

Obviously enter the correct IP address of your Dreambox.

Check your <httpd> settings and you should be ok.

woodseaves · 01-09-2009

Hi fascinating stuff, just a quickie, what way does the card fit into the omnikey?
I'm struggling but hope to succeed in the end.

Regards

**andel** · 01-09-2009

Originally Posted by woodseaves

Hi fascinating stuff, just a quickie, what way does the card fit into the omnikey?
I'm struggling but hope to succeed in the end.

Regards

after a bit of messing around and asking myself that exact question i realised you put it in upside down compared to your sly box (chip up)

**andel** · 03-09-2009

well after a couple of days messing around and countless reboots I can now access newcs web interface and see my full entitlements I dont fully understand why i couldnt access it before but never mind.
I am only sharing on my local network and was previously using the internal reader and the newcs downloaded from the green panel. I am still using the same newcs.xml (apart from the usb reader part) and the same CCcam.cfg on my DM800 and the same CCcam.cfg that I was using on my DM500...but now i am not getting anything.
When i run CCcam via telnet I see the following

Code:

15:30:53.466 CCcam: cam[0] ecm odd nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:30:53.566 CCcam: cam[0] ecm odd nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:30:53.667 CCcam: newcamd ecm -> 192.168.1.64:60000
15:30:53.766 CCcam: newcamd ecm <- 192.168.1.64:60000 error
15:30:53.767 CCcam: cam[0] ecm odd nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)
15:30:53.866 CCcam: cam[0] ecm odd nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:30:53.967 CCcam: cam[0] ecm odd nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:30:54.071 CCcam: newcamd ecm -> 192.168.1.64:60000
15:30:54.072 CCcam: newcamd ecm <- 192.168.1.64:60000 failure from cache
15:30:54.073 CCcam: cam[0] ecm odd nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)
15:30:54.166 CCcam: cam[0] ecm odd nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:30:54.266 CCcam: cam[0] ecm odd nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:30:54.367 CCcam: newcamd ecm -> 192.168.1.64:60000
15:30:54.367 CCcam: newcamd ecm <- 192.168.1.64:60000 failure from cache
15:30:54.368 CCcam: cam[0] ecm odd nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)
15:30:59.587 CCcam: newcamd ecm -> 192.168.1.64:60000
15:30:59.676 CCcam: newcamd ecm <- 192.168.1.64:60000 error
15:30:59.679 CCcam: client andel ecm request for handler 0x14c1 0x963(0x0) sid 0
x122a ok: 0
15:31:01.567 CCcam: cam[0] ecm even nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:31:01.667 CCcam: cam[0] ecm even nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:31:01.713 CCcam: newcamd server 192.168.1.64:60000 user: andel
15:31:01.729 CCcam: newcamd caid 0963 providers 1 userid: 0
15:31:01.729 CCcam: newcamd card serial:    00000000
15:31:01.730 CCcam: newcamd prov 00 000000  00000000
15:31:01.758 CCcam: newcamd server 192.168.1.64:60000 user: andel
15:31:01.769 CCcam: newcamd ecm -> 192.168.1.64:60000
15:31:01.772 CCcam: newcamd ecm <- 192.168.1.64:60000 connection error
15:31:01.772 CCcam: cam[0] ecm even nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)
15:31:01.800 CCcam: newcamd first read failed 0
15:31:01.802 CCcam: newcamd receive error -1
15:31:01.868 CCcam: cam[0] ecm even nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:31:01.967 CCcam: cam[0] ecm even nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:31:02.067 CCcam: cam[0] ecm even nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)
15:31:02.167 CCcam: cam[0] ecm even nok caid:0x960 id:0x0 pid:0x509 SKY UK (28E)
15:31:02.268 CCcam: cam[0] ecm even nok caid:0x961 id:0x0 pid:0x509 SKY UK (28E)
15:31:02.369 CCcam: cam[0] ecm even nok caid:0x963 id:0x0 pid:0x509 SKY UK (28E)

my client was recieving at hops2 as I never worked out how to recieve at hops1.
I have an F:line in my .cfg and a C:line & N:line in my client .cfg

...any ideas?

Also i noticed if i look at the stats in the web console it says its recieving ECM req's but its not got any ECM Resp with 0% hits, i presume this is relevant tome not getting a pic?

**B16MCC** · 04-09-2009

Andel, you need to simplify this to start with. Let me get this straight, are you using a linux pc and a DM800 ? Why do I see references to 0961 and 0963 ? Do you have old and new card in place here ? If so, remove the old card. Take it out of the equation.

If so, the only thing you need in the CCcam.cfg of the DM800 is an N line.
This N line must match the user you have entered in NewCS on your linux server.

1. Stop CCcam on the DM800 by selecting Common Interface.
2. Kill NewCS in the linux server.
3. Now, start NewCS via telnet / terminal on your server. Wait for the output to report 'Ready to Go'
4. If you don't see this message then there's no point moving on to the Dreambox, you have a problem with your NewCS / Reader / Card.
5. If you see this message then start CCcam on your DM800.
6. Back in the terminal / telnet window you should see the message reporting the DM800 has connected.
7. Now, in the Web Interface you can check entitlements, you can check CAID, and you can check if the DM800 is showing connected.

Check all this and report back, please detail as much information as possible.

**andel** · 05-09-2009

Ok...yesterday I had my stupid head on, today Ive got my clever head on so things are fine.
FYI I was getting all my C's F's and N's in a muddle but I'm learning fast!!!!!
I did have a C line which was looking at a server hosting an old blue card, I think i was starting cccam before newcs which was also giving me problems. So many thanks for your help once again as my white card is now running cool as a cucumber

!

This should be a sticky because for all the people who are worried about the card overheating this is a great solution for around £7

sblinx · 11-09-2009

@B16MCC mate

i've read this thread with some interest. have you only tested with newcs .. do you know if it work with cccam only?
one other question .. do you think it is possible to have both smargo and omnikey inserted in the 8000?

thanks

**B16MCC** · 11-09-2009

The omnikey is a pcsc reader, CCcam doesn't support that. Yes you could have an omnikey in NewCS and a smargo in NewCS or CCcam at the same time.

vampsthevampyre · 14-09-2009

Just finished updating to a white card (once again thanks for your great progs and thread assistance), now its time to try and get my omnikey reader working.

Is it possible to do an idiots guide (me being the idiot) as to how to get this installed.

I'm curently running a nabilosat v0.11 image on a 7025 with newcs 1.66 (i think or 1.65) and cccam 2.1.1, installed from the addon menu.

How do I get the new version of newcs on the box and replace the currently running version and what can I do to check that it is functioning correctly

TIA

Ian

**B16MCC** · 14-09-2009

The idiots guide is this thread. Go back to the beginning of it and ready it all 3 times.

**marcaaron20** · 21-09-2009

hi, just bought meself 1 of these Omnikey 3121 readers for my Dreambox 8000, not sure if I needed 1 or not but I thought I may as well get 1 seen as there are only £7.50, no harm in having 1 anyways...

just wondering, is it just for using the white s*y cards or can you use other cards in it too?? if so, which cards and which version of NewCS or CCcam (and any others) also am i able to use both CCcam and NewCS?? CCcam on the internal reader and NewCS on the Omnikey reader??

Thanks,

**andel** · 21-09-2009

if you look on post 3 b16mcc says he has tried it on other cards with no problems, personally i have not tried it but I do not doubt our satellite god's comments!!!

As for using newcs and cccam, always use the latest versions and there is no reason why you cant use them to read another card on the internal reader. Just add another reader in the 'device' section of your newsc.xml. The type is sci, node is dev/sci0 and serve it on a different port.
As for using just cccam on the internal reader, again not something that I have tried but I dont see why it wouldnt work but I'm sure to stand corrected if im wrong.

vampsthevampyre · 21-09-2009

B16MCC once again thanks for the advice, although you forgot to tell me to read it slowly. finally on the fourth attempt realised that I'd for got to change the newcs for the newcs.pcsc version, that and forgettin that the newcs web page was 8080 (really stupid mistake), I'd convinced myself that newcs wasnt working and thought that the port was 15001 - doh.

One problem I did have was copying Andel's xml file that mentions <node> 1 </node> this didnt work for me kept saying node in use, changed it to node 0 and it all came to life.

I have another omnikey reader here so I may try running two and see what happens with another node number (if the wife lets me take over the telle again)

woodseaves · 22-09-2009

When the file newcs.mips.pcsc is ftp'd to usr/bin and renamed has it got to be renamed the same as the newcs you are running, eg I am running newcs 1.66 and cccam 2.1.1 as I do not know how to download 1.67 if it is not on the blue button. I have tried both methods (renaming to 1.66 and 1.67) but with no success. I have the white card running fine now both locally (internal LAN) and Externally (dns). I am desperate to get it working in the omnikey. this is my newcs 1.66 for you to look at and see if there is anything obviously wrong:
<newCSconfig>
<globals>
<listening-ip>192.168.1.**</listening-ip>
</globals>
<readers name="Card Readers">
<device>
<name>Lower</name>
<type>Sci</type>
<node>/dev/sci0</node>
<mhz>357</mhz>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>no</blocksa>
<blockua>no</blockua>
<blockga>yes</blockga>
<boxkey>********</boxkey>
<PTShandshake>no</PTShandshake>
<crypto-special>no</crypto-special>
<carddetect>yes</carddetect>
<newcamd_port>12000</newcamd_port>
<priority>round</priority>

</device>

<device>
<name>Upper</name>
<type>Sci</type>
<node>/dev/sci1</node>
<mhz>357</mhz>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>no</blocksa>
<blockua>no</blockua>
<blockga>yes</blockga>
<boxkey>********</boxkey>
<PTShandshake>no</PTShandshake>
<crypto-special>no</crypto-special>
<carddetect>yes</carddetect>
<newcamd_port>12001</newcamd_port>
<priority>round</priority>

</device>
<device>
<name>USB</name>
<type>pcsc</type>
<node>0</node>
<mhz>357</mhz>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>no</blocksa>
<blockua>no</blockua>
<blockga>yes</blockga>
<blockc0>yes</blockc0>
<boxkey>********</boxkey>
<PTShandshake>no</PTShandshake>
<crypto-special>no</crypto-special>
<carddetect>yes</carddetect>
<newcamd_port>12002</newcamd_port>
<priority>round</priority>
</device>

</readers>
<radegastserver>
<enabled>No</enabled>
<port>16000</port>
<allow>
<hostname>localhost</hostname>
</allow>
</radegastserver>
<cache>
<emm>2</emm>
<ecm>3</ecm>
</cache>
<debug>
<password>NewCSpwd</password>
<level>normal</level>
<type>init</type>
<output>console,tcp</output>
<console_options>normal,init</console_options>
<tcp_port>3001</tcp_port>
<tcp_options>normal,init</tcp_options>
</debug>
<newcamdserver>
<enabled>Yes</enabled>
<name>newcs</name>
<deskey>01 02 03 04 05 06 07 08 09 10 11 12 13 14</deskey>
<user>
<name>*******</name>
<password>********</password>
<au>off</au>
<sidoverride>off</sidoverride>
<spider>No</spider>
</user>

<user>
<name>********</name>
<password>*********</password>
<au>off</au>
<sidoverride>off</sidoverride>
<spider>No</spider>
</user>
<user>
<name>********</name>
<password>********</password>
<au>off</au>
<sidoverride>off</sidoverride>
<spider>No</spider>
</user>

</newcamdserver>

<httpd>
<server>
<port>8080</port>
<enabled>yes</enabled>
</server>
<user>
<name>admin</name>
<password>admin</password>
<accesslevel>admin</accesslevel>
</user>
</httpd>
</newCSconfig>

I've blocked out the users, two are internal one external all different usernames and passwords and all working OK. I am using a DM 7025.

I have followed all the instructions at the beginning of this thread, this is a copy of the newcs 8080 to see if this helps

Newcamd Port: 12000 - CAID: 0000 - Reader: 0 (Lower)
ID Username Status Ok ECM Bd ECM EMM Hostname Client Spdr AU SO
02 DM7025 Offline 0 0 0 Offline Offline
03 DM8000 Offline 0 0 0 Offline Offline
04 andiprem Offline 0 0 0 Offline Offline

Newcamd Port: 12001 - CAID: 0963 - Reader: 1 (Upper)
ID Username Status Ok ECM Bd ECM EMM Hostname Client Spdr AU SO
02 DM7025 00d 11:21:43 0 0 0 192.168.1.** CCcam
03 DM8000 00d 11:22:01 0 0 0 192.168.1.** CCcam
04 ******** 00d 00:21:31 0 16 0 **.***.***.** CCcam

Newcamd Port: 12002 - CAID: 0000 - Reader: 2 (USB)
ID Username Status Ok ECM Bd ECM EMM Hostname Client Spdr AU SO
02 DM7025 Offline 0 0 0 Offline Offline
03 DM8000 Offline 0 0 0 Offline Offline
04 ******** Offline 0 0 0 Offline Offline

Readers Status

Status CAID Mhz Resets ECMs Net ECM Node Reader
0000 357 0 0 0 /dev/sci0 0 (Lower)
0963 357 0 16 0 /dev/sci1 1 (Upper)
0000 357 0 0 0 0 2 (USB)
there is no card in the usb, but if there was it wouldn't show.

regards

**andel** · 22-09-2009

Ok lets try to start it step by step.
1. First google newcs-1_67RC1 and download the top link
2. Rename newcs.mips.pcsc to whatever you want but lets say its newcs_1.67.pcsc and ftp to /usr/bin and chmod to 755
3. Using the blue button download/install CCcam 212
3. Use the blue button to select the common interface as your default cam (this will kill the CCcam)
4. Now I suggest you do a hard reboot.
5. Telnet to the DM and use.... /usr/bin/newcs_1.67.pcsc -C /etc/tuxbox/config/newcs.xml (the first path is pointing to the newcs bin, the -C is the switch to point to the path of your newcs.xml)
6. Once that says ready to go and you can access your newcs web interface telnet again and use... /usr/bin/CCcam_212 -dv (to start CCcam)

Hopefully I've done this correct from memory and you should be up and running. Report back and let us know

woodseaves · 22-09-2009

Thanks Andel,

step 5 just puts me in a loop.

**andel** · 22-09-2009

what do you mean by it puts you in a loop?

after you telnet the command below what output are you getting?
Is your newcs.xml located in /etc/tuxbox/config ?

Code:

/usr/bin/newcs_1.67.pcsc -C /etc/tuxbox/config/newcs.xml

woodseaves · 22-09-2009

Hi
I can't give you the output the output justkeeps scrolling round and round. I have gone through the whole lot again but the result is still the same.

Kill NewCS in the linux server, how do I do this?

If I put the card in the omnikey it recognises it and shows entitlements but it does not free up the channels.

Well, I've tweeked and tweeked, shutdown restarted, re-named etc. You name it i've done it. All worth it though, Omnikey working. Good eh.

Thanks for reading and helping

Regards

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)