Trouble with Terratec H7 and CAM (2 Viewers)

[mm1352000]

Thanks everyone for testing!
*sigh* - I was hoping everything would just work.

aat:

I’m, still accessing my setup with remote desktop, so don’t know much about the use for watching TV/recordings. But I have installed and tested the new patch, and so far both the Cinergy and the H7 has run for hours without crash or freeze when zapping on remote desktop or when recording by schedule.

Excellent!

CI-menu navigation is working fine on my H7 (dvb-c part).

Also excellent!

CI-menu on the Cinergy C is unchanged - scramblingproblem I solved, but CI-menu doesn’t respond.

Do you have logs to show this? If the menu works on the H7 then theoretically it should also work on the Cinergy. There is one small thing that could possibly cause this. It would be a 5 second check if you can post the tv.log file. Copy-paste from RDP would be okay.

ogir_xx:

1 - Updated from 1.2.1 to 1.2.2 and installed your new patch
Channel switching seemed ok. But no contact with CI menu, but probably because my current test setup with M****

You can't access a CI menu with M***I. The menu is built into the CAM firmware. Without a CAM you can't have a menu to enter. You can still have a menu with a CAM that doesn't have a smartcard inserted. Some entries or information might be missing.

2 - Deleted all channels and tried a complete rescan with 1.2.2 and your new patch to regenerate missing logs from my previous findings and post.
Almost same results; only found a few channels and tuning them resulted in "unknown error".

I can't explain the unknown errors without the MP client logs - something strange was happening there. To expand a little: TV Server was successfully tuning and then [I think] being told to stop timeshifting by the MP client. It might be a combination of changes that I've made + M****.

3 - Reinstalled 1.2.1 and cleared all channels to eliminate possible cause of tuning trouble.
Rescanned for channels again, this time approx 140 channels found.

Maybe off topic here; but MPTVserver setup seemed to hang when trying to clear channels
So had to restart/reboot several times. Hopefully the logs show all info

The strange thing from my findings, is when upgrading to 1.2.2 with the channels from before intact, tuning and watching seemed ok. But rescanning for channels didnt. I initially thought my M**** had screwed channel tuning to a mess. But ALAS the tuning problem was experienced only on 1.2.2 and with the new patch.

I have the sneaking suspicion that the fix that causes the long term stability for channel changing is causing the problems with the scan.
paalkr, aat: did you test a full scan?

paalkr:

I really appreciate the dedication and effort in helping out mm!! With the latest v1.5 path the TwinHan and Terratec card seems to work in daily operation. I can tune any channel and both tuners works well after being idle.

Well that is good.

The CI menu does not work though, on either cards. I manage to get som info in the CI menu for the Twinhan card once, but for the most time the TV service crashes when I try to open the CI menu. The one time I manage to load the menu for the Twinhan card I had big trouble selecting any entries in the menu, because any selection in the menu was reset almost immediately. i looked like the CI menu refreshed itselves constantly, and then any selections where reset as well (hope you understand).

I think the difference between the failure here for you and the success for aat could be down to the CAM. In the case of the AD-TP300 (I think you tested that first?) it looks like the CAM was still being initialised by the tuner driver when you tried to enter the menu:

2012-01-04 19:01:08.435410 [Twinhan MMI handler(22)]: Twinhan: MMI handler thread start polling
2012-01-04 19:01:08.435410 [Twinhan MMI handler(22)]: Twinhan: CI state change, old state = Empty_Old, new state = CamOkay
2012-01-04 19:01:08.435410 [Twinhan MMI handler(22)]: Twinhan: MMI state change, old state = Uninitialised, new state = MenuInit

I'm still learning what the CI and MMI states mean though - there is no good documentation from Twinhan or anyone else.

One point: I notice in the logs that you tried to enter the menu several times for each tuner within 10 seconds. The menu can take quite a long time to show - sometimes 10 or 15 seconds depending on the CAM and whether the tuner driver has finished initialising the CI. Please try again and give a little more time for the menu to show. If it doesn't show after 30 seconds then that would be a problem.

I have attached a log where the TVservices crashes when entering the CI menu.

This is something I'm not able to fully explain. The exception is here:

2012-01-04 19:02:05.125909 [SetupTv(1)]: Exception ystem.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.0.11:31456



Server stack trace:

at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)

at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)

at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)



Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at TvControl.IController.remove_OnCiMenu(CiMenuCallback value)

at TvControl.RemoteControl.UnRegisterCiMenuCallbacks(CiMenuCallbackSink sink)

at SetupTv.Sections.CI_Menu_Dialog.OnSectionDeActivated()

at SetupTv.Sections.CardDvbT.OnSectionDeActivated()

at SetupTv.SetupTvSettingsForm.cancelButton_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

This same kind of exception actually happened several times. I wonder: are you using a static or dynamic IP address on the server, and when you performed the test was it after resuming from standby?

But, to be honest. I really don't see what kind of information the CI menu actually will provide me, and if I need the menu for anything. I'm happy as long as the tuners works for recordings and watching TV

I know what you mean. I think the main thing about the CAM menu is not the menu itself but the notifications from the CAM about decrypt failures. Having said that, on some CAMs you can do really useful things with it like turn multidecrypt on/off or enable/disable child protection etc. Anyhow, that is my opinion. Other people seem to really like the feature.

BTW. I discovered that the pairing signal for the CAM was not picked up if the option for grabbing EPG was disabled on a tuner, where the CAM was inserted. I was kind of stressed for some hours, when my new CAM and keycard refused to pair, and hence no encrypted channels worked. I even called my provider several times and asked them to send out new paring signals.

Feedback noted. The team are aware that TV Server is missing the ability to timeshift and wait for the pairing signal and the stream to become clear. Enabling EPG grabbing is a very clever work-around (I will suggest that to other people ) however in the future I would really like to find a better way to do this.

mm

 

[ogir_xx]

Hi MM

Got my new HW, so did som test with my Terratec Cinergy PCI HD with CI module.
( - off topic; HD TV channels with no stuttering seems acheviable at last!!!!)

1) installed a clan MP 1.2.1 and did a channel scan - ok 139 channels found
2) Updated to MP 1.2.2, cleared channels and did a rescan - ok 139 channels found
3) Cleared channels and installed your patch, rescanned - ok 139 channels found - viewing channels almost 100% ok, both scrambeled and FTA - CI meny in MPserver setup NOT ok. To be more precise; nothing happend when activating the meny tab and waiting for 1 min. Tried several times. One or two situations when tuning to HD channels, the channels was reported as not found. Rescanning the same channels solved it though.

So no CI meny - but scanning and viewing seems ok.

Driver for cinergy used: 1.01.02.501

MP and TV service logs for all 3 steps added.

I have modified my H7 usb and power connections for my old ION mother board, so has to reengineer my soldering before I test the H7 on my new motherboard, with the CI and cam and without M****. Hopefully i get time during tomorrow.

Hope logs help

 

[mm1352000]

Hi again ogir_xx

*Thank you* for the thorough testing!

( - off topic; HD TV channels with no stuttering seems acheviable at last!!!!)

1) installed a clan MP 1.2.1 and did a channel scan - ok 139 channels found
2) Updated to MP 1.2.2, cleared channels and did a rescan - ok 139 channels found
3) Cleared channels and installed your patch, rescanned - ok 139 channels found - viewing channels almost 100% ok, both scrambeled and FTA...

Hmmmm, I see one error in the logs when you tried to view "KTV SVT1 HD" with my patch, but happily I can explain what happened because the CAM reported it (in the logs at least) through the CI menus (!!! ):

[COLLAPSE]2012-01-05 22:50:44.672407 [(3)]: card: WaitForTimeShiftFile - waiting _eventAudio & _eventVideo
2012-01-05 22:50:49.073659 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuClosed, new state = MenuOkay
2012-01-05 22:50:49.074659 [Twinhan MMI handler(12)]: Twinhan: read MMI response
2012-01-05 22:50:49.075659 [Twinhan MMI handler(12)]: Twinhan: result = success
2012-01-05 22:50:49.076659 [Twinhan MMI handler(12)]: Twinhan: menu
2012-01-05 22:50:49.076659 [Twinhan MMI handler(12)]: title =
2012-01-05 22:50:49.077659 [Twinhan MMI handler(12)]: sub-title =
2012-01-05 22:50:49.077659 [Twinhan MMI handler(12)]: footer =
2012-01-05 22:50:49.078659 [Twinhan MMI handler(12)]: # choices = 1
2012-01-05 22:50:49.078659 [Twinhan MMI handler(12)]: choice 1 = Ingen tilgang
2012-01-05 22:50:49.087660 [Twinhan MMI handler(12)]: type = 1
2012-01-05 22:50:49.588688 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuOkay, new state = MenuClosed
2012-01-05 22:50:53.588917 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuClosed, new state = MenuClose
2012-01-05 22:50:53.589917 [Twinhan MMI handler(12)]: Twinhan: menu close request
2012-01-05 22:50:53.593917 [Twinhan MMI handler(12)]: Twinhan: close menu
2012-01-05 22:50:53.593917 [Twinhan MMI handler(12)]: Twinhan: result = success
2012-01-05 22:50:54.094946 [Twinhan MMI handler(12)]: Twinhan: menu close request
2012-01-05 22:50:54.097946 [Twinhan MMI handler(12)]: Twinhan: close menu
2012-01-05 22:50:54.098946 [Twinhan MMI handler(12)]: Twinhan: result = success
2012-01-05 22:50:54.598975 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuClose, new state = MenuClosed
2012-01-05 22:50:59.674265 [(3)]: card: WaitForTimeShiftFile - no audio was found after 15,001858 seconds
2012-01-05 22:50:59.675265 [(3)]: card: WaitForTimeShiftFile - audio and video stream is scrambled[/COLLAPSE]

According to Google translate, Ingen tilgang means something like "access denied" (???). Maybe your subscription doesn't allow you to see that channel.

CI meny in MPserver setup NOT ok. To be more precise; nothing happend when activating the meny tab and waiting for 1 min. Tried several times.

I think there must be some bugs in the CI menu handling for all tuners because I can see in the logs that the menu was successfully entered:

[COLLAPSE]2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuClosed, new state = MenuOkay
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: Twinhan: read MMI response
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: Twinhan: result = success
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: Twinhan: menu
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: title = Conax CA
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: sub-title = Main menu2
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: footer = Press 'OK' to select; Press 'EXIT' to return2
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: # choices = 10
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 1 = Abonnementsstatus
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 2 = Event-status
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 3 = Tokens Status2
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 4 = Endre CA-PIN
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 5 = Aldersgrense
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 6 = Modem Ordering2
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 7 = Om Conax CA
2012-01-05 22:41:46.086452 [Twinhan MMI handler(12)]: choice 8 = Message2
2012-01-05 22:41:46.102052 [Twinhan MMI handler(12)]: choice 9 = Språk
2012-01-05 22:41:46.102052 [Twinhan MMI handler(12)]: choice 10 = Loader status
2012-01-05 22:41:46.102052 [Twinhan MMI handler(12)]: CI menu received but no listeners available
2012-01-05 22:41:46.102052 [Twinhan MMI handler(12)]: type = 1
2012-01-05 22:41:46.616853 [Twinhan MMI handler(12)]: Twinhan: MMI state change, old state = MenuOkay, new state = MenuClosed[/COLLAPSE]

The problem is that "no listeners available" part - it means that TV Server configuration was not actually listening to the CAM. ai don't understand why the error occurred (maybe morpheus_xx has more idea) but personally I have found that it is more reliable to test the menu from within MP using the context menu. I'm not saying that TV Server setup doesn't work at all - just that sometimes it does strange things.

I have modified my H7 usb and power connections for my old ION mother board, so has to reengineer my soldering before I test the H7 on my new motherboard, with the CI and cam and without M****. Hopefully i get time during tomorrow.

There is no big rush. I am in the meantime working on refactoring and improving support for other hardware (also some new hardware - I don't want to say too much right now but I hope that I can add support for quite a lot of new hardware over the next few months ).

Best regards,
mm

 

[ogir_xx]

Eager to help out, so in the silence of the night i couldnt sleep...
Fetched my soldering iron and mucked up a fast onboard current and usb solution for the H7 on my new mainboard

My findings with the H7:

1) Disabled my Cinergy PCI tuner and cleared all channels
2) With the H7 I GOT CONTACT WITH THE CI meny - Could see that my subscribtion status with my cable provider was up to date. The meny showed up in approx 10 secs.
3) Completely new rescan of channels with the H7, but only 9 was found.

5) Deleted all channels again and disabled the CAM for the H7 tuner in server setup
6) Completely new scan again with same results only 9 channels found

6) Reactivated Cinergy PCI tuner, cleared all channels and did a rescan. Mapped all (139) channels to both cards.
7) Deactivated Cinergy PCI, so that H7 was only tuner active.
8) Then swapping channels with CI and Cam on the H7 worked fine!

So it seems that your assumtion about the patch messing up only the tuning is correct.
Driver - TerraTec H7: 1.00.07.601

See logs attatched: Ps i did forget to change the signal cable to MY H7, on my first test of viewing the channels scanned with the Cinergy PCI. So a few "no signal" errors in the logs is due to this

Your comment on the "not allowed" channel SVT1HD - I must admit im not shure if its part of my subscription or not.... SVT1 in SD is but maybe not the HD version.

Off to bed... to few hours to an early start .(

Regards

 

[ogir_xx]

Have been testing som more today and channel changing and viewing seems pretty stable on the H7, WHEN the tuner and the CI is properly recognized.
What I experienced is that when restarting the computer, some of the channels threw a "signal scrambeled" message. Althoug I managed to tune yesterday.

I then opened Tv server setup and found that the CI menu didnt work despite yesterday.
If I CHANGED either Cam support on/off or disabled "preload card" on off AND saved the new settings forcing a Tv server restart, the cam menu (in TV setup) and tuning/watching channels would work again (in MP).

Recon the behavior pattern is enough to get You thinking - but can post logs if u need them.

Ps 1: Ive got a fast SSD no, so restart is quite quick
Ps 2: I have NOT set any delay on MP on startup to let tuner cards "start".
Ps 3: Initially on restart I have my card setup to "preload"

So it may be that in order to get the menu to work - the tuner card has to be finished initialized? - well U know better, just sharing my novice thoughts

Regards

 

[kse]

AW: Re: Trouble with Terratec H7 and CAM

BREAKTHROUGH!!!!!!

THANK YOU for being Awesome and investing so much time

tested it a few moments ago and it works like a charm with my cynergi C HD + CI

 

[mm1352000]

Hi again

So it may be that in order to get the menu to work - the tuner card has to be finished initialized? - well U know better, just sharing my novice thoughts

Your "novice" thoughts are not far wrong.

Have been testing som more today and channel changing and viewing seems pretty stable on the H7, WHEN the tuner and the CI is properly recognized.
What I experienced is that when restarting the computer, some of the channels threw a "signal scrambeled" message. Althoug I managed to tune yesterday.

Yes, I could understand how that would happen. It takes some time for the driver to initialise the CAM and make it ready to start descrambling or show the menu. You could test: if you wait for about 1 minute after TV Server has started before tuning any scrambled channels does it make any difference? My intention once I've finished refactoring all the classes is to add "wait for CAM (seconds)" and "retries" settings so that this situation [for descrambling] can be automatically handled for all tuners and all CAMs (different CAMs and different tuners take different lengths of time to become ready).

If I CHANGED either Cam support on/off or disabled "preload card" on off AND saved the new settings forcing a Tv server restart, the cam menu (in TV setup) and tuning/watching channels would work again (in MP).

This may also be part of the problem. Right now there is no updating of the CAM status unless you've attempted to enter the CAM menu. Again, that is something that I need to fix. Should be quite simple.

mm

 

[ogir_xx]

Hi again.

In my previous tests i have only had ONE tuner active simultaniosly.
Today I tested with both one H7 and one Cinergy PCI HD tuners active at the same time.

1) Well, suddenly channelswitching is not reliable, with almost every try resulting in a "channel is scrambeld" error message.

2) So, I mapped FTA channels to the Cinergy PCI + all channels to the H7 with CI, Cam and Card inserted. - No difference from results in # 1

3) Also tried different setups for # numbers of cards to try when tuning - no effect. And Cam on/off for the Cinergy although no Cam/card inserted - no effect.

4) Deactivated Cinergy PCi HD tuner - everyting working ok with the H7. (exept for initalizing problems)

5) TV has been constantly on tuned to the same channel for approx 6 hours now, and recently switched channels. (with tuner: H7). All ok, seems pretty stable

No logs attached - tell me if u want them

Regards

 

[mm1352000]

Hi again ogir_xx

Yes, I want the logs. I can't think of any possible explaination for this...

mm

 

[ogir_xx]

OK - ill post them tomorrow, off to a family dinner now
Sorry for not posting logs initially, thought you might had an explanation for the behavior.
regards