VS Platinum & XX-Client

I there, I have a VS Platinum running with the RQ SSP bin. It is attached to a WRT54GS running XX-Client v2.5.57.273 via a serial cable with no luck getting picture. All I can see in the OpenWRT syste log is:

Sep 28 19:12:14 OpenWrt user.debug syslog: xx-client: Connected to xxxxxxx.xxx.xx
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1802]
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Waiting for requests.
Sep 28 19:13:15 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]
Sep 28 19:13:30 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]


Any help will be much appreciated.
Thanks!

set ignore_caid=1 in xx-client.ini

Quote:

---

Originally Posted by negritosanto

I there, I have a VS Platinum running with the RQ SSP bin. It is attached to a WRT54GS running XX-Client v2.5.57.273 via a serial cable with no luck getting picture. All I can see in the OpenWRT syste log is:

Sep 28 19:12:14 OpenWrt user.debug syslog: xx-client: Connected to xxxxxxx.xxx.xx
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1802]
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Waiting for requests.
Sep 28 19:13:15 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]
Sep 28 19:13:30 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]


Any help will be much appreciated.
Thanks!

---

Just curious negritosanto; I have a real close setup as yours (except VS Ultra)
Syslog same as yours; except CaID:1816; and I don't have your last 2 lines.
VS works with windows version of Rq-sssp; but can't get going with router
versions (tried both Rq-SSP & XX-Client)
If not mistaken null modem cable uses only 3 wires (RX, Tx & Gnd.)
That makes me suspect comm settings or adapter board not working properly.
If you have yours running; would love to know what kind of TTL to RS232 adapter
board you have or any peculiar settings you had to change.
Any advice much appreciated.

Quote:

---

Originally Posted by joefish

Just curious negritosanto; I have a real close setup as yours (except VS Ultra)
Syslog same as yours; except CaID:1816; and I don't have your last 2 lines.
VS works with windows version of Rq-sssp; but can't get going with router
versions (tried both Rq-SSP & XX-Client)
If not mistaken null modem cable uses only 3 wires (RX, Tx & Gnd.)
That makes me suspect comm settings or adapter board not working properly.
If you have yours running; would love to know what kind of TTL to RS232 adapter
board you have or any peculiar settings you had to change.
Any advice much appreciated.

---

Hi there Joe... the TTL adapter I'm using is the simplest one using the MAX232 chip (you can see it at hxxp://www.jbprojects.net/articles/wrt54gl_mods/) and the serial cable is the same that I use to program the VS. Goofather has been kind enough to give some pointers but to this day I haven't managed to make the VS work with the router. I've only changed the INI's files with my own server data, serial speed (115200) and SSP protocol (I believe is #3)..Everything else is as stock.... Sorry I wasn't much of a help....

VS Ultra working fine with xx2.4 for windows and easy to set just make sure the correct com port is same as pc/laptop
and you dont need the other stuff

Thanks for the reply negritosanto. I'm familiar with the JBprojects webpage & comparing the board schematics there
with the board I got from nkcelectronics; they look very similar. I also noticed on the jbprojects page a way to test
serial port communications using hyperterminal & the echo command directing it out to /dev/tts/1 when you
SSH into router.
So far no luck, which is probably the why the router doesn't work with rqssp / xx-client.
I haven't given up yet; but I'm getting pretty close.

Quote:

---

Originally Posted by negritosanto

I there, I have a VS Platinum running with the RQ SSP bin. It is attached to a WRT54GS running XX-Client v2.5.57.273 via a serial cable with no luck getting picture. All I can see in the OpenWRT syste log is:

Sep 28 19:12:14 OpenWrt user.debug syslog: xx-client: Connected to xxxxxxx.xxx.xx
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1802]
Sep 28 19:12:15 OpenWrt user.debug syslog: xx-client: Waiting for requests.
Sep 28 19:13:15 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]
Sep 28 19:13:30 OpenWrt user.debug syslog: xx-client: No server with matching CaID. [0 != 1802]


Any help will be much appreciated.
Thanks!

---

you are getting connected
you have a CaID mismatch which would need to be remapped

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

negritosanto; as I was typing my post just a few minutes ago it occurred to me the one thing I did not try.
I was thinking since I had a null modem adapter (swaps pin 2 & 3) on output, I did not have to worry about
confusing Tx/Rx. But then a light came on. I swapped Tx/Rx on the input side of max232 presto.
The whole damn thing works. In other words Tx on router must go to TxIN on max232; Rx on router must go
to RxOUT on max232. Also, follow the instructions on jb projects page for testing serial port using echo;
that worked as well.

Quote:

---

Originally Posted by bobby

you are getting connected
you have a CaID mismatch which would need to be remapped

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

---

The same thing said to me Goofather to do but it didn't work.... But as I said I'm not yet to give up...

Quote:

---

Originally Posted by joefish

negritosanto; as I was typing my post just a few minutes ago it occurred to me the one thing I did not try.
I was thinking since I had a null modem adapter (swaps pin 2 & 3) on output, I did not have to worry about
confusing Tx/Rx. But then a light came on. I swapped Tx/Rx on the input side of max232 presto.
The whole damn thing works. In other words Tx on router must go to TxIN on max232; Rx on router must go
to RxOUT on max232. Also, follow the instructions on jb projects page for testing serial port using echo;
that worked as well.

---

Thst's great but, Have you managed to make it work?

negritosanto,

Been out of town last few days.
Yes, working fine with rq-sssp, just have not got around to try xx-client yet.
My problem was a serial communications issue; not sure about yours.
That's why I mentioned testing your serial port per instructions on JB Projects page.
Assuming you have a PC with serial port, that test just takes a few minutes to setup.
Your serial port has to pass that test or you will never get xx-client or rq-sssp to work.

Now I get this on the OpenWRT log:

Oct 17 20:31:17 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 17 20:31:27 OpenWrt user.debug syslog: xx-client: Server timeout on xxxx.xxx.xx ( > 10 seconds )
Oct 17 20:31:27 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 17 20:31:27 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xxx.xx .
Oct 17 20:31:28 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 17 20:31:30 OpenWrt user.debug syslog: xx-client: Control words not retrieved.
Oct 17 20:31:30 OpenWrt user.debug syslog: xx-client: Channel 0104 unavailable.
Oct 17 20:31:31 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xxx.xx .
Oct 17 20:31:32 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 17 20:31:42 OpenWrt user.debug syslog: xx-client: Server timeout on xxxx.xxx.xx ( > 10 seconds )
Oct 17 20:31:42 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 17 20:31:43 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xxx.xx .
Oct 17 20:31:44 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 17 20:31:44 OpenWrt user.debug syslog: xx-client: Control words not retrieved.

What "Control words not retrieved" means?....

Thanks in advance for any help....

means that it couldnt get the decryption codes.. Probably due to the ongoing ECM.. I would wait a while till the servers recuperate.

Quote:

---

Originally Posted by JCO

means that it couldnt get the decryption codes.. Probably due to the ongoing ECM.. I would wait a while till the servers recuperate.

---

Thanks JCo.. I'll wait a while...

Now I'm getting this:

Oct 19 02:06:10 OpenWrt user.info sysinit: ** xx-client ** Starting /root/xx-cliente//root/xx-cliente/xx-client-broadcom
Oct 19 02:06:12 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:06:13 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:06:13 OpenWrt user.debug syslog: xx-client: Waiting for requests.
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Failed to read network stream.
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:21:19 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Failed to read network stream.
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:23:37 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:23:47 OpenWrt user.debug syslog: xx-client: Server timeout on xxxx.xx.xx. ( > 10 seconds )

It's now "Failed to read network stream."... So, what could it be?

Quote:

---

Originally Posted by negritosanto

Now I'm getting this:

Oct 19 02:06:10 OpenWrt user.info sysinit: ** xx-client ** Starting /root/xx-cliente//root/xx-cliente/xx-client-broadcom
Oct 19 02:06:12 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:06:13 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:06:13 OpenWrt user.debug syslog: xx-client: Waiting for requests.
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Failed to read network stream.
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 19 02:21:18 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:21:19 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Failed to read network stream.
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Retrying. ( 1 of 1 )
Oct 19 02:23:35 OpenWrt user.debug syslog: xx-client: Connected to xxxx.xx.xx.
Oct 19 02:23:37 OpenWrt user.debug syslog: xx-client: Login successful. [CaID: 1816]
Oct 19 02:23:47 OpenWrt user.debug syslog: xx-client: Server timeout on xxxx.xx.xx. ( > 10 seconds )

It's now "Failed to read network stream."... So, what could it be?

---

Up to now here is what I have done and checked:
1. XX-client installed in wrt54g connected to a VS Platinum via serial cable. What I get in the OpenWRT when it tries to retrieve data from server log is "Control words not retrieved".
2. I use another wrt54g but this one has goo-ware v3. Solaris STB does coneect to it and does manage to retrieve data from the same server as above (in another words, I can watch DN).

Any thoughts?

Hello;
Do you have a factory bin for platinum?? I want to start it fresh and looks to me I can't find it anywhere.
Thank you