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: 1198347" data-attributes="member: 82144"><p>In my opinion understanding and solving this part of the problem should be the first priority. If the dish is in the wrong position, other problems will follow.</p><p></p><p>So, on this subject...</p><p>First, I'm a little confused. You say here that the "GoToX position for 13.0E is totally messed...". This seems to contradict your earlier reply when you said that tuning from 1 -> 2/3 could fail, but then <u>immediately</u> tuning 1 -> 5 -> 2/3 would succeed. How could this work if the position is messed up? ...or did you leave out the re-save/re-scan part of this test (between failure with 2/3 and succeeding with 1 -> ...)?</p><p></p><p>The explanations I can think of for a motor moving to the wrong position are:</p><ol> <li data-xf-list-type="ol">TV Server is sending the wrong command due to wrong position stored in the database.</li> <li data-xf-list-type="ol">TV Server is sending the wrong command due to a bug in the DiSEqC handling code.</li> <li data-xf-list-type="ol">The commands received by the motor are corrupted due to insufficient delay between the motor command and the continuous 22 kHz tone.<br /> </li> <li data-xf-list-type="ol">The motor's stored positions are somehow getting corrupted.</li> </ol><p></p><p>We can check #1:</p><ol> <li data-xf-list-type="ol">Delete all channels.</li> <li data-xf-list-type="ol">Use your normal procedure to create a <u>minimal</u> set of test channels - ideally only 2 transponders.</li> <li data-xf-list-type="ol">If possible, confirm that the channels are all working correctly without messing up the stored positions.</li> <li data-xf-list-type="ol">Use the import/export section of TV Server config to export the TV channels.<br /> </li> <li data-xf-list-type="ol">Do whatever you have to do to mess up the stored positions.<br /> </li> <li data-xf-list-type="ol">Use the import/export section of TV Server config to export the TV channels again.</li> <li data-xf-list-type="ol">Zip and attach the 2 exports, and tell me which channel(s)/positions you think are messed up. I can check if there are any differences before and after.</li> </ol><p>#2 is harder to check... but since you didn't have this problem with the SkyStar HD2, I doubt that #2 is involved.</p><p></p><p>There's no way to check #3 without an oscilloscope or equivalent to monitor the commands on the wire. However if this corruption were happening, I'd expect you'd find that moving the motor/dish by switching to low band channels (transponder frequency less than 11700 MHz) would be more reliable. That doesn't seem to be the case in practice. When you try to go from 1 -> 2/3, that is switching both motor position (19.2E = pos 1 --> 13E = pos 2) as well as high band (22 kHz on) to low band (22 kHz off). I'd have expected this to work more reliably. Therefore I also doubt that #3 is involved.</p><p></p><p>Again, I don't think there's any way to test #4. I can only suggest that maybe the motor gets confused with the mixed use of USALs and GoToX commands.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1198347, member: 82144"] In my opinion understanding and solving this part of the problem should be the first priority. If the dish is in the wrong position, other problems will follow. So, on this subject... First, I'm a little confused. You say here that the "GoToX position for 13.0E is totally messed...". This seems to contradict your earlier reply when you said that tuning from 1 -> 2/3 could fail, but then [U]immediately[/U] tuning 1 -> 5 -> 2/3 would succeed. How could this work if the position is messed up? ...or did you leave out the re-save/re-scan part of this test (between failure with 2/3 and succeeding with 1 -> ...)? The explanations I can think of for a motor moving to the wrong position are: [LIST=1] [*]TV Server is sending the wrong command due to wrong position stored in the database. [*]TV Server is sending the wrong command due to a bug in the DiSEqC handling code. [*]The commands received by the motor are corrupted due to insufficient delay between the motor command and the continuous 22 kHz tone. [*]The motor's stored positions are somehow getting corrupted. [/LIST] We can check #1: [LIST=1] [*]Delete all channels. [*]Use your normal procedure to create a [U]minimal[/U] set of test channels - ideally only 2 transponders. [*]If possible, confirm that the channels are all working correctly without messing up the stored positions. [*]Use the import/export section of TV Server config to export the TV channels. [*]Do whatever you have to do to mess up the stored positions. [*]Use the import/export section of TV Server config to export the TV channels again. [*]Zip and attach the 2 exports, and tell me which channel(s)/positions you think are messed up. I can check if there are any differences before and after. [/LIST] #2 is harder to check... but since you didn't have this problem with the SkyStar HD2, I doubt that #2 is involved. There's no way to check #3 without an oscilloscope or equivalent to monitor the commands on the wire. However if this corruption were happening, I'd expect you'd find that moving the motor/dish by switching to low band channels (transponder frequency less than 11700 MHz) would be more reliable. That doesn't seem to be the case in practice. When you try to go from 1 -> 2/3, that is switching both motor position (19.2E = pos 1 --> 13E = pos 2) as well as high band (22 kHz on) to low band (22 kHz off). I'd have expected this to work more reliably. Therefore I also doubt that #3 is involved. Again, I don't think there's any way to test #4. I can only suggest that maybe the motor gets confused with the mixed use of USALs and GoToX commands. [/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