This record type is normally used to send an integer value of up to 64 bits to an output device. The record supports alarm, drive, graphics and control limits.
The record-specific fields are described below.
These fields control how the record determines the value to be output when it gets processed:
Field Summary Type DCT Default Read Write CA PP OMSL Output Mode Select MENU (menuOmsl) Yes Yes Yes No DOL Desired Output Loc INLINK Yes Yes Yes No DRVH Drive High Limit INT64 Yes Yes Yes Yes DRVL Drive Low Limit INT64 Yes Yes Yes Yes VAL Desired Output INT64 Yes Yes Yes Yes
The following steps are performed in order during record processing.
The OMSL menu field is used to determine whether the DOL link field should be used during processing or not:
supervisory the DOL link field is not used.
The new output value is taken from the VAL field,
which may have been set from elsewhere.closed_loop the DOL link field is used to obtain a value.The output value is clipped to the range DRVL to DRVH inclusive, provided that DRVH > DRVL. The result is copied into the VAL field.
These fields control where the record will read data from when it is processed:
Field Summary Type DCT Default Read Write CA PP DTYP Device Type DEVICE Yes Yes Yes No OUT Output Specification OUTLINK Yes Yes Yes No
The DTYP field selects which device support layer should be responsible for writing output data.
The int64out device support layers provided by EPICS Base are documented in the "Device Support" section.
External support modules may provide additional device support for this record type.
If not set explicitly,
the DTYP value defaults to the first device support that is loaded for the record type,
which will usually be the Soft Channel support that comes with Base.
The OUT link field contains a database or channel access link or provides hardware address information that the device support uses to determine where the output data should be sent to.
These parameters are used to present meaningful data to the operator. They do not affect the functioning of the record.
Field Summary Type DCT Default Read Write CA PP DESC Descriptor STRING [41] Yes Yes Yes No EGU Units name STRING [16] Yes Yes Yes No HOPR High Operating Range INT64 Yes Yes Yes No LOPR Low Operating Range INT64 Yes Yes Yes No
The user configures limit alarms by putting numerical values into the HIHI, HIGH, LOW and LOLO fields, and by setting the associated alarm severities in the corresponding HHSV, HSV, LSV and LLSV menu fields.
The HYST field controls hysteresis to prevent alarm chattering from an input signal that is close to one of the limits and suffers from significant readout noise.
The LALM field is used by the record at run-time to implement the alarm limit hysteresis functionality.
Field Summary Type DCT Default Read Write CA PP HIHI Hihi Alarm Limit INT64 Yes Yes Yes Yes HIGH High Alarm Limit INT64 Yes Yes Yes Yes LOW Low Alarm Limit INT64 Yes Yes Yes Yes LOLO Lolo Alarm Limit INT64 Yes Yes Yes Yes HHSV Hihi Severity MENU (menuAlarmSevr) Yes Yes Yes Yes HSV High Severity MENU (menuAlarmSevr) Yes Yes Yes Yes LSV Low Severity MENU (menuAlarmSevr) Yes Yes Yes Yes LLSV Lolo Severity MENU (menuAlarmSevr) Yes Yes Yes Yes HYST Alarm Deadband INT64 Yes Yes Yes No LALM Last Value Alarmed INT64 No Yes No No
These parameters are used to determine when to send monitors placed on the VAL field. The monitors are sent when the current value exceeds the last transmitted value by the appropriate deadband. If these fields are set to zero, a monitor will be triggered every time the value changes; if set to -1, a monitor will be sent every time the record is processed.
The ADEL field sets the deadband for archive monitors (DBE_LOG events),
while the MDEL field controls value monitors (DBE_VALUE events).
The remaining fields are used by the record at run-time to implement the record monitoring deadband functionality.
Field Summary Type DCT Default Read Write CA PP ADEL Archive Deadband INT64 Yes Yes Yes No MDEL Monitor Deadband INT64 Yes Yes Yes No ALST Last Value Archived INT64 No Yes No No MLST Last Val Monitored INT64 No Yes No No
The following fields are used to operate the record in simulation mode.
If SIMM (fetched through SIML) is YES, the record is put in SIMS severity and the value is written through SIOL. SSCN sets a different SCAN mechanism to use in simulation mode. SDLY sets a delay (in sec) that is used for asynchronous simulation processing.
See Output Simulation Fields for more information on simulation mode and its fields.
Field Summary Type DCT Default Read Write CA PP SIML Simulation Mode Link INLINK Yes Yes Yes No SIMM Simulation Mode MENU (menuYesNo) No Yes Yes No SIOL Simulation Output Link OUTLINK Yes Yes Yes No SIMS Simulation Mode Severity MENU (menuAlarmSevr) Yes Yes Yes No SDLY Sim. Mode Async Delay DOUBLE Yes -1.0 Yes Yes No SSCN Sim. Mode Scan MENU (menuScan) Yes 65535 Yes Yes No
Whenever an output record is put into INVALID alarm severity, IVOA specifies the action to take.
Continue normally (default)Write the value. Same as if severity is lower than INVALID.
Don't drive outputsDo not write value.
Set output to IVOVSet VAL to IVOV, then write the value.
Field Summary Type DCT Default Read Write CA PP IVOA INVALID output action MENU (menuIvoa) Yes Yes Yes No IVOV INVALID output value INT64 Yes Yes Yes No
The following are the record support routines that would be of interest to an application developer.
Other routines are the get_units,
get_graphic_double,
get_alarm_double and get_control_double routines,
which are used to collect properties from the record for the complex DBR data structures.
This routine first initializes the simulation mode mechanism by setting SIMM if SIML is a constant.
It then checks if the device support and the device support's write_int64out routine are defined.
If either one does not exist,
an error message is issued and processing is terminated.
If DOL is a constant, then VAL is initialized with its value and UDF is set to FALSE.
If device support includes init_record,
it is called.
Finally, the deadband mechanisms for monitors and level alarms are initialized.
See next section.
Routine process implements the following algorithm:
write_int64out routine are defined.
If either one does not exist,
an error message is issued and processing is terminated with the PACT field set to TRUE,
effectively blocking the record to avoid error storms.convert: if drive limits are defined then force value to be within those limits.write_int64out output routine has started,
but not completed writing the new value.
In this case,
the processing routine merely returns,
leaving PACT TRUE.The record requires device support to provide an entry table (dset) which defines the following members:
typedef struct {
long number;
long (*report)(int level);
long (*init)(int after);
long (*init_record)(int64outRecord *prec);
long (*get_ioint_info)(int cmd, int64outRecord *prec, IOSCANPVT *piosl);
long (*write_int64out)(int64outRecord *prec);
} int64outdset;
The module must set number to at least 5, and provide a pointer to its write_int64out() routine; the other function pointers may be NULL if their associated functionality is not required for this support layer. Most device supports also provide an init_record() routine to configure the record instance and connect it to the hardware or driver support layer.
The individual routines are described below.
This optional routine is called by the IOC command dbior and is passed the report level that was requested by the user. It should print a report on the state of the device support to stdout. The level parameter may be used to output increasingly more detailed information at higher levels, or to select different types of information with different levels. Level zero should print no more than a small summary.
This optional routine is called twice at IOC initialization time. The first call happens before any of the init_record() calls are made, with the integer parameter after set to 0. The second call happens after all of the init_record() calls have been made, with after set to 1.
This optional routine is called by the record initialization code for each int64out record instance that has its DTYP field set to use this device support. It is normally used to check that the OUT address is the expected type and that it points to a valid device, to allocate any record-specific buffer space and other memory, and to connect any communication channels needed for the write_int64out() routine to work properly.
This optional routine is called whenever the record's SCAN field is being changed to or from the value I/O Intr to find out which I/O Interrupt Scan list the record should be added to or deleted from. If this routine is not provided, it will not be possible to set the SCAN field to the value I/O Intr at all.
The cmd parameter is zero when the record is being added to the scan list, and one when it is being removed from the list. The routine must determine which interrupt source the record should be connected to, which it indicates by the scan list that it points the location at *piosl to before returning. It can prevent the SCAN field from being changed at all by returning a non-zero value to its caller.
In most cases the device support will create the I/O Interrupt Scan lists that it returns for itself, by calling void scanIoInit(IOSCANPVT *piosl) once for each separate interrupt source. That routine allocates memory and inializes the list, then passes back a pointer to the new list in the location at *piosl.
When the device support receives notification that the interrupt has occurred, it announces that to the IOC by calling void scanIoRequest(IOSCANPVT iosl) which will arrange for the appropriate records to be processed in a suitable thread. The scanIoRequest() routine is safe to call from an interrupt service routine on embedded architectures (vxWorks and RTEMS).
This essential routine is called when the record wants to write a new value to the addressed device. It is responsible for performing (or at least initiating) a write operation, using the value from the record's VAL field.
If the device may take more than a few microseconds to accept the new value, this routine must never block (busy-wait), but use the asynchronous processing mechanism. In that case it signals the asynchronous operation by setting the record's PACT field to TRUE before it returns, having arranged for the record's process() routine to be called later once the write operation is over. When that happens, the write_int64out() routine will be called again with PACT still set to TRUE; it should then set it to FALSE to indicate the write has completed, and return.
A return value of zero indicates success, any other value indicates that an error occurred.
...
Two soft device support modules, Soft Channel and Soft Callback Channel, are provided for output records not related to actual hardware devices. The OUT link type must be either a CONSTANT, DB_LINK, or CA_LINK.
This module writes the current value using the record's VAL field.
write_int64out calls dbPutLink to write the current value.
This module is like the previous except that it writes the current value using asynchronous processing that will not complete until an asynchronous processing of the target record has completed.