Finished up documentation
This commit is contained in:
@@ -152,7 +152,12 @@ asynStatus detectorTowerController::writeInt32(asynUser *pasynUser,
|
||||
|
||||
/*
|
||||
Due to a bug which is currently not understood, the reset has to be handled
|
||||
here rather than in sinqController.
|
||||
here rather than using the default implementation in sinqController. Piping
|
||||
the motor reset request to sinqController causes segfaults. It might be due
|
||||
to the fact that the default `reset` implementation of sinqAxis locks the
|
||||
controller in order to perform some fast polls and that for some reason this
|
||||
behaviour cannot be overwritten even by providing custom `reset` methods for
|
||||
all three axes.
|
||||
*/
|
||||
if (pasynUser->reason == motorReset_) {
|
||||
detectorTowerAngleAxis *aAxis = getDetectorTowerAngleAxis(pasynUser);
|
||||
|
||||
Reference in New Issue
Block a user