SamyGO

bump..

can someone give me the output of his device - how the text should look like?
if it's just crypted linear or false encoding i can crack it up then using statistics on the text..

Sorry, I didn't reply on IRC because i was away.
Anyway. CI+ exLink has absolutely no difference in terms of encoding of the Text. It should be just plain Text.

I got unreadable outputs too sometimes, but just on the first Poweron after connecting the cable. A reboot or two usually fixed it.
PL2303 shouldn't be a problem here (@juuso, this isn't a TTL converter. It just emulates a COM Port via USB. This is uncritical in this case, since timing isn't that relevant for exLink)

All I can suggest is checking your cable, try again, or maybe get some "real" rs232 interface just for testing, who knows, maybe your PL2303 is faulty.
For Cable Testing you could connect RX and TX on the 3.5mm plug and type anything in putty. If you get an echo, the cable should be okay.

langerhans wrote:I got unreadable outputs too sometimes, but just on the first Poweron after connecting the cable. A reboot or two usually fixed it.
PL2303 shouldn't be a problem here (@juuso, this isn't a TTL converter. It just emulates a COM Port via USB. This is uncritical in this case, since timing isn't that relevant for exLink)

i tryed it more then once and even after 10 reboots i get the same or nearly same output every time. (some parts of the output are changeing places some time - maybe not fixed boot order or something like that)

langerhans wrote:All I can suggest is checking your cable, try again, or maybe get some "real" rs232 interface just for testing, who knows, maybe your PL2303 is faulty.
For Cable Testing you could connect RX and TX on the 3.5mm plug and type anything in putty. If you get an echo, the cable should be okay.

i will try with a real rs232 as soon as i get hands on one.
sure i have tested the adapter first as loopback (direct at the adapter and with cable in between).
i don't think it is a faulty pl2303 because loopback workes fine with and without cable.
i tested it again one minute ago and it still workes fine in loopback but i found out something interesting:
i can connect to the virtual com port only if the tv is off. if it is on i can't connect to the virtual com port (of course if it is not in use from other programs).

is it possible this is a windows 7 or driver issue?

is it possible that this is also a "feature" the newest firmware was bringing to the device and was not overwritten with the old one?
as written some posts before i had to downgrade it with FFB.
maybe they changed something in production? (bought the device 10/24/2010).

embarrassing...
seems like i mixed up GND and RXD somehow-.-
it looks much better now...
sry for all your effort and help!

edit:
i compared it again to the picture in the wiki and some posts before...
i did it like described there so it seems like samsung twisted the pins in my tv...
(i checked the adapter - the gnd is connected directly to usb gnd so it has to be the tv)