Van: NFPS works with Coolsats directly connected to PC. However, you must understand that in general private IKS such as NFPS is up and down quite a bit. The software is easy to install - they say it works much better under Linux, but it also works well with Windows XP SP2 and above. You would need to have your PC on all the time you are using your Coolsat.
Dear Sada, I just got my new i-link 9500 HD receiver as I read the forum it seems like I need the file to down load to my receiver in order to watch T.V. Please help me to setup it up and were can I find the file. My signal s/q is OK Thanks in advance.
General Instruction for the COOLSAT 4000, 5000 and 6000
Setup for COOLSAT 4000, 5000, 6000
# rq-sssp-client configuration file # # All configuration options in this file observe the same format: # # <configuration_name>=<configuration_value> #
General configuration
# Serial port where the client receiver is connected. # Examples: # Linux PC: /dev/ttyS0, /dev/ttyS1, ... /dev/ttyS<n> # Dreambox/TD/DGS: /dev/tts/0, /dev/tts/1, ... /dev/tts/<n> # Windows: COM1, COM2, ... COM<n> serial_port=COM1
# Serial port communication settings. # Example: 115200|8|N|1 = 115200bps, 8 data bis, no parity, 1 stop bit. serial_port_settings=115200|8|N|1
# Sets the byte write delay. The default value of this parameter is 200us # which should work for most receivers. You can tweak this value in case # you're having communication problems. Sensible values for this parameter # go from 0 to 500 (microseconds). # # NOTE: This parameter *has no effect* in the Dreambox versions (PPC and MIPS). byte_write_delay=200
# SSSP protocol variant # 0 - Captiveworks SSSP Protocol (Captiveworks receivers) # 1 - Coolsat SSSP Protocol (Coolsat receivers) # 2 - Gbox SSSP Protocol (Digiwave, Technomate and many other EU receivers) receiver_protocol=1
# CaID mappings. This is used to solve CaID mismatch errors when a # receiver reports the wrong CaID (this can happen when the provider uses # multiple CaIDs). If you're sure the card server you're using supports the # provider, you can override the CaID mismatch check this way. # # Format: # caid_mappings=<original_caid>:<mapped_caid>|<origi>:<mapped_caid>| ... # # Example: Your receiver may report CaID 1802, the card server # reports CaID 1816. Add this mapping: # # caid_mappings=1802:1816 # # You can also add several mappings like this: # # caid_mappings=1802:1816|1803:1816| ... caid_mappings=
# If enabled either the even or odd control word is returned for each # ECM. The single control word is duplicated. This is intended as a fix # for freezing on some receivers when using NDS providers. # 0 - Disabled # 1 - Return Even on 0x80 ECM table id, Odd on 0x81 ECM table id # 2 - Return Odd on 0x80 ECM table id, Even on 0x81 ECM table id # 3 - Always return Even # 4 - Always return Odd return_single_cw=0
# Enable or disable background execution # 0 - Disable # 1 - Enable # # NOTE: Ignored in the WIN32 version. background_execution=1
# This sets the level of console output for debugging: # 0 - Silent, 1 - Basic debug info, 2 - Extended debug info, # 3 - Show all debug info debug_level=1
# This option enables or disables the writing of debug information to the # console. log_to_console=1
# This option enables or disables the writing of console output to a log file log_to_file=0
# When log_to_file is set to 1, this is the path and filename to write console # ouput to. # # NOTE: In the WIN32 version, if enabled, this should be set to a valid # Windows/DOS path. logfile_name=/var/bin/rq-sssp-client.log
# URL of card-server to use, formats are as follows: # # newcamd://<username>:<password>@<hostname>:<port>/<des_key>/[EMM] # # Example: # newcamd://foo:bar@192.168.0.100:12345/0CE3476FF2E1C9D9A0A109B371E3/EMM # # NOTE: The "EMM" suffix is optional and tells rq-sssp-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. # # Multiple card-server url's can be specified for server fail-over. # If the client 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 65 servers can be added from index 0 to 63, plus a non-indexed parameter
# named "card_server_url" EXAMPLE: #1 card_server_url_1=newcamd://godaddy:godaddy@fenfu.dynsite.net:10210/610340344540 6970987123412134/EMM EXAMPLE #2 #card_server_url_0=newcamd://dummy_2:dummy_2@127.0.0.1:10000/0102030405060708091 011121314/EMM EXAMPLE#3 #card_server_url_1=newcamd://dummy_3:dummy_3@127.0.0.1:10000/0102030405060708091 011121314/EMM FIN
These problems can occur because one or both of the following conditions are true:
* The proxy server does not allow connections to local addresses. * Internet Explorer is using the wrong proxy settings or invalid proxy settings. * You got ripped off