Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't set "stop" field true if driver returns RA_PROBLEM true #109

Merged
merged 2 commits into from
Aug 21, 2018

Conversation

kmpeters
Copy link
Member

Partially reverts commit 303a920

Fixes issue #100:

There have been multiple problems caused by the motor record sending a stop when the problem bit is set.

One problem is discussed here:
https://epics.anl.gov/tech-talk/2018/msg01338.php

The commit that introduced the stop is 303a920. I vaguely recall the change being a workaround for less-than-idea behavior of a motor controller, but neither @rsluiter nor I remember which controller that was.

Motor drivers should be modified to send the stop command when the condition that triggers the setting of the problem bit is detected, if needed.

the driver's responsiblity to stop a motor if the condition that results
in the RA_PROBLEM bit being set doesn't result in the motor
automatically stopping.

This partially reverts commit 303a920
@kmpeters kmpeters added this to the R6-11 milestone Aug 21, 2018
@kmpeters kmpeters merged commit f6e9f26 into epics-modules:master Aug 21, 2018
@kmpeters kmpeters deleted the issue100 branch August 21, 2018 17:34
tboegi added a commit to EuropeanSpallationSource/motor that referenced this pull request Oct 2, 2018
Merge f6e9f26: "Merge: 741d429 26771f2"
  Date:   Tue Aug 21 12:34:24 2018 -0500

  Merge pull request epics-modules#109 from kmpeters/issue100

  Don't set "stop" field true if driver returns RA_PROBLEM true

  Partially reverts commit 303a920

  Fixes issue epics-modules#100:
  > There have been multiple problems caused by the motor record
  > sending a stop when the problem bit is set.
  >
  > One problem is discussed here:
  > https://epics.anl.gov/tech-talk/2018/msg01338.php
  >
  > The commit that introduced the stop is 303a920.
  > I vaguely recall the change being a workaround for less-than-idea
  > behavior of a motor controller, but neither @rsluiter nor I remember
  > which controller that was.
  >
  > Motor drivers should be modified to send the stop command when
  > the condition that triggers the setting of the problem bit is detected,
  > if needed.

Remove the bit from .MFLG as well:
	modified:   motorApp/MotorSrc/asynMotorController.cpp
	modified:   motorApp/MotorSrc/asynMotorController.h
	modified:   motorApp/MotorSrc/motor.h
	modified:   motorApp/MotorSrc/motorRecord.cc

Conflicts:
	motorApp/MotorSrc/motorRecord.cc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant