KNC DVB-S2 twin - has anyone got this to work with 1.2RC? (3 Viewers)

[Django.edwards]

Hi mm,

and thanks for your reply.

It's good to hear that you are still working on the KNC support.
I'm not shure why you mean that I'm not using the DVBS provider. I'm using it. Because without this setting I'm not able to do a working fullscan. So I'm pretty shure (just verified) that I'm using the correct setting. But thanks for the remark.

Hope that you have benefit from your break on work on mediaportal! Even with all our problems that we have with Mepo... Life is still the most importend thing!

I will give these newer dll a try and wait for any news about the KNC support.

for your help.

 

[JeanBuilder]

Hi MM,

Eeeeh

The CAM doesnt work with any of the tv-library's.

But....
-Do you have a specific tv-library in mind for my testing?
-Do i need to use watchdog?
-What actions you want me to perform to get a good test.

Greetings from holland.
Jean.

 

[mm1352000]

Hi again Jean

The CAM doesnt work with any of the tv-library's.

This might be an obvious question so please forgive me in advance: have you enabled the CAM in the tuner settings?
Details are -->here<-- - you need to edit the tuner properties and enable the CAM for decrypting and the CI menu to work.

-Do you have a specific tv-library in mind for my testing?

The current DLLs are more targeted at DiSEqC since I thought that may be part of the reason why chr0non is/was experiencing problems. However I knew that there was also an error in the previous DLL that I provided so this DLL was meant to fix that (and I though maybe fixing the error would make basic CAM support work).

-Do i need to use watchdog?

Yes and no. What I'm really interested in right now is:
1. Tuner initialisation (this happens when you first start viewing TV with the tuner, or when TV Server starts if the tuner preloading is enabled).
2. CAM/CI states. In other words, what state does the driver report when:
- there is no CI slot connected
- the CI slot is empty
- the CAM is inserted
- the CAM is ready to decrypt
- the CAM starts decrypting
- the CAM stops decrypting
- the CAM is removed

These might seem very simple, but it is very important to me. If I can't get this information then it is difficult to write stable and correct code. The information that I will be looking for is in the tv.log file (or maybe error.log... hopefully not!!! ). You can find those files by:
- opening TV Server configuration
- click "open log directory" in the top left hand corner

-What actions you want me to perform to get a good test.

I will try to be very specific to make this as easy as possible for both of us.

-------------------------------------------------------
General instructions

First, please ensure you have enabled the CAM ("default" as type is correct unless you have an Astoncrypt CAM), chosen "stop card", and selected the "DVBS" network provider. All of those settings are in the tuner properties. Make sure you do that for both tuners. Once you've done that we can start testing.

Before each test, please delete the tv.log and error.log files and restart the TV Server (in the manual control section of TV Server configuration click "stop service"... then "start service").

After each test, please take a copy of the tv.log and error.log files - I'm going to want to look at them. You can put them in a zip file named test_***.zip or something like that so that it is easy to post them.

-------------------------------------------------------

Test 1
Please perform this test with the "TVLibrary[1.2.1_dll].zip" DLL. Remember to install the DLL while TV Server is stopped (you'll also need to close TV Server configuration otherwise the file will be locked).

Use the manual control section of TV Server configuration to start timeshifting on any free channel with the first Twin tuner. If you don't have a free channel then it is okay to try an encrypted one.

Test 2
Do test 1 with the second tuner.

-------------------------------------------------------

...and that is all for the moment. *Very* simple, but the information in the logs will tell me if my code is completely wrong and it will allow us to test quickly without taking too much of your time.

chr0non and Django:
If you would like to help then I'd *really* appreciate it. You can perform the same tests as Jean. I know this might seem basic, but the basic tests provide the base for stable operation.

Best regards and *thank you* in advance!
mm

 

[Django.edwards]

Hi mm,

as you know, I'm always glad to provide you with some help. So ask if you need it.

Can you explain me the difference of the different dll's? What is the difference of the tvlibrary, kscontrol and ksproperty Version?
Should I do these tests with all versions?
As you know, I own 2 KNC One TV-Station with single tuner, but each of them with a CI module.
I did some tests with my current setup, and I can see, that I have always a problem with the DiseqC commands. It seems that the card is not able to tune or to reliable send out the diseqc commands. I have the feeling, that if the diseqc switch is switched into one position, the card can't switch him reliable to the other position.
For example, i did some test while scanning a single transponder. I scanned both LNB with the same frequency (11240000) wich is located on Hotbird. When I scan this frequency on both LNB (Atra + Hotbird) the scan find the same channels on both LNB, which is not possible. In the logs I can see that the diseqc command are send propperly (simple A 0x00, and simple B 0x01) but it seems that the switch is not responding to that. These tests where made with the original 1.2.1 tvlibrary dll.
So if you want, I can do this test also with the newer ones?

Regards
Django

 

[mm1352000]

Hi Django

as you know, I'm always glad to provide you with some help. So ask if you need it.

The difference between the DLLs is 3 different ways of sending DiSEqC commands:
1. (default) = by calling a function provided by the KNCBDACTRL.DLL
2. KsProperty = by including the code within the DLL in TV Server
3. KsControl = this is similar to KsProperty but uses a more exact version of the code in the DLL

The 1.2.1 default TVLibrary uses yet another method. I've wanted to replace that method for some time since it only supports four port switching. The other methods above support "raw" commands, so we could implement motor/positioner and 16 port switch control for KNC-compatible tuners.

You'd be very welcome to test DiSEqC switching with the 3 DLLs. In addition there are the tests that I asked for Jean to do - it would be helpful if you could perform those tests three times:
1. Both tuners have CI slots connected and CAMs inserted.
2. Tuner 1 has a CI slot connected with CAM inserted; tuner 2 has the CI slot disconnected.
3. Tuner 2 has a CI slot connected with CAM inserted; tuner 1 has the CI slot disconnected.

Feel free to ask questions if that doesn't make sense!

mm

 

[Django.edwards]

Hi mm,

this testscenario makes absolut sense!

But before I try this, I would give you another hint. I'm trying with the KNC Software (Globe TV). Here the Diseqc switching works very reliable. What I discovered is that they use an very new dll. See attached one. Is it possible that you have an old one?

Will do your test as soon as possible. At the moment I'm not in front of the server.

 

[mm1352000]

Hi Django

It is possible that you could use that DLL with MediaPortal. I will check the dependencies and function parameters when I get home tonight and let you know.

mm

 

[JeanBuilder]

Hi MM,

Here are the testresults from test 1 and 2.

Test 1 succeeded so there is a good log attached.
Test 2 with tuner 2 failed because there was an error with the tv Server while scanning channels.

Greetz Jean.

 

[JeanBuilder]

Hi again MM,

I did some other testing with only tuner 1.
Maybe i dont get it but i dont know how to select tuner in the manual control window.

I hope you can make something out of this.
The error logs are posted to....

Greetings from Holland.

Jean

 

[chr0non]

Hi mm,

Apologies for the silence but I appear to have stopped getting notifications of updates to this thread. I'd actually logged in to give you a gentle nudge and I see you've been hard at work building new DLLs for us to try

Hopefully, making a new post will reactivate the notifications, but in any case I'll try out the new DLL tomorrow morning (when there is less competition for access to the TVserver) and send you the logs as usual. Is your main interest for now the results from the KNCBDACTRL functions?

Regards
C