NARA 5SDH-2
NARA 5SDH-2
This program controls one PPCI. Normally a copy of this program is run for each PPCI in the system.
This program is part of the NEC AMS dosimetry system.
Argument processing is done using Unix long argument syntax.
The values of all of the parameters listed here (whether or not they were supplied on the command line) are printed on stderr when the program starts.
The environment variable DBMAN_HOST is used if present.
If this argument is not supplied and DBMAN_HOST is not set the default is "localhost".
The environment variable DOSE_HOST is used if present.
If this argument is not supplied and DOSE_HOST is not set the default is "localhost".
The environment variable MBS_HOST is used if present.
If this argument is not supplied and MBS_HOST is not set the default is "localhost".
If this argument is not supplied the default is 0.
If this argument is not supplied the default is "/dev/kbuss".
If this argument is not supplied the default is "./MNGRconf".
This allows the configuration information for several PPCIs to be stored in one file.
If this argument is not supplied the default is "PPCItask".
The argument <n> is optional. If it is not present the verbosity level defaults to 1.
If <n> is used the = must be present.
g1 - integrator channel
1 controls
g2 - integrator channel 2 controls
g3 - current source controls
g4 - master controls
The parameter names are shown below as "<func> <idx>".
Please see libmngr(3mngr) for general information on the format and usage of parameters of this type.
Unless specified otherwise below, the Preset field is not used and may be left blank.
The value is placed in the Label field. The RefName field may be left blank.
Valid values are:
le_cup1
le_cup2
le_cup3
le_cup4
le_cup5
le_cup6
he_cup1
he_cup2
he_cup3
he_cup4
he_cup5
he_cup6
If this parameter is missing a file will not be produced when PPCItask is asked to do so by the DOSE system.
Valid values are:
0.0 - range0
1.0 - range1
2.0 - range2
3.0 - range3
4.0 - range4
5.0 - range5
6.0 - range6
7.0 - range7
8.0 - range8
9.0 - range9
The control key should be set to IDecE.
Permissions and ownership of the parameter do not matter to PPCItask.
This controls a relay in the front end of the integrator which grounds the input or routes it to the integrator front end.
Valid values are:
0.0 - ground
1.0 - input
There are several possible control keys which may be used. However, the usual value is IncN.
Permissions and ownership of the parameter do not matter to PPCItask.
This control is used to null out offset in the integrator front end.
See the section "Analog control configuration" for information on configuring this parameter.
Normally this control is set by PPCItask when a new range is selected. At this time the parameter isn’t write locked so it can be adjusted by the user but it’s probably better not to do this.
Valid values are:
0.0 - nop
1.0 - start
The control key should be set to Mom.
Permissions and ownership of the parameter do not matter to PPCItask.
This is the "raw" deltaV from the integrator. The value comes from the integrator’s pvm register.
See the section "Voltage read configuration" for information on configuring this parameter.
This is the integrator voltage after software correction is applied.
See the section "Voltage read configuration" for information on configuring this parameter.
See the section "Voltage read configuration" for information on configuring this parameter.
See the section "Voltage read configuration" for information on configuring this parameter.
See the section "Voltage read configuration" for information on configuring this parameter.
Valid values are:
0.0 - nop
1.0 - active
The usual control key is RSet although this doesn’t really matter to PPCItask.
Permissions and ownership of the parameter must be such that PPCItask can write to the data point.
NOTE: this parameter is marked "optional" because the program will function without it. It is, however, needed if one expects to use the current source in the intended manner.
This control chooses the current source range.
There are 6 ranges:
0.0 - off
1.0 - +/-100nA
2.0 - +/-1uA
3.0 - +/10uA
4.0 - +/100uA
5.0 - +/1mA
In "norm" mode the value of this parameter is set when the current control (comm1) is changed.
In "raw" mode this control may be directly adjusted.
This control adjusts the output of the current source within one range.
In "norm" mode the value of this parameter is set when the current control (comm1) is changed.
In "raw" mode this control may be directly adjusted.
See the section "Analog control configuration" for information on configuring this parameter.
This control is used to null out offset in the current source.
In "norm" mode the value of this parameter is set when the current control (comm1) is changed.
In "raw" mode this control may be directly adjusted.
See the section "Analog control configuration" for information on configuring this parameter.
This chooses between "norm" operation, i.e. the current control parameter is used to control the current source, and "raw" mode where the range, vernier, and offset controls are used to control the current source.
Valid values are:
0.0 - norm
1.0 - raw
There are several possible control keys which may be used. However, the usual value is IncN.
Permissions and ownership of the parameter do not matter to PPCItask.
Valid values are:
0.0 - off
1.0 - internal
2.0 - external
3.0 - not used
The usual control key is IDecE.
Permissions and ownership of the parameter do not matter to PPCItask.
Valid values are:
0.0 - off
1.0 - adcA
2.0 - adcB
3.0 - aux
The usual control key is IDecE.
Permissions and ownership of the parameter do not matter to PPCItask.
Valid values are:
0.0 - ok
1.0 - +lim
2.0 - -lim
3.0 - not_used
The usual control key is RSet although this doesn’t really matter to PPCItask.
Permissions and ownership of the parameter must be such that PPCItask can write to the data point.
As explained above the master control parameters use g4.
This chooses between operating as two separate integrator channels, i.e. "normal mode" or operation in a mode where the channel one integrator front end and ADC is shared between the FIFO fifo backends, i.e. "dual integrate mode".
Valid values are:
0.0 - norm
1.0 - dual
There are several possible control keys which may be used. However, the usual value is IncN.
Permissions and ownership of the parameter do not matter to PPCItask.
The value is placed in the Label field. The RefName field may be left blank.
Valid values are:
diag1
diag2
diag3
diag4
In this case this means that all access to the parameters uses the Label/Refname for access and no use is made of the "data" interface.
As a consequence of this the DATA record DrvKey is usually set to "VIRT" (hence the name virtual parameter) and the DevKey is set to "NULL".
The PPCI hardware uses 16 bit bipolar DACs for these parameters.
Many times virtual parameters are defined in the AccelNET database with the DATA record DTkey field set to "F" and M and B are set to 1.0 and 0.0 in the DESC record.
In this case it is recommended that these parameters instead be set up as follows:
DATA.DTkey = U
DESC.DataType = Lin
DESC.CrtKey = F4
DESC.CtlKey = RSet
DESC.Size = 16
DESC.Offset = 0
DESC.DRkey = I
DESC.MBconvKey = Y
DESC.MBsetIncKey = Y
DESC.SpanMin = -100.0
DESC.SpanMax = 100.0
DESC.PhyMin = -100.0
DESC.PhyMax = 100.0
This allows the database to quantize the numbers sent to PPCItask such that the physical values fall on the binary steps of the hardware.
The physical range expected by PPCItask for these parameters is -100.0 to 100.0 percent. CrtKey should be set to F4 to provide enough resolution to see all of the binary steps.
In this case most of the usual virtual parameter configuration ideas apply. They may be configured like this;
DATA.DTkey = F
DESC.DataType = Lin
DESC.CrtKey = F4
DESC.CtlKey = RSet
DESC.Size = 32
DESC.Offset = 0
DESC.DRkey = I
DESC.MBconvKey = N
DESC.MBsetIncKey = N
DESC.SpanMin = -10.0
DESC.SpanMax = 10.0
DESC.PhyMin = -10.0
DESC.PhyMax = 10.0
DESC.M = 1.0
DESC.B = 0.0
DESC.IncVal = 0.0 (this isn’t used)
The physical range expected by PPCItask for these parameters is -10.0 to 10.0 volts. Setting CrtKey to F4 provides enough resolution to see all of the binary steps. However, in practice this may be a bit too much resolution due the noise floor of the system.
In this case most of the usual virtual parameter configuration ideas apply. They may be configured like this;
DATA.DTkey = F
DESC.DataType
= Lin
DESC.CrtKey = E4
DESC.CtlKey = RSet
DESC.Size = 32
DESC.Offset = 0
DESC.DRkey = I
DESC.MBconvKey = N
DESC.MBsetIncKey = N
DESC.SpanMin = -1.0
DESC.SpanMax = 1.0
DESC.PhyMin = -1.0
DESC.PhyMax = 1.0
DESC.M = 1.0
DESC.B = 0.0
DESC.IncVal = 0.0 (this isn’t used)
The physical range for these parameters is set to -1.0 to 1.0 amperes.
Setting CrtKey to E4 easily provides enough resolution to see all of the binary steps. However in practice this may be a bit too much resolution due the noise floor of the system.
PPCItask --dbman_host localhost --dose_host localhost \
--mbs_host localhost --dev /dev/kbuss \
-
-
mngr /AccelNET/demo/config/PPCIconf --mngr_pn he_PPCItask
