home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
TV-Cards
DVB S/S2 cards on legacy PCI interface.
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Kotik" data-source="post: 1198569" data-attributes="member: 89825"><p>With 2000ms delays these are the results:</p><p></p><p><strong><u>[2016-10-19 22:12:41,562] [Log ] [18 ] [INFO ] - DiSEqC: goto position 2</u></strong></p><p>[2016-10-19 22:12:41,655] [Log ] [18 ] [INFO ] - ProfRed: setdiseqc returned:0</p><p>[2016-10-19 22:12:42,765] [Log ] [18 ] [INFO ] - ProfRed: setdiseqc returned:0</p><p><strong><u>[2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmiting tunerequest Channel:THT subChannel:0</u></strong></p><p>[2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb:using existing subchannel:0</p><p>[2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest size:1 new:0</p><p>[2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - subch:0 OnBeforeTune</p><p>[2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest calling put_TuneRequest</p><p>[2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest done calling put_TuneRequest</p><p>[2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - subch:0 OnAfterTune</p><p>[2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - RunGraph</p><p>[2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - subch:0 OnGraphStart</p><p>[2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - dvb: RunGraph</p><p>[2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - dvb: LockInOnSignal ok</p><p>[2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - subch:0 OnGraphStarted</p><p>[2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - subch:0 SetupPmtGrabber<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" />id 12C sid:6A7</p><p>[2016-10-19 22:12:46,453] [Log ] [18 ] [INFO ] - subch:0 set pmt grabber pmt:12C sid:6A7</p><p>[2016-10-19 22:12:46,453] [Log ] [18 ] [DEBUG] - TimeShifter.OnAfterTune: resetting audio/video time</p><p>[2016-10-19 22:12:46,453] [Log ] [18 ] [DEBUG] - WaitForPMT: Waiting for PMT 12C</p><p>[2016-10-19 22:12:46,500] [Log ] [16 ] [INFO ] - subch:0 OnPMTReceived() pmt:12C ran:True dynamic:False</p><p>[2016-10-19 22:12:46,515] [Log ] [18 ] [DEBUG] - WaitForPMT: Found PMT after 0.0625058 seconds.</p><p>[2016-10-19 22:12:46,515] [Log ] [18 ] [INFO ] - subch:0 SendPmt:6A7 6A7 FFFFFFFF 1</p><p></p><p>As u can see there is approx. 2 seconds delay before two commands and we get a positive result the result is not consistent, meaning that I calculated the time my dish needs to travel from 19.2E to 13.0E, my motor specs state that the motor can move 1.9 degrees / per second under 12 volts (so for channels with Vertical polarization) and 2.5 degrees / per second under 18 volts (so for channel with Horizontal polarization), 19.2 - 13 = 6.2 degrees since the channel I am tunning to has vertical polarization it will use 12 volts, so 6.2 / 1.9 = 3.2 seconds, as u can see I need 3.2 seconds for s complete move.</p><p></p><p>Now we delay 2000ms which is a bit shorter but if we add tuner delays and some other added up delays I think we are around 2.5 seconds which is still shorter than 3.2. What I want to know is why we are sending DiseqC commands twice? and how exactly does it work? are we sending them both at the same time? [USER=82144]@mm1352000[/USER] I need ur wisdom here.</p><p></p><p>Another part that we have to make sure is applied is a stop tune command, we really need to instruct the tuner to stop whatever it is doing BEFORE we start moving the dish.I will try to explain the reason without confusing u even more <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>I will talk only about TBS and specifically only about TBS 6902, I got no idea how other cards are working but lets try for now see how exactly TBS 6902 is working.</p><p></p><p>Things we know for a fact:</p><p>1. It ignores tuning parameters, it will respect the frequency parameter but can ignore polarization, fec rate, symbol rate and modulation. As far as I understand this is something that more cards might be doing as well.</p><p>2. It will always try to re-lock on a signal loss, the time out for this one is unknown to me, but after testing I would say it is huge. The card will keep trying even after 20 seconds. Unless it is instructed different tuning parameters.</p><p></p><p>As per TBS the proper way of using this card (not sure about the rest as I was instructed specifically for this one) with a motor is the following. 1st move the motor and then supply tune parameters.</p><p>I would add here another major step, BEFORE moving the motor send a stop tune command to the card, this is very important and I will explain why, the problem is that TBS 6902 and any other card that is using the same aggressive locking mechanism will try to re lock automatically on signal lost, this means that if the dish is moving and a similar frequency is found during the movement it will lock on it and report success. By adding a delay in submitting tuning parameters we make sure the card wont lock on any similar frequency of the NEXT channel but we are not making sure that the card will not re-lock on any similar frequency of the PREVIOUS channel.</p><p></p><p>Ideally the steps should look like that:</p><p></p><p>STOP ------->MOVE(add delay here)------>SEND TUNE PARAMETERS------->START and this logic should be applied always ONLY IF the dish has to move.</p><p></p><p>I hope I didn't confuse anyone.</p></blockquote><p></p>
[QUOTE="Kotik, post: 1198569, member: 89825"] With 2000ms delays these are the results: [B][U][2016-10-19 22:12:41,562] [Log ] [18 ] [INFO ] - DiSEqC: goto position 2[/U][/B] [2016-10-19 22:12:41,655] [Log ] [18 ] [INFO ] - ProfRed: setdiseqc returned:0 [2016-10-19 22:12:42,765] [Log ] [18 ] [INFO ] - ProfRed: setdiseqc returned:0 [B][U][2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb:confused:ubmiting tunerequest Channel:THT subChannel:0[/U][/B] [2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb:using existing subchannel:0 [2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb:confused:ubmit tunerequest size:1 new:0 [2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - subch:0 OnBeforeTune [2016-10-19 22:12:43,781] [Log ] [18 ] [INFO ] - dvb:confused:ubmit tunerequest calling put_TuneRequest [2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - dvb:confused:ubmit tunerequest done calling put_TuneRequest [2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - subch:0 OnAfterTune [2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - RunGraph [2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - subch:0 OnGraphStart [2016-10-19 22:12:44,515] [Log ] [18 ] [INFO ] - dvb: RunGraph [2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - dvb: LockInOnSignal ok [2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - subch:0 OnGraphStarted [2016-10-19 22:12:46,437] [Log ] [18 ] [INFO ] - subch:0 SetupPmtGrabber:pid 12C sid:6A7 [2016-10-19 22:12:46,453] [Log ] [18 ] [INFO ] - subch:0 set pmt grabber pmt:12C sid:6A7 [2016-10-19 22:12:46,453] [Log ] [18 ] [DEBUG] - TimeShifter.OnAfterTune: resetting audio/video time [2016-10-19 22:12:46,453] [Log ] [18 ] [DEBUG] - WaitForPMT: Waiting for PMT 12C [2016-10-19 22:12:46,500] [Log ] [16 ] [INFO ] - subch:0 OnPMTReceived() pmt:12C ran:True dynamic:False [2016-10-19 22:12:46,515] [Log ] [18 ] [DEBUG] - WaitForPMT: Found PMT after 0.0625058 seconds. [2016-10-19 22:12:46,515] [Log ] [18 ] [INFO ] - subch:0 SendPmt:6A7 6A7 FFFFFFFF 1 As u can see there is approx. 2 seconds delay before two commands and we get a positive result the result is not consistent, meaning that I calculated the time my dish needs to travel from 19.2E to 13.0E, my motor specs state that the motor can move 1.9 degrees / per second under 12 volts (so for channels with Vertical polarization) and 2.5 degrees / per second under 18 volts (so for channel with Horizontal polarization), 19.2 - 13 = 6.2 degrees since the channel I am tunning to has vertical polarization it will use 12 volts, so 6.2 / 1.9 = 3.2 seconds, as u can see I need 3.2 seconds for s complete move. Now we delay 2000ms which is a bit shorter but if we add tuner delays and some other added up delays I think we are around 2.5 seconds which is still shorter than 3.2. What I want to know is why we are sending DiseqC commands twice? and how exactly does it work? are we sending them both at the same time? [USER=82144]@mm1352000[/USER] I need ur wisdom here. Another part that we have to make sure is applied is a stop tune command, we really need to instruct the tuner to stop whatever it is doing BEFORE we start moving the dish.I will try to explain the reason without confusing u even more :) I will talk only about TBS and specifically only about TBS 6902, I got no idea how other cards are working but lets try for now see how exactly TBS 6902 is working. Things we know for a fact: 1. It ignores tuning parameters, it will respect the frequency parameter but can ignore polarization, fec rate, symbol rate and modulation. As far as I understand this is something that more cards might be doing as well. 2. It will always try to re-lock on a signal loss, the time out for this one is unknown to me, but after testing I would say it is huge. The card will keep trying even after 20 seconds. Unless it is instructed different tuning parameters. As per TBS the proper way of using this card (not sure about the rest as I was instructed specifically for this one) with a motor is the following. 1st move the motor and then supply tune parameters. I would add here another major step, BEFORE moving the motor send a stop tune command to the card, this is very important and I will explain why, the problem is that TBS 6902 and any other card that is using the same aggressive locking mechanism will try to re lock automatically on signal lost, this means that if the dish is moving and a similar frequency is found during the movement it will lock on it and report success. By adding a delay in submitting tuning parameters we make sure the card wont lock on any similar frequency of the NEXT channel but we are not making sure that the card will not re-lock on any similar frequency of the PREVIOUS channel. Ideally the steps should look like that: STOP ------->MOVE(add delay here)------>SEND TUNE PARAMETERS------->START and this logic should be applied always ONLY IF the dish has to move. I hope I didn't confuse anyone. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
TV-Cards
DVB S/S2 cards on legacy PCI interface.
Contact us
RSS
Top
Bottom
