To remove a bad actuator requires an identificaiton of the bad actuator, modify the bad_actuators.list and execute and IDL script.
  • Check in the AdSec Mirror GUI and the log files to identify which actuator is bad behaving.
  • Actuator identified.
    • example actuator 567 reading a bad position.
  • goto the directory on the adsec machine.
    • cd $ADOPT_ROOT/conf/adsec/current/TS(3/4/5)/
  • edit the file: bad_actuators.list with the information of the actuiator and from where it has to be removed.
    • Line descriptios.
      • actuator number: - do not apply current to actuator (0 = no, 1 = yes): ignore actuator position (0 = no, 1 = yes): do not include actuator in integrated current control loop (0 = no, 1 = yes): Date this actuator was included in format YYYYMMDD: - Initials of who added this actuator. The given initials are compared to a list in routine adsec_make_bad_act_files.pro: - Comment about why the actuator was removed, etc
    • example 567 remove from positions.
      • scroll the file down in the file to: # No Position
      • add a new line with:
      • 567 : 0 : 1 : 0 : 20220224 : XZ GB JC : reading wrong position
  • start idl terminal
  • Execute in IDL terminal> adsec_make_bad_act_files

Bad actuator list file.

The bad_actuators.list file has a header informaiton to give the instruction, see below:

# Usage:
#
# IDL> adsec_make_bad_act_files, list, retval
#
# Inputs:
#
# list = Name of the configuration file to read. If this is an empty string the the default
# bad actuator list is read ($ADOPT_ROOT/conf/adsec/current/TS(3/4/5)/bad_actuators.list
#
# Outputs:
#
# retval = return value (0 = success, 1 = failure)
#
# Note, neither the input nor the output variables are required:
#
# IDL> adsec_make_bad_act_files
#
# Each line REQUIRES seven fields to have data:
#
# 1 - actuator number
# 2 - do not apply current to actuator (0 = no, 1 = yes)
# 3 - ignore actuator position (0 = no, 1 = yes)
# 4 - do not include actuator in integrated current control loop (0 = no, 1 = yes)
# 5 - Date this actuator was included in format YYYYMMDD
# 6 - Initials of who added this actuator. The given initials are compared to a list in routine adsec_make_bad_act_files.pro
# 7 - Comment about why the actuator was removed, etc
#
# The routine checks that all fields have data. If not, the routine writes a descriptive message and then exits.
# No files are written.
#
# As each line is read, the values of each field are checked if they are valid (types, ranges, existance). If there
# is a problem, the routine writes a descriptive message and then exits. No files are written.
#
# If the routine is successful, two files are written:
#
# ($ADOPT_ROOT/conf/adsec/current/TS(3/4/5)/elec.txt
# ($ADOPT_ROOT/conf/adsec/current/processConf/fastdiagn/fastdiagn.param
#
# Before these files are written the original files (elec.txt and fastdiagn.param, plus the bad_actuators.list)
# are written to a ./backup directory with the suffix of the current date and time.

-- XianyuZhang - 25 Jan 2024
Topic revision: r1 - 25 Jan 2024, XianyuZhang
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback