Reply to thread

Message: <blockquote data-quote="Channel Hopper" data-source="post: 955960" data-attributes="member: 175144">From your last two posts I think that it might be a mismatch of the receiver data to the motor rather than a fault. Many combinations of the two will have issues on certain satellite positions since the coding was AFAIK not written in the Eutelsat specification for DiSEqC, though there was mention of some 60 satellite position limit in many slave boards that found their way into motors.It might be worth creating your own manual table of positions to orbital slots.</blockquote>