CNX cnxemu v0.1a (alpha release)

cnxemu v0.1a (alpha release)
----------------------------
This Linux app acts like an "IX-200" dongle for Conaxsat boxes.
It will allow you to use your Conaxsat with normal SSSP clients by
converting the "IX-200" dongle format into a more usable "Captiveworks"
SSSP format.

This is compiled for i386 basic CPU type, and will run on any Intel-like
Linux system. With x86_64 you will probably need the 32-bit compatibility
packages installed, however you do that on your distro.

Usage:
./cnxemu <serial device>

If no serial device is given, the default is /dev/ttyS0
You must provide the entire path to the device (include /dev/ always)
You need a "null modem" cable between the Conaxsat and your Linux box.

Upon launch, it will report which PTY device (fake serial port) it has
created for use by your SSSP client software. Configure your SSSP client
to use that port instead of a normal serial device, and make sure it also
supports normal "Captiveworks" type SSSP format, as that is what this app
outputs. Of course you also need to configure your SSSP client to give
it some card sharing server(s) or not much will happen.

This has only been tested with rq-sssp-client v1.04, but there should be
no reason any other SSSP client shouldn't work as well, as long as you can
get them to use a specific device. Some may require symlinks or fiddling
to trick them into opening the PTY device rather than a more standard one.
(hint: "sudo ln -s /dev/pts/8 /dev/ttyS5" and then set your SSSP client to
use /dev/ttyS5 or "COM6" or such, depending on what it expects)

Note the menus on the Conaxsat will show normal information as expected, and
any networking changes are accepted but silently ignored. They don't matter
anyway and you should be configuring your Linux box as normal, so it can get
to the servers you use in your SSSP client. This app does not do any actual
network socket connection, it is only a bridge between the Conaxsat format
and the Captiveworks SSSP format (your SSSP client is what connects to the
server). This also has nothing to do with the server(s) the real dongle would
connect to, it just allows you to use the dongle-enabled STB firmware to do
the same thing most other generic SSSP-enabled receivers can do.

You must run this app and the SSSP client app on the same Linux box, in case
you thought you didn't. The PTY device is only available locally. So just
use "screen" or pop another terminal/console window and be sure to run cnxemu
first (since it dynamically creates the PTY device) and the SSSP client next.
Also if you stop cnxemu with CTRL-C, it will automatically locate and kill the
SSSP client (or whatever is on the other end of the PTY), so no more worries
about it camping out on the device for the next launch of cnxemu.
You do still need to manually fire up the SSSP client when you start cnxemu
again - and cnxemu will complain rather loudly if nothing is picking up the
other end of the PTY, to remind you.

Proper Setup Procedure (tested on the original Nano):
1) IF YOU HAVE A NANO: Obtain these three bins and put them on USB stick:
NAN_7.10_Factory.NPB ("factory" bin)
NAN_4.22.NPB (the "422" bin)
IF YOU HAVE A DIFFERENT MODEL: Same as above just the ones for that instead.
2) Connect the USB stick to the front USB port, fire up the STB
3) Go to menu "Utility" -> "USB"
4) Navigate to the factory bin, select it, install using "Bootloader" option
5) Wait for it to finish and reboot. Sometimes it will sit there with 0
on the front panel, press the remote power button if so (it's in soft-off)
6) Go to menu "Utility" -> "Factory Default", enter PIN, say yes
7) Repeat step 3-6 but with the "422" bin instead
8) Connect serial. Fire up cnxemu. Double check /dev/pts/ path and set it in
your SSSP client. Fire up the SSSP client. (use "screen" or two terms)
9) Go to menu "Utility" -> "System Information" and watch the bottom line for
it to change from "unknown" to "cnxemu v0.1a" (it will take a second)
This verifies your serial connection and that cnxemu is ready.
10) Set up your satellites and do an autoscan, etc
11) Go to a channel you know your IKS provider handles, watch TV.






rq-sssp-client-1.04

RQ-SSSP-client version 1.04

*Coolsat models 4k,5k and 6k will need a Straight-thru Serial Cable as apposed to the Null Modem Cable type.
The C/P below and along with more info can be found in the txt document included in the zip folder which is attached below.

---C/P---
rq-sssp-client, sssp client by raton_craquero
2010-04-08 v1.04

- Added a new configuration parameter to set the timeout for receiving control
words from server (control_words_timeout). Check rq-sssp-client.conf for
details.

- Added a port for OpenWRT routers that use the Atheros chipset
(rq-sssp-client.openwrt-ar231x).

- Added a port to ARM EABI architecture (rq-sssp-client.plug). This port runs on
Plug Computers (plugcomputer.org), such as the SheevaPlug.

- Added a port to the BeagleBoard (rq-sssp-client.beagle). Check out beagleboard.org
It is untested as of this release, please test and report your results.

- NOTE: The OpenWRT Broadcom binary has been renamed to rq-sssp-client.openwrt-bcm947xx

- NOTE: Starting from this release, I won't be including the libstdc++.so.6
file (needed for the router binaries). I suggest you install the Standard C++
Runtime Library using the package management system of OpenWRT, as this is the best
way. There's a way to do it through its web interface or command-line. Look into it.

Attached Files

	cnxemu-0.1a.zip (12.0 KB, 10 views)
	rq-sssp-client-1.04.zip (2.63 MB, 12 views)

__________________

Please don't PM me with fta related questions, ask them in open forums so others can benefit from them too.