[solved] Hauppauge Nova-S PCI, Technotrend TT-budget S-1500: DiSEqC problem solved (1 Viewer)

[Joutungwu]

Why are you using the old driver and not the latest 5.0.1.8?

That's correct. I use the old version 4.4.10.18 because it is not possible to run the Nova-S with version 5.0.1.8 at all, independent of the DiSEqC problem. This issue is not only specific to Mediaportal, but also appears with other DVB applications like SmartDVB and the TT-Viewer itself. (TT-Viewer seems to be a "light" version of the DVB Viewer). That's why i attached the old version to the wiki page.

So it seems that DiSEqC should be working for at least the ... S1500

Maybe the S-1500 runs with version 5.0.1.8 in contrast to the Nova-S. I can't check that. But, have a second look to Dadeo's wiki entry. The date of version 5.0.1.8 is 16.01.09. The wiki page was last modified at 27.11.2010 and Dadeo still mentioned:

The Solution below therefore applies to the latest BDA driver. It is possible the DiSEqC method implemented in the TechnoTrend S1500 driver is not the same as the TechnoTrend S2-3200 (apparently DiSEqC works with this card).

I suppose that @Dadeo tried to get DiSEqC to work with 5.0.1.8, but it failed. Therefore i guess, that the DiSEqC problem still perstists also with the S-1500. Otherwise it would make no sense to recommend the pseudo DVB-T Mode, if DiSEqC works. It would be helpful, if someone actually using the S-1500 can provide some information about it to this thread in order to clarify these matters.

 

[mm1352000]

This is an interesting situation.

That's correct. I use the old version 4.4.10.18 because it is not possible to run the Nova-S with version 5.0.1.8 at all, independent of the DiSEqC problem.

What do you mean by "not possible"?
Is it not possible to install the driver?
...or does the tuner fail to load, lock on signal etc. with that driver?
...or...?

I mean, from the INF files it looks like the NOVA-S should be supported. All the hardware IDs that are present in the 4.4.10.18 driver are also present in the 5.0.1.8 driver.

On the other hand, the release notes for the 5.* driver that I quoted in my previous reply only mention:

• TT-budget S2-3200
• TT-budget S2-1600
• TT-budget S-1500
• TT-budget S-1401
• TT-budget S-1400
• TT-budget C-1500
• TT-budget C-1501
• TT-budget T-1500

There is no mention of:

• %TTBudget_1003.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100313c2 ;TT-budget DVB-S - ALPS-BSRV2/VES1893 or ALPS-BSRU6/STV0299
• %TTBudget_1004.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100413c2 ;TT-budget DVB-C - ALPS-TDBE2/VES1820
• %TTBudget_1005.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100513c2 ;TT-budget DVB-T - Grundig/LS64781
• %TTBudget_100C.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100C13c2 ;TT-budget DVB-S - ALPS-BSRU6/STV0299
• %TTBudget_100F.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100F13c2 ;TT-budget S-1100 - PHILIPS-SU1278S/STV0299
• %TTBudget_1011.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_101113c2 ;TT-budget T-1100 - PHILIPS-TDM1316/TDA10045

...which includes the SUBSYS_100313c2 that is the NOVA-S.

Maybe the S-1500 runs with version 5.0.1.8 in contrast to the Nova-S.

Yes, I think the S-1500 probably does work with 5.0.1.8. Based on the driver device IDs and comments it looks like the NOVA-S and S-1500 are completely different cards/hardware.

NOVA-S = ALPS-BSRV2/VES1893 or ALPS-BSRU6/STV0299
S-1500 = BSBE1/0299 or Samsung with PN1010 (S5H1420)

But, have a second look to Dadeo's wiki entry. The date of version 5.0.1.8 is 16.01.09. The wiki page was last modified at 27.11.2010 and Dadeo still mentioned...

I wonder whether @Dadeo actually created that page, or whether those dates come from the wiki migration which I think happened sometime in 2010.

My guess is that the page content was actually created in 2007 based on this thread:
https://forum.team-mediaportal.com/...t-s1500-diseqc-did-i-by-the-wrong-card.22249/

@Dadeo
Heya
I'd really appreciate it if you could clarify by confirming whether you did or did not have a TechnoTrend S-1500 tuner.

It would be helpful, if someone actually using the S-1500 can provide some information about it to this thread in order to clarify these matters.

Yes, I agree.
Currently I suspect that your workaround may only be required for the tuners which are not supported by the 5.* driver:

• %TTBudget_1003.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100313c2 ;TT-budget DVB-S - ALPS-BSRV2/VES1893 or ALPS-BSRU6/STV0299
• %TTBudget_100C.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100C13c2 ;TT-budget DVB-S - ALPS-BSRU6/STV0299
• %TTBudget_100F.Name%=ttBudget2_W2K,PCI\VEN_1131&DEV_7146&SUBSYS_100F13c2 ;TT-budget S-1100 - PHILIPS-SU1278S/STV0299

 

[mm1352000]

One more update...
I found this thread where somebody claims to be using an S-1100 with driver version 5.0.1.8:
https://forum.team-mediaportal.com/threads/random-crash-on-tv-happens-about-once-a-day.87356/

So, maybe only two tuners instead of three are affected.

 

[Joutungwu]

What do you mean by "not possible"?
Is it not possible to install the driver?
...or does the tuner fail to load, lock on signal etc. with that driver?
...or...?

The driver installation is possible without problems. But it is not possible to scan or tune. If i try to tune a channel, Mediaportal says: "No free card available." Please have a look at the corresponding log files i made recently with 5.0.1.8 installed.

I wonder whether @Dadeo actually created that page, or whether those dates come from the wiki migration which I think happened sometime in 2010. My guess is that the page content was actually created in 2007 based on this thread: https://forum.team-mediaportal.com/t...t-s1500-diseqc-did-i-by-the-wrong-card.22249/

Yes, I guess you are right then. I didn't know that there was a wiki migration in 2010, so that the author/change/date informations of the older wiki are lost. Combining this knowledge and the release information of driver version 5.0.0.19, i think it can be assumed now, that the S-1500 works correctly including DiSEqC.

One more update...
I found this thread where somebody claims to be using an S-1100 with driver version 5.0.1.8:
https://forum.team-mediaportal.com/threads/random-crash-on-tv-happens-about-once-a-day.87356/
So, maybe only two tuners instead of three are affected.

That should be the case, if shreilly did not use the DVB-T Mapper for the S-1100, which we don't know exactly. Some years ago, I tried the DVB-T Mapper with 5.0.1.8 installed as it is explained in the wiki. It worked at least for the Nova-S.

 

[mm1352000]

The driver installation is possible without problems.

Okay.

But it is not possible to scan or tune. If i try to tune a channel, Mediaportal says: "No free card available." Please have a look at the corresponding log files i made recently with 5.0.1.8 installed.

I do not see any attempts to scan, however I can see the failed tune attempt:
[collapse]
[2016-02-12 06:34:51,134] [Log ] [23 ] [INFO ] - Controller: find free card for channel WDR HD Aachen
[2016-02-12 06:34:51,146] [Log ] [23 ] [INFO ] - Controller: find card for channel WDR HD Aachen
[2016-02-12 06:34:51,934] [Log ] [23 ] [INFO ] - Controller: got 1 tuning details for WDR HD Aachen
[2016-02-12 06:34:51,938] [Log ] [23 ] [INFO ] - Controller: channel #1 DVBS:tv:ARD WDR HD Aachen Freq:12604000 ONID:1 TSID:1111 SID:28544 PMT:0x15E0 FTA:True LCN:10000 SymbolRate:22000 Modulation:ModNotSet Polarisation:LinearH InnerFecRate:Rate5_6 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet
[2016-02-12 06:34:51,944] [Log ] [23 ] [INFO ] - Controller: card:1 type:RadioWebStream cannot tune to channel
[2016-02-12 06:34:51,948] [Log ] [23 ] [INFO ] - Controller: card:2 typevbIP is disabled
[2016-02-12 06:34:52,184] [Log ] [23 ] [INFO ] - Controller: card:10 typevbS channel not mapped
[2016-02-12 06:34:52,225] [Log ] [23 ] [INFO ] - Controller: found 0 card(s) for channel
[2016-02-12 06:34:52,225] [Log ] [23 ] [INFO ] - AdvancedCardAllocation.GetAvailableCardsForChannel took 1079 msec
[2016-02-12 06:34:52,254] [Log ] [23 ] [INFO ] - Controller: found 0 free card(s)[/collapse]

This error at least has nothing to do with the driver and everything to do with TV Server Configuration. TV Server is trying to tell you that it doesn't think there are any tuners available to tune the channel. You can fix this simply by mapping the channels to the tuner. This tells TV Server that it can use the tuner to tune the channel.
http://wiki.team-mediaportal.com/1_...Server_Configuration/03_TV_Channels/2_Mapping

1. Select the tuner up the top.
2. Select all the channels on the left (select the first channel, hold the CTRL key, then press the END key).
3. Click ">>".

Now that problem should be solved. Maybe there are other problems (=> new log files required), or maybe it works now...?

Yes, I guess you are right then. I didn't know that there was a wiki migration in 2010, so that the author/change/date informations of the older wiki are lost. Combining this knowledge and the release information of driver version 5.0.0.19, i think it can be assumed now, that the S-1500 works correctly including DiSEqC.

Yes, I agree.
I now start to think about deleting those 2 wiki pages to avoid confusion. If I've understood correctly, the only reason to keep them is if the 4.* driver is used. Hopefully you can help me to confirm that the 4.* is not required. I assume if the 5.* driver can work with the NOVA-S then it can work with all TT tuners. After all, the NOVA-S seems to be the oldest tuner made by TT with a BDA driver.

That should be the case, if shreilly did not use the DVB-T Mapper for the S-1100, which we don't know exactly. Some years ago, I tried the DVB-T Mapper with 5.0.1.8 installed as it is explained in the wiki. It worked at least with the Nova-S.

To be clear, I have assumed that if the 5.0.1.8 driver can be installed and used successfully, DiSEqC should also work without the need for the DVB-T mapping.

 

[Joutungwu]

Sorry, i din't know that mapping was required.
Now i have mapped the channels to the card and Mediaportal says after channel tuning: "An unknown error has occured."
Please have a look at the new log files!

I do not see any attempts to scan, ...

That's because Watchdog unfortunately has no option to log the TV-Server configuration (SetupTV.exe), as far as i know. So, I deleted all log files of

C:\ProgramData\Team MediaPortal\MediaPortal TV Server\log

and did some scanning afterwards. Then i copied all new log files of the log folder into ZIP files and attatched them separately. I hope these include the relevant log files now. If not, please tell me!

 

[mm1352000]

Now i have mapped the channels to the card and Mediaportal says: "An unknown error has occured."
Please have a look at the new log files!

Hmmm, here is the source of the error:
[2016-02-12 23:12:25,368] [Log ] [27 ] [INFO ] - dvb: RunGraph returns: 0x8007001F

This error comes from the tuner driver. Unfortunately it's quite generic. For example, it can mean that the tuner is being used by other software, was loaded too soon after resume/reboot etc. etc. etc.

Can you please power cycle (reboot) the PC and then try again. If it still doesn't work, try again after setting "preferred network provider" to "DVBS":
http://wiki.team-mediaportal.com/1_...nfiguration/02_TV_Servers#Edit_Tuner_Settings

That's because Watchdog unfortunately has no option to log the TV-Server configuration (SetupTV.exe), as far as i know.

TV Server log files are always included by the Watchdog if TV Server is running on the same PC as MediaPortal.
In that case you can use Watchdog option 3 (export existing...) to collect TV Server log files after a scan.

 

[Joutungwu]

Sorry for the late answer!

Can you please power cycle (reboot) the PC and then try again.

The power cycle changed nothing. The behaviour is still the same.

If it still doesn't work, try again after setting "preferred network provider" to "DVBS"

I tried that, too. Scanning still does not work. The Mediaportal message after tuning a channel is: "No signal." I have attached the log files (Watchdog method 3).

 

[Joutungwu]

I have interesting and good news!

TT BDA driver 5.0.3.6, officially described by TT to work with Windows Mediacenter only, seems to work as good as version 4.4.10.18. I don't know why i didn't see that before. Maybe i lost the overview while testing all these different driver versions with different DVB applications and their own special configurations. But the DiSEqC problem remains with Mediaportal. I still have to "switch off" KNCBDACTRL.dll as i described in the wiki before. Please have a look at the following log files!

 

[mm1352000]

Those are strange and confusing results. I'm surprised that the 5.0.3.6 driver partially works, and even more surprised that the 5.0.1.8 driver does not work at all.

One thing that I notice in the 5.0.3.6 log files:
[2016-02-15 21:24:04,206] [Log ] [26 ] [INFO ] - dvb:Add Generic Network Provider

If the 5.0.3.6 driver works with the generic network provider then I'd have expected the same for the 5.0.1.8 driver... but you've already confirmed that it doesn't.

I don't know what else to say or suggest. The results speak for themselves: the NOVA-S requires either the 4.4.10.18 or 5.0.3.6 driver with generic DiSEqC (which can be achieved by moving or deleting KNCBDACTRL.dll).