First a tip of the hat to CrazyCat for the Prof7500 module and pointing me in the correct direction to post about my situation.
Basically: ProgDVB will not change polarity with TBS.eBDA2 loaded.
Here is a description of my environment:
Win7_64, ProgDVB 6.70.6 Pro x64, Prof 7500, CrazyCat's patched x64 Prof 7500 driver.
The Prof is cabled to an 8-position DiSEqC 1.1 switch, and four of its inputs are cabled to 4x8 multiswitches, such that:
DiSEqC port 1 -> Multiswitch 1:
22 kHz off - Western C band dish H and V (separate LNBs - 18/13v switched)
22 kHz on - Eastern C band dish H and V (separate LNBs - 18/13v switched)
DiSEqC port 2 -> Multiswitch 2:
Quad Universal LNBF on Western Ku band dish (22 kHz and 18/13v switched)
DiSEqC port 3 -> Multiswitch 3:
Quad Universal LNBF on Eastern Ku band dish (22 kHz and 18/13v switched)
DiSEqC port 4 -> Multiswitch 4:
cabled to two dual-output US "standard" LNBFs on two fixed Ku dishes, not yet tested for the problem I describe below.
All positioning is done via outboard positioners.
I have ProgDVB configured to use a 16-port DiSEqC 1.1 switch, with an additional 22 kHz switch on Port 1 (and 4), so:
--switch
:: -- Western C dish
:: -- Eastern C dish
--Western Ku dish
--Eastern Ku dish
--switch
::-- fixed Ku dish 1
::-- fixed Ku dish 2
--empty
--empty .... all others empty up to position #16
I should also state here that this configuration works perfectly with numerous other receivers (stb and usb), and that CrazyCat's CrazyScan/BLScan software also works perfectly on the Windows machine in question.
Here is the problem. With the CrazyCat modules in place in ProgDVB's Modules folder, the Prof will not change polarities on the Western C dish. If I remove them, it does.
Example step by step:
1) No CrazyCat module in place. Perform a satellite scan, transponders and channels scan in on the Western C dish, I can receive channels on H transponders, and channels on V transponders. Let's say that the last channel I tuned in this step was a V.
2) Insert CrazyCat module. Before even doing a blindscan, tune previously scanned channels. Only signals on V transponders will tune. H transponders result in no signal and no quality.
3) Blindscan with CrazyCat module installed. Channels scan in as expected on V, including some new ones But when the blindscan routine switches to H to scan: it ALSO scans the V transponders, since polarity never gets changed. So I wind up with identical scanned channels on V and on H.
4) Tune the newly scanned channels. Receive same signals on V and on H (but they are all V signals, since polarity switching is not working).
5) Remove CrazyCat module. Tune newly-scanned channels. The V ones show up properly, the H duplicates are 0 signal and 0 quality. This is expected, since polarity switching is working again. The original, *actual* H channels (never scanned when CrazyCat module present) also tune correctly.
I should point out that the Universal quad LNBs on DiSEqC positions #2 and #3 do NOT exhibit this problem. They work perfectly with CrazyCat modules present or absent. And, again, stand-alone CrazyScan/BLScan switches polarity correctly on the same box with the same Prof 7500 and switching setup.
I have a second problem unrelated to the presence or absence of the CrazyCat module but will leave that for a bug posting (basically, I cannot receive anything at all on the Eastern C dish with ProgDVB - something goes wrong with the 22 kHz switching "on" required for that DiSEqC position. Once I try to tune there, unsuccessfully, I have to restart ProgDVB to tune anything else on any other DiSEqC position).
Thanks for reading through this long description! I'll be happy to supply additional details upon request.
ncjay
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#2in Modules/TBS.ini set LevelsType=0.
this also must help for TBS8910/Prof6200, Prof7301/8000. But MultiStream selection in this mode not supported (used tuning via driver). But this not important for this devices, because demod not handle 8PSK/VCM multistreams.
this also must help for TBS8910/Prof6200, Prof7301/8000. But MultiStream selection in this mode not supported (used tuning via driver). But this not important for this devices, because demod not handle 8PSK/VCM multistreams.
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#3Thanks, CrazyCat! This suggestions solved the immediate problem described in great detail above
I'm still doing testing with ProgDVB here, and may have further questions this weekend especially with respect to my perceived 22kHz switching problem (described briefly above).
ncjay
I'm still doing testing with ProgDVB here, and may have further questions this weekend especially with respect to my perceived 22kHz switching problem (described briefly above).
ncjay
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#4TBS.eBDA2 submodule updated to 1.0.0.711:
http://crazycat69.narod.ru/sattelite/Pr ... BDAExt.zip
http://crazycat69.narod.ru/sattelite/Pr ... AExt64.zip
LNB voltage switching (polarity) fixed for TBs8910/Prof6200, Prof 7301/7500/8000, TBS6925 V1. Must work with LevelsType=1 or 2.
P.S. 22Khz switching problems related to BDA-drivers. Now must work with tuning via direct control (LevelsType=1 or 2).
http://crazycat69.narod.ru/sattelite/Pr ... BDAExt.zip
http://crazycat69.narod.ru/sattelite/Pr ... AExt64.zip
LNB voltage switching (polarity) fixed for TBs8910/Prof6200, Prof 7301/7500/8000, TBS6925 V1. Must work with LevelsType=1 or 2.
P.S. 22Khz switching problems related to BDA-drivers. Now must work with tuning via direct control (LevelsType=1 or 2).
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#5Thanks CrazyCat - the new version appears to work the same as the older version for me; with LevelsType set to 0, or 1, or 2, I still cannot switch to 22kHz "on" with DiSEqC port 1 (i.e. the eastern C dish). Universal Ku LNBFs on ports 2 and 3 work correctly, and of course western C dish on port 1 (22 khz off) works correctly. I've left LevelsType set to 0 as you recommended earlier.
If I understand you correctly, the 22kHz switching problem is due to the "base" BDA driver and not your driver. If that is the case, then I shall file a bug report in the main Bugs forum.
nc-jay
If I understand you correctly, the 22kHz switching problem is due to the "base" BDA driver and not your driver. If that is the case, then I shall file a bug report in the main Bugs forum.
nc-jay
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#6With LevelType=1,2 transponder tuned via direct chip programming, skip BDA-driver.
My TBS-submodule write some log to Modules\TBS.log. Close ProgDVB, delete old TBS.log, start ProgDVB with LevelsType=1 or 2. And try lock transponders on both C-band satellites on 22Khz switch. And show me TBS.log.
My TBS-submodule write some log to Modules\TBS.log. Close ProgDVB, delete old TBS.log, start ProgDVB with LevelsType=1 or 2. And try lock transponders on both C-band satellites on 22Khz switch. And show me TBS.log.
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#7I've just completed the testing you asked about above. First - a summary of the results, then lots of detail
Test satellites:
107.3W (West C dish; 22kHz = off)
22.0W (East C dish; 22 kHz = on)
SUMMARY
----------
LevelsType = 1 and 2 will only tune H signals on 107.3 - no V signals. When Blindscanning, it scans in only H signals, once on V and once again on H. It looks like the 18v/13v switch is not happening correctly.
LevelsType = 1 and 2 will not tune H signals or V signals on 22.0. It looks like ProgDVB is not turning 22 kHz tone on. Cannot blindscan; progress window appears momentarily, then closes.
LevelsType = 0 will tune both H and V signals on 107.3. Blindscanning will scan in both H and V signals properly.
LevelsType = 0 will not tune H signals or V signals on 22.0. Cannot blindscan; progress window appears momentarily, then closes.
Now the strange part: the "standard" ProgDVB channel scanning routine **does** work on 22.0. Levels and quality appear; channel names scan in. But they still cannot be tuned, either with your extended driver present or without it. So it looks like ProgDVB scanning CAN turn 22 kHz on, but its tuning routine cannot turn it on.
LOTS OF DETAIL
-------------------
LevelsType = 2 test is logged in TBS-LevelsType2.log, pasted below. Here is what I tuned, in order:
107.3w - Montreal - 4040H/30000 (tuned successfully)
107.3w - Ma Maison - 3780V/28350 (did not tune succesfully, showed signal but no quality)
107.3w - CBHT-DT - 4160H/30000 - (tuned successfully)
107.3w - TAC - 3747V/6744 (did not tune successfully)
107.3w - Moncton - 4040H/30000 (tuned successfully)
22.0w - TRRHD - 3994H/30000 (did not tune successfully, and did not get written to logfile)
22.0w - Bolivision - 3761V/22650 (did not tune successfully, and did not get written to logfile)
107.3w - Montreal - 4040H/30000 (tuned succesfully)
107.3w - APTN - 3924V/3000 (did not tune successfully)
Repeating this same set of tuning steps with LevelsType = 0 resulting in *all* successful tunes on 107.3w for both H and V signals, but no successful tunes on 22.0w. Unfortunately, no TUNE entries are written to the logfile with LevelsType = 0 - ??, only the five lines that are written upon initialization of the logfile/ProgDVB execution. (BLSCAN events, however, are written to the logfile.)
Thanks
nc-jay
-----------------------------------------TBS-LevelsType2.log---------------------------------------------
12:44:11 ProgDVB engine BDA-extension module for TBS/Prof v1.0.0.707
12:44:11 Tuner name: Prof 7500 DVBS Tuner
12:44:11 TBS STV090X direct control init ...
12:44:11 Tuner IC: STB6100
12:44:11 Frontend/demod IC: STV090X (cut 2.0)
12:44:14 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:45:05 TUNE: Freq=3780.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=28350 KS, MIS=-1
12:45:05 STV090X_Search() - Search failed
12:45:57 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:45:57 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:47:29 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
12:47:31 STV090X_Search() - Search failed
12:48:02 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:48:03 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:50:19 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:51:07 TUNE: Freq=3924.232 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=3000 KS, MIS=-1
12:51:12 STV090X_Search() - Search failed
Test satellites:
107.3W (West C dish; 22kHz = off)
22.0W (East C dish; 22 kHz = on)
SUMMARY
----------
LevelsType = 1 and 2 will only tune H signals on 107.3 - no V signals. When Blindscanning, it scans in only H signals, once on V and once again on H. It looks like the 18v/13v switch is not happening correctly.
LevelsType = 1 and 2 will not tune H signals or V signals on 22.0. It looks like ProgDVB is not turning 22 kHz tone on. Cannot blindscan; progress window appears momentarily, then closes.
LevelsType = 0 will tune both H and V signals on 107.3. Blindscanning will scan in both H and V signals properly.
LevelsType = 0 will not tune H signals or V signals on 22.0. Cannot blindscan; progress window appears momentarily, then closes.
Now the strange part: the "standard" ProgDVB channel scanning routine **does** work on 22.0. Levels and quality appear; channel names scan in. But they still cannot be tuned, either with your extended driver present or without it. So it looks like ProgDVB scanning CAN turn 22 kHz on, but its tuning routine cannot turn it on.
LOTS OF DETAIL
-------------------
LevelsType = 2 test is logged in TBS-LevelsType2.log, pasted below. Here is what I tuned, in order:
107.3w - Montreal - 4040H/30000 (tuned successfully)
107.3w - Ma Maison - 3780V/28350 (did not tune succesfully, showed signal but no quality)
107.3w - CBHT-DT - 4160H/30000 - (tuned successfully)
107.3w - TAC - 3747V/6744 (did not tune successfully)
107.3w - Moncton - 4040H/30000 (tuned successfully)
22.0w - TRRHD - 3994H/30000 (did not tune successfully, and did not get written to logfile)
22.0w - Bolivision - 3761V/22650 (did not tune successfully, and did not get written to logfile)
107.3w - Montreal - 4040H/30000 (tuned succesfully)
107.3w - APTN - 3924V/3000 (did not tune successfully)
Repeating this same set of tuning steps with LevelsType = 0 resulting in *all* successful tunes on 107.3w for both H and V signals, but no successful tunes on 22.0w. Unfortunately, no TUNE entries are written to the logfile with LevelsType = 0 - ??, only the five lines that are written upon initialization of the logfile/ProgDVB execution. (BLSCAN events, however, are written to the logfile.)
Thanks
nc-jay
-----------------------------------------TBS-LevelsType2.log---------------------------------------------
12:44:11 ProgDVB engine BDA-extension module for TBS/Prof v1.0.0.707
12:44:11 Tuner name: Prof 7500 DVBS Tuner
12:44:11 TBS STV090X direct control init ...
12:44:11 Tuner IC: STB6100
12:44:11 Frontend/demod IC: STV090X (cut 2.0)
12:44:14 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:45:05 TUNE: Freq=3780.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=28350 KS, MIS=-1
12:45:05 STV090X_Search() - Search failed
12:45:57 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:45:57 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:47:29 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
12:47:31 STV090X_Search() - Search failed
12:48:02 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:48:03 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:50:19 TUNE: Freq=4040.012 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
12:51:07 TUNE: Freq=3924.232 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=3000 KS, MIS=-1
12:51:12 STV090X_Search() - Search failed
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#8look like old build 707 update module to latest 711ncjay wrote: 12:44:11 ProgDVB engine BDA-extension module for TBS/Prof v1.0.0.707
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#9oh goodness, how embarrassing :\
OK, will repeat the testing process tomorrow with the updated module
OK, will repeat the testing process tomorrow with the updated module
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#10I just repeated my tests above with v711 in place and with LevelsType = 1.
My results were mostly the same as above, except I can tune the 22 kHz=off position on both H and V polarities with success. I still cannot tune the 22 kHz=on position, in fact, the module's logging routine logs nothing at all when I try to tune that position. And the blindscan "progress" window still disappears almost immediately when attempting a blind scan.
In my log file (pasted below), I tune 7 channels on 107.3w (DiSEqC 1, 22 kHz=off) - alternating between V and H. The channels tune and display correctly. Then I tune an H and a V channel on 22.0w (DiSEqC 1, 22 kHz=on) - but nothing gets written to the logfile. The Ku frequencies I tune after that are on 87.0w, via a universal LNBF on DiSEqC position 2, - and it *does* tune correctly there - both H and V.
A screencap of my LNB/Switch configuration is here: http://dl.dropbox.com/u/5146413/capture ... 173626.jpg
The 22 kHz switch is in DiSEqC position 1, with the west dish on the switch's first position (off) and the east dish (menu expanded) on the switch's second position. I selected "properties" on that LNB so you could see that the LNB type is set correctly. And DiSEqC positions 2 and 3 are the two dishes with universal LNBs.
Thanks
nc-jay
-----------------------------------------------------------
17:10:35 ProgDVB engine BDA-extension module for TBS/Prof v1.0.0.711
17:10:35 Tuner name: Prof 7500 DVBS Tuner
17:10:35 TBS STV090X direct control init ...
17:10:35 Tuner IC: STB6100
17:10:35 Frontend/demod IC: STV090X (cut 2.0)
17:10:38 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:10:53 TUNE: Freq=4100.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=28350 KS, MIS=-1
17:11:01 TUNE: Freq=4040.013 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:11:08 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
17:11:09 TUNE: Freq=4040.013 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:11:24 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
17:11:33 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:15:20 TUNE: Freq=11736.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=8333 KS, MIS=-1
17:15:33 TUNE: Freq=11716.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=4858 KS, MIS=-1
17:15:58 TUNE: Freq=12044.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=3200 KS, MIS=-1
17:15:59 TUNE: Freq=12044.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=3200 KS, MIS=-1
17:16:32 TUNE: Freq=11960.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=29270 KS, MIS=-1
17:16:33 TUNE: Freq=11960.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=29270 KS, MIS=-1
My results were mostly the same as above, except I can tune the 22 kHz=off position on both H and V polarities with success. I still cannot tune the 22 kHz=on position, in fact, the module's logging routine logs nothing at all when I try to tune that position. And the blindscan "progress" window still disappears almost immediately when attempting a blind scan.
In my log file (pasted below), I tune 7 channels on 107.3w (DiSEqC 1, 22 kHz=off) - alternating between V and H. The channels tune and display correctly. Then I tune an H and a V channel on 22.0w (DiSEqC 1, 22 kHz=on) - but nothing gets written to the logfile. The Ku frequencies I tune after that are on 87.0w, via a universal LNBF on DiSEqC position 2, - and it *does* tune correctly there - both H and V.
A screencap of my LNB/Switch configuration is here: http://dl.dropbox.com/u/5146413/capture ... 173626.jpg
The 22 kHz switch is in DiSEqC position 1, with the west dish on the switch's first position (off) and the east dish (menu expanded) on the switch's second position. I selected "properties" on that LNB so you could see that the LNB type is set correctly. And DiSEqC positions 2 and 3 are the two dishes with universal LNBs.
Thanks
nc-jay
-----------------------------------------------------------
17:10:35 ProgDVB engine BDA-extension module for TBS/Prof v1.0.0.711
17:10:35 Tuner name: Prof 7500 DVBS Tuner
17:10:35 TBS STV090X direct control init ...
17:10:35 Tuner IC: STB6100
17:10:35 Frontend/demod IC: STV090X (cut 2.0)
17:10:38 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:10:53 TUNE: Freq=4100.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=28350 KS, MIS=-1
17:11:01 TUNE: Freq=4040.013 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:11:08 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
17:11:09 TUNE: Freq=4040.013 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:11:24 TUNE: Freq=3747.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=13V, SR=6774 KS, MIS=-1
17:11:33 TUNE: Freq=4160.000 Mhz, LOF=5150.000 Mhz, 22Khz=off, LNB Voltage=18V, SR=30000 KS, MIS=-1
17:15:20 TUNE: Freq=11736.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=8333 KS, MIS=-1
17:15:33 TUNE: Freq=11716.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=4858 KS, MIS=-1
17:15:58 TUNE: Freq=12044.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=3200 KS, MIS=-1
17:15:59 TUNE: Freq=12044.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=13V, SR=3200 KS, MIS=-1
17:16:32 TUNE: Freq=11960.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=29270 KS, MIS=-1
17:16:33 TUNE: Freq=11960.000 Mhz, LOF=10600.000 Mhz, 22Khz=on, LNB Voltage=18V, SR=29270 KS, MIS=-1
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#11look like bug in ProgDVB engine but your dishes config really crazy
Re: polarity switching prob: v6.70.6 Pro+Prof7500+CrazyCat m
#12Would you suggest a different way? This configuration works perfectly with three stb's and various other Windows and Linux software, including CrazyScan/BLScan..... ?
But yes, I agree it is a bug in ProgDVB. I will post in the BUGS subforum.
Thanks CrazyCat!
But yes, I agree it is a bug in ProgDVB. I will post in the BUGS subforum.
Thanks CrazyCat!