Reply to thread

Message

<blockquote data-quote="jeallen01" data-source="post: 1093571" data-attributes="member: 176704">[USER=332642]@a33[/USER]IIIRC, a year or two ago, I mentioned here that one of my Alsat motors suffered the same issue on several occasions, i.e. it would drive West OK, but not East past 28E - I eventually realised that this only happened after I had been steering it with the Free Sat V7S but then swopped to another receiver (usually the TM5402). Thus I haven't used the V7S since then!NB: the problem didn't happen with an Openbpx V8, nor with either of the SX88's, or when a motor was driven by the SX and then by the TM, or vice-versa.In both instances, trying&nbsp; a remote motor reset from the Rx didn't work, so I had to use almost the same on-the-motor reset method as greencajun - although, per the Alsat instructions, I had to disconnect the feed from the Rx just before doing that, and then reconnect it afterwards.Therefore I suspect the issue could be more common than you might think - and that the cause could well be the Rx sending corrupted DiSEqC signals to the motor, and that some receivers are more prone to causing it than others.</blockquote>

[QUOTE="jeallen01, post: 1093571, member: 176704"] [USER=332642]@a33[/USER] IIIRC, a year or two ago, I mentioned here that one of my Alsat motors suffered the same issue on several occasions, i.e. it would drive West OK, but not East past 28E - I eventually realised that this only happened after I had been steering it with the Free Sat V7S but then swopped to another receiver (usually the TM5402). Thus I haven't used the V7S since then! [I]NB: the problem didn't happen with an Openbpx V8, nor with either of the SX88's, or when a motor was driven by the SX and then by the TM, or vice-versa.[/I] In both instances, trying a remote motor reset from the Rx didn't work, so I had to use almost the same on-the-motor reset method as greencajun - although, per the Alsat instructions, I had to disconnect the feed from the Rx just before doing that, and then reconnect it afterwards. Therefore I suspect the issue could be more common than you might think - and that the cause could well be the Rx sending corrupted DiSEqC signals to the motor, and that some receivers are more prone to causing it than others. [/QUOTE]

Verification