Quantcast XX-Client v2.5.57.273 for Linux x86-Atheros-Broadcom and Windows - FTA Bin Files Servers LinkBox Pinwheel DreamLink Jynxbox IPTV

Members: 163,983
Threads: 139,431
Posts: 683,732
Online: 4390

Newest Member: zagiyodaq




b42891 sat's 91-82 Channel Master dish alignment Dreamlink T5 channels DTV dish mod ftaconcept is back!!! IKS south Linkbox 9000I 110 Linkbox IPTV m3u file nano 2 Quetz @ 77w Samsung sat9182 announcement Sonicview bin transponders

* New promotion VIP sign up, $1 per month. Click Here for more info. The money will help us with the costs to host and maintain this site *

Go Back   FTA Bin Files Servers LinkBox Pinwheel DreamLink Jynxbox IPTV > FTA Receivers - Discussions & Files > XX Client > XX Client Files

Notices


XX-Client v2.5.57.273 for Linux x86-Atheros-Broadcom and Windows

XX Client Files


Closed Thread
 
Thread Tools Display Modes
Old 11-01-2014, 12:59 PM   #1
Filecasterô
VIP Member
 
Filecasterô's Avatar
 
Join Date: Jul 2010
Posts: 574
Reputation: 1409066
Filecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond reputeFilecasterô has a reputation beyond repute

Default XX-Client v2.5.57.273 for Linux x86-Atheros-Broadcom and Windows

c/p

===============================
XX-Client Release v2.5 - Linux
===============================

Protocols supported:

Viewsat
CNX
Coolsat
Captiveworks
Nfusion

Notes:

[INI Format]

All lines that start with a '#' are ignored by XX-Client. All settings consist of a setting name followed by a value.

Example: settings_name=value

[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.

Example: serial_port=/dev/ttyS0
----------------------------------------------------------------------
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.

Example: serial_speed=115200
----------------------------------------------------------------------
Setting: server_timeout
Description:

Control word retrieval timeout in seconds.

Example: server_timeout=8
----------------------------------------------------------------------
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.

Example: server_retries=0
----------------------------------------------------------------------
Setting: receiver_protocol
Description:

Receiver protocol to use.
1 = Viewsat/X-Factor
2 = CNX
3 = SSSP Viewsat/SSSP Pansat/Coolsat
4 = Captiveworks
5 = Nfusion

Example: receceiver_protocol=3

Notes about Nfusion protocol:

The receiver's gateway must be the IP of the device that is running XX-Client.

In a Linux distro such as Ubuntu, you will have to run XX-Client as Root (Administrator).

Example: sudo ./xx-client-x86

serial_port and serial_speed settings are both ignored when receiver protocol is set to 5 (Nfusion).
----------------------------------------------------------------------
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.

Example: ignore_caid=0
----------------------------------------------------------------------

The trick to getting the Nfusion protocol to work is to set the gateway on the nfusion receiver to the router or Linux PC that is running xx-client.

Nfusion bin observations with xx-client Nfusion protocol:

NfHD with bin 27 works with South
NfHD with bin 25 works with North and South
NfHD with bin 24 doesn't work at all (working on getting it to work)

NfSD bins seem to work for both North and South with no problems. Fast provider switching and bad channel recovery.

Note:

This version has no external library requirements. Meaning there is no need to hunt down libstdc++ or pthreads for your router.
__________________
Do not ask me questions. Do not send me PM's. Do not ask to be on my Friends list, I am a 'Bot'.

Filecasterô Version 1.6 for vBulletinģ Copyright ©2005-2013, Autobot Software Ltd.

Last edited by Filecasterô; 11-01-2014 at 01:02 PM.
Filecasterô is offline  
Closed Thread

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:50 PM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
The content on this website is here for educational and test purposes ONLY, use at your own risk. We, FTAConcept will not be held responsible for any problems or actions commited by the users of our site or the files/information posted. If you know anyone is posting illegal files, please use "Contact US" button below to notify us and we will remove it right away.
FTAConcept ©2007 - 2019