Help us to nail down the general problems with some technotrend cards (2 Viewers)

[MediaFreak Ralf]

Hi Loendersloot,

I will test this rightaway, sounds very, very good! I will update this post so you can see my experiences.

Ralf

UPDATE: Thank you so Much! I can 'see clearly' now! Channel changing goes as fast as i have seen in ProgDVB. So it is clear that the problem lies in the Technotrend Drivers from Jan '09. Finally everything works!

This weekend i won't be around, but a large amount of Recordings are scheduled, so i will see after the weekend if the server makes the weekend!


morpheus_xx : i still use your updated TSWriter, do you think this is part of the solution? Or could it be just TT's buggy drivers?

 

[loendersloot]

You have to use the tswriter from Morpheus. He made this one especially for us technotrend users.

So in short terms:

Use the previous tt drivers. (attached)

At TVServer Configuration,
General settings:
Scan->PMT: 30
Timeshift-> Wait for unscrambled signal: 30
Timeshift->Wait for timeshifting file: 30

Use the latest svn:
https://forum.team-mediaportal.com/...t-03-22-2009-14-53h-revision-22029-rar-56831/

And install Morpheus his tswriter.
(overwrite the one in your tvserver folder)

Now everything should be okay.

 

[ChristerS]

Okey, then i don't try the jan 09 version of the driver. It's seems like this driverversion for TT3650 is not a god combination with TVServer.

Morpheus_xx:
Will this TT fix be in future SVN?

 

[morpheus_xx]

Morpheus_xx:
Will this TT fix be in future SVN?

Yes, it already is included. When the next public build is realeased it's in

 

[ChristerS]

Greate!

I have done some more research.

I previously have use MPStandbyhandler to restart my both TT card, Stop and Start MP and TVServer.

I no have tried a clean MP solution. Without MPSH and checked that Powerschedular shall reinit the services.

In this setup, after return from suspend, I notice that there also seems to be a problem with the latest driver (5.0.1.8) for TT S2-3200. With this driver it couldn't always switch between channels properly. I got an error message (No card... - 4TR error message) and had to try again and sometimes with success.

I reverted to previous version (5.0.0.19) and with this drive there seems to be no problem when returning from suspend. I will try this setup and see how it works the upcoming days.

 

[loendersloot]

I cheerded too early. Just got home from work and there was a long list of the next message of tswriter:

26-03-2009 07:27:50.343 TechnoTrend: slot:0 empty
26-03-2009 07:27:50.468 TechnoTrend: slot:0 module inserted

And in the tvlog, when I tried to start live tv:

2009-03-26 07:27:45.953125 [12]: card: CAM enabled : True
2009-03-26 07:27:45.953125 [12]: start subch:0 No PMT received. Timeshifting failed

 

[te3hpurp]

It seems that lately this thread has focused for TT S2-3650 problems.

Well i have TT s2 3200 with dilog cam & CD nordic subscription. It's working like charm with with cam and with that "other" method,
not mentioned here . It was somewhere in Nov 2008 that things started to get stable and nowadays it's okay.

regards,

 

[loendersloot]

What "other" method do you mean?

 

[morpheus_xx]

I cheerded too early. Just got home from work and there was a long list of the next message of tswriter:

26-03-2009 07:27:50.343 TechnoTrend: slot:0 empty
26-03-2009 07:27:50.468 TechnoTrend: slot:0 module inserted

And in the tvlog, when I tried to start live tv:

2009-03-26 07:27:45.953125 [12]: card: CAM enabled : True
2009-03-26 07:27:45.953125 [12]: start subch:0 No PMT received. Timeshifting failed

I'm afraid there is not much we can do, if the card/driver/api tells us that is has no cam inserted, and that's changing in every 7 seconds

26-03-2009 07:25:35.640 TechnoTrend: slot:0 empty
26-03-2009 07:25:35.750 TechnoTrend: slot:0 module inserted
26-03-2009 07:25:42.656 TechnoTrend: slot:0 empty
26-03-2009 07:25:42.781 TechnoTrend: slot:0 module inserted

2009-03-26 07:27:42.937500 [12]: TechnoTrend IsCamReady(): IsCamPresent:True, IsCamReady:False
2009-03-26 07:27:42.937500 [12]: subch:0 SendPmt failed cam flags:False
2009-03-26 07:27:45.937500 [12]: WaitForPMT: Timed out sending PMT to CAM 12 seconds.

Maybe a "reset" of CI would help, but there is no such function available in API. One approach could be:

• sending PMT fails, because "slot is empty"
• then a timeout occures in sending PMT
• in this case: close API / HW completly, then Open it again

Maybe this would be kind of "reset". Don't know.

But this behaviour would have drawbacks also: You could enter a endless loop, if your card has a CI but you don't have a CAM inserted (this is what "slot empty" means)....

And we would try to circumvent a bad behaving hardware or driver

 

[mortstar]

What "other" method do you mean?

The first rule of the other method, is you do not talk about the other method. :sorry: