diff --git a/modules/database/src/std/ComponentReference.pod b/modules/database/src/std/ComponentReference.pod index c43394d50..029b19980 100644 --- a/modules/database/src/std/ComponentReference.pod +++ b/modules/database/src/std/ComponentReference.pod @@ -14,9 +14,9 @@ documentation is now being published. =over -=item * L +=item * L -=item * L +=item * L =back diff --git a/modules/database/src/std/rec/aaoRecord.dbd.pod b/modules/database/src/std/rec/aaoRecord.dbd.pod index cfb70af2b..cbec0c9ba 100644 --- a/modules/database/src/std/rec/aaoRecord.dbd.pod +++ b/modules/database/src/std/rec/aaoRecord.dbd.pod @@ -45,7 +45,7 @@ its output. It can be a hardware address, a channel access or database link, or a constant. Only in records that use soft device support can the OUT field be a channel access link, a database link, or a constant. Otherwise, the OUT field must be a hardware address. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses and database links. =head4 Fields related to array writing diff --git a/modules/database/src/std/rec/aiRecord.dbd.pod b/modules/database/src/std/rec/aiRecord.dbd.pod index 7b051725b..2bedf9058 100644 --- a/modules/database/src/std/rec/aiRecord.dbd.pod +++ b/modules/database/src/std/rec/aiRecord.dbd.pod @@ -46,7 +46,7 @@ input data should come from. The format for the INP field value depends on the device support layer that is selected by the DTYP field. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for a description of the various hardware address formats supported. =head3 Units Conversion @@ -212,7 +212,7 @@ positive number of seconds will delay the record going into or out of a minor alarm severity or from minor to major severity until the input signal has been in the alarm range for that number of seconds. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/aoRecord.dbd.pod b/modules/database/src/std/rec/aoRecord.dbd.pod index 6d596644f..2b838e092 100644 --- a/modules/database/src/std/rec/aoRecord.dbd.pod +++ b/modules/database/src/std/rec/aoRecord.dbd.pod @@ -162,7 +162,7 @@ OUT field. For analog outputs that write their values to devices, the OUT field must specify the address of the I/O card. In addition, the DTYP field must contain the name of the device support module. Be aware that the address format differs according to the I/O bus used. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses. For soft records the output link can be a database link, a channel diff --git a/modules/database/src/std/rec/biRecord.dbd.pod b/modules/database/src/std/rec/biRecord.dbd.pod index 4ef5be036..d2c4672a8 100644 --- a/modules/database/src/std/rec/biRecord.dbd.pod +++ b/modules/database/src/std/rec/biRecord.dbd.pod @@ -47,13 +47,13 @@ field contains the address from where device support retrieves the value. If the binary input record gets its value from hardware, the address of the card must be entered in the INP field, and the name of the device support module must be entered in the DTYP field. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of the hardware address. For records that specify C or C device support routines, the INP field can be a channel or a database link, or a constant. If a constant, VAL can be changed directly by dbPuts. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of database and channel access addresses. Also, see L in this chapter for information on soft device support. @@ -107,7 +107,7 @@ C. The ZSV field holds the severity for the zero state; OSV, for the one state. COSV causes an alarm whenever the state changes between 0 and 1 and the severity is configured as MINOR or MAJOR. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/boRecord.dbd.pod b/modules/database/src/std/rec/boRecord.dbd.pod index 6bc4e9892..80d0ab609 100644 --- a/modules/database/src/std/rec/boRecord.dbd.pod +++ b/modules/database/src/std/rec/boRecord.dbd.pod @@ -45,7 +45,7 @@ continuous control, a database link to a control algorithm record should be entered in the DOL field. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on hardware addresses and links. =fields DOL, OMSL @@ -105,13 +105,13 @@ It must specify the address of an I/O card if the record sends its output to hardware, and the DTYP field must contain the corresponding device support module. Be aware that the address format differs according to the I/O bus used. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses. Otherwise, if the record is configured to use the soft device support modules, then it can be either a database link, a channel access link, or a constant. Be aware that nothing will be written when OUT is a constant. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of the database and channel access addresses. Also, see L in this chapter for more on output to other records. diff --git a/modules/database/src/std/rec/calcRecord.dbd.pod b/modules/database/src/std/rec/calcRecord.dbd.pod index 798b06bb5..c8758ad53 100644 --- a/modules/database/src/std/rec/calcRecord.dbd.pod +++ b/modules/database/src/std/rec/calcRecord.dbd.pod @@ -42,7 +42,7 @@ the value they are configured with and can be changed via C. They cannot be hardware addresses. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on how to specify database links. =fields INPA - INPL @@ -522,7 +522,7 @@ reporting of limit alarms until the signal has been within the alarm range for that number of seconds (the default AFTC value of zero retains the previous behavior). -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/calcoutRecord.dbd.pod b/modules/database/src/std/rec/calcoutRecord.dbd.pod index f61d13342..994df0f56 100644 --- a/modules/database/src/std/rec/calcoutRecord.dbd.pod +++ b/modules/database/src/std/rec/calcoutRecord.dbd.pod @@ -656,7 +656,7 @@ conditions. The HYST field defines an alarm deadband for each limit. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/compressRecord.dbd.pod b/modules/database/src/std/rec/compressRecord.dbd.pod index 20c52f496..aa526f89c 100644 --- a/modules/database/src/std/rec/compressRecord.dbd.pod +++ b/modules/database/src/std/rec/compressRecord.dbd.pod @@ -88,7 +88,7 @@ As stated above, the ALG field specifies which algorithm to be performed on the The INP should be a database or channel access link. Though INP can be a constant, the data compression algorithms are supported only when INP is a database link. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on specifying links. diff --git a/modules/database/src/std/rec/dfanoutRecord.dbd.pod b/modules/database/src/std/rec/dfanoutRecord.dbd.pod index 4993accaa..074296450 100644 --- a/modules/database/src/std/rec/dfanoutRecord.dbd.pod +++ b/modules/database/src/std/rec/dfanoutRecord.dbd.pod @@ -60,7 +60,7 @@ undergoes no conversions before it is sent out to the output links. The OUTA-OUTH fields specify where VAL is to be sent. Each field that is to forward data must specify an address to another record. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on specifying links. The SELL, SELM, and SELN fields specify which output links are to be @@ -135,7 +135,7 @@ in the corresponding field (HHSV, LLSV, HSV, LSV) and can be either NO_ALARM, MINOR, or MAJOR. In the hysteresis field (HYST) can be entered a number which serves as the deadband on the limit alarms. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/eventRecord.dbd.pod b/modules/database/src/std/rec/eventRecord.dbd.pod index 131eb7b89..e7a17c499 100644 --- a/modules/database/src/std/rec/eventRecord.dbd.pod +++ b/modules/database/src/std/rec/eventRecord.dbd.pod @@ -92,7 +92,7 @@ support module. The address format differs according to the card type used. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses and specifying links. For soft records, the INP field can be a constant, a database link, or a channel diff --git a/modules/database/src/std/rec/longoutRecord.dbd.pod b/modules/database/src/std/rec/longoutRecord.dbd.pod index 9fead68d4..03e33ed76 100644 --- a/modules/database/src/std/rec/longoutRecord.dbd.pod +++ b/modules/database/src/std/rec/longoutRecord.dbd.pod @@ -78,7 +78,7 @@ channel access link. If the link is a constant, the result is no output. The DTYP field must then specify the C<<< Soft Channel >>> device support routine. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses and database links. =fields OUT, DTYP, OOPT, OOCH @@ -233,7 +233,7 @@ The HYST field sets an alarm deadband around each limit alarm. For an explanation of the IVOA and IVOV fields, see L. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/mbbiRecord.dbd.pod b/modules/database/src/std/rec/mbbiRecord.dbd.pod index 56b0d42f2..483316e7f 100644 --- a/modules/database/src/std/rec/mbbiRecord.dbd.pod +++ b/modules/database/src/std/rec/mbbiRecord.dbd.pod @@ -436,7 +436,7 @@ state occurs, if set to MAJOR or MINOR. The other fields, when set to MAJOR or MINOR, trigger an alarm when VAL equals the corresponding state. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/mbboDirectRecord.dbd.pod b/modules/database/src/std/rec/mbboDirectRecord.dbd.pod index d40cb48c7..84dd5e083 100644 --- a/modules/database/src/std/rec/mbboDirectRecord.dbd.pod +++ b/modules/database/src/std/rec/mbboDirectRecord.dbd.pod @@ -89,7 +89,7 @@ For records that are to write values to hardware devices, the OUT output link must contain the address of the I/O card, and the DTYP field must specify the proper device support module. Be aware that the address format differs according to the I/O bus used. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on the format of hardware addresses. During record processing VAL is converted into RVAL, which is the actual 32-bit @@ -298,7 +298,7 @@ the IVOV field to the output. See L for more information about IVOA and IVOV. -See L +See L for a complete explanation of record alarms and of the standard fields. L lists other fields related to alarms that are common to all record types. diff --git a/modules/database/src/std/rec/printfRecord.dbd.pod b/modules/database/src/std/rec/printfRecord.dbd.pod index a3bef9610..9bb98b0cc 100644 --- a/modules/database/src/std/rec/printfRecord.dbd.pod +++ b/modules/database/src/std/rec/printfRecord.dbd.pod @@ -148,7 +148,7 @@ which type of the data is requested through the appropriate input link. As with C a C<*> character may be used in the format to specify width and/or precision instead of numeric literals, in which case additional input links are used to provide the necessary integer parameter or parameters. See L
+Specification|https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html#address-specification> for information on specifying links. The formatted string is written to the VAL field. The maximum number of