Moderator Control Panel ]

TBS5925-BlindScan.exe, why are parameters in L-Band...

TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby User5925 » Sun Nov 06, 2011 10:27 pm

Probably 99 percent of users will be totally confused that the frequency range is not the published satellite transponder frequencies.

There should also be a setting for the 22KHz tone that will automatically follow/adjust-to the frequency band.
User5925
 
Posts: 2
Joined: Sun Nov 06, 2011 10:34 am

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby starman345 » Sun Nov 06, 2011 11:22 pm

seems sttrange they are doing the same thing with the 5925 as with the 8921 months ago...Read here:
viewtopic.php?f=27&t=191
10' dish- Bullseye II c/ku
55.5W to 139W
Windows 8.1 64 bit
TBS 8922 Prof 7301 TBS 6925
starman345
 
Posts: 67
Joined: Wed Jan 19, 2011 6:52 am

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby steven » Fri Nov 18, 2011 11:59 am

Hi User5925

About the Blindscan input frequency range is not the published satellite transponder frequencies.
We are updating this now,and new version will be released soon.

Thanks
steven
 
Posts: 2239
Joined: Fri Aug 06, 2010 3:23 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby Peon » Fri Nov 18, 2011 11:31 pm

Indication tuning is nonlinear. 10% pre-tuning = 95% indication :oops: . It would be an indication of the current scanning frequency. :!: Thanks
TBS 5925, TBS 5927, TBS 6522, TBS 6903, TBS 6983, Prof Revolution 7301,
250cm Prime foc. 96,5E- 53W, 370cm dual Gregorian NWIEE, LNB: C-Band Norsat 8115F,15K, Ku-band NJR2842S PLL + -3ppm, full range Ka band.
And other "iron" for DX reception.
Peon
 
Posts: 28
Joined: Fri Nov 04, 2011 3:39 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby Peon » Sun Feb 19, 2012 6:41 pm

Hi steven,
A new version ( 3.0.0.9) has no change in the entering of frequencies :(
TBS 5925, TBS 5927, TBS 6522, TBS 6903, TBS 6983, Prof Revolution 7301,
250cm Prime foc. 96,5E- 53W, 370cm dual Gregorian NWIEE, LNB: C-Band Norsat 8115F,15K, Ku-band NJR2842S PLL + -3ppm, full range Ka band.
And other "iron" for DX reception.
Peon
 
Posts: 28
Joined: Fri Nov 04, 2011 3:39 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby steven » Tue Feb 21, 2012 2:13 pm

Hi Peon

This new version added all scan for L/H band.
Next week, I will give you a beta version which can enter frequence. : )

Thanks
steven
 
Posts: 2239
Joined: Fri Aug 06, 2010 3:23 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby steven » Fri Feb 24, 2012 3:16 pm

Hi Peon

Here is the new version which have used the satellite frequence .
Hers is the linker:
http://hotfile.com/dl/147624251/ec25c21/tbs-blindscan_v3.0.1.0.zip.html

Would you mind using this new version to have a test.if have any problem, just contact me. :D

Best regards
steven
 
Posts: 2239
Joined: Fri Aug 06, 2010 3:23 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby Peon » Sat Feb 25, 2012 1:50 am

Hi Steven
Thank you. But it works only in the Ku band. The C band is not. Can not scan. Not accept the entry of any frequency. Please fix.
Thanks
Best Regards
Attachments
Error freq. 3.jpg
Error freq.2.jpg
Error freq. 1.jpg
TBS 5925, TBS 5927, TBS 6522, TBS 6903, TBS 6983, Prof Revolution 7301,
250cm Prime foc. 96,5E- 53W, 370cm dual Gregorian NWIEE, LNB: C-Band Norsat 8115F,15K, Ku-band NJR2842S PLL + -3ppm, full range Ka band.
And other "iron" for DX reception.
Peon
 
Posts: 28
Joined: Fri Nov 04, 2011 3:39 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby steven » Mon Feb 27, 2012 4:11 pm

Hi Peon

Thanks for your test report.
And here is the new version.
Would you mind having a test again. :D
Here is the file linker:
http://hotfile.com/dl/147984471/3484fcd/tbs-blindscan_v3.0.1.0.zip.html
Thanks

Best regards
steven
 
Posts: 2239
Joined: Fri Aug 06, 2010 3:23 pm

Re: TBS5925-BlindScan.exe, why are parameters in L-Band...

Postby starman345 » Mon Feb 27, 2012 9:24 pm

With the new test version, and my TBS 8922 ku band blind scanning works fine, on C band, all transponders are scanned correctly if I select pol:v or pol:h, however if I select pol:ALL then only v is scanned, then the program quickly reports total number of found transponders, it seems h is not scanned when pol:ALL is selected.
10' dish- Bullseye II c/ku
55.5W to 139W
Windows 8.1 64 bit
TBS 8922 Prof 7301 TBS 6925
starman345
 
Posts: 67
Joined: Wed Jan 19, 2011 6:52 am

Next

Return to Windows

Who is online

Users browsing this forum: No registered users and 0 guests

cron