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

Joutungwu

Portal Pro
April 27, 2014
103
25
Home Country
Germany Germany
Hi,
I found a way to fix the DiSEqC problem for the Hauppauge Nova-S PCI card. I guess the same solution can also be applied to Technotrend TT-budget S-1500 cards. If you have such a card, you may have a look at the wiki troubleshooting section: http://wiki.team-mediaportal.com/1_...t/Troubleshooting/DiSEqC_Hauppauge_Nova-S_PCI
The annoying Pseudo DVB-T Mapping should not be needed anymore. :)

At first i expected the Technotrend API to cause the problem. But after excluding all Vendor APIs from the TV-Server one after another, it was very surprising, that the KNC One API caused the DiSEqC problem for the Technotrend card. Maybe someone could explain this curiosity? :confused:

Best regards,
Joutungwu
 

mm1352000

Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Maybe someone could explain this curiosity? :confused:
    Your post has completely confused me so I can offer no explanation.

    I found a way to fix the DiSEqC problem for the Hauppauge Nova-S PCI card.
    Which problem is this?
    (Description, links, log files etc. would be useful. Otherwise people like me have no idea what you're talking about. ;) )

    Did you create that wiki page?
    Regardless of the problem, it's not a good idea to recommend recommending installing a TechnoTrend driver for a Hauppauge product without any warning. Such an action might work for certain systems/cards (eg. maybe only certain revisions/versions of Hauppauge NOVA-S) but there's also a reasonable chance of damaging hardware. A big warning is needed or the page should be deleted. Otherwise people can blame us for their tuner no longer working.

    ...caused the DiSEqC problem for the Technotrend card.
    First you talk about fixing a problem for a Hauppauge tuner, but now you talk about a TechnoTrend tuner. :confused:
     

    Joutungwu

    Portal Pro
    April 27, 2014
    103
    25
    Home Country
    Germany Germany
    Sorry, confusion was not intended.

    Which problem is this?
    As i described in the wiki: "DiSEqC 1.0 does not work properly . The tuner scans the first LNB (Level1AA) only and ignores the other satellite positions."
    The problem is some years old. The Nova-S PCI as well as the TT-budget S-1500 are affected. A few years ago @Dadeo wrote about the problem here: http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/16_Support/Troubleshooting/Diseqc
    His card was a TT-budget S-1500 and the solution was to run the card in pseudo DVB-T Mode, which is very complex to configure. But that was the only solution to run DiSEqC with these cards until now. Now I found out, that the problem is caused by the existence of the KNCBDACRTL.dll file. By renaming this file and restarting Windows afterwards, DiSEqC runs perfectly. All LNBs can be scanned/tuned without problems.

    First you talk about fixing a problem for a Hauppauge tuner, but now you talk about a TechnoTrend tuner. :confused:
    The Nova-S was manufactured by Technotrend. Hauppauge mentions that on their hompage. Have a look at the "legacy products" here: http://www.hauppauge.co.uk/site/support/index.html#
    The hardware id of the Nova-S is PCI\VEN_1131&DEV_7146&SUBSYS_100313c2. This ID can be found in the INF files of the latest Hauppauge WDM driver 2.18c (Manufacturer: Technotrend), the latest Technotrend TT-budget S-1500 WDM driver 2.19h, the Technotrend TT-budget S-1500 BDA driver 4.4.10.18 (latest version of 4.x.x.x) as well as of the latest Technotrend TT-budget S-1500 BDA driver 5.0.1.8

    it's not a good idea to recommend recommending installing a TechnoTrend driver for a Hauppauge product without any warning. Such an action might work for certain systems/cards (eg. maybe only certain revisions/versions of Hauppauge NOVA-S) but there's also a reasonable chance of damaging hardware.
    I guess, if there would be incompatible revisions/versions of the Nova-S PCI, these would be different in the subsystem id, so that the hardware id wouldn't match to the INF file and the BDA driver cannot be installed at all, as long as the INF file is not modified itself. And modifiying the INF file, I do not recommend. :whistle:
    Installing the compatible Technotrend BDA driver does not damage the Nova-S PCI.

    Dadeo said:
    Some users have reported problems getting DiSEqC to work with Technotrend S1500 Budget cards. The Hauppage NOVA-S cards are exactly the same so the same issues may apply.
    That is not totally correct. The cards themselves are different, but they are both compatible with the Technotrend TT-budget S-1500 BDA driver.

    I have attached log files. Perhaps you can compare them to find out what is going on with the KNCBDACRTL.dll:
    ...KNCBDACTRL_off.zip: DLL switched off by renaming => DiSEqC works
    ...KNCBDACTRL_on.zip: DLL switched on with default name => DiSEqC is not working
     
    Last edited:

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    KNCBDACTRL_on.zip: DLL switched on with default name => DiSEqC is not working
    Please can you provide new log files after restarting the TV service. I need to see the tuner loading ("graph building").
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Does Hauppauge provide any BDA driver?
    If yes, what happens if you try to use it?
     

    Joutungwu

    Portal Pro
    April 27, 2014
    103
    25
    Home Country
    Germany Germany
    Does Hauppauge provide any BDA driver?
    No, Hauppauge never did. Every driver belonging to the Nova-S PCI, even the WDM on Hauppauge's homepage, is of Technotrend origin.

    Please can you provide new log files after restarting the TV service. I need to see the tuner loading ("graph building").
    I attached new log files. The TV-Server was restarted before logging each time. The alteration date of the graph file changed respectively during the Watchdog procedures.
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Okay, thank you for the new log files.

    It seems when you delete the KNCBDACTRL.dll, the KNC handler is activated by coincidence. The KNC DiSEqC method/code is the same as the generic DVB-S/S2 DiSEqC method/code. That method is supported by many vendors so it isn't really surprising that it works for your card. Unfortunately it's limited to DiSEqC 1.0 (4 port switches), but I guess you're happy that at least it works.

    I'm surprised that the standard TechnoTrend DiSEqC handling does not work. I doubt that we could get TT to fix it since your hardware was sold by Hauppauge and also very old now. Instead we might be able to fix it by making an exception in our code.

    In the TT PCI INF file (ttBudget2.inf) we have the following DVB-S/S2 tuner IDs:
    %TTBudget_1003.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100313c2 ;TT-budget DVB-S - ALPS-BSRV2/VES1893 or ALPS-BSRU6/STV0299
    %TTBudget_100C.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100C13c2 ;TT-budget DVB-S - ALPS-BSRU6/STV0299
    %TTBudget_100F.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100F13c2 ;TT-budget S-1100 - PHILIPS-SU1278S/STV0299
    %TTbudget_1016.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101613c2 ;TT-budget S-1400 - Samsung-S5H1420/PN1010
    %TTbudget_1018.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101813c2 ;TT-budget S-1401 - Philips Silicon/TDA10086
    %TTbudget_1017.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101713c2 ;TT-budget S-1500 - BSBE1/0299 or Samsung with PN1010 (S5H1420)
    %TTbudget_101B.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101B13c2 ;TT-budget S-1500b - BSBE1 with 0288
    %TTbudget_101C.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101C13c2 ;TT-budget S2-1600
    %TTbudget_1019.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101913c2 ;TT-budget S2-3200

    Of these I know that the TechnoTrend DiSEqC handling works for the "TT-budget S2-3200" (I have one for testing), however I have no idea about the rest of them. Which ones do you know are not working?
     

    Joutungwu

    Portal Pro
    April 27, 2014
    103
    25
    Home Country
    Germany Germany
    Thank you for the explanation!

    Which ones do you know are not working?
    I can assure that the problem exists for the following card:
    %TTBudget_1003.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100313c2 ;TT-budget DVB-S - ALPS-BSRV2/VES1893 or ALPS-BSRU6/STV0299
    (Nova-S PCI)

    Indirectly confirmed by Dadeo's wiki page: http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/16_Support/Troubleshooting/Diseqc
    EDIT: or here: https://forum.team-mediaportal.com/threads/technotrend-budget-dvb-s-1500-diseqc.12379/
    %TTbudget_1017.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_101713c2 ;TT-budget S-1500 - BSBE1/0299 or Samsung with PN1010 (S5H1420)
    (TT-budget S-1500)

    I presume that the following cards are also affected, but i cannot confirm. EDIT: Found a thread:
    https://forum.team-mediaportal.com/threads/hauppauge-nova-ci-s-and-diseqc-problems.26568/
    %TTBudget_100C.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100C13c2 ;TT-budget DVB-S - ALPS-BSRU6/STV0299
    (Nova-CI S)
    %TTBudget_100F.Name%=ttBudget2,PCI\VEN_1131&DEV_7146&SUBSYS_100F13c2 ;TT-budget S-1100 - PHILIPS-SU1278S/STV0299
    (Nova-CI S variant)
     
    Last edited:

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Hmmm, those threads are from 2006 and 2007 with old drivers. This does not tell me if the same problems are likely to exist today.

    When I read this newer (but still old) post I have the impression that this problem should already be solved:
    https://forum.team-mediaportal.com/...iver-5-0-0-2-5-0-0-6.30504/page-4#post-223925
    New in Version 5.0.0.12
    - DiSEqC Probleme with TT-budget S-1500 solved (breaks between DiSEqC commands)

    Your log file tells me you are using driver version 4.4.10.18, so I wonder if that is why DiSEqC is not working for you.

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

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    In fact now I found the driver release notes on TT's German download page:
    http://www.tt-downloads.de/Versionshinweise 5.0.0.19.pdf
    [collapse]
    Hinweise TT-budget® Treiber Version 5.0.1.8 Unterstützte Produkte: 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 Unterstützte Betriebssysteme: Windows XP 32bit Windows Vista 32bit Windows 7 32bit Windows 8 32bit
    Windows XP 64bit Windows Vista 64bit Windows 7 64bit Windows 8 64bit Download: 5.0.1.8 (16.01.2009, 628KB) Neuerungen in der Version 5.0.1.8 - Bugfix: DVB-T Emulation - Diverse Optimierungen
    Neuerungen in der Version 5.0.1.6 - Bugfix: DiSEqC-Wiederholung für S-1401
    Neuerungen in der Version 5.0.1.5 - Bugfix: DiSEqC-Wiederholung für S-1400
    Neuerungen in der Version 5.0.1.4 - Bugfix: DiSEqC für S-1401
    Neuerungen in der Version 5.0.1.2 - Bugfix: DiSEqC für S-1400, S-1500
    Neuerungen in der Version 5.0.1.0 - Bugfix: Parallelbetrieb mehrerer Karten des gleichen Typs (S-1500, S2-1600)
    Neuerungen in der Version 5.0.0.25 - Unterstützung für Vista TV-Pack
    Neuerungen in der Version 5.0.0.23 - DVB-T Emulation für S2-1600
    Neuerungen in der Version 5.0.0.21 - Bugfix: DiSEqC für S2-3200
    Neuerungen in der Version 5.0.0.20 - Unterstützt S2-1600 - Fehler beim Laden des Treibers werden im Gerätemanager angezeigt - Verkürzte Umschaltzeit für S2-3200

    Neuerungen in der Version 5.0.0.19 - Frontend TT-budget C-1501 wurde überarbeitet. Im Fall einer Initialisierung ohne vorhandenes Signal (z.B. beim Rechnerstart kein Kabel angeschlossen), wird beim ersten Tunen eine Reinitialisierung vorgenommen. - Für die korrekte Funktion ist das TTBdaDrvApiPaket_1_0_1_16 erforderlich. Neuerungen in der Version 5.0.0.12 - Behebung der DiSEqC Probleme mit der TT-budget S-1500 (Pause zwischen den DiSEqC Kommandos) - Problem mit erhöhter CPU-Last bei geteilten IRQs behoben[/collapse]

    So it seems that DiSEqC should be working for at least the S-1400, S-1401, S1500 and S2-3200. I cannot say for the S-1100 and older cards, but surely not many people are using such tuners today given that they don't support DVB-S2.
     

    Users who are viewing this thread

    Top Bottom