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="mm1352000" data-source="post: 1198507" data-attributes="member: 82144"><p>Mmmm, it's not their DiSEqC method that they would have to fix. There doesn't seem to be anything wrong with that. If anything, it's their tuning method. In my opinion they should stick to the provided tuning parameters.</p><p></p><p>Consider the DMAX to THT transition again:</p><p>1. DMAX</p><p>19.2E</p><p>12480 V DVB-S</p><p>MPEG-2 27500</p><p>3/4</p><p></p><p>2. THT</p><p>13.0E</p><p>11034 V DVB-S</p><p>MPEG-2 27500</p><p>3/4</p><p></p><p>If your theory is correct (...and I can only assume that it is, because I haven't got any better theory! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> ), I guess the reason for the failure is that the tuner is locking onto 19.2E 11038.00 V DVB-S QPSK 22000 5/6 (<a href="http://en.kingofsat.net/tp.php?tp=24" target="_blank">link</a>). This guess is based on the similarity of the frequencies. However the symbol rates and FEC code rates don't match. Therefore I would say that the tuner should be skipping/ignoring it.</p><p></p><p></p><p>Nice idea. <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></p><p>Sure! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>It's here:</p><p><a href="https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVLibrary/Implementations/DVB/DisEqC/DiSEqCMotor.cs#L432-L452" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVLibrary/Implementations/DVB/DisEqC/DiSEqCMotor.cs#L432-L452</a></p><p></p><p>There you can see:</p><ul> <li data-xf-list-type="ul">first go-to command<br /> </li> <li data-xf-list-type="ul">100 ms delay</li> <li data-xf-list-type="ul">repeated go-to command</li> <li data-xf-list-type="ul">100 ms delay</li> </ul><p>According to the DiSEqC specifications each message bit takes 1.5 ms to transmit. Since each go-to command contains 4 bytes (=> 32 bits), each command will take 48 ms to transmit. The driver may also add its own delays.</p><p></p><p>In that class/function you have access to _currentPosition - TV Server's record of the motor's current position. That will be correct as long as you don't use some external agent to move the motor. Since you know the mappings between position numbers and longitudes (eg. position #1 is 19.2E), you could calculate approximately how far the motor has to move. Therefore you could also make the delay proportionate to the distance.</p><p></p><p>Note that the motor will move faster or slower depending on the polarisation of the currently tuned transponder, because that determines the voltage on the cable. If the tuner is tuned to a horizontal or circular left transponder the voltage will be 18 V; otherwise the voltage will be 13 V (=> slower movement). That class/function does not have access to the current transponder details, so it would be safest to assume slow movement. However if wanted you could pass in the polarisation as an extra parameter.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1198507, member: 82144"] Mmmm, it's not their DiSEqC method that they would have to fix. There doesn't seem to be anything wrong with that. If anything, it's their tuning method. In my opinion they should stick to the provided tuning parameters. Consider the DMAX to THT transition again: 1. DMAX 19.2E 12480 V DVB-S MPEG-2 27500 3/4 2. THT 13.0E 11034 V DVB-S MPEG-2 27500 3/4 If your theory is correct (...and I can only assume that it is, because I haven't got any better theory! :) ), I guess the reason for the failure is that the tuner is locking onto 19.2E 11038.00 V DVB-S QPSK 22000 5/6 ([URL='http://en.kingofsat.net/tp.php?tp=24']link[/URL]). This guess is based on the similarity of the frequencies. However the symbol rates and FEC code rates don't match. Therefore I would say that the tuner should be skipping/ignoring it. Nice idea. :) Sure! :) It's here: [URL]https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVLibrary/Implementations/DVB/DisEqC/DiSEqCMotor.cs#L432-L452[/URL] There you can see: [LIST] [*]first go-to command [*]100 ms delay [*]repeated go-to command [*]100 ms delay [/LIST] According to the DiSEqC specifications each message bit takes 1.5 ms to transmit. Since each go-to command contains 4 bytes (=> 32 bits), each command will take 48 ms to transmit. The driver may also add its own delays. In that class/function you have access to _currentPosition - TV Server's record of the motor's current position. That will be correct as long as you don't use some external agent to move the motor. Since you know the mappings between position numbers and longitudes (eg. position #1 is 19.2E), you could calculate approximately how far the motor has to move. Therefore you could also make the delay proportionate to the distance. Note that the motor will move faster or slower depending on the polarisation of the currently tuned transponder, because that determines the voltage on the cable. If the tuner is tuned to a horizontal or circular left transponder the voltage will be 18 V; otherwise the voltage will be 13 V (=> slower movement). That class/function does not have access to the current transponder details, so it would be safest to assume slow movement. However if wanted you could pass in the polarisation as an extra parameter. [/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