software limits are stored in the receiver....the only limits on the motor itself are hardware limits that are set with stop pins....that is why i said if its happening with two different receivers then its not a software problem....its a hardware problem with the motor itself....
I believe that if you read the specs on the motor, you will see Programmable software limits as a feature of the MOTOR, in the spec sheet supplied with the motor. The receiver sets and clears these software limits, but the positions are stored in the motor . Since there is NO position feedback from the motor to the receiver, there is no way the receiver could detect when a limit was made , or not. Only the motor has internal position feedback, pulses from an encoder or hall effect sensor, for example, to tell it how many pulses past it's zero point it is, either east or west. Comparing it's current position with it's stored east-west limits is the test of whether to move further on the arc.
IF the position were stored in the receiver, there would be nothing to prevent the user manually moving the motor via the pushbutton route, but this is not possible, because the MOTOR limit has been reached. Once the receiver sends it's command to the motor to clear the limits, then the motor has no impediment to continuing it's motion.
I use a gbox 3000 to control an actuator. The receiver doesn't know that the Gbox 3000 is not a motor. It only uses the Diseqc 1.2 command set to tell the Gbox what to do, including setting east and west limits, which are stored in the GBOX, not in the receiver. The receiver just sends Diseqc 1.2 commands down the coax. If there is a Diseqc 1.2 device attached, the device responds accordingly. Since there is no feedback to the receiver in the Disqec 1.2 command structure, there is simply no way the software limits could be stored in the receiver.
