Project

General

Profile

Bug #1960

Motorized setup not working as intended

Added by Gary Brown almost 11 years ago. Updated about 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2014-02-02
Due date:
% Done:

0%

Estimated time:
Found in version:
Master
Affected Versions:

Description

when i setup the latest version with my motorized dish tvheadend only seems to either fail on the finding of the mux or it may sometimes tune into a real mux and list them channels but when it tunes to the next mux it will show the same channels, the system goes between the two each time.

this time I added 2 mux's off of 2 satellites (28.2e and 1w) it appeared to search the 28.2e satellite but failed on finding the signal but when it went to change the satellite location to 1w it then found channels for the first mux but these channels seemed to be from the 28.2e satellite. the other mux found nothing.

Files

tvh2.log (13.7 MB) tvh2.log a log with all traces except tsdemux Gary Brown, 2014-02-02 04:24

History

#1

Updated by Adam Sutton almost 11 years ago

  • Status changed from New to Accepted
#2

Updated by Gary Brown over 10 years ago

Ii've been looking into the rotor issue and I'm 99% certain I know the problem. I know I'm looking at the right code but cannot seem to find any indication of grace time. if it's in there can you point to where the code pauses to allow the dish to move and is trying to tune after moving less than 0.1degree. this can slowly put the rotor out overtime

in src/input/mpegts/linuxdvb/linuxdvb_satconf.c lines 872 -930

#3

Updated by Gary Brown over 10 years ago

My pull request fixes the only error in the rotor code so this can be closed because of the new issue https://tvheadend.org/issues/2098

#4

Updated by Andy Brown about 10 years ago

  • Status changed from Accepted to Resolved

Marked resolved.

#5

Updated by Jaroslav Kysela about 10 years ago

  • Status changed from Resolved to Fixed

Also available in: Atom PDF