The Factory Setting You Must Change on Install
Why this matters
Equipment ships with safe, generic factory defaults so it survives shipping and powers up without hurting anything. Those defaults are not your settings. They are placeholders that assume nothing about the building, the load, or the application. A unit left on its factory defaults will often run, which is exactly the trap: it looks commissioned but it is mis-set, and it short cycles, underperforms, trips, or quietly runs inefficient for years. Knowing which defaults must be changed on every install separates a unit that was installed from a unit that was commissioned.
The principle: defaults are a starting point, not a setting
A factory default is chosen to be harmless across the widest possible range of installs. Harmless is not optimal, and it is frequently wrong for your specific application. The manufacturer cannot know your size, your distances, your conditions, or your local rules, so they ship a neutral value and expect the installer to set the real one. When you skip that, you have left the manufacturer's guess in place of your knowledge.
The discipline is simple: assume every adjustable shipped at a default needs to be reviewed and set to the application, and prove you have done it by recording the as-set value.
Settings that almost always need changing
These are the usual defaults that bite when left alone. The categories are generic on purpose; the exact parameters depend on the equipment.
- Size or capacity selection. Many units ship sized for a range and must be told the actual capacity for this install. Left wrong, the unit cycles incorrectly or never satisfies.
- Application or operating mode. A default mode may not match how this unit is used. The wrong mode produces backward or partial operation.
- Limits and cutouts. Default protective limits are often conservative. They may need setting to the design conditions so normal operation does not trip them, or tightening so a real fault is actually caught.
- Speeds, flows, and output levels. Defaults rarely match the actual demand. Left wrong, the unit overworks, underperforms, or makes noise.
- Time delays. Default delays may be too short for this install (hard cycling) or too long (sluggish response).
- Sensor and addressing setup. Defaults may not match the sensors or the network this unit lives on, producing phantom faults.
Settings driven by safety or code
Some defaults are not just about performance. Leaving them generic can be a safety or compliance problem.
- Protective setpoints that must match the local conditions to actually protect.
- Lockouts and interlocks that ship permissive and must be set restrictive for the application.
- Anything governed by local rules. A factory default is set for a generic jurisdiction; your local code may require a different value. When safety or code is involved, the correct value is not optional, and the default is not a defense.
When a default touches safety or code, treat changing it as part of making the install safe, not as a tuning nicety.
How to know which defaults to change
You do not have to memorize every unit. You need a method.
| Step | What you do |
|---|---|
| Read the commissioning section | The documentation lists which parameters require setting for the application |
| Compare default to nameplate and design | A default that does not match the actual conditions needs changing |
| Look for "set for application" language | Manufacturers flag the placeholders you must replace |
| Check anything protective or code-related | These get verified against local requirements, not left generic |
| Record every as-set value | Proof it was reviewed, and a baseline for later |
The habit that protects you: walk the commissioning parameter list on every install, decide each one, and write down what you set. A parameter you consciously left at default is fine. A parameter you never looked at is a future callback.
Why this is a diagnostic skill, not just an install skill
When you arrive at a unit that runs badly, "is it still on a factory default" is one of the first questions to ask. A short cycle, a nuisance trip, a performance complaint, or a phantom fault on a recently installed unit very often traces to a default that was never changed. Reading the as-set values against the application is faster than chasing the symptom as a part failure, and it catches the install error the original crew left behind.
The mental model to keep: the factory ships a safe guess; commissioning replaces the guess with your knowledge. A unit running on defaults is a unit nobody finished setting up.
References
- Manufacturer commissioning and parameter-setting documentation
- Trade-standard practice for configuring equipment to the application
- Applicable local codes for protective setpoints and interlocks
- See related: Right Part, Wrong Setting on Startup (decision tree); Commissioning Readings to Record as a Baseline; The Startup Sequence That Catches Install Errors