Multidec setup (Viaccess, cardreader, Yankse, WinCSC, NewCS..)

[nkh]

Now that I have my DVB-C card working with FTA channels, I'd like to get a bit further and get to view all the channels I've paied for

Maybe my Google-skills aren't up to it, but I'm having quite bad luck trying to find a detailed guide/explanation on how these Multidec parts fit together and how they should be configured. So I'm hopeing someone here can point me in the right direction.

This is what I've now:

• GB-PVR v1.1.5
  
• a Twinhan DVB-C CI (AD-CP300 / 2033)
  
• a Phoenix/Smartmouse cardreader, running in Phoenix mode
  
• a digital cable tv connection from YouSee (in Denmark)
  
• a Viaccess subscription card from YouSee
  

I've tried to follow this guide: http://www.hyperlinkx.com/pmwiki/pmwiki....s.MultiDec

But it looks like I can't get the parts to talk together correctly, maybe I've chosen the wrong components, maybe I've set it up wrong, I'm not quite sure :confused: but I'll try to break it down so you can see what I've done...


MultiDec API

• Downloaded it from http://www.hyperlinkx.com/pmwiki/pmwiki....s.MultiDec
  
• mdapifilter.ax - v1.1.6.0
  

NewCS v1.50

• I run it with this command:
  Code:

  c:\Programmer\newcs-1.50\win32\newcs.exe -c c:\Programmer\newcs-1.50\configs\newcs.xml.windows
• I changed this in newcs.xml.windows:
  • The com port
    
  • and set the radegastserver part like this:
    Code:

    <radegastserver>
            <enabled>yes</enabled>
            <port>16000</port>
            <allow>
                <hostname>localhost</hostname>
            </allow>
    </radegastserver>
• When I run it, I get this output (I noticed that it finds my Viaccess smartcard, so I assume it's working):
  Code:

  Reading Config file from c:\Programmer\newcs-1.50\configs\newcs.xml.windows
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
[ 12:13:14 ] [ Box detect ] Windows XP Build 2600
[ 12:13:14 ] [ Config ] Value in <ipk> for device 0 (Phoenix Interface) is INVALID, skipping...
[ 12:13:14 ] [ Config ] Value in <ucpk> for device 0 (Phoenix Interface) is INVALID, skipping...
[ 12:13:14 ] [ Config ] Pincode for device 0 (Phoenix Interface): 0000
[ 12:13:14 ] [ Config ] COM3 ECM priority: round
[ 12:13:14 ] [ EMM Cache ] Initialising Cache with 20 entries
[ 12:13:14 ] [ ECM Cache ] Initialising dynamic Cache
[ 12:13:14 ] [ Loader ] Starting Telnet on port 1001
[ 12:13:14 ] [ Loader ] Reader type 2 on node COM3
[ 12:13:14 ] [ Phoenix ] Opening device COM3
[ 12:13:14 ] [ Phoenix ] Setting parity to ODD on node COM3
[ 12:13:14 ] [ Phoenix ] Setting 1 Stop bit on node COM3
[ 12:13:14 ] [ Phoenix ] Setting baud to 9600
[ 12:13:16 ] [ Loader ] Clearing all autosids on reader ...
[ 12:13:16 ] [ ATR ] T=0  1etu=8.68us  Guardtime:12etu  WWT:115200etu
[ 12:13:16 ] [ ATR ] Historical bytes: [C1] [14] [01] [A2] h [90] [00]
[ 12:13:16 ] [ Loader ] Init Viaccess card
[ 12:13:16 ] [ Phoenix ] Setting parity to ODD on node COM3
[ 12:13:16 ] [ Phoenix ] Setting 1 Stop bit on node COM3
[ 12:13:16 ] [ Phoenix ] Setting baud to 9600
[ 12:13:16 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000000 for caid 0000 ID=1280
[ 12:13:16 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid FFF490 ID=1280
[ 12:13:16 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid 20300 ID=1280
[ 12:13:17 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid 20310 ID=1280
[ 12:13:17 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid 20320 ID=1280
[ 12:13:17 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid 20330 ID=1280
[ 12:13:17 ] [ Keyman ] Adding key C216BB05 type 0 on Provider 000001 for caid 20340 ID=1280
[ 12:13:17 ] [ Loader ] Card 0500 on port COM3 ready
[ 12:13:17 ] [ Loader ] Starting Newcamd Server on port 15000
[ 12:13:17 ] [ Loader ] Starting Radegast Server on port 16000
• When I start a recording in GB-PVR on an encrypted channel it gives this message:
  Code:

  [ 12:53:11 ] [ SockSrv ] New connection from 127.0.0.1 on socket 884 [SSL 0]
  So I assume one of the Multidec plugins are connecting to it
  

WinCSC v1.2.0.2483 - I'm not sure what this should do..

• I have set it up to use radegast like this:
  
  
  (I blurred the key eventhough it looks like a placeholder or something, it's not always there, sometimes the field is just blank)
  

Yankse v1.3.2.1/U TT

• My yankse.ini looks like this:
  Code:

  [yankse]
Disabled=0
Log=0
LogECM=0
LogPMT=0
LogFirstECM=0
ReadPMT=1
AutoECM=1
FilterBogusECM=0
FilterUnknownECM=0
AllowAutoPIDS=1
LogBadKeys=0
LogCW=0
CWDelay=0
ShowOSD=1
ForcePMTCA=1
Language=0409-ENU
[CardServer]
server=127.0.0.1
port=1001
enabled=1
• Most of the time the monitor window is blank except for the [* PMT:] field showing "0(0x0000)" and the [SID:] field showing the same..
  

When I try to record something on an encryptet channel in GB-PVR I just get a 4KB dvr-ms file, and this is what gets logged in GBPVRRecordingService.exe-native.log: GBPVRRecordingService.exe-native-log-16-02-2008-multidec.txt

Am I missing something in my setup? Is something setup wrong?

Any help will be much apreciated!

[sub]

This type of stuff isnt usually discussed here. A good place to go to discuss this multidec stuff is the DVBN forums: http://dvbn.happysat.org

[nkh]

Thanks Sub, I'll try my luck there.

[varesino]

Port number in wincsc must match what you specify in newcs (16000 instead of 1001)

[nkh]

Port number in wincsc must match what you specify in newcs (16000 instead of 1001)

Ah, yeah, that makes sense thanks!

I changed it in yankse.ini too, but it doesn't seem to change anything... hmm, pretty confusing :confused:

[nkh]

I've posted the same thread over at the DVBN forum, just so anyone having the same challenges as me knows where the continuation of this is: http://dvbn.happysat.org/viewtopic.php?t=44901

I'll still be more than happy to get any suggestions that can bring me further though

[SIZE="1"]The status is now that I've changed the protocol in NewCS and WinCSC to Newcamd and Yanksee is now getting some card info, but it doesn't look like it's getting any keys and it's not doing any decoding.[/size]