Page 1 of 1
TBS 5925 and Gold Code

Posted:
Thu Mar 07, 2013 7:15 pm
by stp
Hi to all,
I'm new on this forum, thanks for your welcome.
I have a TBS 5925 since a few days and I would like to known if an update of drivers and TBS TS Recorder is "on the way" to lock DVBS2 Gold Code Transponder (like 6925).
I use Windows 8 (32 bits) and I can lock only 2 transponders in multistream :
45 east 11591 v 30000
12 west 12718 h 36512
I have tried driver 1.0.1.5, 1.0.1.6 and 1.0.1.6_ 1019.
At the moment I use 1.0.1.6 driver and TS Recorder 3.0.0.6
Thanks for reply and sorry for my poor English !
Regards
Re: TBS 5925 and Gold Code

Posted:
Thu Mar 21, 2013 10:19 pm
by stp
Hello,
Thanks steven for new driver 1.0.1.7 and TS Recorder 3.0.0.7 for TBS-5925.
I use Windows 8 - 32bits with those new drivers and this new TS Recorder.
Test 1 = 5°west 12648 V 29500 Gold Code 121212 transponder alternately locked/unlocked (no succes with other values in Gold or Root)
Test 2 = 5°west 12606 V 29900 Root Code 8 transponder alternately locked/unlocked (no succes with other values in Gold or Root)
Test 3 = 5°west 11676 H 30000 Root Code 16416 transpondeur Locked but no input stream indentify except 0 but not other values
Test 4 = 5°west 11637 V 30000 Root Code 16416 transpondeur Locked but no input stream indentify except 0 but not other values
Test 5 = 5°west 11179 V 30000 Root Code 16416 transpondeur Locked but no input stream indentify except 0 but not other values
Test 6 = 12.5west 12718 H 36515 Code 0 transpondeur Locked but no input stream indentify, I can see 0 but not other values
I can identify the input stream 33 34 35 36 with ProgDVB and scan the channels
This transponder was locked with previous version of TS Recorder and the stream identify 33 34 35 36
Test 7 = 45°east 11591 V 30000 Code 0 transpondeur Locked but no input stream indentify except 0 but not other values
If you want I can test on other transponders between 68.5°east and 45°west in Ku Band with my 1.1m dish.
Sorry for my english...
Regards
Re: TBS 5925 and Gold Code

Posted:
Fri Mar 22, 2013 9:32 am
by steven
Hi stp
>Test 6 = 12.5west 12718 H 36515 Code 0 transpondeur Locked but no input stream indentify, I can see 0 but not other values
I can identify the input stream 33 34 35 36 with ProgDVB and scan the channels
This transponder was locked with previous version of TS Recorder and the stream identify 33 34 35 36
The previous version of TS Recorder have not send the code,if 12.5west 12718 H 36515 have not code value to be set,Please do not
set the value and try again.
Kind Regards
steven
Re: TBS 5925 and Gold Code

Posted:
Fri Mar 22, 2013 4:28 pm
by stp
Hi steven,
Thanks for reply
That 's what I do for this transponder without root or gold, I set no value for code, only "lock TP" the transponder is locked but only "0" appear in the little windows below and not other value !
The Stream are not identified.
Regards
Re: TBS 5925 and Gold Code

Posted:
Fri Mar 22, 2013 8:49 pm
by Derrick
The Stream are not identified.
confirmed!
Just installed new driver and recorder 3.0.0.7 for my 5925. PLS can be set correctly -> lock, but for MIS the input streams can't be identified -> 0
Re: TBS 5925 and Gold Code

Posted:
Fri Mar 22, 2013 10:18 pm
by Derrick
Warning!Do not use this tool !!!
After playing for a while with recorder 3.0.0.7 and driver 1.0.1.7 my 5925 card was completely dead. Pulling the usb- and/or supply-plug didn't help. Down to driver 1.0.1.6 didn't help either. Frustrated I've shut down everything and went for a walk. When I came back the card was working ok again. I must say all (new) tools and drivers from TBS are crap! Pay Crazycat a visit and ask if he will take over

Re: TBS 5925 and Gold Code

Posted:
Tue Mar 26, 2013 4:27 pm
by stp
Hello steven,
Can we hope a fix ?
Thanks for your support.
Regards
Re: TBS 5925 and Gold Code

Posted:
Tue Apr 09, 2013 10:05 pm
by stp
Hello to all,
Since version 6.92.6pro, ProgDVB can identify Multistream with Physical Layer Scrambling (Gold and Root Code) !
I can with my TBS-5925 identify some streams on some transponders but not all the time, the values of stream are not always correctly identified !
I think the problem is "maybe" TBS 5925 drivers ?
Tested with 1.0.1.6 and 1.0.1.7
