Incorrect acceleration calculation for controllers that don't support VBAS

[kmpeters]

Problem

If a motor controller doesn't support setting a base velocity and the associated motor record is configured to have a non-zero VBAS, the motor record will calculate an acceleration that results in a shorter acceleration period than the one specified by ACCL.

Proposed solution

• Add a bit to the MSTA field to allow drivers to tell the motor record if they support setting a base velocity (0=base velocity is supported, for backwards compatibility).
• Set this new bit to 1 in every driver that doesn't support setting a base velocity.

Previous discussion

#75

[tboegi]

A first attempt is here:
#80

[kmpeters]

Likely to be fixed by #81

[kmpeters]

#81 was closed, so this will still be an issue.

An example of how drivers can workaround the problem by correcting the acceleration passed by the motor record to give the desired acceleration time (ACCL) can be found here:

motor/motorApp/AMCISrc/ANF2Driver.cpp

Line 632 in 3683d3f

double ANF2Axis::correctAccel(double minVelocity, double maxVelocity, double acceleration)

[tboegi]

#81 was closed, so this will still be an issue.
It was closed because
a) Adding bits to MSTA is not a good way to go
b) The problem is that the driver may want to "push" VBAS from the driver into the record,
and this is not at all addressed by the patch.

A possible solution how to push values from driver (in this case the softlimits,
sometimes named "read only soft limits) can be seen here:
https://github.com/EuropeanSpallationSource/motor/blob/ess-6.9.x/motorApp/MotorSrc/motorRecord.cc#L1525