Micromod MOD: 30ML and Modcell Maintenance for 2001N, 2002N, and 1800R - Manual (Page 145)

Instrument Overconfigured
Diagnostic alarm in MOD
30ML/Modcell
Problem Description:
The overconfigured diagnostic indicates that it is taking longer than the configured time to execute the
database. This usually is not a problem, if it occurs occasionally. If the diagnostic is continuously active,
the database should be revised to correct the error.
Applies to:
MOD 30ML and MODCELL Multiloop Processor
Solution:
There are nine scan intervals, 1 through 5 are for user configured functions, 6 is for the Interface Block itself,
and 7 through 9 are for communication channels. Scan intervals 1 through 5 can be configured in increments
of 50mS. Scan interval 6, which is fixed at 50mS, is for managing instrument states, diagnostics, events and
I/O. Scan intervals 7 and 8 are for managing the communications ports one and two. Scan interval 9 is for
communications port 3 on Modcell MultiLoop Processor, or the display and built-in I/O on the MOD 30ML.
Scan intervals 7 through 9 are fixed at 50mS for installed ports and set to zero for unused ports.
To accurately determine the scan times, the instrument must be configured, in the RUN state, and with valid
I/O connected. Using the Application Builder status screen, issue the command CLR_MT to reset all MTIME
values to zero. If these attributes are not zeroed after startup, they may represent a startup “surge” in some
cases. After waiting a few minutes, or longer if required for supervisory messages or event-triggered
operations to be executed, issue the command R XTIMES and record the MTIME values. From these
readings, it can be determined to what degree the instrument is overconfigured. It is easiest to base the
calculations on the shortest scan interval, which is 50mS.
Topic: MOD 30ML/Modcell Technote: TNML0302-2
MicroMod Automation, Inc. Rev. 2, Mar-2002
Overconfig.doc Page 1 of 2