Hello, it is a known problem, which should be solved with the Patch 2 (2.6.2). Hint: when you multiply the velocity of the first and the last step in the DataLayer with the factor of 360, then it works also. (After that modification, you must also validate it!)
... View more
Hello, the delay is the result of the following reasons (In the CML-System there was a delay of 4 cycles): + Fineinterpolation in the drive according to Parameter P-0-0187 (default values => 2 cycles) + Transmission of command value and receiving of actual value (1 + 1 cycle) + actual values are transfered to axisprofile/distribution after Motion (1 cycle) + command values are not directly transfered to the drive (1 cycle) This is independent of the operation mode (also in position mode and so on). To be synchron this must be compensated.
... View more
The error message signals that floating point parameter is not correct. So there are different possibilites for it. Above I mentioned some reasons, but there could be more, e.g. division through zero. So in my opionion you should check the real inputs of the function block in the error case. One input is in my opinion not correct. There exist also a open function block with which you can check the values before you assign them to the function block.
... View more
According to the help you have an invalid floating point parameter. So in my opinion you have to check the parameters of the fucntion block. Do you e.g. use some pointer and the pointer is not initialized? Do you work with OnlineChanges, that the storage is overwritten?
... View more