Re: limit switch fields in the motor record

["Peterson, Kevin M. via Tech-talk" <tech-talk@aps.anl.gov>]

The limit status is updated regardless of the direction starting in 
R6-11 of the motor module:

   https://github.com/epics-modules/motor/releases/tag/R6-11

The pull request that changed this limit behavior was merged on June 26, 
2018:

   https://github.com/epics-modules/motor/pull/36

Kevin

On 4/9/19 12:59 PM, Mark Rivers via Tech-talk wrote:
> I agree that this is a bad behavior and I have complained about it for years.  I think it's origin was in an old motor controller that could only tell you that it was at a limit, but not which one.  So it needed to use the direction to figure that out.
> 
> I would like to be able to unplug my motor cable with the limit connections and immediately see both limit lights on the OPI screen.
> 
> Mark
> 
> 
> -----Original Message-----
> From:tech-talk-bounces@aps.anl.gov  <tech-talk-bounces@aps.anl.gov>  On Behalf Of Davis, Mark via Tech-talk
> Sent: Tuesday, April 9, 2019 12:57 PM
> To:tech-talk@aps.anl.gov
> Subject: limit switch fields in the motor record
> 
> Is there a reason that the xLS/RxLS limit switch fields in the motor record only work when the TDIR field's value indicates that the motor is or was last moving in the direction that would normally trigger the corresponding limit switch?
> 
> This means that that only way to know if a limit switch has REALLY been triggered is to monitor the bits in the MSTA field.
> 
> I am using version 6-9 of the motor record if that makes any difference.
> 
> Mark Davis, NSCL/FRIB
> Control Systems Software Engineer
> davism50@msu.edu
>