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: 1198389" data-attributes="member: 89825"><p>So back with info.</p><p></p><p>Situation is as following, there are currently 2 issues and they are not tied with each other:</p><p></p><p>No Signal ----> Always results from a wrong dish movement.</p><p></p><p>No PMT Found ----> This is a tricky one but read my findings and maybe u will understand what is going on.</p><p></p><p>Let me 1st focus on the No PMT Found issue, I spent pretty much half the day at my roof top with my TeamViewer, I did notice that 90% of the time moving from a channel (not all channels but many) that is located on 19.2E to 13.0E will result into a No PMT Found error. But there was a 10% chance that it will succeed, in order to troubleshoot it I decided to do a manual dish movement from the MP DiseqC tab, so I tune a channel on 19.2E from manual control tab, then I stop timeshifting and I go to the DiseqC tab, over there I manually send the dish to 13.0E and then revisit the manual control tab and start timeshifting a channel on 13.0E. It works 90%, note that the 10% failure is the No Signal bug (read on regarding that one).</p><p></p><p>The results of these tests made me thinking, then I remembered that 2 days ago I actually thought that I fixed the issue when I replaced the LNB and for a brief time I was able to switch between 19.2E and 13.0E with a higher success rate (around 50%), I tried to remember what could have changed and why my success rate went again back to 10% from 50%, the reason is that I adjusted my LNB after placing it to get higher signal quality and after that adjustment my success rate dropped again, so how could higher signal quality affect the issue? At that point I immediately got an idea, what if the issue is that MP/TBS is trying to find PMT while the dish is still moving? What if there is a Lock On happening before the dish arrives into its proper location?</p><p></p><p>To test it out I used my hands<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> I moved the dish to 19.2E tuned to a channel and then switched to a channel that is located @ 13.0E BUT when the dish started moving I covered the LNB with my palm and waited out the whole movement, when the dish parked I removed my palm and lord and behold, NO error, crystal clear signal with no issues. Sounded too good to be true so I did it a couple more times. 100% success ratio. I then combined this finding with the accidental 50% increased chance of success due to LNB adjustment and it made sense.</p><p></p><p>To make sure I am not hallucinating I tried out my theory without the help of my palm<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> I changed the LNB skew in a way that the signal quality is low, yes LOW, my theory at that point was the following: we are sending a command to move the dish but at the same time send the tune command, as a result if during the movement there are other frequencies found the tuner will lock on them and MP will start searching for PMT, but there wont be any cause the dish is still moving. By blocking the LNB with my hand I prevent the tuner from locking into any signal while the dish is still moving, this will also explain why manually moving the dish from the DiseqC tab is working, cause during that move we are not trying to tune to any channel.</p><p></p><p>So back to the part of changing the LNB skew, the reason I did it was to see if I can get as low signal as possible and prevent the card from locking into anything while moving, cause this way the signal quality of non relevant frequencies will be too low to lock into and the only frequency that will work will be the one that the motor will stop on. The results are positive, by adjusting the skew I got a signal quality of 50 out of 100 for a specific channel that I wanted to test, after that switching from 19.2E to this specific channel always worked.</p><p></p><p>Now I am not sure whether the tuner is locking into irrelevant frequencies while the dish is moving or it is locking into the right frequency but too early, but I am pretty sure it is a timing issue, it is an issue of how we/TBS tune into a channel.</p><p></p><p>I don't know exactly the logic behind the motor support inside MP, so I got no idea how to work around that. At this point I am not even sure if my theory is correct but it sure does explain lots of issues that I am having.</p><p></p><p>Of course sitting at my roof top and blocking my LNB each time I want to switch a channel is not a solution, neither is purposely lowering the signal quality, as this prevents me from finding channels on other satellites that already got low signal at my region.</p><p></p><p>Regarding the No Signal error, this one is random, and I mean totally random, and it has a 10% - 20% of happening, for some strange reason the dish will either stop half way or will move to the opposite direction. I got no idea or theory as to why it is happening but [USER=82144]@mm1352000[/USER] I can confirm that it is not the GoToX positions that are getting corrupted. Moving to a different sat after the error will result in proper movement and then I can move again to the previous sat and it will work, so this means the GoToX positions are not corrupt but it means that the command itself is either sometimes randomly wrong or it is confusing the motor somehow.</p><p></p><p>So [USER=82144]@mm1352000[/USER] does any of this make any sense to you?</p></blockquote><p></p>
[QUOTE="Kotik, post: 1198389, member: 89825"] So back with info. Situation is as following, there are currently 2 issues and they are not tied with each other: No Signal ----> Always results from a wrong dish movement. No PMT Found ----> This is a tricky one but read my findings and maybe u will understand what is going on. Let me 1st focus on the No PMT Found issue, I spent pretty much half the day at my roof top with my TeamViewer, I did notice that 90% of the time moving from a channel (not all channels but many) that is located on 19.2E to 13.0E will result into a No PMT Found error. But there was a 10% chance that it will succeed, in order to troubleshoot it I decided to do a manual dish movement from the MP DiseqC tab, so I tune a channel on 19.2E from manual control tab, then I stop timeshifting and I go to the DiseqC tab, over there I manually send the dish to 13.0E and then revisit the manual control tab and start timeshifting a channel on 13.0E. It works 90%, note that the 10% failure is the No Signal bug (read on regarding that one). The results of these tests made me thinking, then I remembered that 2 days ago I actually thought that I fixed the issue when I replaced the LNB and for a brief time I was able to switch between 19.2E and 13.0E with a higher success rate (around 50%), I tried to remember what could have changed and why my success rate went again back to 10% from 50%, the reason is that I adjusted my LNB after placing it to get higher signal quality and after that adjustment my success rate dropped again, so how could higher signal quality affect the issue? At that point I immediately got an idea, what if the issue is that MP/TBS is trying to find PMT while the dish is still moving? What if there is a Lock On happening before the dish arrives into its proper location? To test it out I used my hands:) I moved the dish to 19.2E tuned to a channel and then switched to a channel that is located @ 13.0E BUT when the dish started moving I covered the LNB with my palm and waited out the whole movement, when the dish parked I removed my palm and lord and behold, NO error, crystal clear signal with no issues. Sounded too good to be true so I did it a couple more times. 100% success ratio. I then combined this finding with the accidental 50% increased chance of success due to LNB adjustment and it made sense. To make sure I am not hallucinating I tried out my theory without the help of my palm:) I changed the LNB skew in a way that the signal quality is low, yes LOW, my theory at that point was the following: we are sending a command to move the dish but at the same time send the tune command, as a result if during the movement there are other frequencies found the tuner will lock on them and MP will start searching for PMT, but there wont be any cause the dish is still moving. By blocking the LNB with my hand I prevent the tuner from locking into any signal while the dish is still moving, this will also explain why manually moving the dish from the DiseqC tab is working, cause during that move we are not trying to tune to any channel. So back to the part of changing the LNB skew, the reason I did it was to see if I can get as low signal as possible and prevent the card from locking into anything while moving, cause this way the signal quality of non relevant frequencies will be too low to lock into and the only frequency that will work will be the one that the motor will stop on. The results are positive, by adjusting the skew I got a signal quality of 50 out of 100 for a specific channel that I wanted to test, after that switching from 19.2E to this specific channel always worked. Now I am not sure whether the tuner is locking into irrelevant frequencies while the dish is moving or it is locking into the right frequency but too early, but I am pretty sure it is a timing issue, it is an issue of how we/TBS tune into a channel. I don't know exactly the logic behind the motor support inside MP, so I got no idea how to work around that. At this point I am not even sure if my theory is correct but it sure does explain lots of issues that I am having. Of course sitting at my roof top and blocking my LNB each time I want to switch a channel is not a solution, neither is purposely lowering the signal quality, as this prevents me from finding channels on other satellites that already got low signal at my region. Regarding the No Signal error, this one is random, and I mean totally random, and it has a 10% - 20% of happening, for some strange reason the dish will either stop half way or will move to the opposite direction. I got no idea or theory as to why it is happening but [USER=82144]@mm1352000[/USER] I can confirm that it is not the GoToX positions that are getting corrupted. Moving to a different sat after the error will result in proper movement and then I can move again to the previous sat and it will work, so this means the GoToX positions are not corrupt but it means that the command itself is either sometimes randomly wrong or it is confusing the motor somehow. So [USER=82144]@mm1352000[/USER] does any of this make any sense to you? [/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