Normal
Hi again mm1352000!Actually I cannot ask or demand anything from you and I am really grateful that you are helping!As to the situation:Indeed in majority of cases the problem occurs on sat change and it rarely occurd with the very first tune (to the same sat) after TV Server start, however with your builds with diseqc command resending I've never experienced it, and of cource I can tune to other channels on the same sat without an issue.As to the switch command and the motor move, I think that ideally this could look like:1 command to move the motor to the position with a fake parameters for the LNB so that high voltage (18V) is provided to the motor (to speed up the move)2 angular delta in sats positions multiplied by the MotorTimeout. This timeout should be user controlled since it depends not only on particular motor but on user's longtitude and for different users the actual turn angle between thу same satellites can differ.3 real LNB switch command sent twice (in any case, irrespectively whether motor moves or not) just as a control shoot with another user controlled Timeout and the TuneTimeout starts running.Since 2 represents quite an issue - to read strings, etc. this can be replaced by a fixed MotorTimeout.I think that for example ProgDVB usues the same logic - by default it uses 1000 ms timeout per turn degree (MotorTimeout), for TwinHan cards resends commands 2 times (adjustable) with 200 ms timeout which is also adjustable.Do you think this if this is logical?Refards,MaxTups, sorry I've seen your post only after posted mine - was speaking over the phone. Will test are write back
Hi again mm1352000!
Actually I cannot ask or demand anything from you and I am really grateful that you are helping!
As to the situation:
Indeed in majority of cases the problem occurs on sat change and it rarely occurd with the very first tune (to the same sat) after TV Server start, however with your builds with diseqc command resending I've never experienced it, and of cource I can tune to other channels on the same sat without an issue.
As to the switch command and the motor move, I think that ideally this could look like:
1 command to move the motor to the position with a fake parameters for the LNB so that high voltage (18V) is provided to the motor (to speed up the move)
2 angular delta in sats positions multiplied by the MotorTimeout. This timeout should be user controlled since it depends not only on particular motor but on user's longtitude and for different users the actual turn angle between thу same satellites can differ.
3 real LNB switch command sent twice (in any case, irrespectively whether motor moves or not) just as a control shoot with another user controlled Timeout and the TuneTimeout starts running.
Since 2 represents quite an issue - to read strings, etc. this can be replaced by a fixed MotorTimeout.
I think that for example ProgDVB usues the same logic - by default it uses 1000 ms timeout per turn degree (MotorTimeout), for TwinHan cards resends commands 2 times (adjustable) with 200 ms timeout which is also adjustable.
Do you think this if this is logical?
Refards,
MaxT
ups, sorry I've seen your post only after posted mine - was speaking over the phone. Will test are write back