Diseqc 1.2 is NOT working in version 4.5!

[lujo]

I had reported this previously when version 4.5 was beta2: viewtopic.php?f=61&t=18957&hilit=lujo

Today I have installed final version 4.5 only to see that DVBLogic team was not able to to implement the same feature from version 4.1.1 into version 4.5

Diseqc 1.2 in version 4.5 simply don't work.

TV card = TBS 6922: http://www.tbsdtv.com/products/tbs6922- ... -card.html

If Diseqc 1.2 is working with version 4.1.1 and after uninstalling version 4.1.1 and installing 4.5 Diseqc 1.2 is not working anymore than there must be something wrong with version 4.5

First I have tried to install everything from beginning, add raw commands and scan for different satellites, only to see that Diseqc 1.2 in not working!
Second I had deleted TVSource (TBS_6922) and used backup xml file from previously installation (from 4.1.1) to restore everything in version 4.5. After that Diseqc 1.2 is still not working!

This drives me crazy because I cannot understand that the same team can broke Diseqc 1.2 support for the second time (first version 4.1.0 and second in version 4.5)
In version 4.1.1 Diseqc 1.2 is working.

Unbelievably!

[lujo]

Now I have proof that DiSEqC 1.2 is broken again in version 4.5

I only don't understand that Oberon won't admit this.

My guess is that DVBLink team don't have motorized dish to test DiSEqC 1.2. Is this true?

The solution is to replace bda.dev from C:\Program Files\DVBLogic\DVBLink\sources\TBS_6922\devices with bda.dev from version 4.1.1. This, fine working, bda.dev is from 30-12-2011

Oberon how is this possible, to broke it for the second time?
And more important: when can we expect fix for this problem?

[lujo]

Any news/answer about this?

[Oberon]

There is no update yet. We will be looking into this.

[Oberon]

Now I have proof that DiSEqC 1.2 is broken again in version 4.5

I only don't understand that Oberon won't admit this.

My guess is that DVBLink team don't have motorized dish to test DiSEqC 1.2. Is this true?

The solution is to replace bda.dev from C:\Program Files\DVBLogic\DVBLink\sources\TBS_6922\devices with bda.dev from version 4.1.1. This, fine working, bda.dev is from 30-12-2011

Oberon how is this possible, to broke it for the second time?
And more important: when can we expect fix for this problem?

I assume that you are using 4.5 still with the old bda.dev? Put the new bda.dev back in place, reproduce the issue with it and log level set to info and attach zipped dvblink_server.log here.
Your backup can be successfully restored in our test setup and diseqc commands are processed correctly with other tuners (we do not have 6922 for tests). It might be that tuner is not detected properly.

[lujo]

I assume that you are using 4.5 still with the old bda.dev? Put the new bda.dev back in place, reproduce the issue with it and log level set to info and attach zipped dvblink_server.log here.
Your backup can be successfully restored in our test setup and diseqc commands are processed correctly with other tuners (we do not have 6922 for tests). It might be that tuner is not detected properly.

Yes, I am using 4.5 version with the old (4.1.1) bda.dev.

info log = check
4.5 bda.dev = check

The strange thing is that it now works with the channels which are scanned with the old (4.1.1) bda.dev. So changing between Ned1 HD (23.5) and RTL4 (19.2) and others are working.

But...

If I go to http://xxx.xxx.x.xxx:39876/c/sources/tv ... e=TBS_6922

And try to scan transponder on 23.5 while my dish is on 19.2 I get only channels which are on 19.2 transponder. I thought maybe TVsource was beginning with scanning before dish has moved so I tried again to scan those same transponder on 23.5 but still get the same channels which are on 19.2 satellite.

[edit]
See also this:

Code: Select all

2012-Jul-20 12:26:47:   [I]
2012-Jul-20 12:26:47:   [I] CTVSStreamSource::TuneTransponder. Transponder tuning request: diseqc 23, freq 11739000, modulation 6, polarization 1, symbol rate 27500000, LOF 10600000, LNB selection signal 1, FEC 86
2012-Jul-20 12:26:47:   [I] CTVSStreamSource::SelectLNB. Selecting LNB for diseqc value 23
2012-Jul-20 12:26:47:   [I] SendDiseqc()  E0 31 6B 04  Len:4
2012-Jul-20 12:26:47:   [I] turbosight_nxp_send_diseqc(<E0 31 6B 04 >, 4)
2012-Jul-20 12:26:47:   [I] Success: Turbosight NXP BDA_DISEQC_MESSAGE success!
2012-Jul-20 12:26:47:   [I] SetTuner() 11739000, V, 27500000  Mod:6 LOF:10600000  22Khz:1
2012-Jul-20 12:26:48:   [I] CTVSChannelScanner::Scan. Received channel scan request
2012-Jul-20 12:26:48:   [I] CTVSChannelScanner::SwitchToSDTScan. Switching to SDT scan state
2012-Jul-20 12:26:48:   [I] CTVSStreamSource::AddPID. Requesting PID 17
2012-Jul-20 12:26:51:   [I] CTVSChannelScanner::ProcessCompletedSections. Channel scan is completed. Found 16 channels in total, new 16 channels

19.2 11739 V = 16 channels
23.5 11739 V = 21 channels
[/edit]

[lujo]

Solution to this problem is deleting: tbsciapi.dll from C:\Program Files\DVBLogic\DVBLink\sources\TBS_6922\devices

Without this file (tbsciapi.dll) 4.5 versionn of bda.dev is also working with DiSEqC 1.2 on TBS 6922 DVB card.

Questions:
1. Was this file also used in version 4.1.1?
2. Is there any reason why tbsciapi.dll is used in version 4.5?

[Oberon]

That´s interesting. This file was added in 4.5 and is meant (as the name says) for CI support of capable TBS tuners - 5980CI etc. This file comes from TBS itself. I assume that for your tuner - 6922 - it is not needed. We will contact TBS to see if this file may cause this kind of side effects.

[lujo]

I hope TBS can give more explanation for this behaviour. At this point everything seems to work fine.
TBS 6922: http://www.tbsdtv.com/products/tbs6922- ... -card.html

[coyote]

DISEQC will not work either in version 4.5 with Tevii S480, I have to use version 4.1.1 of bda.dev to get it to switch. I already have to use version 4.0.1 of bda.dev to be able to use my Terrated H5 DVB-C tuner. I wonder what will be next ...

[lujo]

DISEQC will not work either in version 4.5 with Tevii S480, I have to use version 4.1.1 of bda.dev to get it to switch. I already have to use version 4.0.1 of bda.dev to be able to use my Terrated H5 DVB-C tuner. I wonder what will be next ...

There is also TeVii.dll. Try to temporally remove this file and restart dvbink_server. Who knows will this be the solution for you?

[lujo]

Oberon,

I have one more question regarding my DiSEqC 1.2 problems. I have also asked TBS team about this issue: http://www.tbsdtv.com/forum/viewtopic.p ... 408#p25408

My question is:

The only problem is when I try to scan transponder that is also on another satellite

Example:

- Dish is on 19.2
1. Scan transponder 11739 on 23.5 gives me channels which are on 11739 but on 19.2
2. Scan transponder 11739 on 23.5 gives me right channels. Channels that are on 23.5

So I need to scan for the second time to get the right channels.

My conclusion is that TBS 6922 beging with scanning before diseqc is working and dish is moved to another position.

Question: Is this behaviour caused by the faulty driver or by the software TVSource?

Is it possible to use "timer": If DiSEqC command is used then wait X seconds before beginning to scan?

[Oberon]

Frankly speaking I think that the issue is with tbsciapi.dll. I have seen in the sample code that TBS has kindly provided us with that they load the library only for tuners that have CI onboard (by checking the tuner identity). We are not doing this to be compliant with the upcoming tuners with CI. Obviously we have assumed that simple presence of a loaded tbsci dll should not influence diseqc commands, but apparently it does. I am curious to heear wwhat TBS will say about it.

[lujo]

Ok, but at the moment of testing tbsciapi.dll was already deleted. So at that moment this file is not influencing diseqc commands.
This should be simplest solution: "If DiSEqC command is used then wait X seconds before beginning to scan? (only when channels are scanned)"
Is it possible to implement this or is it already implemented?

[spaceboy]

So on 4.5 with a TBS 6984 tuner i suffer from occasions of weak signal, even though i know its very strong, resulting in partial recordings and loss of live tv. is this likely to be the culprit and when can we expect a fix?

thanks