Eurocardsharing

Go Back   Eurocardsharing > Sharing receivers > Technomate > Chat

Chat Discussion, Tm9100 wont open sky with card at Technomate forum; hi Im using Tm 9100 and EDG 4.1 for a while ive been using my tm9100 an all been fine ...

Reply
 
LinkBack Thread Tools Display Modes
Tm9100 wont open sky with card
Old
  (#1)
nufclad147
Member
 
nufclad147's Avatar
 
Offline
Posts: 49

Level: 5 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 120
Magic: 16 / 3321
Experience: 82%

Thanks: 0
Thanked 5 Times in 5 Posts
Join Date: Jul 2008
Age: 49
Tm9100 wont open sky with card - 30-September-2008, 22:41

hi
Im using Tm 9100 and EDG 4.1
for a while ive been using my tm9100 an all been fine receiving channels from my pal but 2night ive browt the offical card to my house an placed it in both slots of the tm9100 an neither will open the channels it just remains blank
ive placed the card with the gold chip conectors both facing up an facing down an no joy either way

when i view edg 4.1 control panel in emulator part ccam 2.09 is selected and can toggle between DDCamd andcommon interface. But ccam2.09 is selected

Below this in card server box it says none ..an not option to toggle change it to anything else,im sure in past i could choose default or common interface options in this area

can anyone suggest why the card wont clear channels
   
Reply With Quote
Old
  (#2)
Robxxx7
Donator
 
Robxxx7's Avatar
 
Offline
Posts: 81

Level: 7 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 173
Magic: 27 / 5649
Experience: 95%

Thanks: 11
Thanked 31 Times in 17 Posts
Join Date: Oct 2006
30-September-2008, 23:10

To open sky with the TM9100 you will either need to use CCcam 1.61 (this will also update the card) or Gbox 221/225 or CCcam+NewCS, where NewCS will read the card and feed it to CCcam for sharing. If you use CCcam+NewCS combination then make sure that NewCS is run first before CCcam otherwise CCcam will grab the card readers
   
Reply With Quote
Sponsored Links
Old
  (#3)
leez
Senior Member
 
leez's Avatar
 
Offline
Posts: 111

Level: 9 [♥ Bé-Yêu ♥]
Life: 0 / 213
Magic: 37 / 6046
Experience: 55%

Thanks: 35
Thanked 1 Time in 1 Post
Join Date: Apr 2008
30-September-2008, 23:27

can the peer still use cc cam 2 . 09 . even if tm 9100 ( server )is using 1.61 cc cam cause . gemini 4.4 dm 500 doesn t have 1.61 cc cam ..cheers
   
Reply With Quote
Old
  (#4)
nufclad147
Member
 
nufclad147's Avatar
 
Offline
Posts: 49

Level: 5 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 120
Magic: 16 / 3321
Experience: 82%

Thanks: 0
Thanked 5 Times in 5 Posts
Join Date: Jul 2008
Age: 49
01-October-2008, 00:24

hi leez

many thanks for your time and support robxxx i got past that 1st hurdle an got channels to clear with your help. leez is the pal i was talking about who was serving the card from his dream box to my tm9100,, but because hes on a eletric key metre we wer sick of the box dieing when eletric dropped an he works away periods so decided i would be server.

i installed gbox 2.25 an the channels cleared ok on my tm9100,, because im not used to messing with gbox i tried intstalling newcs.1.62 and as asked made sure that newcs 1.62 was started first before ccam209. So in control panel in emulator section i have ccam209 and in card server area i have newcs1.62 an channels clear on my tm9100 the hosting box :O)

now....what happens is when i came to edit config file to add my peer the ccam config file is downloaded from server an left defult the channels clear on my hosting box tm9100 but, soon as i edit the ccam config file adding my own server listening port ,,add my friend F line and save an exit the channels go off on my 9100 the host box

Below is my config file but as mentioned my channels go blank on my own 9100 host box when the config edited to this ,,yet left as default untouched downloaded from the boxs server the channels clear on my box. I use this layout because its worked for us in the past both using ccam 209 only. leez dreambox had this layout aswell as my tm9100 an id simply add C an F lines to both boxs accordingly. So for now i simply added my peer leez's F line to the default config an change my server listen port an im told by lee the share working but :O)... but id like to know why it fails to clear channels on my box an il guess his too if i use my own layout on config files as seen below

SERVER LISTEN PORT : xxxxx
F: friend1 passywordy
INFO LISTEN PORT : 16000
HTML INFO LISTEN PORT : 16001
ZAP OSD TIME : 0
OSD USERNAME : root
OSD PASSWORD : dreambox
SHOW TIMING : yes
MINI OSD : yes
DEBUG : yes
DISABLE EMM : yes
EXTRA EMM LEVEL : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID IGNORE FILE : /var/keys/CCcam.ignore
LOG WARNINGS : /tmp/warnings.txt

Below is the default untouched config file which opens my channels and allows share to work by simply addin f line an choose my own swerver listen port numbers

# CCcam team uvadi CCcam v2.0.5

################################################## ####################
# 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:
#
#
# 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.
#
################################################## ####################
# connections #
################################################## ####################
# 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
N: 127.0.0.1 11000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14
N: 127.0.0.1 11001 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14


# 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 : 14447

# 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 : <username>
#WEBINFO PASSWORD : <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,smartreader+
# (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:key16(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


# 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)

Last edited by nufclad147; 01-October-2008 at 02:18..
   
Reply With Quote
Old
  (#5)
nufclad147
Member
 
nufclad147's Avatar
 
Offline
Posts: 49

Level: 5 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 120
Magic: 16 / 3321
Experience: 82%

Thanks: 0
Thanked 5 Times in 5 Posts
Join Date: Jul 2008
Age: 49
02-October-2008, 03:52

guess ive stumped everyone then

really i guess what im askin in a nut shell is.. why does my sky channels go blank when using my own config file but opens using original config file. Id thort that only the sharing side would be effected by editing config file.
So ther must be somthing on my short basic config layout once edited saved suddenly stops my sky channels opening on tm9100 host box. so for now i just added a F line to that huge original config file an give leez the C line an im told from him its working. But id like to come to understanding why my own shorter config file suddenly stops the channels opening on my own host box when used.

Last edited by nufclad147; 02-October-2008 at 03:59..
   
Reply With Quote
Old
  (#6)
Robxxx7
Donator
 
Robxxx7's Avatar
 
Offline
Posts: 81

Level: 7 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 173
Magic: 27 / 5649
Experience: 95%

Thanks: 11
Thanked 31 Times in 17 Posts
Join Date: Oct 2006
02-October-2008, 12:58

on the config file you put in the box, does it also have the following ?

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

also check under entitlements on NewCS to see if it still see's your card with your config ..
   
Reply With Quote
Old
  (#7)
nufclad147
Member
 
nufclad147's Avatar
 
Offline
Posts: 49

Level: 5 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 120
Magic: 16 / 3321
Experience: 82%

Thanks: 0
Thanked 5 Times in 5 Posts
Join Date: Jul 2008
Age: 49
03-October-2008, 19:00

it dont have any N lines the config i use is as posted above the 1 shorter 1 that worked in past using ccam209 only but disables the channels opening on my own box when used with ccam209 and NewCS. So just for now to get it working an watching i used orginal untouched config an just adding 1 simpel F line of my peer to the masses of tex an dont add any N lines, i dont delele nothing an my host biox channels open again an the share also works.
My problem is here we just used ccam an never learned anything else so been asked to look under entitlements on NewCS to see if it still see's your card with your config is abit over my head to where that is and where to looK

Last edited by nufclad147; 03-October-2008 at 19:05..
   
Reply With Quote
Old
  (#8)
Robxxx7
Donator
 
Robxxx7's Avatar
 
Offline
Posts: 81

Level: 7 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 173
Magic: 27 / 5649
Experience: 95%

Thanks: 11
Thanked 31 Times in 17 Posts
Join Date: Oct 2006
03-October-2008, 20:20

Ok, on a TM9100, CCcam on its own will not open sky and share it ... It will with CCcam+NewCS


Looking at the above config you have 2 x N lines configured within CCcam.cfg ..

You will need to FTP into your box and go to Var/tuxbox/config and look for a file called Newcs.xml (this is your newcs config file)

Anyway you can check entitlements by putting the following in your web browser whilst NewCS is running

http://your BoxIP:8080

Then use username/password as newcs

if that doesn't work, check go into the Newcs.xml file and check where it says

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


and then use whatever port it says in there ...

This should allow you to see what NewCS is doing with your card

(03-October-2008 19:23)
There are a couple of other things aswell ..

on your CCcam.cfg file for N lines you have

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

you have to make sure the correct ports of 11000 and 11001 are being used within NewCS.xml (they are the default ports so should be ok)

logging into newcs via web browser should tell you whats happening with your card anyway

Last edited by Robxxx7; 03-October-2008 at 20:23.. Reason: Automerged Doublepost
   
Reply With Quote
Old
  (#9)
nufclad147
Member
 
nufclad147's Avatar
 
Offline
Posts: 49

Level: 5 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 120
Magic: 16 / 3321
Experience: 82%

Thanks: 0
Thanked 5 Times in 5 Posts
Join Date: Jul 2008
Age: 49
03-October-2008, 20:55

the N lines on the ccam config files i did not write an only just notcied them ...i only write F fline on my ccam config an my friend has the shorter config file we always used but with my c line
I do get into newcs manager page and i do see in user managment dummy id's , i think i need to go an read the whole workings of newcs...its pleasing but asnnoyin having somthing working but not knowing why it working

having experimented i found that adding the 2 n lines to my simple ccam config files works keeping my channels open an the share i presume will still be working too. I just dont understand why them N lines do the trick

so my config file now looks like this

SERVER LISTEN PORT : xxxxxx
N: 127.0.0.1 11000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14
N: 127.0.0.1 11001 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14
F: friend1 password1 1 1 1
INFO LISTEN PORT : 16000
HTML INFO LISTEN PORT : 16001
ZAP OSD TIME : 0
OSD USERNAME : root
OSD PASSWORD : dreambox
SHOW TIMING : yes
MINI OSD : yes
DEBUG : yes
DISABLE EMM : yes
EXTRA EMM LEVEL : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID IGNORE FILE : /var/keys/CCcam.ignore
LOG WARNINGS : /tmp/warnings.txt

i think robxxx i need to have a rethink to the whole makeup of the share network an emulators as im alittle worried about this card wont update in the tm9100 host ,id rather this did
I take it reprecusins of this happening would mean placing the card in original sky box the card is married too to enable the update to carry thro. This could be a nusens as the original box broke while back. an i can see a nightmare situation will soon come.
Really we are waiting on the arrival of 3rd dreambox for 3rd party of share and thatwill be it complete an will never change. So the solution i sort after would be in your opinion ROBXXX the best emaulators to place on each box for my needs to easy mentain and have card update on a card share compremising of a host box tm9100 and 2 dream box peers receivers only in 2 locations.
My hunch tells me Gbox would be ok for host box tm9100 an maybe keeping 2 dream boxs in locations ccam ,, or what would you suggest or others for a easy to mentain solution.

thanks for help so far

Last edited by nufclad147; 04-October-2008 at 02:46..
   
Reply With Quote
Old
  (#10)
Robxxx7
Donator
 
Robxxx7's Avatar
 
Offline
Posts: 81

Level: 7 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 173
Magic: 27 / 5649
Experience: 95%

Thanks: 11
Thanked 31 Times in 17 Posts
Join Date: Oct 2006
04-October-2008, 14:25

Hi m8,

The N lines are required as an interface between CCcam + NewCS. Newcs will read your sky card then serve it to CCcam for sharing. The N lines are used to tie the 2 emulators together.

By using NewCS in a TM9100 it will update your sky card and checking the entitlements on the NewCS web browser will show this, but the other shares will see your Sky card as being an extra hop away rather than your local ... no great issue as its all on the same box but will be seen as an extra hop.

Alternatively you could use Gbox on the TM9100 to read and update your sky card directly and then share this to other boxes which have CCcam (you will need to perform some additional config within CCcam.cfg to accept gbox shares) but can be done.

If you are using your TM9100 to act just as a server then i would recommend the Andromeda image, this has CCcam+NewCS already preconfigured so its just a matter of adding your F or C lines and away you go ..

Another alternative if you just want CCcam running on all boxes is to use CCcam 1.61 on the TM9100 as this reads sky cards directly and updates them then share via CCcam to your other dreamboxes.

Plenty of choices, just a matter of what would be easist ... i have used CCcam+Newcs within my own LAN network to share to 3 other boxes and its been no problem whatsoever
   
Reply With Quote
Reply

Bookmarks

Tags
card, open, tm9100


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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Forum Jump



ECS on RSS ECS on Twitter ECS on Facebook ECS on Youtube
Follow us on:

Powered by vBulletin
Copyright 2002 - 2010, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2011, Crawlability, Inc.
Dreambox