NARA 5SDH-2
NARA 5SDH-2
See the ENERGY CALCULATION FORMULAE section of the manual page for more information about the energy calculations.
See the SPARK COUNTER OPERATION section of the manual page for more information about the spark counter function.
See the SPARK INTERLOCK OPERATION section of the manual page for more information about the spark interlock function.
If this is not specified it defaults to "MNGRconf" in the current working directory (i.e. the directory where the program was started).
If this argument is not specified it generally defaults to the program name.
Parameters needed by this program can be combined with parameters belonging to other programs. The "program name" field in the configuration file differentiates the entries.
ENERGYmngr uses "ENERGYmngr" as the program name when searching the file.
If this parameter is missing the program defaults to 0 (source 1).
The "old way" was for this parameter to be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
Now this parameter may be set the "old way" or the "new way".
The "new way" is for this parameter to be owned by any task and be set for direct update
The program works either way but will print a warning in the log file if the parameter is set the "old way".
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
This parameter is used by the calculations in tandem mode. The relationship between this parameter and comm3 is checked in SSAMS mode but it is not used by the calculations.
See the ENERGY CALCULATION FORMULAE section of the manual page for more information.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
This parameter is used by the calculations in tandem mode. The relationship between this parameter and comm2 is checked in SSAMS mode but it is not used by the calculations.
See the ENERGY CALCULATION FORMULAE section of the manual page for more information.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
This parameter should be positive and scaled in KeV.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
ENERGYmngr internally scales this parameter to MeV.
ENERGYmngr internally scales this parameter to MeV.
ENERGYmngr internally scales this parameter to MeV.
ENERGYmngr internally scales this parameter to MeV.
If this parameter is missing no calculation will be performed.
If this parameter is missing no calculation will be performed.
If this parameter is missing no calculation will be performed.
If it is missing the program defaults to tandem calculations.
0 = tandem calculations
1 = single ended calculations
2 = SSAMS calculations
See the ENERGY CALCULATION FORMULAE section of the manual page for more information.
If present and value is 1 then energy calculations are in KeV.
This parameter should have the same range and scaling as the GVM parameter (CFG1 read5).
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
0.0 = disable spark counting
1.0 = enable spark counting
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
0.0 = nop
1.0 = reset the spark counter system
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update by users and unconditional for the owner.
1.0 = ok (below limit)
0.0 = over spark limit
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for direct update for the owner.
Note that "traditional" behavior of this parameter may be changed by using the const1 0 parameter listed below.
0.0 = spark in progress
1.0 = ok
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for direct update for the owner.
If the Label and RefName fields are NULL the value is taken from the Preset field. If the Label and RefName fields are non NULL and the name of a valid database parameter the value is taken from the db.
If the entry is missing from the config file it defaults to 0.1.
If it is missing the program defaults to the behavior described above.
When the parameter is present and the Preset field is set to 1.0 the spark counter limit status output is reversed to produce "traditional" behavior.
0 = behave normally (new behavior)
0.0 = exceeded spark count limit
1.0 = ok
1 = reverse polarity (traditional behavior)
1.0 = exceeded spark count limit
0.0 = ok
Many times this is the TRV control for the TPS (or equivalent).
0.0 = spark in progress
1.0 = ok
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for direct update for the owner.
If the Label and RefName fields are NULL the value is taken from the Preset field. If the Label and RefName fields are non NULL and the name of a valid database parameter the value is taken from the db. If the entry is missing the value defaults to 50%.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update for the users and unconditional update for the owner.
If the Label and RefName fields are NULL the value is taken from the Preset field. If the Label and RefName fields are non NULL and the name of a valid database parameter the value is taken from the db. If the entry is missing the value defaults to 80%.
The parameter should be owned by whatever task ENERGYmngr registers as and the permissions should be set for indirect update for the users and unconditional update for the owner.
When new values for Omass or Imass are entered the new value is tested to make sure the relationship Omass <= Imass is maintained.
No relationship testing of Omass or Imass is performed since these values are not used by the calculations.
When new values for Omass or Imass are entered the new value is tested to make sure the relationship Omass <= Imass is maintained.
Omass or Imass are not used by the energy calculations. However, these parameters may be used in other places within AccelNET such as the bending magnet calculations. ENERGYmngr checks the relationship as a convenience to make sure other parts of the system behave sensibly.
When the GVM (CFG1 read5) rises above the threshold value (comm1) the counter is armed.
If the GVM falls below the threshold minus a window value (int0) the spark counter is incremented and the counter is disarmed until the GVM again rises above the threshold value.
For example:
Starting values are: GVM = 1.9 MV, threshold = 2.0 MV, window = 0.5 MV
The GVM rises to 2.1 MV, the counter is "armed".
The accelerator sparks and the GVM falls to 1.4 MV, the counter is "disarmed" and count is incremented.
The cycle begins again when the GVM rises above 2.0 MV.
Spark counting is enabled by the setting of the enable parameter (comm3). The counter may be reset by the reset parameter (comm4).
The number of sparks in kept in a counter (resp1). If the number of sparks exceeds the spark limit (comm2), the spark limit parameter (resp2) is set.
The motivation for inventing this is DMANserv_v2(8) . We need to have a spark-in-progress signal which always active because it can be disabled from within the DMAN system.
The group1 read5 parameter (GVM) is used for the terminal voltage.
The behavior of the resp1 parameter is very similiar to the spark counter’s resp3 parameter.
The difference is that spark counter uses a threshold control (g2 comm1) and a window for it’s operation while the spark interlock uses the TRV and calculates it’s spark interlock threshold and rearming threshold as a percentage of the current TRV setting.
The spark threshold and the rearming threshold percentages may be changed using the int0 and int1 parameters.
Note that the program enforces limits which prevent the thresholds from being less than 5 percent of each other.
#
# Energy Manager
#
# group 1
#
ENERGYmngr|g1|comm1 |0|SETUP |SrcSel |
ENERGYmngr|g1|comm2 |0|SETUP |Ispecies|
ENERGYmngr|g1|comm3 |0|SETUP |Ospecies|
ENERGYmngr|g1|comm5 |0|SETUP |ChgState|
ENERGYmngr|g1|comm6 |0|SETUP |Elost |
#
ENERGYmngr|g1|read1 |0|INJ S1-1|TotInjV |
ENERGYmngr|g1|read2 |0|INJ S2-1|TotInjV |
ENERGYmngr|g1|read5 |0|TPS TK-1|GvmVR |
#
ENERGYmngr|g1|resp1 |0|SETUP |TotInjE |
ENERGYmngr|g1|resp2 |0|SETUP |TotMachE|
ENERGYmngr|g1|resp3 |0|SETUP |TotPartE|
#
# group 2
#
ENERGYmngr|g2|comm1 |0|SETUP |SparkThr|
ENERGYmngr|g2|comm2 |0|SETUP |SparkLim|
ENERGYmngr|g2|comm3 |0|SETUP |EnableSC|
ENERGYmngr|g2|comm4 |0|SETUP |ResetSC |
#
ENERGYmngr|g2|resp1 |0|SETUP |SparkCnt|
ENERGYmngr|g2|resp2 |0|SETUP |LimitSR |
#
ENERGYmngr|g2|int0 |0|NULL |NULL |0.5
Some of the parameters in group2 and group3 are listed as required. However, they are only "required" if you want to use the spark counter and spark interlock functions. At this time messages are printed in the log file if they are missing. If you aren’t using the spark counter etc. then ignore the messages.
