About bostroemc

As an alternative to the workaround described above, I've found that SoftMotion parameter dwBusModuloMask may be used to force rollover of the position command at a value compatible with the internal drive modulo.  This approach will (in typical cases) allow us to retain the drive's absolute position reference  while maximizing the internal position resolution.  For example, setting dwBusModuloMask = 2^18 - 1 = 262143, we may configure the axis as follows: Running the cam described in the original post now yields the following.  Note that the position command value rollover now corresponds with the actual drive position.  I've tested this configuration for 4+ hours and see no problems and no position drift.  Moreover, the position is retained on program restart or power cycle.  Both forward and backward operation has been verified. @eschwellinger:  Am I missing anything?  Was there a specific reason you did not suggest adjusting dwBusModuloMask? Also, following the documentation I've assigned dwBusBandWidth a value of 262144 = 2^18.  What does this parameter do?      ... View more

Thanks, eschwellinger.  It appears that it is not enough to simply switch the position data format to Absolute.  The issue is that in this case the drive's actual position is rolling over at the Maximum travel range value (S-0-0278):         and I still see the physical axis come to rest once the commanded position becomes sufficiently large: I did verify that by setting S-0-0278 to its maximum value, namely 214748.3647 = (2^31 - 1) / 10000, I could force the commanded and actual positions to rollover simultaneously: In this case it looked like I was able to run in "endless" mode without error.  Setting the max. travel range this high has implications on our absolute encoder evaluation - we'll review internally how best to handle this. If you edit your post to include a reference to my comments here, I'll accept yours as the answer.     ... View more