Hi will some one please inform me on how to and what soft ware needed to make it work i know it can be done but can't seem to do it so i am begging for help. Thank you in advanced.
Printable View
Hi will some one please inform me on how to and what soft ware needed to make it work i know it can be done but can't seem to do it so i am begging for help. Thank you in advanced.
Use the Viewsat/CNX emu to run the xfactor, The last Public IKS files will work
Thanks are you saying to use the last viewsat file but with what loader just a little deeper info please maybe a step by step if you will. And thank you again.
no he didn't say thatQuote:
Originally Posted by chev68
read reply again
The emulator is a program that runs on your computer you can download the emulator HERE
To use your Xfactor with the emulator you will need to connect your receiver to your computer using a serial cable, and run XX-Client following the directions posted in the link above.
yes it's an old thread.
yes it may be a slight jack.
here it goes..
what file to load?
this box uses serial cable instead of null.
using null give receiver data error.
the 0com0 simulator is for null.
this is using xx-client 1.14
install is correct and connects but stops at (client ready waiting for request).
if anyone has made this work please help with above question because they was not answered in earlier request in this thread.
just trying to help members out with a full working description :)
Ive made this work on an xfta router and with xx-client.
the iks file needed is the 3.01 abs. the dgx file is only for the dongle (which isn't used)
the file can be found here...
http://www.satfix.net/showthread.php...S-amp-3-02-DGX
Your com0com settings have to be accurate in order for this to work
What are your com0com settings?
ok that file is loaded(newest).
used the wizard to install.
CNCAO CNCBO is the ports.
here's a working setup.
The serial port in the device manager was set to com1
The virtual ports were assigned com3 & com4 (others use 4&5)
your com0com setup should be found in program files(x86)
make sure there are no hardware conflicts on your com0com drivers
Here 's a hyper-snap of the com0com settings and the config file that reflects those settings
http://www.satfix.net/attachment.php...9&d=1362437716
here's the config file
Code:[General]
serial_port=COM3
emu_serial_port=COM4
receiver_serial_port=COM1
# Timeout for reading data from the receiver in milliseconds.
# Sensible values for this parameter go from 0 to 500 (milliseconds)
# Default Setting: 250
receiver_timeout=250
# Sets the byte read delay for the receiver. This is the pause taken before
# reading data from the COM port connected to the receiver.
# Sensible values for this parameter go from 0 to 500 (milliseconds)
# Note: Especially useful for older hardware. The lower the setting the faster
# channel changes will be. Set higher if you are having issues reading data
# from the receiver. I.E., getting a "ERROR: Invalid receiver data" message.
# Default Setting: 250
receiver_byte_read_delay=250
# Sets the byte read delay for the server. This is the pause taken before
# reading data from the COM port that communicates with rq-sssp-client.
# Sensible values for this parameter go from 0 to 500 (milliseconds)
# Note: Especially useful for older hardware. The lower the setting the faster
# channel changes will be. Set higher if you are having issues reading data
# from the server. I.E., getting a "ERROR: Invalid server data" message.
# Default Setting: 100
server_byte_read_delay=100
# Serial port communication settings.
# Example: 115200|8|N|1 = 115200bps, 8 data bits, no parity, 1 stop bit.
# Default setting: 115200|8|N|1
serial_port_settings=115200|8|N|1
# Sets the byte write delay for the COM port that communicates with
# rq-sssp-client. You can tweak this value in case you're having
# communication problems. Sensible values for this parameter go from
# 0 to 500 (milliseconds). With virtual ports this could probably be set as
# low as 0 but 50 would be more reasonable. A lower setting could help channel
# changing speed.
# Default setting: 50
byte_write_delay=50
# SSSP protocol variant
# 0 - Viewsat (Weather Forecaster to Captiveworks protocol)
# 0 - CNX (Conaxsat to Captiveworks protocol)
# Must be set to 0 when using xx-client
receiver_protocol=0
# Receiver protocol to emulate
# 0 - Auto detect (May not always work...yet)
# 1 - Viewsat (Ultra, Extreme, Pro, 9000HD, Max)
# 2 - CNX (Nano, Trio, Duo, Mini)
emulator_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>|<original_caid>:<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=
# Enable or disable background execution (Hide console window)
# 0 - Disable
# 1 - Enable
# Default setting: 0
background_execution=0
# This sets the level of console output for debugging:
# 0 - Silent, 1 - Basic debug info, 2 - Extended debug info,
# 3 - Show all debug info
# Default setting: 1
debug_level=3
# This option enables or disables the writing of debug information to the
# console.
# Default setting: 1
log_to_console=1
# This option enables or disables the writing of console output to a log file
# Default setting: 0
log_to_file=1
# When log_to_file is set to 1, this is the path and filename to write console
# ouput to.
#
# NOTE: This should be set to a valid Windows/DOS path.
# Default setting: vs-sssp-client.log
logfile_name=xx-client.log
# Timeout in seconds for receiving control words from server.
# Default setting: 12
control_words_timeout=12
card_server_url=newcamd://input server info here in standard newcamd protocal
my set up shows the ports i mentioned not com3 or com4 in both area's.(CNCAO CNCBO) ports
like i said i used the wizard and those was the ports it gave me.
does any of this have to do with internet or router types?
also does this program supply an ip in the network setting of the STB?
i have read and read but i guess i'm missing something.
it seems like i couldn't change the port setting(error used by something else ect..)
also opened up device manager and seen com1 and drivers are current.
I never bothered with the wizard because it only supported a 32 bit os.Quote:
Originally Posted by yappapi
com0com is just a pair of serial drivers that connect the serial device (the receiver) to the rq-client (which does the serial to tcp/ip conversion)
I can't remember if the xfactor is null or straight through if it's null you just need a null cord if it's straight through you will need a double female straight through cable if your connecting to a usb to serial converter
yes null gives receiver data error and straight says waiting for request.
i tried a file to wake up the STB but it says null failed when i ran it.
it also failed with the straight cable.
using an older pc with xp and the 9 pin serial connection.
it appears the xx-client is trying to work because of the error i get when using the null cable.
just seems the STB is not asking for request.
ok going to go read and study what you posted and try a manual set up.
thank you homer for your advice.
there are 3 com0com ports listed in device manager.
bus for serial port emulator 0 (CNCA0 <-> CNCB0)
serial port emulator
serial port emulator
setting are just like homer posted except instead or com3 and com4
these are CNC0 AND CNB0
also the same settings as the config he posted.
null cable gives receiver data error.
serial cable says connected and then says waiting for request.
many boots and channel changes also changed config file around with no success.
eyes are smoked..
i'll wait for some more feedback.
thanks
edit
this is how mine reads at top of config.
# One of the paired virtual serial ports from a driver like com0com.
# Example:
# COM1, COM2, ... COM<n>
serial_port=\\.\CNCA0
# The other one of the paired virtual serial ports from a driver like com0com.
emulator_serial_port=\\.\CNCB0
# Serial port where the receiver is connected.
# Default setting: COM1
receiver_serial_port=COM1
if anyone can make heads or tales..here is the config.
DOS screen
calibrating delay (322) ----done
initializing serial communication----------done
connected
client ready!-- waiting on request...
still using the wizard..manual install confused me :)
not up on commands or changes in DOS if that's needed.
i feel like such a dumbarse..
################################################## #############################
# XX-CLIENT v1.14 [rq-sssp-client wrapper] #
# System Requirements: Windows XP or newer (Pentium I or better) #
# Release Date: April 03, 2012 #
# hxxp://xxxxxxx.xxxp.xxxx #
# All configuration options in this file observe the same format: #
# <configuration_name>=<configuration_value> #
################################################## #############################
############################# XX-CLIENT Settings ##############################
# The other one of the paired virtual serial ports from a driver like com0com.
# NOTE: If you used the WIZARD.EXE app or the INSTALL_VIRTUAL_PORTS.EXE app
# this setting does not need to be changed.
emulator_serial_port=\\.\CNCA0
# Serial port where the receiver is connected.
# Default setting: COM1
receiver_serial_port=COM1
# Timeout for reading data from the receiver in milliseconds.
# Sensible values for this parameter go from 0 to 2000 (milliseconds)
# Default Setting: 500
receiver_timeout=500
# Sets the byte read delay for the receiver. This is the pause taken before
# reading data from the COM port connected to the receiver.
# Sensible values for this parameter go from 0 to 500 (milliseconds)
# Note: Especially useful for older hardware. The lower the setting the faster
# channel changes will be. Set higher if you are having issues reading data
# from the receiver. I.E., getting a "ERROR: Invalid receiver data" message.
# Default Setting: 250
receiver_byte_read_delay=250
# Sets the byte read delay for the server. This is the pause taken before
# reading data from the COM port that communicates with rq-sssp-client.
# Sensible values for this parameter go from 0 to 500 (milliseconds)
# Note: Especially useful for older hardware. The lower the setting the faster
# channel changes will be. Set higher if you are having issues reading data
# from the server. I.E., getting a "ERROR: Invalid server data" message.
# Default Setting: 100
server_byte_read_delay=100
# Timeout for writing data to the COM ports in milliseconds.
# Sensible values for this parameter go from 50 to 2000 (milliseconds)
# Default Setting: 2000
byte_write_timeout=2000
# Receiver protocol to emulate
# 0 - Auto detect (May not always work...yet)
# 1 - Viewsat (Ultra, Extreme, 9000HD, Max)
# 2 - CNX (Nano, Trio, Duo, Mini)
emulator_protocol=1
########################## rq-sssp-client Settings ############################
[General]
# One of the paired virtual serial ports from a driver like com0com.
# Example:
# COM1, COM2, ... COM<n>
# NOTE: If you used the WIZARD.EXE app or the INSTALL_VIRTUAL_PORTS.EXE app
# this setting does not need to be changed.
serial_port=\\.\CNCB0
# Serial port communication settings.
# Example: 115200|8|N|1 = 115200bps, 8 data bits, no parity, 1 stop bit.
# Default setting: 115200|8|N|1
serial_port_settings=115200|8|N|1
# Sets the byte write delay for the COM port that communicates with
# rq-sssp-client. You can tweak this value in case you're having
# communication problems. Sensible values for this parameter go from
# 0 to 500 (milliseconds). With virtual ports this could probably be set as
# low as 0 but 50 would be more reasonable. A lower setting could help channel
# changing speed.
# Default setting: 50
byte_write_delay=50
# SSSP protocol variant
# 0 - Viewsat (Weather Forecaster to Captiveworks protocol)
# 0 - CNX (Conaxsat to Captiveworks protocol)
# Must be set to 0 when using xx-client
receiver_protocol=0
# 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 nal_caid>:<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=
# Enable or disable background execution (Hide console window)
# 0 - Disable
# 1 - Enable
# Default setting: 0
background_execution=0
# This sets the level of console output for debugging:
# 0 - Silent, 1 - Basic debug info, 2 - Extended debug info,
# 3 - Show all debug info
# Default setting: 1
debug_level=1
# This option enables or disables the writing of debug information to the
# console.
# Default setting: 1
log_to_console=1
# This option enables or disables the writing of console output to a log file
# Default setting: 0
log_to_file=0
# When log_to_file is set to 1, this is the path and filename to write console
# ouput to.
#
# NOTE: This should be set to a valid Windows/DOS path.
# Default setting: vs-sssp-client.log
logfile_name=xx-client.log
# Timeout in seconds for receiving control words from server.
# Default setting: 12
control_words_timeout=12
# URL of card-server to use, formats are as follows:
#
# newcamd://<username>:<password>@<hostname>:<port>/<des_key>/[EMM]
#
# Example:
# newcamd://foo:[email protected]: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"
card_server_url=newcamd://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ok i uninstalled com1 driver and re-installed and checked for updated driver.
after i deleted com1 driver i tried to run client.
error on client said couldn't open com port so that tells me it's trying to talk to STB???
tried all file for this STB even n2 files...blah!
i have a sub/stacker so it's not about the channels it's about making this work like others have.
i have ask this before but here it is again...
should this box filling network information?
i have it on dhcp and it is not filling in.
also i can see in router logs the xx-client is connecting and it shows the port.
so the box is not talking to xx-client??
thanks for any input :)
edit
shows "CW" in router instead of "EST"...
CW= control wait.
EST= established.
still trying..........
STB had to be woke up.
and a (((NULL))) cable used.
the end.
strangeeeeeeeeeeeee :)
not the best deal...gets invalid receiver errors sometimes when going to menu and back ect..
had to use another program to kick start the serial port.
serial cable will not communicate.....
but they will work with xx-client like i had been told.
ok back to the closet with it! :)
added:
# from the receiver. I.E., getting a "ERROR: Invalid receiver data" message.
# Default Setting: 250
receiver_byte_read_delay=500
the above change fixed the data error and pulling back xx's from 12 to 8 stopped the freezing.
it actually works very well with a tune up but it's still going back in the closet..lol
thanks again homer for your info..was good on my end except for the cable type and having to give the box a kick in the rear.