Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 678636" data-attributes="member: 82144">Hi again MaxTThis problem is strange and frustrating! I'm sorry the last build didn't fix it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />The test build that you just tried should have been continually checking for signal lock while the motor was moving. Since the tuner didn't lock, we have proved that the solution is not simply a matter of waiting for the motor to stop moving. It is something else.Let us be very clear: my understanding is that the problem only occurs on change of satellite (when the motor has to move). You can successfully tune to any channel after TV Server starts. You can also successfully tune to other channels on the same satellite.Perhaps the switch command needs to be resent after the motor has stopped? If this is the case then we have a problem because we can't tell when the motor has stopped moving!So you want to do nothing until the motor timeout has expired? Okay then. I'll post two more test builds:1. First, a version that does what you want - it will do nothing until the motor timeout has expired. At that point I will resend the DiSEqC command and move on to check for lock.2. A slight modification to the previous version to record the tuner statistics (locked, present, quality, strength) while TV Server is doing &quot;LockedInOnSignal waiting...&quot;.Two questions for you:1. Are you able to check whether the motor is actually moving to the correct position when the tuner fails to lock?2. When you perform the attempt to tune after lock failure, does the motor move at all?</blockquote>

[QUOTE="mm1352000, post: 678636, member: 82144"] Hi again MaxT This problem is strange and frustrating! I'm sorry the last build didn't fix it. :ooops: The test build that you just tried should have been continually checking for signal lock while the motor was moving. Since the tuner didn't lock, we have proved that the solution is not simply a matter of waiting for the motor to stop moving. It is something else. Let us be very clear: my understanding is that the problem only occurs on change of satellite (when the motor has to move). You can successfully tune to any channel after TV Server starts. You can also successfully tune to other channels on the same satellite. Perhaps the switch command needs to be resent after the motor has stopped? If this is the case then we have a problem because we can't tell when the motor has stopped moving! So you want to do [B]nothing[/B] until the motor timeout has expired? Okay then. I'll post two more test builds: 1. First, a version that does what you want - it will do nothing until the motor timeout has expired. At that point I will resend the DiSEqC command and move on to check for lock. 2. A slight modification to the previous version to record the tuner statistics (locked, present, quality, strength) while TV Server is doing "LockedInOnSignal waiting...". Two questions for you: 1. Are you able to check whether the motor is actually moving to the correct position when the tuner fails to lock? 2. When you perform the attempt to tune after lock failure, does the motor move at all? [/QUOTE]

Verification