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
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
IS there an Option to retune the tuned Channel on Errors?
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: 678583" data-attributes="member: 82144"><p>Okay, so are you saying that you think this is what happens when you shift to a new satellite:</p><p></p><p>1. Send switch command. Switch changes.</p><p>2. Send motor commands. Motor starts to move.</p><p>3. Check for signal lock. Motor still moving.</p><p>4. Lock fails.</p><p>5. Motor finishes moving.</p><p>6. Tune to next channel on the same satellite.</p><p>7. Send switch command. Switch is changes if necessary.</p><p>8. Send motor commands. Motor is already in the right position.</p><p>9. Check for signal lock. Motor is stationary.</p><p>10. Lock succeeds.</p><p></p><p>Ideally you want to wait for the motor to stop moving - a new action between step 2 and 3 - before TV Server checks for signal lock. The problem is that TV Server doesn't support receiving DiSEqC messages, which means it can't tell when the motor has finished moving. Currently TV Server simply instructs the motor to move and then checks for signal lock shortly after that, assuming that the motor is in position...</p><p></p><p>There are a few options:</p><p>1. Have you tried to increase the tune timeout in TV Server Configuration -> General -> Scan (tab)?</p><p>This increases the length of time that TV Server spends in step 3 (above) checking for signal lock. If you could set that to the maximum time that it takes for the motor to move between the two most separate positions then it should solve your problem.</p><p></p><p>2. Add a new timeout similar to the tune timeout. If the motor has to move then the new timeout could be added to the tune timeout to give the motor more time to move when it needs to move. This is better than option 1 because it doesn't affect the normal lock timeout setting.</p><p></p><p>3. Add a field to the motor tab to indicate how fast the motor is at moving (a user defined multiplier like what you suggested). When the motor changes position, TV Server will wait x number of milliseconds per degree that the motor has to move. This could be quite tricky to implement, but certainly possible.</p><p></p><p>Option 1 is okay, but not ideal because it means that signals that can't be locked for other reasons will make the TV Server wait for much longer than necessary.</p><p>Option 2 is better than option 3 because you minimise how long you have to wait for the motor to get to any position. TV Server continually checks for signal while the motor moves. As soon as the motor is in position, the channel will be locked and video can be shown. With option 3, you have to guess how long it takes for the motor to move. You can never be 100% accurate, meaning that you usually wait for longer than necessary (or worse, you don't wait long enough!). Option 3 also assumes that the time it takes to move from one position to another is directly proportional to the distance between the two positions. This is not likely to be true because motors usually take time to start and stop and don't move at constant speed...</p><p></p><p>==> Option 2 is the best in my opinion. It is also much simpler than option 3...</p><p></p><p>Hopefully you understood all of what I said above. I will try to build another test version with the extra setting <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>p.s. At the moment I'm not sure whether the switch command needs to be resent or not. I will leave it out of the next test version to see what happens.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 678583, member: 82144"] Okay, so are you saying that you think this is what happens when you shift to a new satellite: 1. Send switch command. Switch changes. 2. Send motor commands. Motor starts to move. 3. Check for signal lock. Motor still moving. 4. Lock fails. 5. Motor finishes moving. 6. Tune to next channel on the same satellite. 7. Send switch command. Switch is changes if necessary. 8. Send motor commands. Motor is already in the right position. 9. Check for signal lock. Motor is stationary. 10. Lock succeeds. Ideally you want to wait for the motor to stop moving - a new action between step 2 and 3 - before TV Server checks for signal lock. The problem is that TV Server doesn't support receiving DiSEqC messages, which means it can't tell when the motor has finished moving. Currently TV Server simply instructs the motor to move and then checks for signal lock shortly after that, assuming that the motor is in position... There are a few options: 1. Have you tried to increase the tune timeout in TV Server Configuration -> General -> Scan (tab)? This increases the length of time that TV Server spends in step 3 (above) checking for signal lock. If you could set that to the maximum time that it takes for the motor to move between the two most separate positions then it should solve your problem. 2. Add a new timeout similar to the tune timeout. If the motor has to move then the new timeout could be added to the tune timeout to give the motor more time to move when it needs to move. This is better than option 1 because it doesn't affect the normal lock timeout setting. 3. Add a field to the motor tab to indicate how fast the motor is at moving (a user defined multiplier like what you suggested). When the motor changes position, TV Server will wait x number of milliseconds per degree that the motor has to move. This could be quite tricky to implement, but certainly possible. Option 1 is okay, but not ideal because it means that signals that can't be locked for other reasons will make the TV Server wait for much longer than necessary. Option 2 is better than option 3 because you minimise how long you have to wait for the motor to get to any position. TV Server continually checks for signal while the motor moves. As soon as the motor is in position, the channel will be locked and video can be shown. With option 3, you have to guess how long it takes for the motor to move. You can never be 100% accurate, meaning that you usually wait for longer than necessary (or worse, you don't wait long enough!). Option 3 also assumes that the time it takes to move from one position to another is directly proportional to the distance between the two positions. This is not likely to be true because motors usually take time to start and stop and don't move at constant speed... ==> Option 2 is the best in my opinion. It is also much simpler than option 3... Hopefully you understood all of what I said above. I will try to build another test version with the extra setting :D p.s. At the moment I'm not sure whether the switch command needs to be resent or not. I will leave it out of the next test version to see what happens. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
IS there an Option to retune the tuned Channel on Errors?
Contact us
RSS
Top
Bottom