EPICSWIKI - User contributions [en]

RRM 3-14 Histogram

2018-02-09T14:15:44Z

TimSouthern: /* Setting up an IOC to use record type */

[[RRM 3-14|EPICS Record Reference Manual]]

= Histogram =

The histogram record is used to store frequency counts of a signal into an array of arbitrary length. The user can configure the range of the signal value that the array will store. Anything outside this range will be ignored.

== Parameter Fields ==

The fields in this record fall into the following categories:

* scan parameters
* read parameters
* operator display parameters
* monitor parameters
* run-time and simulation mode parameters

=== Scanning Parameters ===

The histogram record has the standard fields for specifying under what circumstances the record will be processed. These fields are listed in [[RRM 3-14 dbCommon#Scan Fields|Scan Fields]]. In addition, [[RRM 3-14 Concepts#Scanning Specification|Scanning Specification]] explains how these fields are used.

=== Read Parameters ===

The SVL is the input link where the record reads its value. It can be a constant, a database link, or a channel access link. If SVL is a database or channel access link, then SGNL is read from SVL. If SVL is a constant, then SGNL is initialized with the constant value but can be changed via dbPuts. The <CODE>Soft Channel</CODE> device support module can be specified in the DTYP field. For a list of other device support modules currently supported at the user's local site, use the <CODE>dbst</CODE> utility in R3.13.

The ULIM and LLIM fields determine the usable range of signal values. Any value of SGNL below LLIM or above ULIM is outside the range and will not be stored in the array. In the NELM field the user must specify the array size, e.g., the number of array elements. Each element in the NELM field holds the counts for an interval of the range of signal counts, the range specified by ULIM and LLIM. These intervals are determined by dividing the range by NELM:

(ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SVL<TD>Signal Value Location (an input link)<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SGNL<TD>Signal Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>Yes<TD>No<TR>
<TD>DTYP<TD>Device Type<TD>DEVCHOICE<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>NELM<TD>Number of elements in array<TD>USHORT<TD>Yes<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>ULIM<TD>Upper Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>LLIM<TD>Lower Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Operator Display Parameters ===

These parameters are used to present meaningful data to the operator. These fields are used to display the value and other parameters of the histogram either textually or graphically. See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for more on the record name (NAME) and description (DESC) fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>NAME<TD>Record Name<TD>STRING [29]<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>DESC<TD>Description<TD>STRING [29]<TD>Yes<TD>Null<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Alarm Parameters ===

The Histogram record has the alarm parameters common to all record types. [[RRM 3-14 dbCommon#Alarm Fields|Alarm Fields]] lists other fields related to a alarms that are common to all record types.

=== Monitor Parameters ===

The MDEL field implements the monitor count deadband. Only when MCNT is greater than the value given to MDEL are monitors triggered, MCNT being the number of counts since the last time the record was processed. If MDEL is -1, everytime the record is processed, a monitor is triggered regardless.

If SDEL is greater than 0, it causes a callback routine to be called. The number specified in SDEL is the callback routines interval. The callback routine is called every SDEL seconds. The callback routine posts an event if MCNT is greater than 0.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>MDEL<TD>Monitor Delta<TD>SHORT<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SDEL<TD>Monitor Seconds Deadband<TD>FLOAT<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

=== Run-time and Simulation Mode Parameters ===

These parameters are used by the run-time code for processing the histogram. They are not configurable by the user prior to run-time. They represent the current state of the record. Many of them are used to process the histogram more efficiently.

The BPTR field contains a pointer to the unsigned long array of frequency values. The VAL field references this array as well. However, the BPTR field is not accessible at run-time.

The MCNT field keeps counts the number of signal counts since the last monitor was invoked.

The WDOG field contains a pointer to the callback control structure and is of no interest to the user.

The collections controls field (CMD) is a menu field with five choices: <CODE>Read</CODE>, <CODE>Clear</CODE>, <CODE>Start</CODE>, <CODE>Stop</CODE>, and <CODE>Setup</CODE>. When <CODE>Read</CODE>, the record retrieves its values and adds them to the signal array. This command will first clear the signal counts which have already been read when it is first invoked. The <CODE>Clear</CODE> command erases the signal counts, setting the elements in the array back to zero. Afterwards, the field is set back to <CODE>Read</CODE>. The <CODE>Start</CODE> command simply causes the record to read signal values into the array. Unlike <CODE>Read</CODE>, it doesn't clear the array first. The <CODE>Stop</CODE> command disables the reading of signal values into the array. The <CODE>Setup</CODE> command waits until the <CODE>start</CODE> or <CODE>read</CODE> command has been issued to start counting.

The CSTA or collections status field implements the CMD field choices by enabling or disabling the reading of values into the histogram array. While FALSE, no signals are added to the array. While TRUE, signals are read and added to the array. The field is initialized to TRUE. The <CODE>Stop</CODE> command is the only command that sets CSTA to FALSE. On the other hand, the <CODE>Start</CODE> command is the only command that sets it to TRUE. Thus, <CODE>Start</CODE> must be invoked after each <CODE>Stop</CODE> command in order to enable counting; invoking <CODE>Read</CODE> will not enable signal counting after <CODE>Stop</CODE> has been invoked.

A typical use of these fields would be to initialize the CMD field to <CODE>Read</CODE> (it is initialized to this command by default), to use the <CODE>Stop</CODE> command to disable counting when necessary, after which the <CODE>Start</CODE> command can be invoked to re-start the signal count.

The WDTH field is a private field that holds the signal width of the array elements. For instance, if the LLIM was configured to be 4.0 and ULIM was configured to be 12.0 and the NELM was set to 4, then the WDTH for each array would be 2. Thus, it is (ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>BPTR<TD>Buffer Pointer<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>VAL<TD>Value Field<TD>See BPTR<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>MCNT<TD>Monitor Counts<TD>SHORT<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDOG<TD>Watchdog Callback<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>CMD<TD>Collections Control<TD>[[RRM 3-14 Menu Choices|RECCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>CSTA<TD>Collections Status<TD>SHORT<TD>No<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDTH<TD>Element Width<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

The following fields are used to operate the histogram record in simulation mode. See [[RRM 3-14 Common#Fields Common to Many Record Types|Fields Common to Many Record Types]] for more information on the simulation mode fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SIOL<TD>Simulation Value Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SVAL<TD>Simulation Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIML<TD>Simulation Mode Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMM<TD>Simulation Mode<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMS<TD>Simulation Mode Alarm Severity<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

== Record Support ==

=== Record Support Routines ===

==== init_record ====

Using NELM, space for the unsigned long array is allocated and the width WDTH of the array is calculated.

This routine initializes SIMM with the value of SIML if SIML type is CONSTANT link or creates a channel access link if SIML type is PV_LINK. SVAL is likewise initialized if SIOL is CONSTANT or PV_LINK.

This routine next checks to see that device support and a device support read routine are available. If device support includes init_record, it is called.

==== process ====

See next section.

==== special ====

Special is invoked whenever the fields CMD, SGNL, ULIM, or LLIM are changed.

If SGNL is changed, add_count is called.

If ULIM or LLIM are changed, WDTH is recalculated and clear_histogram is called.

If CMD is less or equal to 1, clear_histogram is called and CMD is reset to 0. If CMD is 2, CSTA is set to TRUE and CMD is reset to 0. If CMD is 3, CSTA is set to FALSE and CMD is reset to 0.

clear_histogram zeros out the histogram array. add_count increments the frequency in the histogram array.

==== get_value ====

Fills in the values of struct valueDes so that they refer to the array.

==== cvt_dbaddr ====

This is called by dbNameToAddr. It makes the dbAddr structure refer to the actual buffer holding the array.

==== get_array_info ====

Obtains values from the array referenced by VAL.

==== put_array_info ====

Writes values into the array referenced by VAL.

=== Record Processing ===

Routine process implements the following algorithm:

# Check to see that the appropriate device support module exists. If it doesn't, an error message is issued and processing is terminated with the PACT field set to TRUE. This ensures that processes will no longer be called for this record. Thus error storms will not occur.
# readValue is called. See [[RRM 3-14 Common#Input Records|Input Records]] for more information
# If PACT has been changed to TRUE, the device support read routine has started but has not completed writing the new value. In this case, the processing routine merely returns, leaving PACT TRUE.
# Add count to histogram array.
# Check to see if monitors should be invoked. Alarm monitors are invoked if the alarm status or severity has changed. Archive and value change monitors are invoked if MDEL conditions are met. NSEV and NSTA are reset to 0.
# Scan forward link if necessary, set PACT and INIT to FALSE, and return.

== Device Support ==

=== Fields Of Interest To Device Support ===

The device support routines are primarily interested in the following fields:

<TABLE BORDER="1">
<TH>Name<TH> Summary <TH>Description<TR>
<TD>PACT <TD>Processing Active<TD rowspan=5>See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for an explanation of these fields.<TR>
<TD>DPVT<TD>Device Private <TR>
<TD>UDF<TD>VAL Undefined<TR>
<TD>NSEV<TD>New Alarm Severity<TR>
<TD>NSTA<TD>New Alarm Status <TR>
<TD>SVL<TD>Signal Value<TD rowspan=2>The device support module retrieves a value from SGNL for SVL<TR>
<TD>SGNL<TD>Signal Value Location
</TABLE>

=== Device Support Routines ===

Device support consists of the following routines:

==== init_record ====

init_record(precord)

This routine is called by the record support init_record routine. It makes sure that SGNL is a CONSTANT, PV_LINK, DB_LINK, or CA_LINK. It also retrieves a value for SVL from SGNL. If SGNL is none of the above, an error is generated.

==== read_histogram ====

read_histogram(*precord)

This routine is called by the record support routines. It retrieves a value for SVL from SGNL.

=== Device Support For Soft Records ===

Only the device support module <CODE>Soft Channel</CODE> is currently provided, though other device support modules may be provided at the user's site.

==== Soft Channel ====

The <CODE>Soft Channel</CODE> device support routine retrieves a value from SGNL. SGNL must be CONSTANT, PV_LINK, DB_LINK, or CA_LINK.

==== Setting Up an IOC to use Record Type ====

The histogram record type may not be fully included in EPICS base R3.14.x. The record is defined in <EPICSBASE>/src/rec, however it's not included
in <EPICSBASE>/src/misc/base.dbd.

'''Possible errors:'''
# ''Record "TEST:Histo" is of unknown type "histogram" - Error at or before ")" ...''
#: - Missing the record type in base.dbd
# ''Missing device support entry table PV: TEST:Histo histogram: init_record''
#: - Missing device support for the record type

'''How to install'''

To be able to use this record type, one has to install the record's dbd in the application src directory.
# Add histogramRecord.dbd to src/Makefile
#: ie. <App>_DBD += histogramRecord.dbd
# Create a dbd file with following contents saved in src folder. ie. Filename: histogramDeviceSupport.dbd
#: device(histogram,CONSTANT,devHistogramSoft,"Soft Channel")
# Add above dbd to src/Makefile
#:ie. <App>_DBD += histogramDeviceSupport.dbd
# Type 'make' in src directory
Now, one can create db records using the histogram type in the IOC.

----

EPICS Record Reference Manual - 19 MAY 1998

RRM 3-14 Histogram

2018-02-09T14:14:25Z

TimSouthern: /* Setting up an IOC to use record type */

[[RRM 3-14|EPICS Record Reference Manual]]

= Histogram =

The histogram record is used to store frequency counts of a signal into an array of arbitrary length. The user can configure the range of the signal value that the array will store. Anything outside this range will be ignored.

== Parameter Fields ==

The fields in this record fall into the following categories:

* scan parameters
* read parameters
* operator display parameters
* monitor parameters
* run-time and simulation mode parameters

=== Scanning Parameters ===

The histogram record has the standard fields for specifying under what circumstances the record will be processed. These fields are listed in [[RRM 3-14 dbCommon#Scan Fields|Scan Fields]]. In addition, [[RRM 3-14 Concepts#Scanning Specification|Scanning Specification]] explains how these fields are used.

=== Read Parameters ===

The SVL is the input link where the record reads its value. It can be a constant, a database link, or a channel access link. If SVL is a database or channel access link, then SGNL is read from SVL. If SVL is a constant, then SGNL is initialized with the constant value but can be changed via dbPuts. The <CODE>Soft Channel</CODE> device support module can be specified in the DTYP field. For a list of other device support modules currently supported at the user's local site, use the <CODE>dbst</CODE> utility in R3.13.

The ULIM and LLIM fields determine the usable range of signal values. Any value of SGNL below LLIM or above ULIM is outside the range and will not be stored in the array. In the NELM field the user must specify the array size, e.g., the number of array elements. Each element in the NELM field holds the counts for an interval of the range of signal counts, the range specified by ULIM and LLIM. These intervals are determined by dividing the range by NELM:

(ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SVL<TD>Signal Value Location (an input link)<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SGNL<TD>Signal Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>Yes<TD>No<TR>
<TD>DTYP<TD>Device Type<TD>DEVCHOICE<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>NELM<TD>Number of elements in array<TD>USHORT<TD>Yes<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>ULIM<TD>Upper Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>LLIM<TD>Lower Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Operator Display Parameters ===

These parameters are used to present meaningful data to the operator. These fields are used to display the value and other parameters of the histogram either textually or graphically. See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for more on the record name (NAME) and description (DESC) fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>NAME<TD>Record Name<TD>STRING [29]<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>DESC<TD>Description<TD>STRING [29]<TD>Yes<TD>Null<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Alarm Parameters ===

The Histogram record has the alarm parameters common to all record types. [[RRM 3-14 dbCommon#Alarm Fields|Alarm Fields]] lists other fields related to a alarms that are common to all record types.

=== Monitor Parameters ===

The MDEL field implements the monitor count deadband. Only when MCNT is greater than the value given to MDEL are monitors triggered, MCNT being the number of counts since the last time the record was processed. If MDEL is -1, everytime the record is processed, a monitor is triggered regardless.

If SDEL is greater than 0, it causes a callback routine to be called. The number specified in SDEL is the callback routines interval. The callback routine is called every SDEL seconds. The callback routine posts an event if MCNT is greater than 0.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>MDEL<TD>Monitor Delta<TD>SHORT<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SDEL<TD>Monitor Seconds Deadband<TD>FLOAT<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

=== Run-time and Simulation Mode Parameters ===

These parameters are used by the run-time code for processing the histogram. They are not configurable by the user prior to run-time. They represent the current state of the record. Many of them are used to process the histogram more efficiently.

The BPTR field contains a pointer to the unsigned long array of frequency values. The VAL field references this array as well. However, the BPTR field is not accessible at run-time.

The MCNT field keeps counts the number of signal counts since the last monitor was invoked.

The WDOG field contains a pointer to the callback control structure and is of no interest to the user.

The collections controls field (CMD) is a menu field with five choices: <CODE>Read</CODE>, <CODE>Clear</CODE>, <CODE>Start</CODE>, <CODE>Stop</CODE>, and <CODE>Setup</CODE>. When <CODE>Read</CODE>, the record retrieves its values and adds them to the signal array. This command will first clear the signal counts which have already been read when it is first invoked. The <CODE>Clear</CODE> command erases the signal counts, setting the elements in the array back to zero. Afterwards, the field is set back to <CODE>Read</CODE>. The <CODE>Start</CODE> command simply causes the record to read signal values into the array. Unlike <CODE>Read</CODE>, it doesn't clear the array first. The <CODE>Stop</CODE> command disables the reading of signal values into the array. The <CODE>Setup</CODE> command waits until the <CODE>start</CODE> or <CODE>read</CODE> command has been issued to start counting.

The CSTA or collections status field implements the CMD field choices by enabling or disabling the reading of values into the histogram array. While FALSE, no signals are added to the array. While TRUE, signals are read and added to the array. The field is initialized to TRUE. The <CODE>Stop</CODE> command is the only command that sets CSTA to FALSE. On the other hand, the <CODE>Start</CODE> command is the only command that sets it to TRUE. Thus, <CODE>Start</CODE> must be invoked after each <CODE>Stop</CODE> command in order to enable counting; invoking <CODE>Read</CODE> will not enable signal counting after <CODE>Stop</CODE> has been invoked.

A typical use of these fields would be to initialize the CMD field to <CODE>Read</CODE> (it is initialized to this command by default), to use the <CODE>Stop</CODE> command to disable counting when necessary, after which the <CODE>Start</CODE> command can be invoked to re-start the signal count.

The WDTH field is a private field that holds the signal width of the array elements. For instance, if the LLIM was configured to be 4.0 and ULIM was configured to be 12.0 and the NELM was set to 4, then the WDTH for each array would be 2. Thus, it is (ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>BPTR<TD>Buffer Pointer<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>VAL<TD>Value Field<TD>See BPTR<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>MCNT<TD>Monitor Counts<TD>SHORT<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDOG<TD>Watchdog Callback<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>CMD<TD>Collections Control<TD>[[RRM 3-14 Menu Choices|RECCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>CSTA<TD>Collections Status<TD>SHORT<TD>No<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDTH<TD>Element Width<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

The following fields are used to operate the histogram record in simulation mode. See [[RRM 3-14 Common#Fields Common to Many Record Types|Fields Common to Many Record Types]] for more information on the simulation mode fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SIOL<TD>Simulation Value Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SVAL<TD>Simulation Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIML<TD>Simulation Mode Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMM<TD>Simulation Mode<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMS<TD>Simulation Mode Alarm Severity<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

== Record Support ==

=== Record Support Routines ===

==== init_record ====

Using NELM, space for the unsigned long array is allocated and the width WDTH of the array is calculated.

This routine initializes SIMM with the value of SIML if SIML type is CONSTANT link or creates a channel access link if SIML type is PV_LINK. SVAL is likewise initialized if SIOL is CONSTANT or PV_LINK.

This routine next checks to see that device support and a device support read routine are available. If device support includes init_record, it is called.

==== process ====

See next section.

==== special ====

Special is invoked whenever the fields CMD, SGNL, ULIM, or LLIM are changed.

If SGNL is changed, add_count is called.

If ULIM or LLIM are changed, WDTH is recalculated and clear_histogram is called.

If CMD is less or equal to 1, clear_histogram is called and CMD is reset to 0. If CMD is 2, CSTA is set to TRUE and CMD is reset to 0. If CMD is 3, CSTA is set to FALSE and CMD is reset to 0.

clear_histogram zeros out the histogram array. add_count increments the frequency in the histogram array.

==== get_value ====

Fills in the values of struct valueDes so that they refer to the array.

==== cvt_dbaddr ====

This is called by dbNameToAddr. It makes the dbAddr structure refer to the actual buffer holding the array.

==== get_array_info ====

Obtains values from the array referenced by VAL.

==== put_array_info ====

Writes values into the array referenced by VAL.

=== Record Processing ===

Routine process implements the following algorithm:

# Check to see that the appropriate device support module exists. If it doesn't, an error message is issued and processing is terminated with the PACT field set to TRUE. This ensures that processes will no longer be called for this record. Thus error storms will not occur.
# readValue is called. See [[RRM 3-14 Common#Input Records|Input Records]] for more information
# If PACT has been changed to TRUE, the device support read routine has started but has not completed writing the new value. In this case, the processing routine merely returns, leaving PACT TRUE.
# Add count to histogram array.
# Check to see if monitors should be invoked. Alarm monitors are invoked if the alarm status or severity has changed. Archive and value change monitors are invoked if MDEL conditions are met. NSEV and NSTA are reset to 0.
# Scan forward link if necessary, set PACT and INIT to FALSE, and return.

== Device Support ==

=== Fields Of Interest To Device Support ===

The device support routines are primarily interested in the following fields:

<TABLE BORDER="1">
<TH>Name<TH> Summary <TH>Description<TR>
<TD>PACT <TD>Processing Active<TD rowspan=5>See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for an explanation of these fields.<TR>
<TD>DPVT<TD>Device Private <TR>
<TD>UDF<TD>VAL Undefined<TR>
<TD>NSEV<TD>New Alarm Severity<TR>
<TD>NSTA<TD>New Alarm Status <TR>
<TD>SVL<TD>Signal Value<TD rowspan=2>The device support module retrieves a value from SGNL for SVL<TR>
<TD>SGNL<TD>Signal Value Location
</TABLE>

=== Device Support Routines ===

Device support consists of the following routines:

==== init_record ====

init_record(precord)

This routine is called by the record support init_record routine. It makes sure that SGNL is a CONSTANT, PV_LINK, DB_LINK, or CA_LINK. It also retrieves a value for SVL from SGNL. If SGNL is none of the above, an error is generated.

==== read_histogram ====

read_histogram(*precord)

This routine is called by the record support routines. It retrieves a value for SVL from SGNL.

=== Device Support For Soft Records ===

Only the device support module <CODE>Soft Channel</CODE> is currently provided, though other device support modules may be provided at the user's site.

==== Soft Channel ====

The <CODE>Soft Channel</CODE> device support routine retrieves a value from SGNL. SGNL must be CONSTANT, PV_LINK, DB_LINK, or CA_LINK.

==== Setting up an IOC to use record type ====

The histogram record type may not be fully included in EPICS base R3.14.x. The record is defined in <EPICSBASE>/src/rec, however it's not included
in <EPICSBASE>/src/misc/base.dbd.

'''Possible errors:'''
# ''Record "TEST:Histo" is of unknown type "histogram" - Error at or before ")" ...''
#: - Missing the record type in base.dbd
# ''Missing device support entry table PV: TEST:Histo histogram: init_record''
#: - Missing device support for the record type

'''How to install'''

To be able to use this record type, one has to install the record's dbd in the application src directory.
# Add histogramRecord.dbd to src/Makefile
#: ie. <App>_DBD += histogramRecord.dbd
# Create a dbd file with following contents saved in src folder. ie. Filename: histogramDeviceSupport.dbd
#: device(histogram,CONSTANT,devHistogramSoft,"Soft Channel")
# Add above dbd to src/Makefile
#:ie. <App>_DBD += histogramDeviceSupport.dbd
# Type 'make' in src directory
Now, one can create db records using the histogram type in the IOC.

----

EPICS Record Reference Manual - 19 MAY 1998

RRM 3-14 Histogram

2018-02-08T17:31:49Z

TimSouthern: /* Setting up an IOC to use record type */

[[RRM 3-14|EPICS Record Reference Manual]]

= Histogram =

The histogram record is used to store frequency counts of a signal into an array of arbitrary length. The user can configure the range of the signal value that the array will store. Anything outside this range will be ignored.

== Parameter Fields ==

The fields in this record fall into the following categories:

* scan parameters
* read parameters
* operator display parameters
* monitor parameters
* run-time and simulation mode parameters

=== Scanning Parameters ===

The histogram record has the standard fields for specifying under what circumstances the record will be processed. These fields are listed in [[RRM 3-14 dbCommon#Scan Fields|Scan Fields]]. In addition, [[RRM 3-14 Concepts#Scanning Specification|Scanning Specification]] explains how these fields are used.

=== Read Parameters ===

The SVL is the input link where the record reads its value. It can be a constant, a database link, or a channel access link. If SVL is a database or channel access link, then SGNL is read from SVL. If SVL is a constant, then SGNL is initialized with the constant value but can be changed via dbPuts. The <CODE>Soft Channel</CODE> device support module can be specified in the DTYP field. For a list of other device support modules currently supported at the user's local site, use the <CODE>dbst</CODE> utility in R3.13.

The ULIM and LLIM fields determine the usable range of signal values. Any value of SGNL below LLIM or above ULIM is outside the range and will not be stored in the array. In the NELM field the user must specify the array size, e.g., the number of array elements. Each element in the NELM field holds the counts for an interval of the range of signal counts, the range specified by ULIM and LLIM. These intervals are determined by dividing the range by NELM:

(ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SVL<TD>Signal Value Location (an input link)<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SGNL<TD>Signal Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>Yes<TD>No<TR>
<TD>DTYP<TD>Device Type<TD>DEVCHOICE<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>NELM<TD>Number of elements in array<TD>USHORT<TD>Yes<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>ULIM<TD>Upper Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>LLIM<TD>Lower Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Operator Display Parameters ===

These parameters are used to present meaningful data to the operator. These fields are used to display the value and other parameters of the histogram either textually or graphically. See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for more on the record name (NAME) and description (DESC) fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>NAME<TD>Record Name<TD>STRING [29]<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>DESC<TD>Description<TD>STRING [29]<TD>Yes<TD>Null<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Alarm Parameters ===

The Histogram record has the alarm parameters common to all record types. [[RRM 3-14 dbCommon#Alarm Fields|Alarm Fields]] lists other fields related to a alarms that are common to all record types.

=== Monitor Parameters ===

The MDEL field implements the monitor count deadband. Only when MCNT is greater than the value given to MDEL are monitors triggered, MCNT being the number of counts since the last time the record was processed. If MDEL is -1, everytime the record is processed, a monitor is triggered regardless.

If SDEL is greater than 0, it causes a callback routine to be called. The number specified in SDEL is the callback routines interval. The callback routine is called every SDEL seconds. The callback routine posts an event if MCNT is greater than 0.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>MDEL<TD>Monitor Delta<TD>SHORT<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SDEL<TD>Monitor Seconds Deadband<TD>FLOAT<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

=== Run-time and Simulation Mode Parameters ===

These parameters are used by the run-time code for processing the histogram. They are not configurable by the user prior to run-time. They represent the current state of the record. Many of them are used to process the histogram more efficiently.

The BPTR field contains a pointer to the unsigned long array of frequency values. The VAL field references this array as well. However, the BPTR field is not accessible at run-time.

The MCNT field keeps counts the number of signal counts since the last monitor was invoked.

The WDOG field contains a pointer to the callback control structure and is of no interest to the user.

The collections controls field (CMD) is a menu field with five choices: <CODE>Read</CODE>, <CODE>Clear</CODE>, <CODE>Start</CODE>, <CODE>Stop</CODE>, and <CODE>Setup</CODE>. When <CODE>Read</CODE>, the record retrieves its values and adds them to the signal array. This command will first clear the signal counts which have already been read when it is first invoked. The <CODE>Clear</CODE> command erases the signal counts, setting the elements in the array back to zero. Afterwards, the field is set back to <CODE>Read</CODE>. The <CODE>Start</CODE> command simply causes the record to read signal values into the array. Unlike <CODE>Read</CODE>, it doesn't clear the array first. The <CODE>Stop</CODE> command disables the reading of signal values into the array. The <CODE>Setup</CODE> command waits until the <CODE>start</CODE> or <CODE>read</CODE> command has been issued to start counting.

The CSTA or collections status field implements the CMD field choices by enabling or disabling the reading of values into the histogram array. While FALSE, no signals are added to the array. While TRUE, signals are read and added to the array. The field is initialized to TRUE. The <CODE>Stop</CODE> command is the only command that sets CSTA to FALSE. On the other hand, the <CODE>Start</CODE> command is the only command that sets it to TRUE. Thus, <CODE>Start</CODE> must be invoked after each <CODE>Stop</CODE> command in order to enable counting; invoking <CODE>Read</CODE> will not enable signal counting after <CODE>Stop</CODE> has been invoked.

A typical use of these fields would be to initialize the CMD field to <CODE>Read</CODE> (it is initialized to this command by default), to use the <CODE>Stop</CODE> command to disable counting when necessary, after which the <CODE>Start</CODE> command can be invoked to re-start the signal count.

The WDTH field is a private field that holds the signal width of the array elements. For instance, if the LLIM was configured to be 4.0 and ULIM was configured to be 12.0 and the NELM was set to 4, then the WDTH for each array would be 2. Thus, it is (ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>BPTR<TD>Buffer Pointer<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>VAL<TD>Value Field<TD>See BPTR<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>MCNT<TD>Monitor Counts<TD>SHORT<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDOG<TD>Watchdog Callback<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>CMD<TD>Collections Control<TD>[[RRM 3-14 Menu Choices|RECCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>CSTA<TD>Collections Status<TD>SHORT<TD>No<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDTH<TD>Element Width<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

The following fields are used to operate the histogram record in simulation mode. See [[RRM 3-14 Common#Fields Common to Many Record Types|Fields Common to Many Record Types]] for more information on the simulation mode fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SIOL<TD>Simulation Value Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SVAL<TD>Simulation Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIML<TD>Simulation Mode Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMM<TD>Simulation Mode<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMS<TD>Simulation Mode Alarm Severity<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

== Record Support ==

=== Record Support Routines ===

==== init_record ====

Using NELM, space for the unsigned long array is allocated and the width WDTH of the array is calculated.

This routine initializes SIMM with the value of SIML if SIML type is CONSTANT link or creates a channel access link if SIML type is PV_LINK. SVAL is likewise initialized if SIOL is CONSTANT or PV_LINK.

This routine next checks to see that device support and a device support read routine are available. If device support includes init_record, it is called.

==== process ====

See next section.

==== special ====

Special is invoked whenever the fields CMD, SGNL, ULIM, or LLIM are changed.

If SGNL is changed, add_count is called.

If ULIM or LLIM are changed, WDTH is recalculated and clear_histogram is called.

If CMD is less or equal to 1, clear_histogram is called and CMD is reset to 0. If CMD is 2, CSTA is set to TRUE and CMD is reset to 0. If CMD is 3, CSTA is set to FALSE and CMD is reset to 0.

clear_histogram zeros out the histogram array. add_count increments the frequency in the histogram array.

==== get_value ====

Fills in the values of struct valueDes so that they refer to the array.

==== cvt_dbaddr ====

This is called by dbNameToAddr. It makes the dbAddr structure refer to the actual buffer holding the array.

==== get_array_info ====

Obtains values from the array referenced by VAL.

==== put_array_info ====

Writes values into the array referenced by VAL.

=== Record Processing ===

Routine process implements the following algorithm:

# Check to see that the appropriate device support module exists. If it doesn't, an error message is issued and processing is terminated with the PACT field set to TRUE. This ensures that processes will no longer be called for this record. Thus error storms will not occur.
# readValue is called. See [[RRM 3-14 Common#Input Records|Input Records]] for more information
# If PACT has been changed to TRUE, the device support read routine has started but has not completed writing the new value. In this case, the processing routine merely returns, leaving PACT TRUE.
# Add count to histogram array.
# Check to see if monitors should be invoked. Alarm monitors are invoked if the alarm status or severity has changed. Archive and value change monitors are invoked if MDEL conditions are met. NSEV and NSTA are reset to 0.
# Scan forward link if necessary, set PACT and INIT to FALSE, and return.

== Device Support ==

=== Fields Of Interest To Device Support ===

The device support routines are primarily interested in the following fields:

<TABLE BORDER="1">
<TH>Name<TH> Summary <TH>Description<TR>
<TD>PACT <TD>Processing Active<TD rowspan=5>See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for an explanation of these fields.<TR>
<TD>DPVT<TD>Device Private <TR>
<TD>UDF<TD>VAL Undefined<TR>
<TD>NSEV<TD>New Alarm Severity<TR>
<TD>NSTA<TD>New Alarm Status <TR>
<TD>SVL<TD>Signal Value<TD rowspan=2>The device support module retrieves a value from SGNL for SVL<TR>
<TD>SGNL<TD>Signal Value Location
</TABLE>

=== Device Support Routines ===

Device support consists of the following routines:

==== init_record ====

init_record(precord)

This routine is called by the record support init_record routine. It makes sure that SGNL is a CONSTANT, PV_LINK, DB_LINK, or CA_LINK. It also retrieves a value for SVL from SGNL. If SGNL is none of the above, an error is generated.

==== read_histogram ====

read_histogram(*precord)

This routine is called by the record support routines. It retrieves a value for SVL from SGNL.

=== Device Support For Soft Records ===

Only the device support module <CODE>Soft Channel</CODE> is currently provided, though other device support modules may be provided at the user's site.

==== Soft Channel ====

The <CODE>Soft Channel</CODE> device support routine retrieves a value from SGNL. SGNL must be CONSTANT, PV_LINK, DB_LINK, or CA_LINK.

==== Setting up an IOC to use record type ====

The histogram record type is not fully included in EPICS base. To be able to use it, one has to install the record's dbd in the application src directory.
# Add histogramRecord.dbd to src/Makefile
#: ie. <App>_DBD += histogramRecord.dbd
# Create a dbd file with following contents saved in src folder. ie. Filename: histogramDeviceSupport.dbd
#: device(histogram,CONSTANT,devHistogramSoft,"Soft Channel")
# Add above dbd to src/Makefile
#:ie. <App>_DBD += histogramDeviceSupport.dbd
# Type 'make' in src directory
Now, one can create db records using the histogram type in the IOC.

----

EPICS Record Reference Manual - 19 MAY 1998

RRM 3-14 Histogram

2018-02-08T17:12:46Z

TimSouthern:

[[RRM 3-14|EPICS Record Reference Manual]]

= Histogram =

The histogram record is used to store frequency counts of a signal into an array of arbitrary length. The user can configure the range of the signal value that the array will store. Anything outside this range will be ignored.

== Parameter Fields ==

The fields in this record fall into the following categories:

* scan parameters
* read parameters
* operator display parameters
* monitor parameters
* run-time and simulation mode parameters

=== Scanning Parameters ===

The histogram record has the standard fields for specifying under what circumstances the record will be processed. These fields are listed in [[RRM 3-14 dbCommon#Scan Fields|Scan Fields]]. In addition, [[RRM 3-14 Concepts#Scanning Specification|Scanning Specification]] explains how these fields are used.

=== Read Parameters ===

The SVL is the input link where the record reads its value. It can be a constant, a database link, or a channel access link. If SVL is a database or channel access link, then SGNL is read from SVL. If SVL is a constant, then SGNL is initialized with the constant value but can be changed via dbPuts. The <CODE>Soft Channel</CODE> device support module can be specified in the DTYP field. For a list of other device support modules currently supported at the user's local site, use the <CODE>dbst</CODE> utility in R3.13.

The ULIM and LLIM fields determine the usable range of signal values. Any value of SGNL below LLIM or above ULIM is outside the range and will not be stored in the array. In the NELM field the user must specify the array size, e.g., the number of array elements. Each element in the NELM field holds the counts for an interval of the range of signal counts, the range specified by ULIM and LLIM. These intervals are determined by dividing the range by NELM:

(ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SVL<TD>Signal Value Location (an input link)<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SGNL<TD>Signal Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>Yes<TD>No<TR>
<TD>DTYP<TD>Device Type<TD>DEVCHOICE<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>NELM<TD>Number of elements in array<TD>USHORT<TD>Yes<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>ULIM<TD>Upper Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>LLIM<TD>Lower Signal Limit<TD>DOUBLE<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Operator Display Parameters ===

These parameters are used to present meaningful data to the operator. These fields are used to display the value and other parameters of the histogram either textually or graphically. See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for more on the record name (NAME) and description (DESC) fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>NAME<TD>Record Name<TD>STRING [29]<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD> <TR>
<TD>DESC<TD>Description<TD>STRING [29]<TD>Yes<TD>Null<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

=== Alarm Parameters ===

The Histogram record has the alarm parameters common to all record types. [[RRM 3-14 dbCommon#Alarm Fields|Alarm Fields]] lists other fields related to a alarms that are common to all record types.

=== Monitor Parameters ===

The MDEL field implements the monitor count deadband. Only when MCNT is greater than the value given to MDEL are monitors triggered, MCNT being the number of counts since the last time the record was processed. If MDEL is -1, everytime the record is processed, a monitor is triggered regardless.

If SDEL is greater than 0, it causes a callback routine to be called. The number specified in SDEL is the callback routines interval. The callback routine is called every SDEL seconds. The callback routine posts an event if MCNT is greater than 0.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>MDEL<TD>Monitor Delta<TD>SHORT<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SDEL<TD>Monitor Seconds Deadband<TD>FLOAT<TD>Yes<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

=== Run-time and Simulation Mode Parameters ===

These parameters are used by the run-time code for processing the histogram. They are not configurable by the user prior to run-time. They represent the current state of the record. Many of them are used to process the histogram more efficiently.

The BPTR field contains a pointer to the unsigned long array of frequency values. The VAL field references this array as well. However, the BPTR field is not accessible at run-time.

The MCNT field keeps counts the number of signal counts since the last monitor was invoked.

The WDOG field contains a pointer to the callback control structure and is of no interest to the user.

The collections controls field (CMD) is a menu field with five choices: <CODE>Read</CODE>, <CODE>Clear</CODE>, <CODE>Start</CODE>, <CODE>Stop</CODE>, and <CODE>Setup</CODE>. When <CODE>Read</CODE>, the record retrieves its values and adds them to the signal array. This command will first clear the signal counts which have already been read when it is first invoked. The <CODE>Clear</CODE> command erases the signal counts, setting the elements in the array back to zero. Afterwards, the field is set back to <CODE>Read</CODE>. The <CODE>Start</CODE> command simply causes the record to read signal values into the array. Unlike <CODE>Read</CODE>, it doesn't clear the array first. The <CODE>Stop</CODE> command disables the reading of signal values into the array. The <CODE>Setup</CODE> command waits until the <CODE>start</CODE> or <CODE>read</CODE> command has been issued to start counting.

The CSTA or collections status field implements the CMD field choices by enabling or disabling the reading of values into the histogram array. While FALSE, no signals are added to the array. While TRUE, signals are read and added to the array. The field is initialized to TRUE. The <CODE>Stop</CODE> command is the only command that sets CSTA to FALSE. On the other hand, the <CODE>Start</CODE> command is the only command that sets it to TRUE. Thus, <CODE>Start</CODE> must be invoked after each <CODE>Stop</CODE> command in order to enable counting; invoking <CODE>Read</CODE> will not enable signal counting after <CODE>Stop</CODE> has been invoked.

A typical use of these fields would be to initialize the CMD field to <CODE>Read</CODE> (it is initialized to this command by default), to use the <CODE>Stop</CODE> command to disable counting when necessary, after which the <CODE>Start</CODE> command can be invoked to re-start the signal count.

The WDTH field is a private field that holds the signal width of the array elements. For instance, if the LLIM was configured to be 4.0 and ULIM was configured to be 12.0 and the NELM was set to 4, then the WDTH for each array would be 2. Thus, it is (ULIM - LLIM) / NELM.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>BPTR<TD>Buffer Pointer<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>VAL<TD>Value Field<TD>See BPTR<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>MCNT<TD>Monitor Counts<TD>SHORT<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDOG<TD>Watchdog Callback<TD>NOACCESS<TD>No<TD>0<TD>No<TD>No<TD>No<TD>No<TR>
<TD>CMD<TD>Collections Control<TD>[[RRM 3-14 Menu Choices|RECCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>CSTA<TD>Collections Status<TD>SHORT<TD>No<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>
<TD>WDTH<TD>Element Width<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>No<TD>No<TD>No
</TABLE>

The following fields are used to operate the histogram record in simulation mode. See [[RRM 3-14 Common#Fields Common to Many Record Types|Fields Common to Many Record Types]] for more information on the simulation mode fields.

<TABLE BORDER="1">
<TH>Field<TH>Summary<TH>Type<TH>DCT<TH>Initial<TH>Access<TH>Modify<TH>Rec Proc Monitor<TH>PP<TR>
<TD>SIOL<TD>Simulation Value Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SVAL<TD>Simulation Value<TD>DOUBLE<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIML<TD>Simulation Mode Location<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMM<TD>Simulation Mode<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>No<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>
<TD>SIMS<TD>Simulation Mode Alarm Severity<TD>[[RRM 3-14 Menu Choices|GBLCHOICE]]<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No
</TABLE>

== Record Support ==

=== Record Support Routines ===

==== init_record ====

Using NELM, space for the unsigned long array is allocated and the width WDTH of the array is calculated.

This routine initializes SIMM with the value of SIML if SIML type is CONSTANT link or creates a channel access link if SIML type is PV_LINK. SVAL is likewise initialized if SIOL is CONSTANT or PV_LINK.

This routine next checks to see that device support and a device support read routine are available. If device support includes init_record, it is called.

==== process ====

See next section.

==== special ====

Special is invoked whenever the fields CMD, SGNL, ULIM, or LLIM are changed.

If SGNL is changed, add_count is called.

If ULIM or LLIM are changed, WDTH is recalculated and clear_histogram is called.

If CMD is less or equal to 1, clear_histogram is called and CMD is reset to 0. If CMD is 2, CSTA is set to TRUE and CMD is reset to 0. If CMD is 3, CSTA is set to FALSE and CMD is reset to 0.

clear_histogram zeros out the histogram array. add_count increments the frequency in the histogram array.

==== get_value ====

Fills in the values of struct valueDes so that they refer to the array.

==== cvt_dbaddr ====

This is called by dbNameToAddr. It makes the dbAddr structure refer to the actual buffer holding the array.

==== get_array_info ====

Obtains values from the array referenced by VAL.

==== put_array_info ====

Writes values into the array referenced by VAL.

=== Record Processing ===

Routine process implements the following algorithm:

# Check to see that the appropriate device support module exists. If it doesn't, an error message is issued and processing is terminated with the PACT field set to TRUE. This ensures that processes will no longer be called for this record. Thus error storms will not occur.
# readValue is called. See [[RRM 3-14 Common#Input Records|Input Records]] for more information
# If PACT has been changed to TRUE, the device support read routine has started but has not completed writing the new value. In this case, the processing routine merely returns, leaving PACT TRUE.
# Add count to histogram array.
# Check to see if monitors should be invoked. Alarm monitors are invoked if the alarm status or severity has changed. Archive and value change monitors are invoked if MDEL conditions are met. NSEV and NSTA are reset to 0.
# Scan forward link if necessary, set PACT and INIT to FALSE, and return.

== Device Support ==

=== Fields Of Interest To Device Support ===

The device support routines are primarily interested in the following fields:

<TABLE BORDER="1">
<TH>Name<TH> Summary <TH>Description<TR>
<TD>PACT <TD>Processing Active<TD rowspan=5>See [[RRM 3-14 dbCommon#Fields Common to All Record Types|Fields Common to All Record Types]] for an explanation of these fields.<TR>
<TD>DPVT<TD>Device Private <TR>
<TD>UDF<TD>VAL Undefined<TR>
<TD>NSEV<TD>New Alarm Severity<TR>
<TD>NSTA<TD>New Alarm Status <TR>
<TD>SVL<TD>Signal Value<TD rowspan=2>The device support module retrieves a value from SGNL for SVL<TR>
<TD>SGNL<TD>Signal Value Location
</TABLE>

=== Device Support Routines ===

Device support consists of the following routines:

==== init_record ====

init_record(precord)

This routine is called by the record support init_record routine. It makes sure that SGNL is a CONSTANT, PV_LINK, DB_LINK, or CA_LINK. It also retrieves a value for SVL from SGNL. If SGNL is none of the above, an error is generated.

==== read_histogram ====

read_histogram(*precord)

This routine is called by the record support routines. It retrieves a value for SVL from SGNL.

=== Device Support For Soft Records ===

Only the device support module <CODE>Soft Channel</CODE> is currently provided, though other device support modules may be provided at the user's site.

==== Soft Channel ====

The <CODE>Soft Channel</CODE> device support routine retrieves a value from SGNL. SGNL must be CONSTANT, PV_LINK, DB_LINK, or CA_LINK.

==== Setting up an IOC to use record type ====

The histogram record type is not fully included in EPICS base. To be able to use it, one has to install the record's dbd in the application src directory.
1) Add histogramRecord.dbd to src/Makefile ie. <App>_DBD += histogramRecord.dbd
2) Create a dbd file with following contents saved in src folder. ie. Filename: histogramDeviceSupport.dbd
device(histogram,CONSTANT,devHistogramSoft,"Soft Channel")
3)Add above dbd to src/Makefile ie. <App>_DBD += histogramDeviceSupport.dbd
4)make
Now you can create DB record using the histogram as type.

----

EPICS Record Reference Manual - 19 MAY 1998

Msg.db

2014-07-24T14:30:19Z

TimSouthern:

#
Below is a database that will generate 10 messages, each with an associated time stamp. This database is useful for capturing events such as when an alarm comes in with a brief description of the alarm. One could use the records to display a running log that is written as actions are completed.

The pv <b><i>$(S):info</i></b> triggers the database to process. $(S):info FLNKs to the last message record. The last msg record gets the previous msg value then

----
<pre>
#########################################################################
#Program: msg.db
#Purpose: Creates a set of 10 messages that can be displayed in edm.
#

#MACROS:
# S - application specific identifier
# TIME - defines format to display time PVs. Uses formats defined by the
# linux 'date' command. (ie. "@%x %T" displays "mm/dd/yy hh:mm:ss")

#Author: Tim Southern <southerntb@ornl.gov>
#Created: June 10, 2010
#Updated: Feb. 25, 2012
# - Changed reading a PV for time to reading system using soft
# timestamp record type
########################################################################

record(stringin, "$(S):info")
{
field(DESC, "Info from seq")
field(VAL, "Message db intialized")
field(FLNK, "$(S):msg10")
field(PINI, "YES")
}

record(stringin, "$(S):msg01")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time01")
field(INP, "$(S):info")
}

record(stringin, "$(S):time01")
{
field(DESC, "Message History")
field(DTYP, "Soft Timestamp")
field(VAL, "--------------------")
field(INP, "$(TIME)")
}

record(stringin, "$(S):msg02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time02")
field(INP, "$(S):msg01")
}

record(stringin, "$(S):time02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg01")
field(INP, "$(S):time01")
}

record(stringin, "$(S):msg03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time03")
field(INP, "$(S):msg02")
}

record(stringin, "$(S):time03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg02")
field(INP, "$(S):time02")
}

record(stringin, "$(S):msg04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time04")
field(INP, "$(S):msg03")
}

record(stringin, "$(S):time04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg03")
field(INP, "$(S):time03")
}

record(stringin, "$(S):msg05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time05")
field(INP, "$(S):msg04")
}

record(stringin, "$(S):time05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg04")
field(INP, "$(S):time04")
}

record(stringin, "$(S):msg06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time06")
field(INP, "$(S):msg05")
}

record(stringin, "$(S):time06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg05")
field(INP, "$(S):time05")
}

record(stringin, "$(S):msg07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time07")
field(INP, "$(S):msg06")
}

record(stringin, "$(S):time07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg06")
field(INP, "$(S):time06")
}

record(stringin, "$(S):msg08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time08")
field(INP, "$(S):msg07")
}

record(stringin, "$(S):time08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg07")
field(INP, "$(S):time07")
}

record(stringin, "$(S):msg09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time09")
field(INP, "$(S):msg08")
}

record(stringin, "$(S):time09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg08")
field(INP, "$(S):time08")
}

record(stringin, "$(S):msg10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time10")
field(INP, "$(S):msg09")
}

record(stringin, "$(S):time10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg09")
field(INP, "$(S):time09")
}
</pre>

Msg.db

2014-07-23T22:59:46Z

TimSouthern: Created page with "# Comments ---- <pre> ######################################################################### #Program: msg.db #Purpose: Creates a set of 10 messages that can be displayed ..."

#
Comments
----
<pre>
#########################################################################
#Program: msg.db
#Purpose: Creates a set of 10 messages that can be displayed in edm.
#

#MACROS:
# S - application specific identifier
# TIME - defines format to display time PVs. Uses formats defined by the
# linux 'date' command. (ie. "@%x %T" displays "mm/dd/yy hh:mm:ss")

#Author: Tim Southern <southerntb@ornl.gov>
#Created: June 10, 2010
#Updated: Feb. 25, 2012
# - Changed reading a PV for time to reading system using soft
# timestamp record type
########################################################################

record(stringin, "$(S):info")
{
field(DESC, "Info from seq")
field(VAL, "Message db intialized")
field(FLNK, "$(S):msg10")
field(PINI, "YES")
}

record(stringin, "$(S):msg01")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time01")
field(INP, "$(S):info")
}

record(stringin, "$(S):time01")
{
field(DESC, "Message History")
field(DTYP, "Soft Timestamp")
field(VAL, "--------------------")
field(INP, "$(TIME)")
}

record(stringin, "$(S):msg02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time02")
field(INP, "$(S):msg01")
}

record(stringin, "$(S):time02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg01")
field(INP, "$(S):time01")
}

record(stringin, "$(S):msg03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time03")
field(INP, "$(S):msg02")
}

record(stringin, "$(S):time03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg02")
field(INP, "$(S):time02")
}

record(stringin, "$(S):msg04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time04")
field(INP, "$(S):msg03")
}

record(stringin, "$(S):time04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg03")
field(INP, "$(S):time03")
}

record(stringin, "$(S):msg05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time05")
field(INP, "$(S):msg04")
}

record(stringin, "$(S):time05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg04")
field(INP, "$(S):time04")
}

record(stringin, "$(S):msg06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time06")
field(INP, "$(S):msg05")
}

record(stringin, "$(S):time06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg05")
field(INP, "$(S):time05")
}

record(stringin, "$(S):msg07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time07")
field(INP, "$(S):msg06")
}

record(stringin, "$(S):time07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg06")
field(INP, "$(S):time06")
}

record(stringin, "$(S):msg08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time08")
field(INP, "$(S):msg07")
}

record(stringin, "$(S):time08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg07")
field(INP, "$(S):time07")
}

record(stringin, "$(S):msg09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time09")
field(INP, "$(S):msg08")
}

record(stringin, "$(S):time09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg08")
field(INP, "$(S):time08")
}

record(stringin, "$(S):msg10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time10")
field(INP, "$(S):msg09")
}

record(stringin, "$(S):time10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg09")
field(INP, "$(S):time09")
}
</pre>

Example IOC Databases

2014-07-23T22:13:11Z

TimSouthern:

This page is intended to provide pointers to example IOC databases that implement useful behavior.

* [[msg.db]] - Creates a set of 10 messages that can be displayed in edm.
* [[Persistence.db]] - Simulates scope waveform persistence that can be displayed in edm.
* #

Example IOC Databases

2014-07-23T22:01:54Z

TimSouthern:

Talk:Main Page

2014-07-23T21:21:50Z

TimSouthern:

Program: msg.db<br>
Purpose: Creates a set of 10 messages that can be displayed in edm.<br>
MACROS:<br>
S - application specific identifier
TIME - defines format to display time PVs. Uses formats defined by the
linux 'date' command. (ie. "@%x %T" displays "mm/dd/yy hh:mm:ss")

Author: Tim Southern <southerntb@ornl.gov><br>
Created: June 10, 2010<br>
Updated: Feb. 25, 2012 <br>
- Changed reading a PV for time to reading system using soft
timestamp record type
----
record(stringin, "$(S):info")
{
field(DESC, "Info from seq")
field(VAL, "Message db intialized")
field(FLNK, "$(S):msg10")
field(PINI, "YES")
}

record(stringin, "$(S):msg01")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time01")
field(INP, "$(S):info")
}

record(stringin, "$(S):time01")
{
field(DESC, "Message History")
field(DTYP, "Soft Timestamp")
field(VAL, "--------------------")
field(INP, "$(TIME)")
}

record(stringin, "$(S):msg02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time02")
field(INP, "$(S):msg01")
}

record(stringin, "$(S):time02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg01")
field(INP, "$(S):time01")
}

record(stringin, "$(S):msg03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time03")
field(INP, "$(S):msg02")
}

record(stringin, "$(S):time03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg02")
field(INP, "$(S):time02")
}

record(stringin, "$(S):msg04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time04")
field(INP, "$(S):msg03")
}

record(stringin, "$(S):time04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg03")
field(INP, "$(S):time03")
}

record(stringin, "$(S):msg05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time05")
field(INP, "$(S):msg04")
}

record(stringin, "$(S):time05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg04")
field(INP, "$(S):time04")
}

record(stringin, "$(S):msg06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time06")
field(INP, "$(S):msg05")
}

record(stringin, "$(S):time06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg05")
field(INP, "$(S):time05")
}

record(stringin, "$(S):msg07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time07")
field(INP, "$(S):msg06")
}

record(stringin, "$(S):time07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg06")
field(INP, "$(S):time06")
}

record(stringin, "$(S):msg08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time08")
field(INP, "$(S):msg07")
}

record(stringin, "$(S):time08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg07")
field(INP, "$(S):time07")
}

record(stringin, "$(S):msg09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time09")
field(INP, "$(S):msg08")
}

record(stringin, "$(S):time09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg08")
field(INP, "$(S):time08")
}

record(stringin, "$(S):msg10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time10")
field(INP, "$(S):msg09")
}

record(stringin, "$(S):time10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg09")
field(INP, "$(S):time09")
}

Talk:Main Page

2014-07-23T21:03:53Z

TimSouthern: Message db record example

#########################################################################
#Program: msg.db
#Purpose: Creates a set of 10 messages that can be displayed in edm.
#

#MACROS:
# S - application specific identifier
# TIME - defines format to display time PVs. Uses formats defined by the
# linux 'date' command. (ie. "@%x %T" displays "mm/dd/yy hh:mm:ss")

#Author: Tim Southern <southerntb@ornl.gov>
#Created: June 10, 2010
#Updated: Feb. 25, 2012
# - Changed reading a PV for time to reading system using soft
# timestamp record type
########################################################################

record(stringin, "$(S):info")
{
field(DESC, "Info from seq")
field(VAL, "Message db intialized")
field(FLNK, "$(S):msg10")
field(PINI, "YES")
}

record(stringin, "$(S):msg01")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time01")
field(INP, "$(S):info")
}

record(stringin, "$(S):time01")
{
field(DESC, "Message History")
field(DTYP, "Soft Timestamp")
field(VAL, "--------------------")
field(INP, "$(TIME)")
}

record(stringin, "$(S):msg02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time02")
field(INP, "$(S):msg01")
}

record(stringin, "$(S):time02")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg01")
field(INP, "$(S):time01")
}

record(stringin, "$(S):msg03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time03")
field(INP, "$(S):msg02")
}

record(stringin, "$(S):time03")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg02")
field(INP, "$(S):time02")
}

record(stringin, "$(S):msg04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time04")
field(INP, "$(S):msg03")
}

record(stringin, "$(S):time04")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg03")
field(INP, "$(S):time03")
}

record(stringin, "$(S):msg05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time05")
field(INP, "$(S):msg04")
}

record(stringin, "$(S):time05")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg04")
field(INP, "$(S):time04")
}

record(stringin, "$(S):msg06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time06")
field(INP, "$(S):msg05")
}

record(stringin, "$(S):time06")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg05")
field(INP, "$(S):time05")
}

record(stringin, "$(S):msg07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time07")
field(INP, "$(S):msg06")
}

record(stringin, "$(S):time07")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg06")
field(INP, "$(S):time06")
}

record(stringin, "$(S):msg08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time08")
field(INP, "$(S):msg07")
}

record(stringin, "$(S):time08")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg07")
field(INP, "$(S):time07")
}

record(stringin, "$(S):msg09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time09")
field(INP, "$(S):msg08")
}

record(stringin, "$(S):time09")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg08")
field(INP, "$(S):time08")
}

record(stringin, "$(S):msg10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):time10")
field(INP, "$(S):msg09")
}

record(stringin, "$(S):time10")
{
field(DESC, "Message History")
field(VAL, "--------------------")
field(FLNK, "$(S):msg09")
field(INP, "$(S):time09")
}