dcapper
05-03-2014, 03:49 PM
I have 2 south servers running and I was wondering what's the best setup for the xx-client.ini?
# Serial port receiver is connected to.
serial_port=/dev/ttys0
# Set baud to 19200 for most Viewsat, XFactor and CNX receivers that used
# a dongle.
# Set baud to 115200 for most other receivers and Viewsats running SSSP
# firmware.
# serial_speed=19200
# Control word retrieval timeout in seconds.
server_timeout=14
# Number of attempts before connecting to a new server. Setting to '0' will
# make the client try the next server after first failure.
server_retries=0
# Receiver protocol
# 1 - Viewsat/X-Factor
# 2 - CNX
# 3 - SSSP Viewsat/SSSP Pansat/Coolsat
# 4 - Captiveworks *-Mileage may vary
receiver_protocol=1
# If set to 1, CaID reported by the receiver will be ignored and ECM will be
# sent to server even if there is a CaID mismatch. If you are using a single
# provider you should set this to 1.
ignore_caid=0
# Setting to 1 makes XX-Client run in the background, like a Windows service.
background_execution=0
Should I change the server timeout to a smaller timeout? I'm finding it's not switching to the second server or at least not fast enough.
# Serial port receiver is connected to.
serial_port=/dev/ttys0
# Set baud to 19200 for most Viewsat, XFactor and CNX receivers that used
# a dongle.
# Set baud to 115200 for most other receivers and Viewsats running SSSP
# firmware.
# serial_speed=19200
# Control word retrieval timeout in seconds.
server_timeout=14
# Number of attempts before connecting to a new server. Setting to '0' will
# make the client try the next server after first failure.
server_retries=0
# Receiver protocol
# 1 - Viewsat/X-Factor
# 2 - CNX
# 3 - SSSP Viewsat/SSSP Pansat/Coolsat
# 4 - Captiveworks *-Mileage may vary
receiver_protocol=1
# If set to 1, CaID reported by the receiver will be ignored and ECM will be
# sent to server even if there is a CaID mismatch. If you are using a single
# provider you should set this to 1.
ignore_caid=0
# Setting to 1 makes XX-Client run in the background, like a Windows service.
background_execution=0
Should I change the server timeout to a smaller timeout? I'm finding it's not switching to the second server or at least not fast enough.