PDA

View Full Version : Azbox Premium not seeing local card



paulwilko
30-08-2009, 05:36 PM
I have ART full bouquet but my azbox is not seeing it

Anything i need to do to make this happen ?

Thx

Paul

paulwilko
30-08-2009, 07:54 PM
Ok, with Multicas turned on, it reads the card but then does not read cccam

So looks like it is 1 or the other ?
Is that right or is there something i can do to make cccam tell it to use local card ?

Carp95
30-08-2009, 07:57 PM
No not yet

Untill next release off CCcam your hooked on newcs and CCcam

paulwilko
30-08-2009, 08:01 PM
So if i install newcs, i can have both running at same time ?
Where do i get newcs from ?

goran
30-08-2009, 08:51 PM
Read my Sticky - a good starting point... The pdf file is at the bottom of the thread...

paulwilko
30-08-2009, 10:02 PM
Thx, i have now installed the latest newcs but it does not see my card, so iassume there is a config i need to do.
I have no idea what that config is

I have ART card on 13e Viaacess if that helps ?

Please note that i only want newcs to read my card and i want cccam to do the card sharing

goran
31-08-2009, 01:09 AM
Slower reading is preferable...:number-one-043:

It [my thread] says not to use the latest version, unless one uses an external reader... Does it no?!?

So, one can get v. 1.20 from here and various servers, but getting the latest one, i clearly states, is not always the best option, so do not use 1.67, if you are to use your internal reader...:woot-035:

w w w satelites . info / azbox / has it, for instance, if memory serves...

It also has various CCcams...

Once one has it one tries to mess with files and once one shows one's enthusiasm, somebody comes to one's aid...:reddevil::respect-062:

So, in my thread there is a config file for the version I mentioned with a certain Viaccess card... [Tinos]

I mean, it's not like I haven't put your nose right in it but hey... if you prefer to torture yourself, who am I to stop you?!? :rolleyes: :D:respect-023:

hanswurscht
31-08-2009, 10:50 AM
also Multicas has nothing to do with any other Emu!

If you use it, no other Emu can handle the Card. Also Multicas takes API Rights, so you are "out" with this for using CCcam, or any other Emu

paulwilko
31-08-2009, 10:51 AM
Yeah, noticed that with Multicas

Thx

kers
01-09-2009, 08:28 AM
Installing the newcs 1.20RC13 from satelites . info was not possible for me, the add on install with OpenXCAS just just gave an error message.

In the end I gave up, got an external reader and used newcs 1.67RC1.

Taykun
01-09-2009, 08:54 AM
not all link have working newcs (satelites.info), try some other link. It worked for me.
And iam running viaccess 3.0 (i think its 3.0) without a problem!

hanswurscht
01-09-2009, 10:43 AM
also an Error on install at the End is nomal on some Tools.
Install is OK

paulwilko
01-09-2009, 02:05 PM
I ask this with fear of Goran telling me off :respect-057: but i am gonna anyway

I have installed newcs from the servers from the azbox as per Gorans thread. It now says it is 1.6

I found 1.20 on the web, copied the newcs file over but is still showing 1.6 and not reading my card.
Whenever i download newcs files, there is only ever 1 file in the main file, so not sure how to manually install it.

Is there something else i need to copy over to make it 1.20.

I copied it over based on info from another site. Maybe right, maybe wrong ?

Thx

Paul

hanswurscht
01-09-2009, 05:30 PM
http://rapidshare.com/files/274341156/_binnewcs.zip.html

Its the second 1.20, only .bin
Copy it over yours, give rights 755

paulwilko
01-09-2009, 05:49 PM
Great, will report back how i get on, many thx

Paul

paulwilko
01-09-2009, 06:03 PM
Ok, did it, it was a different file size so was a different version, but for some reason it is still showing as 1.6 on CAMD Setup !

I still cant view the card.

Would i be right in saying:

1. Install from one of the online servers
2. Open filezilla and copy the file you mentioned and overwrite the one thats already there
3. Give it 755
4. Reboot Azbox

Then it should show 1.20 ?

If that is the case, i have done all that but still showing 1.6

There are two other files in the newcs folder
newcs.xml
openxcas.conf
These are both set to 644 as per the downloaded set up

Should any of those be 755 ?

Many thx

Paul

goran
01-09-2009, 06:26 PM
:smilielol5:

https://www.satpimps.co.uk/showthread.php?p=650643#post65064 3

hanswurscht
01-09-2009, 06:27 PM
only bin needs 755
You see 1.20 when you start NewCS over telnet only.

And you must start it over telnet, for to see whats happend
make a dowswindow-telnet ipofyourbox
root
azbox if youve set a password like this
now type ps
if you see new cs as process, type
killall newcs
ps again for to see there is no newcs running
now
cd /EMU/OpenXCAS/newcs if your folder in openxcas is called newcs
./newcs

write down the log here so we can see (delete serialnumber or lines bevor)

paulwilko
01-09-2009, 08:11 PM
Goran, you make me laugh ;-)

Here is my log, thx fopr your help

"****** INTERNAL enabled
TCP-log password is disabled!
level: internal
type: all
output: console, tcp
logger config: level 16777215 type 255 output 5
Console log options: level 16777215 type 255
tcp port: 1001
TCP log options: level 16777215 type 255
[ 19:10:32 ] [ Box detect ] Box type 9
[ 19:10:32 ] [ Config ] hwkey not found !
[ 19:10:32 ] [ Config ] ekpair not found !
[ 19:10:32 ] [ Config ] /dev/scard ECM priority: hard
[ 19:10:32 ] [ Config ] No SIDFILTER is configured, disabling SidOverride for de vice 0 (upper)!
[ 19:10:32 ] [ Newcamd ] Server name : local
[ 19:10:32 ] [ Newcamd ] Des key : 0102030405060708091011121314
[ 19:10:32 ] [ Newcamd ] User 2: dummy, Pass: dummy, Host 127.0.0.1, Port: 12000 , Au: Off, Spider allowed: No, Sidoverride: No, reader control: No, level: 0
[ 19:10:32 ] [ EMM Cache ] Initialising Cache with 10 entries
[ 19:10:32 ] [ ECM Cache ] Initialising dynamic Cache
[ NewCS ] Process ID is: 1122
[ 19:10:32 ] Calibrating delay loops
[ 19:10:32 ] usleep(5) takes: 0 s 19 us
[ 19:10:32 ] usleep(10) takes: 0 s 17 us
[ 19:10:32 ] usleep(100) takes: 0 s 107 us
[ 19:10:32 ] usleep(500) takes: 0 s 506 us
[ 19:10:32 ] [ Loader ] Reader type 11 on node /dev/scard
[ 19:10:32 ] [ azbox ] Opening device /dev/scard
SCARD_IOC_CHECKCARD: ATR len=-1
SCARD_IOC_CHECKCARD: ATR len=12
[ 19:10:35 ] ATR: 3F 77 18 00 00 C2 47 40 00 68 90 00
[ 19:10:35 ] [ ******* ] Atr header is 3F 77 [INVERSE]
[ 19:10:35 ] parseAtr: 3F 77 18 00 00 C2 47 40 00 68 90 00 00 00 00 00
[ 19:10:35 ] parseAtr: 00
[ 19:10:35 ] [ ATR ] T=0 1etu=31.00us Guardtime:12etu WWT:115200etu
[ 19:10:35 ] [ ATR ] Fi 1 (372) Di 8 (12)
[ 19:10:35 ] [ ATR ] Historical bytes: [C2] G @ [00] h [90] [00]
[ 19:10:35 ] [ ATR ] freq 1000000.000 sciFreq 5000000.000
[ 19:10:35 ] [ azbox ] Set card type to 0x500 (mode 2)
[ 19:10:35 ] [ Loader ] Init Viaccess card
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAA4000000
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA A4 00 00 00
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAACA40000
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA AC A4 00 00
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: AC
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAB8000007
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA B8 00 00 07
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: B8
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: A4 05 00 C5 63 74 30
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 08
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9008
[ 19:10:35 ] [ Keyman ] Adding key C56***0 type 0 on Provider 000000 for caid 0500 ID=0
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAA4000000
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA A4 00 00 00
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAC000001A
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA C0 00 00 1A
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: C0
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: FF F4 00 40 00 00 3E 84 2D 7C 00 01 02 FF FF FF
[ 19:10:35 ] read: FF FF FF 09 FF FF FF FF FF 0F
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAACA50000
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA AC A5 00 00
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: AC
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAB8000006
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA B8 00 00 06
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: B8
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: A5 04 C5 63 74 30
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 08
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9008
[ 19:10:35 ] [ Keyman ] Adding key C56***30 type 1 on Provider FFF400 for caid 0500 ID=0
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAA4020000
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:35 ] write: CA A4 02 00 00
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 90
[ 19:10:35 ] [ azbox ] Timeout is 714240us
[ 19:10:35 ] read: 00
[ 19:10:35 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:35 ] [ Viaccess ] Sending to Card: CAC000001A
[ 19:10:35 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA C0 00 00 1A
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: C0
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 02 11 18 40 00 BF 3D EC 2D 7C 00 01 02 FF FF FF
[ 19:10:36 ] read: FF FF 08 09 0A 0B 0C 0D 0E 0F
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 00
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAACA50000
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA AC A5 00 00
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: AC
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90 00
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAB8000006
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA B8 00 00 06
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: B8
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: A5 04 C5 63 74 30
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 08
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9008
[ 19:10:36 ] [ Keyman ] Adding key C5****0 type 1 on Provider 021110 for caid 0500 ID=1
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAA4020000
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA A4 02 00 00
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 00
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAC000001A
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA C0 00 00 1A
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: C0
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 02 11 28 40 00 BF 3D D0 2D 7C 00 01 02 FF FF FF
[ 19:10:36 ] read: FF FF 08 09 0A 0B 0C 0D 0E 0F
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 00
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAACA50000
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA AC A5 00 00
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: AC
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90 00
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9000
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAB8000006
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA B8 00 00 06
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: B8
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: A5 04 C5 63 74 30
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 08
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9008
[ 19:10:36 ] [ Keyman ] Adding key C5***30 type 1 on Provider 021120 for caid 0500 ID=2
[ 19:10:36 ] [ Viaccess ] Sending to Card: CAA4020000
[ 19:10:36 ] [ azbox ] Delay is 6us
[ 19:10:36 ] write: CA A4 02 00 00
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 90
[ 19:10:36 ] [ azbox ] Timeout is 714240us
[ 19:10:36 ] read: 08
[ 19:10:36 ] [ Viaccess ] Status Word from Card: 9008
[ 19:10:36 ] [ 0500 ] Init took: 0.787748
[ 19:10:36 ] [ Loader ] Card 0500 on port /dev/scard ready
[ 19:10:36 ] [ Loader ] Starting Newcamd Server on port 20000
[ 19:10:36 ] [ NewCS ] Ready to GO! :)
MMP[newcs]$ [ 19:10:36 ] [ Card queue /dev/scard ] Starting...
[ 19:10:36 ] [ Newcamd:20000 ] rlogin for user dummy fd 8
My sign: D6 EC B3 82 98 20 C2
[ 19:10:36 ] [ Newcamd:20000 ] Bad read? rejecting
cd /EMU/OpenXCAS/newcs"

rtificial
02-09-2009, 07:50 AM
OK, NewCS seems to be able to read your card. Now you need an EMU to connect to NewCS to enable you viewing it.

This can be MGCamd, Mbox, CCCam...

paulwilko
02-09-2009, 08:08 AM
OK, NewCS seems to be able to read your card. Now you need an EMU to connect to NewCS to enable you viewing it.

This can be MGCamd, Mbox, CCCam...
Thx for this

I am already running CCCam and that works but still no card showing

I have seen mentioned that i should add an N line to my cfg but the N line mentioned is already in the cgf (N: 127.0.0.1 20000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14)

Maybe i have put it in the wrong place, maybe i need to add something else ?

Here is my CFG

# CCcam team uvadi CCcam v2.0.5
#
# Special greets go to all our friends all over the world, you know who you are!
#
# Specjalne podziekowania dla Ludzi z Polski, dzieki ktorym jest duzo nowych funkcji w wersji 2.0.0
# Ostatnim razem zapomnielismy o nich wspomniec w readme. DZieki Chlopaki!
#

################################# ################################# ####
# friends #
################################# ################################# ####
# syntax for to add a friend user to CCcam with the max up hops limit (default = 5)
# sharing of emus (default = 1), allow emm (default = 1), and optional
# downshare limits per share (default = no limits) and optional
# downshare limits per share based on caid:id:sid
# and optional timeslots in which share is valid (to block channels on box of children after 19:00 for instance)
# if no timeslot is defined 24 hrs a day is used
# emus are shared only one level down, even if no limits given
#
# max username length 20
# password length 'unlimited'
#
#F: <username> <password> <uphops> <shareemus> <allowemm> ( { caid:id(:downhops), caid:id(:downhops), ... } { caid:id:sid, caid:id:sid, ... } { begintime-endtime, ... } ) hostname/ip address
#
# example:
#
# F: user1 pass1
#
# user1 gets all our shares at max 5 hops from us
# (our local cards + max five hops away). He can share down to his own
# clients. He also receive emu shares (if he has 'yes' behind his C: entry),
# and is allowed to send us emm.
#
# F: user2 pass2 0 1 0 { 0100:000080, 0622:000000:1, 0500:000000:2 }
#
# user2 gets only our local cards but no 0100:000080.
# and our 0622:000000 cards only for himself (1 hop down),
# and 0500 cards for himself plus one additional hop down.
# He also gets our emus, and is NOT allowed to send us emm (updates).
#
# F: user3 pass3 5 0 1 { 0:0:3, 0100:000080:1 }
#
# user3 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
#
# F: user4 pass4 5 0 1 { 0:0:3, 0100:000080:1 } { 0100:000080:15df }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
# He is also not allowed to view channel 0100:000080:15df
#
# F: user4 pass4 5 0 1 { } { } { 12:00-17:00, 19:00-20:00 }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# the share is only valid between 12:00 and 17:00 and between 19:00 and 20:00
# outside these hours the share will not give cw's to the client
#
#
# F: user5 pass5 5 1 1 { } { } { } 192.168.1.1
#
# user5 gets all cards at a maximum of 5 hops away from us
# user5 is only allowed to connect from the host 192.168.1.1
#


################################# ################################# ####
# connections #
################################# ################################# ####

# C: juninhoisgod.dyndns.org

THIS IS WHERE ALL MY PEERS ARE

N: 127.0.0.1 20000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14



# syntax for to add a client connection to other CCcam
# add yes on end to use friends emus (non public private key/emu,etc...),
# but only works when corresponding F line on server has '1' for <shareemus>
# optional limits just like F line, but for incoming shares (ignore shares more than 'uphops' away)
#
#C: <hostname> <port> <username> <password> <wantemus> ( { caid:id(:uphops), caid:id(:uphops), ... } )
#
#note: if {} limits are added, <wantemus> cannot be omitted. Use either yes or no.
#
# example:
#
# C: someserver.somedomain 12000 user1 pass1
# C: 192.168.1.2 12000 user2 pass2
# connects to CCcam without use of friends emus
#
# C: 192.168.1.2 12000 user3 pass3 yes
# connects to CCcam, and receives friends emus also.


# syntax for to add newcamd server connection
#
#N: <ip> <port> <username> <pass> <des(14byte)> <nr_of_hops_away (default: 1)> <stealth mode (default: 0)>
#
# example:
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14
#
# add a newcamd card, give it an offset of 2 hops, in the share list
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 2
#
# stealthy login on newcamd server:
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 1 1
#
# stealth modes: 0 = disabled, 1 = mgcamd new, 2 = mgcamd old, 3 = evocamd, 4 = generic


# syntax for to add radegast server connection
#
#R: <ip> <port> <ca4> <id6> <nr_of_hops_away (default: 1)>
#
# example:
#
# R: 127.0.0.1 678 0100 000080


# syntax for to add camd3 connection
#
#L: <ip> <port> <username> <pass> <ca4> <id6> <nr_of_hops_away (default: 1)>
#
# example:
#
# L: 127.0.0.1 567 dummy dummy 0100 000080


# syntax for add gbox connection
#
#G: <pass> <localhost> <localport> <peerpass> <peeraddress> <peerport>
#
# support optional limits just like C line (ignore shares more than 'uphops' away)
# { caid:id(:uphops), caid:id(:uphops), ... }
#
# example:
#
# G: AABBCCDD my.address.tv 2500 12345678 peer.address.tv 2500

################################# ################################# ####
# Other config settings #
################################# ################################# ####
# server shall listen on this port pro incoming connections
# default port is 12000, disable server with parm -s or set port 0
#
#SERVER LISTEN PORT : 12000

# server can give some info about server and client connections
# and cardinfo using telnet or webbrowser.
#
# Switch on/off access to info
# default is yes
#
#ALLOW TELNETINFO: no
#ALLOW WEBINFO: no

# Show extended client info when showing client list
# default is yes
#
#SHOW EXTENEDED CLIENT INFO : no
# The webinfo service can be protected with a username and password.
# This is switched off by default
#
#WEBINFO USERNAME :
#WEBINFO PASSWORD :

# The telnetinfo service can be protected with a username and password.
# This is switched off by default
#
#TELNETINFO USERNAME : <username>
#TELNETINFO PASSWORD : <password>

# default port for telnet is 16000
# default port for web is 16001
# supported commands:
# info
# activeclients
# clients
# servers
# shares
# providers
# entitlements
# example use:
# echo servers | telnet localhost 16000
# go with your browser to http://ip_CCcam_server:16001
#
#TELNETINFO LISTEN PORT : 16000
#WEBINFO LISTEN PORT : 16001

# time in seconds to keep On Screen Display active.
# default is 0 (turned off)
#
#ZAP OSD TIME : 3

# username used to show popup (default : root)
#OSD USERNAME : root

# password used to show popup (default : dreambox)
#OSD PASSWORD : dreambox

# port used to show popup (default : 80)
#OSD PORT : 80

# Serial reader config. Add as many as you have attached too your system
# replaces old name 'PHOENIX READER PATH', but still works.
# default is none
# optionally add readertype : phoenix,mouse,uniprog,sc8in1,smar treader+
# (when non readertype given defaults to uniprog (e.g. for mastera))
#
# SERIAL READER : <device> <type>
#
# example
#
#SERIAL READER : /dev/tts/0

# Serial reader smartcard write delay.
# Setting to finetune smartcard write speed, optimal setting depends on speed of system, and
# speed of card. Default value is calculated, but can overrule by setting.
# Use number of microseconds delay between bytes, 0 = no delay, -1 = calculated default
# Note: huge difference between values 0 and 1, because of schedular overhead
#
# SMARTCARD WRITE DELAY : <device> <delay>
#
# example, 10ms write delay on smartcard in reader attached to /dev/ttyUSB0
#
#SMARTCARD WRITE DELAY: /dev/ttyUSB0 10000
#
# NOTE on sc8in1; because 8 smartcards are used on the same devicename, use
# devicename_0 .. devicename_7 for settings which require devicename to make
# settings per smartcard. example /dev/ttyS0_0, /dev/ttyS0_1 ..
# example, 8ms write delay between bytes to smartcard on last sc8in1 channel, attached to /dev/tts/0
#
#SMARTCARD WRITE DELAY: /dev/tts/0_7 8000

# Smartcard clock speed override
# Setting override specified speed for smartcard.
# Don't add setting unless you're sure what you're doing.
# In 99% of the cases the reader selects the optimal speed.
# Adding this setting either slows your card down, or might destroy it.
#
# SMARTCARD CLOCK FREQUENCY : <device> <freq>
#
# example
#
#SMARTCARD CLOCK FREQUENCY: /dev/ttyUSB0 5500000

# if timing should be shown in OSD and debug output
# default is no (turned off)
#
#SHOW TIMING : yes

# enables mini OSD which shows server(type), cardreader, keys or fta only
# default is no (turned off)
#
#MINI OSD : yes

# turns debugging on and off
# default is no (turned off)
#
#DEBUG : yes


# should CCcam try to read and parse newcamd.conf for server connections
# default is no (turned off)
#
#NEWCAMD CONF : yes


# configure what EMM blocker you want. Add as many as readers you have attached
# default is blocking nothing
#
# B: /dev/sci0 01
# 00 - nothing
# 01 - sa blocked
# 02 - ua blocked
# 04 - ga blocked
# and sum of for combinations
#
#examples
#
#B: /dev/tts/0 07
#B: /dev/sci0 01

# disable all local EMM readers
# saves lots of CPU, but you won't get any updates anymore
# (unless you get updates from your clients)
#
# default: no
#
#DISABLE EMM : yes

# with this setting you can
# allow a client on two hops away
# to send the updates to the cardserver
#
# default : no
#
#EXTRA EMM LEVEL : yes

# with this setting you can
# configure how many emm listeners are started.
# for example use 2 when recording
# and viewing different systems and both need constant updates
#
# default : 1
#
#EMM THREADS : 1

# overrule the nds boxkey (4 byte hex)
#
# BOXKEY: <device> <byte1> <byte2> <byte3> <byte4>
#
#example
#
#BOXKEY: /dev/sci0 00 11 22 33

# set card pin
# * please be very careful with this option as you could lock your card *
#
# PIN: <device> <pin>
#
#example
#
#PIN: /dev/sci0 1234

# overrule the irdeto camkey (8 byte hex), default 11 22 33 44 55 66 77 88
#
# CAMKEY: <device> <byte1> <byte2> <byte3> <byte4> <byte5> <byte6> <byte7> <byte8>
#
#example
#
#CAMKEY: /dev/sci0 11 22 33 44 55 66 77 88

# overrule the irdeto camdata (64 byte hex)
# trailing zero bytes can be omitted
# default for unknown ASC's is 11 22 33 44 55 66 77 88 00 00 .. 00, known ASC's have other defaults
#
# CAMDATA: <device> <byte1> <byte2> <byte3> <byte4> <byte5> <byte6> ... <byte64>
#
#example, when only the first 15 camdata bytes are nonzero
#
#CAMDATA: /dev/sci0 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff

# custom add id's for BEEF patched cards
#
# BEEF ID: <ident1> <ident2> <ident3> <ident4> <ident5> <ident6> <ident7> <ident8> <device>
#
#example
#
#BEEF ID: 4101 0 0 0 0 0 0 0 /dev/sci0

# what Softcam.Key should CCcam try to read
# defaults to /var/keys/SoftCam.Key
#
#SOFTKEY FILE : /var/keys/SoftCam.Key


# what AutoRoll.Key should CCcam try to read
# defaults to /var/keys/AutoRoll.Key
#
#AUTOROLL FILE : /var/keys/AutoRoll.Key


# what constant.cw should CCcam try to read
# defaults to /var/keys/constant.cw
# file content can be like
#
# ca4:id6:sid4:pmtpid4:ecmpid4:key1 6(01 02 03...)
#
#STATIC CW FILE : /var/keys/constant.cw


# in this file you can configure what CAIDs CCcam should prefer or ignore
# defaults to /var/etc/CCcam.prio
# file content can have ignores (I) and prio lists (P)
#
# note 1: I line affects both for ecm and emm (receive no emm on ignored systems)
# P line only affects ecm choice (emm still received for all available systems, not just the priority system)
#
# note 2: ident 0 means 'all idents'. So 'caid:0' is the same as 'caid'.
#
# note 3: for some systems (e.g. nagra (caid 18xx)), the ident is not known at the time the
# prio lists are checked. In that case, matching is done on caid only, even if the P line
# defines nonzero idents. So for example '1801:401' behaves the same as '1801' in a P line
# I lines work differently, they are checked two times, once before ecm or emm is received, again
# after ecm or emm are received (and nagra ident should be known)
# P lines are only checked once, before ecm received.
#
# note 4: if a P line contains caid:ident pairs which are not available for the current
# channel, that P line is not used for that channel.
# Example, channel has systems 626, 1801:401 then P line with "1801,100:96,626" is ignored by that channel,
# because channel doesn't have 100:96.
# But P line with "1801" works, and also "626,1801" will work for channel
#
# note 5: P lines are parsed in the order in which they are found in the prio file.
# Only the first matching P line is used
#
# situation 1: ignore allways this caid, all idents, on all channels
# I: caid
#
# situation 2: ignore allways this caid/ident pair
# I: caid:ident
#
# situation 3: ignore this caid/ident pair, on channel 'sid'
# I: caid:ident:sid
#
# situation 4: when both caid1 and caid2 exist for a channel, prefer caid1 over caid2
# P: caid1, caid2
#
# situation 5: when caid1:ident1 till caidN:identN exist for a channel, use them in order of this list.
# P: caid1:ident1, caid2:ident2, .., caidN:identN
#
# situation 6: when caid1:ident1 till caidN:identN exist for channel 'sid', use them in order of this list.
# Sid on first caid/ident pair identifies sid for which list is used. All other sids ignore this list.
# P: caid1:ident1:sid, caid2:ident2, .., caidN:identN
#
#CAID PRIO FILE : /var/etc/CCcam.prio

#
# In this file all provider idents are defined
# The info from this file is being used in the web interface
# format:
# <caid><ident> "Provider description"
#
# PROVIDERINFO FILE : /var/etc/CCcam.providers

#
# In this file all channel idents are defined
# The info from this file is being used in the web interface
# format:
# caid:ident:sid "Channel description"
#
# CHANNELINFO FILE : /var/etc/CCcam.channelinfo

# write wrong logins to file
# defaults is off
#
#LOG WARNINGS : /tmp/warnings.txt

# global setting for stealthy login to newcamd/newcs server, N line can overrule
# stealth modes: 0 = disabled, 1 = mgcamd new, 2 = mgcamd old, 3 = evocamd, 4 = generic
# default: 0
#
#NEWCAMD STEALTH : 0

# load balancing between identical cards, list device names of card readers containing identical cards,
# optionally followed by a list of service id's which are to be excluded from loadbalancing
# LOADBALANCE : <device1> <device2> .. <devicen> { <exceptsid1>, <exceptsid2> .. , <exceptsidn> }
#
# multiple loadbalance groups can be configured, by adding multiple lines
# warning: restart is required, when loadbalance group config changes
#
#example 1: load balance requests for three identical cards
#
# LOADBALANCE : /dev/ttyS0 /dev/ttyS1 /dev/ttyS2
#
#example 2: load balance requests for two almost identical cards, sid 0df3 and 0de1 are only available
#on one of the cards, so requests for these sids shouldn't be loadbalanced
#
# LOADBALANCE : /dev/ttyS5 /dev/ttyS6 { 0df3,0de1 }

# in version 1.2.1 and lower there was a problem which could lead to disconnecting clients
# in version 1.4.0 network load was significantly reduced
# in version 1.7.0 dangerous password bug was fixed
# in order to take advantage of these fixes, all clients should upgrade
# with this setting you can force that clients at least use a certain version otherwise they are denied when logging in
#
# default : accept all versions
#
#example 1: avoid disconnecting clients problem
#
#MINIMUM CLIENT VERSION : 1.3.0
#
#example 2: achieve network load decrease
#
#MINIMUM CLIENT VERSION : 1.4.0
#
#example 3: don't allow potentially wrong passwords (pre 1.7.0 has password bug)
#
#MINIMUM CLIENT VERSION : 1.7.0
F: . .

# Irdeto smartcards: option to disable smart chid checking for irdeto smartcards.
# Default, only chids advertised by card are accepted.
# This avoids a lot of unwanted card traffic
#
# But if smartcard has hidden/unknown chids, all chids should be tried.
# In that case specify 'TRY ALL CHIDS' option for cardreader.
# Use with care, enabling option causes more card traffic.
# Only use setting when some channels don't work without it.
# note: if even this setting don't help decode all channels, try using
# commandline arg -l, to disable all self-learning features (warning: slower)
#
#TRY ALL CHIDS : <device>
#
#example: card in /dev/ttyUSB0 gets ecm for all possible chids, not
#just the chids it officially supports
#
#TRY ALL CHIDS : /dev/ttyUSB0

# perform smartcard post init commands
#
# POSTINIT : <device> <filename> (<autodelete>)
#
# send commands in 'filename' to 'device', and delete 'filename' when
# optional 'autodelete' argument nonzero
#
#example:
#
#POSTINIT : /dev/sci0 /tmp/postinit
#
#example /tmp/postinit contents:
#c134000003000000
#c13201000a

# Option to override autodetected dvb api version. Restart needed.
#
#DVB API: <value>
#
# <value> <1 = no dvb, 1 = dvb api 1, 3 = dvb api 3>
#
# WARNING: only use when autodetect fails!
#
#example, disable nonworking dvb hardware:
#DVB API: -1

# Option to set global share limits
#
#GLOBAL LIMITS: { caid:id(:downhops), caid:id(:downhops), ... }
#
#example:
#
#GLOBAL LIMITS : { 0100:000080, 0622:000000:1, 0500:000000:2 }
#
# all users get no 0100:000080.
# and our 0622:000000 cards only for themself (1 hop down),
# and 0500 cards for themself plus one additional hop down.
# global limits are overridden by client specific limits (see F:)

# Option to reject shares with less than required downhops on clientside
#
#MINIMUM DOWNHOPS: <value>
#
# default: 0 (don't ignore any shares)
#
#example:
#
#MINIMUM DOWNHOPS: 1
#
# ingore shares that have less than 1 'downhops' (i.e. can not be shared
# further down to other clients)

hanswurscht
02-09-2009, 08:52 AM
If I remember right, on some Via Access was a Problem, needed RSA or Boxkey 00000000, but Im not sure, dont have a Card like this.
Also deactivate spider, not needed!

You must now search for some Infos to handle your Card, working with old NewCS 1.20R13

A but is coming direct, CCcam is not really working good with actual Firmware.
Maybe some (more)channelswitching can help

This is not good:
[ 19:10:36 ] [ Newcamd:20000 ] Bad read? rejecting


My Tip is, forget this actual CCcam on actual firmware and try Mbox 0.6.10 as Client

paulwilko
02-09-2009, 09:31 AM
If I remember right, on some Via Access was a Problem, needed RSA or Boxkey 00000000, but Im not sure, dont have a Card like this.
Also deactivate spider, not needed!

You must now search for some Infos to handle your Card, working with old NewCS 1.20R13

A but is coming direct, CCcam is not really working good with actual Firmware.
Maybe some (more)channelswitching can help

This is not good:
[ 19:10:36 ] [ Newcamd:20000 ] Bad read? rejecting


My Tip is, forget this actual CCcam on actual firmware and try Mbox 0.6.10 as Client

Hiya

I appreciate your advice regarding using Mbox, but even getting Newcs was a big challenge to me and to be fair, although not great cccam is working okay and i almost understand it. So my preference would be to get this combo working before trying mbox.

Any other thoughts please ?

valerica
02-09-2009, 12:13 PM
Use the following newcs.xml :


<newCSconfig>
<readers name="Card Readers">
<device>
<name>upper</name>
<type>azbox</type>
<node>/dev/scard</node>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>no</blocksa>
<blockua>no</blockua>
<blockga>No</blockga>
<newcamd_port>20000</newcamd_port>
<autosid>no</autosid>
<carddetect>yes</carddetect>
<priority>hard</priority>
<PTShandshake>no</PTShandshake>
<mhz>357</mhz>
<boxkey>79FDC0E18D278138</boxkey>
<rsa>9ED52515321F04BCF7772151149D68951 54B559A8D825A4E7D711A9FAFD5C66BF6 4689501B254DF1832F754C21095379CF9 7B4E5BE6E0F1C9CEBF0A0E91D5ACD</rsa>
</device>
</readers>
<xmlserver>
<enabled>0</enabled>
</xmlserver>
<radegastserver>
<enabled>0</enabled>
</radegastserver>
<cache>
<emm>10</emm>
<ecm>-1</ecm>
</cache>
<debug>
<darint39>sintoi51</darint39>
<level>internal</level>
<type>all</type>
<output>console, tcp</output>
<logfile>/tmp/newcs.txt</logfile>
<console_options></console_options>
<file_options></file_options>
<udp_host>172.16.1.1</udp_host>
<udp_port>9000</udp_port>
<udp_options></udp_options>
<tcp_port>1001</tcp_port>
<tcp_options></tcp_options>
</debug>
<newcamdserver>
<enabled>yes</enabled>
<name>local</name>
<deskey>01 02 03 04 05 06 07 08 09 10 11 12 13 14</deskey>
<user>
<name>dummy</name>
<password>dummy</password>
<hostname>127.0.0.1</hostname>
<port>12000</port>
</user>
</newcamd_server>
</newCSconfig>

and create a file newcamd.list inside folder mgcamd with the following :


CWS = 127.0.0.1 20000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan local
CWS_INCOMING_PORT = 12000

Now start both newcs & mgcamd in plug-ins menu with no other emu activated . Reboot az .

Cheers ,
Val .

paulwilko
02-09-2009, 12:33 PM
Val, i appreciate your help, but i am not using mgcamd, i am using cccam and that is working.

Is there a reason you mention MGCamd ?

valerica
02-09-2009, 01:42 PM
The reason is my via 2.6 card doesn't work with newcs+cccamd . All I get in /tmp ecm.info is "unsupported cas" .

Cheers ,
Val .

paulwilko
02-09-2009, 02:54 PM
I believe mine and the new ART cards are Viaaccess 3.0 ?

goran
02-09-2009, 03:11 PM
It should work in Mbox, without NewCS...

When the update comes - activate NewCS and MGcamd, then, after the AU is done - back to Mbox...

Because, for now Mbox doesn't handle EMMs, so no updates in it.

But we are hopeful Mower will deal with it soon, one way or another... Maybe even via MultiCAS?

We'll see...:cheers2:

paulwilko
02-09-2009, 03:29 PM
It should work in Mbox, without NewCS...

When the update comes - activate NewCS and MGcamd, then, after the AU is done - back to Mbox...

Because, for now Mbox doesn't handle EMMs, so no updates in it.

But we are hopeful Mower will deal with it soon, one way or another... Maybe even via MultiCAS?

We'll see...:cheers2:
THx matey

So are we saying that my combination of CCcam + newcs + Art card is never gonna work ?
My peers will be pleased :ack2:

If that is the case, I have an Eagle box which worked perfectly, is there anyway i can have two boxes on the same network, Eagle for my peers and my Azbox reading from the Eagle CCcam ? Or is this getting way too complicated ?

I dont need my eagle to be connected to my satelitte or anything so literally just onto the network i would assume ?

hanswurscht
02-09-2009, 06:16 PM
it has NOTHING to do with Box, EMu are in basics all the same from Funktion!
As I say, get Infos about your Card how to get it working in NewCS or MPCS or any Server.
Other can do this also, and also with AZHD

But I see you only writing, not reading any

goran
02-09-2009, 06:21 PM
Sadly, your last sentence seems quite true...:smash:

paulwilko
02-09-2009, 06:45 PM
it has NOTHING to do with Box, EMu are in basics all the same from Funktion!
As I say, get Infos about your Card how to get it working in NewCS or MPCS or any Server.
Other can do this also, and also with AZHD

But I see you only writing, not reading any
I find your last sentence a bit harsh actually, please do not get onto Gorans bandwagon.

The trouble with this hobby and many others is that alot of info gets very fragmented all over the web with many different theories on what works and what doesnt and hard to put it all together easily when you are relatively new to it.

Now if you want to talk to me about something you did not understand, do you think i would just give you link after link and say go read, i would help with your specific issue.

Gorans guide although helpful, falls short of specifics, hence why i am asking.
Guides are good, but because each individuals cir***stances are different, specific questions need to be asked.

Now if i have missed something, that does not mean i have not read, it means i just plain dont undestand.

If you dont want to help, thats fine, but to accuse without actually knowing how many hours i put into reading, is nothing short of just wrong.

In reply to your comment, i have read my card does work on some but not on othes and sadly my combination seems to be a non working one.
I got all that from reading, if you know different, then please point me in the direction of where you read the info stating it works.

Why are alot of people so intent on having a go instead helping, i would help if i could and if you look, i have done my best to help someone today with the limited knowledge i have an dthere was no hint of a link in my reponse !!!!!

Thx

Paul

hanswurscht
02-09-2009, 06:50 PM
No my Friend I hate Ignorance and also posting not the Trues (see ur other thread)
My tip again, try with reading or take a broken Eagle

paulwilko
02-09-2009, 07:08 PM
No my Friend I hate Ignorance and also posting not the Trues (see ur other thread)
My tip again, try with reading or take a broken Eagle
I don't tell untruths. If i am mistaken, thats exactly what it is, mistaken, not a lie on purpose, so you will have to tell me what it is i have said that is untrue ?
So now you are calling me ignorant as well as your freind !!!!

Please read, who mentioned a broken Eagle ?

Mine works perfectly except for no HD, that is the only reason i bought the Azbox, not for any fancy stuff, literally to card share and watch HD

goran
03-09-2009, 05:04 AM
Why would anyone who reads carefully still want to use CCcam over Mbox, if in both cases one needs to use NewCS to read one's card?

CCcam is buggy, the interceptor makes it slow, it locks up after a few changes/zapping etc. etc. Great to have it but...

We all tell you to switch to Mbox and you are still ignoring it. Oh, well...

paulwilko
03-09-2009, 09:26 AM
Why would anyone who reads carefully still want to use CCcam over Mbox, if in both cases one needs to use NewCS to read one's card?

CCcam is buggy, the interceptor makes it slow, it locks up after a few changes/zapping etc. etc. Great to have it but...

We all tell you to switch to Mbox and you are still ignoring it. Oh, well...
In all seriousness, I have also read that people have issues with MBOX.
Although it seems slightly better, i have come to the conclusion that my cccam is working to a certain degree and good enough until we get a fully working AZBOX that accepts all sorts.

We'll see, i may yet change, but as you know, i am still to get to grips with the box anyway before i start to change again

rtificial
03-09-2009, 01:00 PM
In all seriousness, I have also read that people have issues with MBOX.
Although it seems slightly better, i have come to the conclusion that my cccam is working to a certain degree and good enough until we get a fully working AZBOX that accepts all sorts.

We'll see, i may yet change, but as you know, i am still to get to grips with the box anyway before i start to change again

I'm trying to bring this with all required respect, but going through your extensive amount of postings, the general way you present yourself is with a lot of questions, brought to the forum as 'problems'.

I hope you see the difference between questions and problems.

As a suggestion, I hope you are able to accept that some of the topics you involve yourself in, are maybe not the topics on which you have an extensive knowledge. This may lead to the situation where your lack of knowledge is the real problem, and the situation you're facing, or the wish you have, might better be approached while listening to people who try to help you, and carefully evaluating their suggestions.

Taykun
03-09-2009, 01:27 PM
In all seriousness, I have also read that people have issues with MBOX.
Although it seems slightly better, i have come to the conclusion that my cccam is working to a certain degree and good enough until we get a fully working AZBOX that accepts all sorts.

We'll see, i may yet change, but as you know, i am still to get to grips with the box anyway before i start to change again

sorry but you are wrong. Mbox works great. IIt has a few problem but you probably wont noticed them. Mbox is still beta but atm its working great for me.
I tested all cccams on azbox. The best one is 0.2 but its only client. Native one sucksss. Mbox much better!

paulwilko
03-09-2009, 01:36 PM
I'm trying to bring this with all required respect, but going through your extensive amount of postings, the general way you present yourself is with a lot of questions, brought to the forum as 'problems'.

I hope you see the difference between questions and problems.

As a suggestion, I hope you are able to accept that some of the topics you involve yourself in, are maybe not the topics on which you have an extensive knowledge. This may lead to the situation where your lack of knowledge is the real problem, and the situation you're facing, or the wish you have, might better be approached while listening to people who try to help you, and carefully evaluating their suggestions.

Questions are problems !!! Don't get that at all, dont bother replying because it doesnt matter !!

My issue is now sorted anyway.

I had the good fortune of a guy called jimrare from this forum contacting me via PM

What a nice guy, helped and did not hinder, do you understand the difference ?

Anyway, luckily i still have my Eagle box, so i stuck my card in my Eagle, put it on the network and configured the cfg file with all the F Lines
On the azbox i configured the CFG file with all C lines

Now i get my card as hop 1 to my azbox and all my peers get it also

I am now happy until AZbox does a new FW that will make it work with CCcam.

What jimrare did for me is not on any links that have been given to me, so this is why i needed help on a specific issue, it was not standard really.

Anyway, all is done

If i can help anyone with a similar issue, then i will try

THx all

Paul

rtificial
03-09-2009, 02:38 PM
Good to hear that you found help and have been able to get things running. :respect-054:

As you describe it is not in any way like it was described in this thread, it would be nice if you could explain what the working configuration looks like.

hanswurscht
03-09-2009, 03:09 PM
Questions are problems !!! Don't get that at all, dont bother replying because it doesnt matter !!

My issue is now sorted anyway.

I had the good fortune of a guy called jimrare from this forum contacting me via PM

What a nice guy, helped and did not hinder, do you understand the difference ?

Anyway, luckily i still have my Eagle box, so i stuck my card in my Eagle, put it on the network and configured the cfg file with all the F Lines
On the azbox i configured the CFG file with all C lines

Now i get my card as hop 1 to my azbox and all my peers get it also

I am now happy until AZbox does a new FW that will make it work with CCcam.

What jimrare did for me is not on any links that have been given to me, so this is why i needed help on a specific issue, it was not standard really.

Anyway, all is done

If i can help anyone with a similar issue, then i will try

THx all

Paul

Its a Workaround but not a Solution.

You can trust me, I dont need an Hour to get your Card working on AZHD(newCS on AZHD and also Client CCcam on AZHD and Card in AZHD) with connecting to CCcam, this is easy, and Im NOT an Expert, but a good Reader.
I try to understand, if not I read again and very very low Questions
But (of course there is a but) I have no Interest to do your Job!

We all give you the Basic of Knowledge, but the special Things for your Card, your Network and so on is your Part.
The only Part is seraching the Information, how have other People get it working, specially this Card and voila, you must only repeat that.

At the End a Word to CCcam, its not stable, its not reliable, its freezing all the time and no Record really working.

If this Bugs are the Price for present Peers, OK, its your Price then.

If you want an 99% errorfree CS without any Reboot over Month, with a perfect Record, with most never freezing, you are on the wrong Road, the the next right exit and get mbox.

paulwilko
03-09-2009, 03:17 PM
Its a Workaround but not a Solution.

You can trust me, I dont need an Hour to get your Card working on AZHD(newCS on AZHD and also Client CCcam on AZHD and Card in AZHD) with connecting to CCcam, this is easy, and Im NOT an Expert, but a good Reader.
I try to understand, if not I read again and very very low Questions
But (of course there is a but) I have no Interest to do your Job!

We all give you the Basic of Knowledge, but the special Things for your Card, your Network and so on is your Part.
The only Part is seraching the Information, how have other People get it working, specially this Card and voila, you must only repeat that.

At the End a Word to CCcam, its not stable, its not reliable, its freezing all the time and no Record really working.

If this Bugs are the Price for present Peers, OK, its your Price then.

If you want an 99% errorfree CS without any Reboot over Month, with a perfect Record, with most never freezing, you are on the wrong Road, the the next right exit and get mbox.

I appreciate there is probably a better solution out there, but right now i am pleased i wont be getting emails asking where has my local card gone.

You are right, it is a workaround.
Now i have it working, i can maybe look at the alternatives again with a little more patience.

Cheers

Paul

joopajaa
03-09-2009, 03:29 PM
Little offtopic:

What I need (plugin, cam??) to use my original conax (cable) card and watch pay-channels here in Finland?

Box is still in "shipping" status but will be:

- Premium with 500GB
- dvb-s (+dvb-c tuner) ordered
- propably I will install newest FW ASAP.


off-off topic: Can I install the dvb-c as second tuner or do I have to remove the dvb-s and replace it with c (I have no dish)? Twintuner status?

hanswurscht
03-09-2009, 03:57 PM
Twintuner will not work with actual Hardware.
Ive heard about a peace of change on Tuner or additional Hardware on Tuner.
At the Moment you can install both Tuner, no need to change. But you can use only one at same Time, so record from one and looking from other is not possible now

joopajaa
09-09-2009, 06:38 AM
Got it yesterday, some notes:

- I can seek only manually DVB-C channels (there is only "general, germany, brazil in country selection, no finland yet :/ )

- I cant see scrambled channels, I think my local card is NOT seen by unit. I have original CONAX-cable card (works as a charm with other STB)

--> What should I install?? I remember I used cccam on dreambox, same here??



- Very buggu FW (lost hdmi audio all the time, crashes, not playing .mkv 1080p....

- the metal "plate" from dvb-c tuner is missing (have to contact seller) so I really cant attaach my second tuner as it remains loose.

joopajaa
09-09-2009, 08:04 PM
Please, anyone has information about conax? I installed cccam 0.2 but it did not help.

Also: can I even use the smartcard slot? I have no card on CI-slots, I only have one original conax card in the smartcard slot.


SOLVED: works using openxcas and multicas