- September 1, 2008
- 21,577
- 8,224
- Home Country
- New Zealand
- Thread starter
- #41
Okay, understood. Why not resend the DiSEqC command after waiting 1-2 seconds for lock?
The new algorithm could be:
1. Try send DiSEqC command normally (before graph is running).
2. Run graph.
3. Before checking for lock, resend the DiSEqC command if the first command failed.
4. If lock is not aquired after x seconds in LockedInOnSignal() then resend the DiSEqC command again.
Thoughts?
[Edit: By the way, the reason I asked about the motor is because of this issue...]
The new algorithm could be:
1. Try send DiSEqC command normally (before graph is running).
2. Run graph.
3. Before checking for lock, resend the DiSEqC command if the first command failed.
4. If lock is not aquired after x seconds in LockedInOnSignal() then resend the DiSEqC command again.
Thoughts?
[Edit: By the way, the reason I asked about the motor is because of this issue...]