Nothing assures that the step per unit is set before the velocity.
So far it was just a happy accident that this happened.
Testing with sardana py3 on tango 9 we saw that in some occasions, when the Pool starts, the memorized values of step_per_unit and velocity and set in the reverse order.
In these cases, icepap controller was assuming step_per_unit = 1 and setting the corresponding velocity gave an error on startup. As a consequence, some motors were left with wrong velocites
Nothing assures that the step per unit is set before the velocity. So far it was just a happy accident that this happened.
Testing with sardana py3 on tango 9 we saw that in some occasions, when the Pool starts, the memorized values of step_per_unit and velocity and set in the reverse order. In these cases, icepap controller was assuming step_per_unit = 1 and setting the corresponding velocity gave an error on startup. As a consequence, some motors were left with wrong velocites
This PR tries to fix this