the drive should do a relative positioning.
Therefore, there is a input mask for velocity, acc+dec, turns right and left. Because the drive has a gearbox (324:100) all input data should belong to the tool -> means an input speed of 2400 rpm is an engine speed 7776 rpm.
When doing this with ctrlX sometimes it seems to be right, but most of the time it looks like this - see image attached
Is it because the drive (IndraDrive MPB - FW20) is configurated for output values but ctrlX motion app for??? There is no possibility for any gearbox or something.
With the same process(function it worked well with IndraDrive MLD!
-see code for movement (function block) attached as well
-a second image of a strange thing just before doing the command itself. There is some positioning - why? no reason for that!
Solved! Go to Solution.
I do not completely get your problem. Could you send me a private message with your contact data so we can have look to it.
For the positioning done at the beginning, that you do no expect, in the moment you change opmode:
arAxisCtrl_gb[AxisIndex].Admin._OpMode := MODEPOSREL;
a movement command will be create. Also in your step number 10.
Issue is solved now.
Because there was an delay time after power on in parameter S-0-0206 of 180ms (although there is no brake in use and therefore the parameter is not visible), the drive started positioning with that delay time. But the control started without delay so there was a lack between control and current value. This led to a strange behaviour and the drive didn't do what was expected.
To set S-0-0206 to 0ms (no delay time) it is necessary to have set parameter P-0-2206 to 0ms as well otherwise S-0-0206 has a low limit of P-0-2206.
This concerns if using a non-Rexroth servo-engine