Twinhan can not tune any horizontal channel.

[Benarty]

Well first of all, installing a ATI radeon x1600 did solve video problems, video quality is also better compared with the on-board I945GM.

 

The LNB and coax are replaced but now another problem appears:

 

When DVBViewer or the native twinhand DVB software ..well, all mediacenter software is scanning for the channels, then they can not find any horizontal channel, only the vertikal channels are recognized.

 

This is not a fault of the LNB cause the nokia mediamaster 9500S set top box could scan both horizontal as vertical.

 

 

Now, videocard (ati X1600) is using IRQ16, twinhan 1030A also using IRQ16 so irq sharing is used, stupid cause there are several IRQ's below 13 that are still free (stupid XP)

Now, I can't change the IRQ cause the system uses ACPI and disabling it after windows has been installed is not a wise move. I don't think that IRQ sharing woul cause this, on the other hand, the old situation, , meaning on-board I945-GM and twinhan 1030A where not using the same IRQ.

The I945-GM is now disabled since the ati x1600 does the job now.

[Benarty]

Well first of all, installing a ATI radeon x1600 did solve video problems, video quality is also better compared with the on-board I945GM.

 

The LNB and coax are replaced but now another problem appears:

 

When DVBViewer or the native twinhand DVB software ..well, all mediacenter software is scanning for the channels, then they can not find any horizontal channel, only the vertikal channels are recognized.

 

This is not a fault of the LNB cause the nokia mediamaster 9500S set top box could scan both horizontal as vertical.

Now, videocard (ati X1600) is using IRQ16, twinhan 1030A also using IRQ16 so irq sharing is used, stupid cause there are several IRQ's below 13 that are still free (stupid XP)

Now, I can't change the IRQ cause the system uses ACPI and disabling it after windows has been installed is not a wise move. I don't think that IRQ sharing woul cause this, on the other hand, the old situation, , meaning on-board I945-GM and twinhan 1030A where not using the same IRQ.

The I945-GM is now disabled since the ati x1600 does the job now.

 

 

Weird:

 

I've scanned without choosing astra 19.2 transponder list so from low to high frequency in steps of 5Mhz.

Then DVBViewer can find the horizontal polarized channels but only the horizontal. I have now all channels after scanning with the astra 19,2° transponder list which finds only the vertikal polarized channels.

 

But : I had no problems with tuning at all before but now with new universal LNB and ATI 1600X has been installed, werid tuning problem.

 

OT but informative:

Twinhan 1030A has no problem with the SECA II CAM which is checked with a PCMCIA bus extender and cam data logger/tester.it was clear that the cam acts fast on any request without interrupts.

Strange is, as soon when the computer has to communicate with the CAM, then there is an additional delay of 1,15 seconds. Now that's not a problem but at least a bit weird.

 

WHQL'ed BDA drivers still don't work. The cam is detected, so DVBViewer gives no error that the channel is not accessible but just empty screen on all encrypted channels. For the time being: DVBViewer classified as buggy when CI is involved.

[Engelbert]

PRO-beta waits for the next one for CI-CAM.

 

The tool uses to scan TransEdit (Members area).

One can examine all four levels specifically there.

[Klaus_1250]

OT but informative:

Twinhan 1030A has no problem with the SECA II CAM which is checked with a PCMCIA bus extender and cam data logger/tester.it was clear that the cam acts fast on any request without interrupts.

Strange is, as soon when the computer has to communicate with the CAM, then there is an additional delay of 1,15 seconds. Now that's not a problem but at least a bit weird.

 

I see similiar behaviour with my Twinhan DVB-C Mantis (2033a) and the Alphacrypt CAM. From what I have observed it is either a bug in the Twinhan driver, DVBViewer or a combination of the two.

 

If I startup DVBViewer on an encrypted channel (just clicking on the DVBViewer icon which then starts to autoplay a previously chosen encrypted channel) the screen sometimes stays black, sometimes there is an error-message from the CAM visible ("Not entitled to view the Program") and sometimes the programs shows a view seconds later.

 

It all depends wheter or not I have set "Extract original PMT" to off | auto | on in the CAM menu. When set to "off", I have substantially more problems, when set to "On", less/no problems and no stuttering but very slow, "auto" seems to work best but has stuttering for a few seconds after a channel change.

[Benarty]

I see similiar behaviour with my Twinhan DVB-C Mantis (2033a) and the Alphacrypt CAM. From what I have observed it is either a bug in the Twinhan driver, DVBViewer or a combination of the two.

 

If I startup DVBViewer on an encrypted channel (just clicking on the DVBViewer icon which then starts to autoplay a previously chosen encrypted channel) the screen sometimes stays black, sometimes there is an error-message from the CAM visible ("Not entitled to view the Program") and sometimes the programs shows a view seconds later.

 

It all depends wheter or not I have set "Extract original PMT" to off | auto | on in the CAM menu. When set to "off", I have substantially more problems, when set to "On", less/no problems and no stuttering but very slow, "auto" seems to work best but has stuttering for a few seconds after a channel change.

 

 

What I don't understand is that, on CI side, the 2.432 version based on the 2.41 WDM ...administrator/moderators, read carefully, WDM... has the best results.

BDA drivers have always huge cam problems , no matter which version, latest 3.0 cause even scan failure (DVBViewer hangs). WHQL'ed BDA drivers do work erraticly related to cam.

 

Unfortunatly, wdm has it's own problems but i'm pretty sure... read again admins/mod's ...that DVBViewer causes the cullprit.

Wat I do miss in DVBViewer is a signal strenght indicator advanced LNB/rotor settings.

Things like 22kHz, burst mode, disecq mode, usals etc...

 

Back on problems:

 

The freaking part of it is that the errors are not reproducable, I had WHQL'ed drivers running with ci and now that doesn't work at all, and even the wdm needed sometimes two reboots before DVBViewer could find the driver. WDM is also best for overlay/vrm7 and vrm9 while BDA has problems with VRM7 and VRM9 = OSD lost. the OSD fix in the options can not fix this.

 

Odd, DVBViewer works now 30 minutes without errors. But it's 3:10 ..yes dear admins, I spend alot of time on this and I can not arrive every day as a zombie at work.

[Klaus_1250]

Not sure if it us useful, BUT, it seems that Twinhan has released their latest Mantis driver (1.0.3.0) with some sample code and documentation. Perhaps it can help the devs to track down issues /etc...