Interpret Axis exposure time units before changing shutter limits

Bottom line: Translate an exposure-limit value into a time before changing it. Preserve the sign, unit interpretation and relevant hardware frame-rate context so a copied number does not silently become a different shutter limit.

Source fact: documented behavior

Axis’s Imaging API describes the sensor parameter group as product dependent and instructs readers to check product-specific parameters, defaults and valid values first.

For MaxExposureTime, a negative value represents a number of frames at the frame rate the hardware can generate, while a positive value represents microseconds.

The source’s example interprets -5 at hardware generation of 30 frames per second as 5/30 second, approximately 167 milliseconds; MinExposureTime uses the same value interpretation.

What the source does not establish

Do not substitute a requested stream frame rate for an unverified hardware-generation rate. Do not infer that a numerically valid limit meets a motion-detail requirement. Keep this unit-conversion check separate from shutter architecture, WDR selection and measured recorded cadence. Obtain product-specific context before proposing a frame-based value.

Applicability questions

• Which sensor channel and supported exposure parameters are being read or changed?
• Is the proposed value negative and frame-based or positive and in microseconds?
• What official product information establishes the relevant hardware frame-rate context?
• What operational motion detail must the recorded image preserve after the change?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends documenting the interpreted duration beside every proposed exposure-limit value before applying it.

1. Read the existing supported exposure limits from the exact device and identify the associated sensor channel. Preserve the values exactly, including their signs, and record the product-specific valid range. For a frame-based limit, obtain the hardware-generation context from an appropriate official source or escalate the uncertainty. Do not fill the worksheet with an assumed rate taken from a client’s requested frame-rate field.
2. Use the documentation’s -5 and 30-frame-per-second example as a labeled desk exercise. Have the reviewer calculate 5/30 second and distinguish it from a positive five-microsecond value. For the actual proposed setting, write the analogous duration and its established basis. Review minimum and maximum together without assuming that a larger signed number always represents a longer duration.
3. Apply an approved limit only in an authorized image-quality test. Keep other relevant settings stable and use representative permitted target motion and illumination. Retrieve the recording through the intended review path and compare the required detail with the accepted baseline. If the result misses the task, restore or revise the supported configuration with the owner rather than defending it solely because the API accepted the number.

Verification and evidence

Retain exact before-and-after values, parameter support evidence, the duration calculation and the source establishing any hardware-rate assumption. Separate the desk example from the actual device worksheet. Have another reviewer reproduce the conversion and identify unresolved context before approving a field change.

Keep the permitted recording samples and task assessment alongside the configuration evidence. Record whether the intended motion detail passed, failed or remains untested. This proposed exercise does not establish a universal shutter setting, a measured hardware frame rate or a completed image-quality result.

Official references

• Imaging API — Axis Communications; official VAPIX documentation.

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.