Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1198755" data-attributes="member: 60104">Hi <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> we has work into solution that works but for now only for satellite in the same range EAST or WEST but still works in your case for ex.The workaround will be to create an xml files that read sat value (position stored in motor and position of satellite) this way MP code will wait per degree (like 500ms for ex).This means, that a difference between 19.2 to 4.9 will give us a delta value of 14.3 degrees x 500ms = a waiting time of 7150 ms and the tune will start after that <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" /></blockquote>

[QUOTE="Sebastiii, post: 1198755, member: 60104"] Hi :) we has work into solution that works but for now only for satellite in the same range EAST or WEST but still works in your case for ex. The workaround will be to create an xml files that read sat value (position stored in motor and position of satellite) this way MP code will wait per degree (like 500ms for ex). This means, that a difference between 19.2 to 4.9 will give us a delta value of 14.3 degrees x 500ms = a waiting time of 7150 ms and the tune will start after that :P [/QUOTE]

Verification