Hello and welcome to our community! Is this your first visit?
Register
Results 1 to 1 of 1
  1. #1
    Super Moderator TAZ's Avatar
    Join Date
    Apr 2013
    Location
    Up the road
    Posts
    523

    All XX-Client Releases - (Linux+Windows) - Viewsat/X-Factor/CNX/Coolsat/Captiveworks

    ===============================
    XX-Client Release v2.4
    ===============================

    Protocols supported:

    Viewsat
    CNX
    Coolsat
    Captiveworks

    Notes:

    [caid.ini]

    If you need to use CaID remapping simply place a line for each CaID that needs to be remapped.

    Like so -

    1841=1815
    1802=1816

    [xx-client.ini]

    ----------------------------------------------------------------------
    Setting: serial_port
    Description:

    Serial port receiver is connected to.
    ----------------------------------------------------------------------
    Setting: serial_speed
    Description:

    Serial port speed. I found a baud rate of 19200 works for receivers that use to use a Weather Forecaster and variants (CNX). While a baud rate of 115200 works for all other receivers, including the new Viewsat firmwares that use the Coolsat protocol.
    ----------------------------------------------------------------------
    Setting: server_timeout
    Description:

    Control word retrieval timeout in seconds.
    ----------------------------------------------------------------------
    Setting: server_retries
    Description:

    Number of attempts before connecting to a new server. Setting to '0' will make the client try the next server after first failure.
    ----------------------------------------------------------------------
    Setting: receiver_protocol
    Description:

    Receiver protocol to use.
    1 = Viewsat/X-Factor
    2 = CNX
    3 = SSSP Viewsat/SSSP Pansat/Coolsat
    4 = Captiveworks
    ----------------------------------------------------------------------
    Setting: ignore_caid
    Description:

    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. CaID matching is used to make provider switching faster.
    ----------------------------------------------------------------------
    Setting: background_execution
    Description:

    Setting to 1 makes XX-Client run in the background, like a Windows service. Setting to 0 shows a console Window where input/output data can be monitored.
    ----------------------------------------------------------------------

    [kickstart.bat]

    This should only be necessary for XFactor receivers that have never used a dongle. This causes XX-Client to send a command to the receiver so it will start sending ECM requests, even after hard/soft boots.

    Attached Files


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •