-
d-rothe authored
* concept for error reporting to set_error - destination is DOOCS EqFct::set_error(code, message) - StatusMonitor variables and/or Device status variables as input - configuration per location via xml - only single data source for set_error - consistent updates of error code and error message, to remove duplicate log lines this depends on changes in ApplicationCore/DeviceModule! * remove deprecated use of boost/test/test_case_template.hpp * make configuration of status message input unneccesary it will be found from the naming convention * some refactoring which was neccesary because Status definitions moved to ControlSystemAdapter * add docu for set_error * add basic test for set_error tag Co-authored-by:
Dietrich Rothe <dietrich.rothe@desy.de>
d-rothe authored* concept for error reporting to set_error - destination is DOOCS EqFct::set_error(code, message) - StatusMonitor variables and/or Device status variables as input - configuration per location via xml - only single data source for set_error - consistent updates of error code and error message, to remove duplicate log lines this depends on changes in ApplicationCore/DeviceModule! * remove deprecated use of boost/test/test_case_template.hpp * make configuration of status message input unneccesary it will be found from the naming convention * some refactoring which was neccesary because Status definitions moved to ControlSystemAdapter * add docu for set_error * add basic test for set_error tag Co-authored-by:
Dietrich Rothe <dietrich.rothe@desy.de>