How Exactly Does Startup Calibration Work?

Per Part 75, calibrated parameters are required to run an online calibration within eight hours of coming online, also called the eight-hour grace period. We can automate this for you!

To accommodate, calibrations within an ESC datalogger can be configured with a startup delay so they will trigger at a certain time after startup. This field can be accessed under the Calibration Sequences folder within StackStudio, or by pressing Ctrl-R while viewing the calibration sequence in the logger.

Calibration Delay and Calibration Minute

The Calibration Delay setting specifies how long the calibration will wait after the unit comes online before triggering an automatic startup calibration. This can be set to anything on the minute or hourly basis. Leaving the field set to zero seconds will disable the startup calibration.
The Startup Minute will specify the minute that the calibration should run. Once the calibration delay has finished, the datalogger will wait until the next Startup Minute to begin a startup calibration.

For example, say a calibration is programmed to have a startup delay of one hour, and a startup minute of 05. If the unit comes online at 09:06, the startup calibration will run at 11:05 as it will wait one hour (10:06) and then wait until the next :05 minute. If the startup minute is set to 99, the startup calibration will begin immediately after the startup delay.

Should You Keep Other Cals in Startup?

When this field is set to ‘Y’ (or the box is checked within StackStudio), any other calibration scheduled to run with one or more affected channels in common with this calibration will continue to run as scheduled. When set to ‘N’, any other startup calibrations that share any affected channels will be cancelled once this calibration has completed.

Miscellaneous Notes on Startup Calibrations:

  • The removal of the ‘F’ flag for one or more of the calibrated channels is the trigger that begins the timer for a startup calibration. If the startup delay has finished and one or more of the calibrated channels still has an ‘F’ flag, the startup calibration is delayed until the next startup minute.
  • If a startup calibration is completed successfully either online or offline, no other startup calibration will be scheduled for the next eight hours. So if the unit goes offline before the calibration has finished, that particular calibration is considered to be offline and does not satisfy the eight-hour grace period. A calibration should be run manually if the unit comes back online before another eight hours passes.
  • A unit must be offline for one full clock hour, and must not have run an online calibration within the last eight hours for a startup calibration to be scheduled.
  • All automatic calibrations will be blocked while a startup calibration is scheduled to work. If the calibration is an externally initiated calibration, the trigger to start the calibration is set elsewhere in the configuration and will NOT be blocked by the startup calibration.
  • If a manual calibration is triggered while a startup calibration is scheduled to run, the startup calibration is cancelled.
  • If the unit is offline when the startup calibration is scheduled to run, the startup calibration will continue to be delayed by one hour until eight hours after the startup calibration was initially triggered, in which it will be cancelled.
  • The Startup Delay and Startup Minute fields cannot be configured for an instrument controlled calibration. 
Contact our sales team today to inquire about how our data loggers can work for you.
512-250-7902  •

Clint Anderson, Systems Implementation Engineer, ESC    Published: 10/5/2016 11:47:00 AM

Questions about the ESC Das?

We'd love to answer your questions.

Contact Us

New to Data Acquisition Systems?

Check out our helpful animation that teaches the basics of

What is a DAS?