Reply to thread

Message

Hi mm1352000!

Was a bit overloaded today, so tested V3 just recently. Unfortunately it does not work as expected- have to press tune for the second time . Tested twice: with motor\tune timeouts 33\28 (or smth like this) and 30\5. It seems that no retune command is sent and have not seen the delay for the motor movement.

Also just realised - it seems that initially MP sends the tune command to LNB and then to the motor and then tries to lock the signal. But does not the command to the motor overrides the command to LNB and therefore signal just physically cannot be locked or these commands do not overlap?

If so, the way you suggest in general is the only way to make thing working rather than a hack, hack is only item 3 to speed up/unify motor speed and it adds convenience rather than fuctionallity. So it is possible to give it up although it would be nice to have. What do you think?

BTW after this you will be extremely close to USALS implementation which so many dream about

Regards,

MaxT

<blockquote data-quote="MaxT" data-source="post: 678758" data-attributes="member: 100229">Hi mm1352000!Was a bit overloaded today, so tested V3 just recently.&nbsp; Unfortunately it does not work as expected- have to press tune for the second time <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />.&nbsp; Tested twice: with motor\tune timeouts 33\28 (or smth like this) and 30\5.&nbsp; It seems that no retune command is sent and have not seen the delay for the motor movement.Also just realised - it seems that initially MP sends the tune command to LNB and then to the motor and then tries to lock the signal.&nbsp; But does not the command to the motor overrides the command to LNB and therefore signal just physically cannot be locked or these commands do not overlap?If so, the way you suggest in general is the only way to make thing working rather than a hack, hack is only item 3 to speed up/unify motor speed and it adds convenience rather than fuctionallity. So it is possible to give it up although it would be nice to have.&nbsp; What do you think?BTW after this you will be extremely close to USALS implementation which so many dream about <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Regards,MaxT</blockquote>

[QUOTE="MaxT, post: 678758, member: 100229"] Hi mm1352000! Was a bit overloaded today, so tested V3 just recently. Unfortunately it does not work as expected- have to press tune for the second time :(. Tested twice: with motor\tune timeouts 33\28 (or smth like this) and 30\5. It seems that no retune command is sent and have not seen the delay for the motor movement. Also just realised - it seems that initially MP sends the tune command to LNB and then to the motor and then tries to lock the signal. But does not the command to the motor overrides the command to LNB and therefore signal just physically cannot be locked or these commands do not overlap? If so, the way you suggest in general is the only way to make thing working rather than a hack, hack is only item 3 to speed up/unify motor speed and it adds convenience rather than fuctionallity. So it is possible to give it up although it would be nice to have. What do you think? BTW after this you will be extremely close to USALS implementation which so many dream about :) Regards, MaxT [/QUOTE]