Re: [vdr] about the hvr-4000 tuning problems
>> I have following in my channel conf for dvb-t and dvb-s channels: >> YLE >> TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 >> arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 >> > > Concerning Arte, I've got that same setting in my channels.conf. And I'm > able to see that channel instantly. > >> Klaus, do you have any idea from which functions I should try to track >> more for finding the problem? >> > > I use a Hauppauge NOVA-HD-S2 and I've updated to the latest S2API drivers > on the s2-liplianin repository. It uses the same kernel-driver as the > HVR-4000. And I don't have any tuning problems at all on Hotbird 13.0, > Astra 19.2, Astra 23.5 and Astra 28.2. This is with VDR 1.7.0 and my own > S2API patch as well as with VDR 1.7.3. I have tried both with the s2-liblianin and v4l-dvb versions of the drivers and I do not see any differences. scan,szap,szap-s2,scan-s2 and vdr-1.6.0 works ok with all of them. It's just that neither vdr-1.7.0 with your patches or vdr-1.7.2 or vdr-1.7.3 without patches are working. > > By any chance, did you try disabling diseqc? Because I had tuning problems > when I used standard diseqc values with no retries with my diseqc 1.0 > switch. I had to use the following safe diseqc commands for my diseqc 1.0 > configuration: I do not have diseqc in my system and I checked that at least the cDvbTuner::SetFrontEnd() method from dvbdevice.c detected that correctly and went to else part of the block. (=no diseqcs) When I try to change to a (not previously tuned with szap) dvb-s/s2 channel, vdr will just notice that the tunerStatus variable in Action() method is = 2, which means that "tuned". It will never go to state 3 which means "locked". With szap-s2,szap or vdr-1.6.0 I can however get the locks immediately. So I am wondering that what could be the most potential places in vdr code where I should try to make some changes to tuning/locking code for testing. Is it the cDvbTuner::SetFrontEnd method or is there also some other methods that are really interfacing with S2API and could affect to the tuning or locking? Mika > # > # port 1 > S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W100 [E0 10 38 F0] W100 [E0 > 11 00] W100 A W15 t > S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W100 [E0 10 38 F1] W100 [E0 > 11 00] W100 A W15 T > S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W100 [E0 10 38 F2] W100 [E0 > 11 00] W100 A W15 t > S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W100 [E0 10 38 F3] W100 [E0 > 11 00] W100 A W15 T > # port 2 > S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W100 [E0 10 38 F4] W100 [E0 > 11 00] W100 B W15 t > S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W100 [E0 10 38 F5] W100 [E0 > 11 00] W100 B W15 T > S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W100 [E0 10 38 F6] W100 [E0 > 11 00] W100 B W15 t > S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W100 [E0 10 38 F7] W100 [E0 > 11 00] W100 B W15 T > # port 3 > S23.5E 11700 V 9750 t v W15 [E0 10 38 F8] W100 [E0 10 38 F8] W100 [E0 > 11 00] W100 A W15 t > S23.5E 9 V 10600 t v W15 [E0 10 38 F9] W100 [E0 10 38 F9] W100 [E0 > 11 00] W100 A W15 T > S23.5E 11700 H 9750 t V W15 [E0 10 38 FA] W100 [E0 10 38 FA] W100 [E0 > 11 00] W100 A W15 t > S23.5E 9 H 10600 t V W15 [E0 10 38 FB] W100 [E0 10 38 FB] W100 [E0 > 11 00] W100 A W15 T > # port 4 > S28.2E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 > 11 00] W100 B W15 t > S28.2E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 > 11 00] W100 B W15 T > S28.2E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 > 11 00] W100 B W15 t > S28.2E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 > 11 00] W100 B W15 T > S28.5E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 > 11 00] W100 B W15 t > S28.5E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 > 11 00] W100 B W15 T > S28.5E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 > 11 00] W100 B W15 t > S28.5E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 > 11 00] W100 B W15 T > >> Mika >> > > Regards, > > Niels Wagenaar > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] about the hvr-4000 tuning problems
Op Do, 15 januari, 2009 23:30, schreef Mika Laitio: > Hi > > -- SNIP -- > > I have following in my channel conf for dvb-t and dvb-s channels: > YLE > TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 > arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 > Concerning Arte, I've got that same setting in my channels.conf. And I'm able to see that channel instantly. > Klaus, do you have any idea from which functions I should try to track > more for finding the problem? > I use a Hauppauge NOVA-HD-S2 and I've updated to the latest S2API drivers on the s2-liplianin repository. It uses the same kernel-driver as the HVR-4000. And I don't have any tuning problems at all on Hotbird 13.0, Astra 19.2, Astra 23.5 and Astra 28.2. This is with VDR 1.7.0 and my own S2API patch as well as with VDR 1.7.3. By any chance, did you try disabling diseqc? Because I had tuning problems when I used standard diseqc values with no retries with my diseqc 1.0 switch. I had to use the following safe diseqc commands for my diseqc 1.0 configuration: # # port 1 S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W100 [E0 10 38 F0] W100 [E0 11 00] W100 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W100 [E0 10 38 F1] W100 [E0 11 00] W100 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W100 [E0 10 38 F2] W100 [E0 11 00] W100 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W100 [E0 10 38 F3] W100 [E0 11 00] W100 A W15 T # port 2 S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W100 [E0 10 38 F4] W100 [E0 11 00] W100 B W15 t S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W100 [E0 10 38 F5] W100 [E0 11 00] W100 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W100 [E0 10 38 F6] W100 [E0 11 00] W100 B W15 t S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W100 [E0 10 38 F7] W100 [E0 11 00] W100 B W15 T # port 3 S23.5E 11700 V 9750 t v W15 [E0 10 38 F8] W100 [E0 10 38 F8] W100 [E0 11 00] W100 A W15 t S23.5E 9 V 10600 t v W15 [E0 10 38 F9] W100 [E0 10 38 F9] W100 [E0 11 00] W100 A W15 T S23.5E 11700 H 9750 t V W15 [E0 10 38 FA] W100 [E0 10 38 FA] W100 [E0 11 00] W100 A W15 t S23.5E 9 H 10600 t V W15 [E0 10 38 FB] W100 [E0 10 38 FB] W100 [E0 11 00] W100 A W15 T # port 4 S28.2E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.2E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.2E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.2E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T S28.5E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.5E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.5E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.5E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T > Mika > Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] about the hvr-4000 tuning problems
Hi I have tried to add some more printouts to dvbdevice.c for trying to understand why the vdr-1.7.x fails to tune to dvb-s or dvb-s2 channels. hvr-1300 is in /dev/dvb/adapter0 and hvr-4000 is in /dev/dvb/adapter1 I added printouts to SetFrontEnd() and Action() methods. In SetFrontEnd() method it seems that the code is at least always going to correct if/else block. (No, diseq, dvb-t, dvb-s or dvb-s2 depending on what channel I try to tune) If I watch dvb-t channel (which works), I can see a following logs: Action(): cardIndex: 0, tunerStatus: 1, NewStatus: 0 SetFrontEnd(): DVB-T, fd_frontend: 4, cardIndex: 0 Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 1 ... Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 ... If I instead try to tune to new dvb-s channel that I have not previously pre-tuned with szap or szap-s2 (for example arte), vdr will fail to show the channel and I can see a following: Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 1, tunerStatus: 1, NewStatus: 31 Setup.DiSeqC == false SetFrontEnd(): DVB-S, fd_frontend: 6, cardIndex: 1 (frequency * 1000UL): 993000 channel.Modulation(): 9 channek.Srate() * 1000UL): 2200 channel.CoderateH(): 5 channel.Inversion(): 2 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 3 frontend 1 lost lock on channel 5, tp 110743 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 ... If I have pre-tuned for example to same arte with szap-s2, then vdr is able to show that channel, and I get a following output: Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 1, NewStatus: 3 Setup.DiSeqC == false Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 SetFrontEnd(): DVB-S, fd_frontend: 6, cardIndex: 1 (frequency * 1000UL): 993000 channel.Modulation(): 9 channek.Srate() * 1000UL): 2200 channel.CoderateH(): 5 channel.Inversion(): 2 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 ... I have following in my channel conf for dvb-t and dvb-s channels: YLE TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 Klaus, do you have any idea from which functions I should try to track more for finding the problem? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
