Discussion about Q-Box HD EMU Edition
- Thread starter djnassar75
- Start date
dexter_nlb
VIP
- Messages
- 67
what does "leaves for little seconds" mean?
it works for a periode and stops? that seems to be a general problem with incubus on all platform and only for some people but ok.
Just maybe its not perfect on QboxHD..but ip9000 shows many issues too.
Hello , I also have a beta box from february but is working with the last image and boot update from 11.06.2009. Incubus 0.83 is not working for me with this image or prevoius ones, the incubus client is conecting to the server but is not sending any ECM, only incubus 0.55 ( and is working fine now ) is working.
dexter_nlb
VIP
- Messages
- 67
if you test it by hand, ie. run binary in shell, then it will fail. you need to use the supplied script(/var/bin/start_incubus) to make it run and send ECM correctly..
that is the only way to work with incubusCamd 0.83 for now.. officially qboxHD is not supported, so this is a workaround and works quite fine.. and remember to use new config supplied with 1.4, as the one ones for 0.55 is not compatible.
Thanks, I reinstall the box image and then the emu and it works :thum: the image appears much faster than 0.55 but unfortunately for me after I change 3- 4 encrypted channels the box hangs up, also if I try to start incubus-newcs or mbox-newcs "2lcamd" process could not be killed and newcs can't access the local card, only the "launcher" process is killed. I tried to manual kill the process from the console but the process is still there active, you have any idea how to kill this process, thanks anyway, you've done a great work.
dexter_nlb
VIP
- Messages
- 67
ok,? 2lcamd is not killed?
problem is my box cannot be upgraded to latest release, so i cannot test, and ive seen the 2lcamd being shutdown fine on previous images?
can you try to use the kill -5 PID? or killall -5 2lcamd ?
problem is my box cannot be upgraded to latest release, so i cannot test, and ive seen the 2lcamd being shutdown fine on previous images?
can you try to use the kill -5 PID? or killall -5 2lcamd ?
dexter_nlb
VIP
- Messages
- 67
and yes, i know the channel switch seems to be a problem in some setups.. not sure if its compatibility or simply incubus issue..
when i tried it on ip9000 in previous versions it was just as unstable, but other reported it worked fine, so im not sure what the reply to your problem should be
when i tried it on ip9000 in previous versions it was just as unstable, but other reported it worked fine, so im not sure what the reply to your problem should be
QBOXHD + incubus 0.83
Newcamd With incubus 0.83
Newcamd gives an image for 5 secs then goes black, gives an image for 5 sec then goes black, .... and so on ...
I use my own newcamd server wich runs very fine for
Diablo newcamd Client
Technomate 6900HD super newcamd Client
CCcam With incubus 0.83 (i use my internal CCcam server)
Incubus gives me 5 Max 10 minutes of very clear video and good audio.
SECA3 (tv vlaanderen en Nederland Digitaal) is a torture.
You have to switch forth and back in order to get a picture.
Sometimes you get Audio with no screen.
Sometimes you get a black screen and you wait 20 secs , then everything works.
Still, incubus is not stable enough to watch anything in my humble opinion ! ( But we are getting closer)
Newcamd With incubus 0.83
Newcamd gives an image for 5 secs then goes black, gives an image for 5 sec then goes black, .... and so on ...
I use my own newcamd server wich runs very fine for
Diablo newcamd Client
Technomate 6900HD super newcamd Client
CCcam With incubus 0.83 (i use my internal CCcam server)
Incubus gives me 5 Max 10 minutes of very clear video and good audio.
SECA3 (tv vlaanderen en Nederland Digitaal) is a torture.
You have to switch forth and back in order to get a picture.
Sometimes you get Audio with no screen.
Sometimes you get a black screen and you wait 20 secs , then everything works.
Still, incubus is not stable enough to watch anything in my humble opinion ! ( But we are getting closer)
I so that this trouble with "2lcamd" process kill depends from image to image, I tried, kill -5 2lcamd or kill -9 2lcamd, for some receiver file system releases is working, for others not. For example with the image that was released today 2lcamd process could be killed with no problem. Regarding incubus for the moment I will remain to 0.55, thanks for your prompt answer.
Example : CCcam + newcamd / Incubus 0.83
for newcamd remove the # before [Prov:00006C:CaID:0100]
& before the newcamdline example
##############################################################################
# incubusCamd configuration file #
# All configuration options in this file observe the same format: #
# <configuration_name>=<configuration_value> #
# #
# Each section are [<section_name>:<option_1>:<option_x>] like. #
# #
# No matter about white spaces on any place or UNIX/DOS style files #
##############################################################################
########################### general configuration ############################
[General]
# Enable (1) or disable (0) background execution
# 0 - Off
# 1 - On
background_execution=1
# This sets the level of console output for debugging:
# 0 - No debug messages, 1 - First level debug messages, 2 - Second level debug messages,
# 3 - Print all debug messages
debug_level=1
# This option enables (1) or disables (0) the writing of debug information to the
# console.
log_to_console=0
# This option enables (1) or disables (0) the writing of console output to a log file
log_to_file=1
# When log_to_file is set to 1, this is the path and filename to write console
# ouput to.
logfile_name=/tmp/incubusCamd.log
# Used to activate on-screen messages. Username and password required if
# HTTP authentication is enabled on enigma.
on_screen_messages_show=1
on_screen_messages_username=root
on_screen_messages_password=
on_screen_messages_key_update=1
on_screen_messages_wait_for_key_update=0
on_screen_messages_ecm=0
on_screen_messages_emm=0
#When activated, camd will listen on the specified port for connections. All
#log activity will be broadcast in real-time to connected clients.
console_logs_broadcast=0
console_logs_broadcast_port=666
############################ caid configuration ##############################
#
# First of all the cam use the incubusCamd.prio file, then use the
# configuration below.
# Sections are defined by the value of the CaID.
# You can choose the default ecm table used by the codify, this means that
# you can choose the first byte of the raw ecm that is downloaded from sat.
# If you don't know what value to insert, use "80". (all value are in hex)
# Default value for ecm_table is 0x80.
# The option "priority" tells if one caid should be selected before try
# another one with a priority value greater.
# The less is the value the greatest is the priority. Choose from "0" to any value,
# priority value is decimal.
#
[CaID:0100]
ecm_table=80
priority=1
[CaID:0500]
ecm_table=80
priority=1
[CaID:0600]
ecm_table=80
priority=1
[CaID:0919]
ecm_table=80
priority=1
[CaID:093B]
ecm_table=80
priority=1
[CaID:0B00]
ecm_table=80
priority=1
[CaID:0D00]
ecm_table=80
priority=1
[CaID:1700]
ecm_table=80
priority=1
[CaID:1800]
ecm_table=80
priority=1
[CaID:2600]
ecm_table=80
priority=1
########################### provider configuration ###########################
#
# All parameters are in hexadecimal notation.
# Each section is defined by the provider id value.
# If you don't know the provider id value then use the provider id "000000" and ca id "0000".
# On provider 000000 caid 0000 goes all provider wich are not declared. If the provider
# is declared then the cam will use the provider founded.
#
#[Prov:00006C:CaID:0100]
# ----------------------------------------------------------------------------
# Decoder type indicates whether the cam will attempt to decode this provider
# in software, or through a card-server. Supported values are:
#
# 0 - Use internal softcams.
# 1 - Connect to a card sharing protocol card-server.
decoder_type=1
# URL of card-server to use, formats are as follows:
#
# newcamd://<username>:<password>@<hostname>:<port>/<des_key>
# aroureos://@<hostname>:<port>
# radegast://@<hostname>:<port>
#
# Example:
# newcamd://foo:[email protected]:12345/0CE3476FF2E1C9D9A0A109B371E3
#
# Multiple card-server url's can be specified for server fail-over.
# If the emu fails to connect or fails to get valid CW's, it will try to
# connect to other servers in a round-robin fashion.
#
# Up to 16 servers can be added from index 0 to 15.
#
# You can choose also to select a cccam or gbox server, but they must be declared
# in the "servers configuration" section ( [Servers] ).
# e.g. : if you want to use a cccam server for a provider you must put it on
# the parameter card_server_url_0=cccam://
# NO MATTER the value after the double slash because server configuration is
# made in the section [Servers].
# Only for newcamd, radegast and aroureos is usefull to put correct connection
# parameters because they are provider dependent.
#
#
# Example i want to use mine card into the slot with newcs for prov 006C on Seca (caid 0100)
#card_server_url_0=newcamd://qbox:[email protected]:51000/0102030405060708091011121314
[Prov:000000:CaID:0000]
# this provider is a stand-in for all cards and all caid not declared previously
#
# For example I choose to use cccam protocol on all other provider.
#
decoder_type=1
card_server_url_0=cccam://
########################### servers configuration ############################
[Servers]
#
# This is the section for the multi-server configuration.
#
# URL of card-server to use, formats are as follows:
#
# cccam://<username>:<password>@<hostname>:<port>/<receive_emu_shared>/[EMM]
# where <receive_emu_shared> should assume value "yes" (without quotes, if you like to receive emus data shared by the server) or "no" (this is assumed by default)
#
# gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>/[EMM]
#
# NOTE: The "EMM" suffix is optional and tells the card-server client whether
# to send EMM's to the card-server or not. Enabling or disabling this only
# has effect if the card-server is configured to accept emms from this client.
#
# NOTE 2: The "card_server_url" is not the same as previously declared in the prov/caid section
# use how many server as you like
#
card_server_url=cccam://qbox:[email protected]:14000/EMM
#card_server_url=cccam://<username>:<password>@<hostname>:<port>
#card_server_url=cccam://<username>:<password>@<hostname>:<port>
#card_server_url=gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>
########################### CaIDs tunneling configuration ############################
[CaIDTunnel]
#
# All values are in hex notation
# In this file you can configure what CAIDs/PIDs incubusCamd should tunnel to another CAID
#
# situation 1: this caid, all idents, on all channels will use the tunnel_caid
# caid:tunnel_caid
#
# situation 2: this caid/ident pair will use the tunnel_caid
# caid:tunnel_caid:ident
#
# situation 3: this caid/ident pair, on channel 'sid' will use the tunnel_caid
# caid:tunnel_caid:ident:sid
#
# i.e:
1833:1702:000000:0082 # this one should tunnel premiereHD nagra3 into betacrypt cards
1833:1702:000000:0081 # this one should tunnel premiereHD nagra3 into betacrypt cards
for newcamd remove the # before [Prov:00006C:CaID:0100]
& before the newcamdline example
##############################################################################
# incubusCamd configuration file #
# All configuration options in this file observe the same format: #
# <configuration_name>=<configuration_value> #
# #
# Each section are [<section_name>:<option_1>:<option_x>] like. #
# #
# No matter about white spaces on any place or UNIX/DOS style files #
##############################################################################
########################### general configuration ############################
[General]
# Enable (1) or disable (0) background execution
# 0 - Off
# 1 - On
background_execution=1
# This sets the level of console output for debugging:
# 0 - No debug messages, 1 - First level debug messages, 2 - Second level debug messages,
# 3 - Print all debug messages
debug_level=1
# This option enables (1) or disables (0) the writing of debug information to the
# console.
log_to_console=0
# This option enables (1) or disables (0) the writing of console output to a log file
log_to_file=1
# When log_to_file is set to 1, this is the path and filename to write console
# ouput to.
logfile_name=/tmp/incubusCamd.log
# Used to activate on-screen messages. Username and password required if
# HTTP authentication is enabled on enigma.
on_screen_messages_show=1
on_screen_messages_username=root
on_screen_messages_password=
on_screen_messages_key_update=1
on_screen_messages_wait_for_key_update=0
on_screen_messages_ecm=0
on_screen_messages_emm=0
#When activated, camd will listen on the specified port for connections. All
#log activity will be broadcast in real-time to connected clients.
console_logs_broadcast=0
console_logs_broadcast_port=666
############################ caid configuration ##############################
#
# First of all the cam use the incubusCamd.prio file, then use the
# configuration below.
# Sections are defined by the value of the CaID.
# You can choose the default ecm table used by the codify, this means that
# you can choose the first byte of the raw ecm that is downloaded from sat.
# If you don't know what value to insert, use "80". (all value are in hex)
# Default value for ecm_table is 0x80.
# The option "priority" tells if one caid should be selected before try
# another one with a priority value greater.
# The less is the value the greatest is the priority. Choose from "0" to any value,
# priority value is decimal.
#
[CaID:0100]
ecm_table=80
priority=1
[CaID:0500]
ecm_table=80
priority=1
[CaID:0600]
ecm_table=80
priority=1
[CaID:0919]
ecm_table=80
priority=1
[CaID:093B]
ecm_table=80
priority=1
[CaID:0B00]
ecm_table=80
priority=1
[CaID:0D00]
ecm_table=80
priority=1
[CaID:1700]
ecm_table=80
priority=1
[CaID:1800]
ecm_table=80
priority=1
[CaID:2600]
ecm_table=80
priority=1
########################### provider configuration ###########################
#
# All parameters are in hexadecimal notation.
# Each section is defined by the provider id value.
# If you don't know the provider id value then use the provider id "000000" and ca id "0000".
# On provider 000000 caid 0000 goes all provider wich are not declared. If the provider
# is declared then the cam will use the provider founded.
#
#[Prov:00006C:CaID:0100]
# ----------------------------------------------------------------------------
# Decoder type indicates whether the cam will attempt to decode this provider
# in software, or through a card-server. Supported values are:
#
# 0 - Use internal softcams.
# 1 - Connect to a card sharing protocol card-server.
decoder_type=1
# URL of card-server to use, formats are as follows:
#
# newcamd://<username>:<password>@<hostname>:<port>/<des_key>
# aroureos://@<hostname>:<port>
# radegast://@<hostname>:<port>
#
# Example:
# newcamd://foo:[email protected]:12345/0CE3476FF2E1C9D9A0A109B371E3
#
# Multiple card-server url's can be specified for server fail-over.
# If the emu fails to connect or fails to get valid CW's, it will try to
# connect to other servers in a round-robin fashion.
#
# Up to 16 servers can be added from index 0 to 15.
#
# You can choose also to select a cccam or gbox server, but they must be declared
# in the "servers configuration" section ( [Servers] ).
# e.g. : if you want to use a cccam server for a provider you must put it on
# the parameter card_server_url_0=cccam://
# NO MATTER the value after the double slash because server configuration is
# made in the section [Servers].
# Only for newcamd, radegast and aroureos is usefull to put correct connection
# parameters because they are provider dependent.
#
#
# Example i want to use mine card into the slot with newcs for prov 006C on Seca (caid 0100)
#card_server_url_0=newcamd://qbox:[email protected]:51000/0102030405060708091011121314
[Prov:000000:CaID:0000]
# this provider is a stand-in for all cards and all caid not declared previously
#
# For example I choose to use cccam protocol on all other provider.
#
decoder_type=1
card_server_url_0=cccam://
########################### servers configuration ############################
[Servers]
#
# This is the section for the multi-server configuration.
#
# URL of card-server to use, formats are as follows:
#
# cccam://<username>:<password>@<hostname>:<port>/<receive_emu_shared>/[EMM]
# where <receive_emu_shared> should assume value "yes" (without quotes, if you like to receive emus data shared by the server) or "no" (this is assumed by default)
#
# gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>/[EMM]
#
# NOTE: The "EMM" suffix is optional and tells the card-server client whether
# to send EMM's to the card-server or not. Enabling or disabling this only
# has effect if the card-server is configured to accept emms from this client.
#
# NOTE 2: The "card_server_url" is not the same as previously declared in the prov/caid section
# use how many server as you like
#
card_server_url=cccam://qbox:[email protected]:14000/EMM
#card_server_url=cccam://<username>:<password>@<hostname>:<port>
#card_server_url=cccam://<username>:<password>@<hostname>:<port>
#card_server_url=gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>
########################### CaIDs tunneling configuration ############################
[CaIDTunnel]
#
# All values are in hex notation
# In this file you can configure what CAIDs/PIDs incubusCamd should tunnel to another CAID
#
# situation 1: this caid, all idents, on all channels will use the tunnel_caid
# caid:tunnel_caid
#
# situation 2: this caid/ident pair will use the tunnel_caid
# caid:tunnel_caid:ident
#
# situation 3: this caid/ident pair, on channel 'sid' will use the tunnel_caid
# caid:tunnel_caid:ident:sid
#
# i.e:
1833:1702:000000:0082 # this one should tunnel premiereHD nagra3 into betacrypt cards
1833:1702:000000:0081 # this one should tunnel premiereHD nagra3 into betacrypt cards
Last edited:
Hello all,
I have connection with incubuscamd 0.83 to a cccamserver, but I can't open de sky uk channels. Does someone know if incubus supports those channels yet?
Is there maybe another way than incubuscamd to connect the qbox HD to a cccamserver?
Thank you for feedback.
I have connection with incubuscamd 0.83 to a cccamserver, but I can't open de sky uk channels. Does someone know if incubus supports those channels yet?
Is there maybe another way than incubuscamd to connect the qbox HD to a cccamserver?
Thank you for feedback.
dexter_nlb
VIP
- Messages
- 67
did you use the script i made, or just run the binary directly?
running binary directly will NOT work!.. use the script from /var/bin/