Ultimo aggiornamento: 7 ottobre 2026
Risposta rapida: Power supply overload recovery describes a component’s response to a fault. It does not specify the controller’s retained state or authorize equipment to restart. An OEM acceptance record should name three separate owners: the power-supply evidence owner, the control-state owner and the equipment restart-permission owner. The WEHO HDR-100-12 sample below illustrates that documentary distinction; it is not a verified load selection, completed installation or fault-test result.
Give “recovery” an owner before accepting it
An equipment requirement that says “the system recovers automatically” can conceal three different promises. The power supply might resume output after its overload condition clears. The controller might resume a previous state, initialize to a different state or require a separate action. The equipment might remain inhibited even after both electrical and control conditions have changed. A statement about one of these layers does not establish the behavior of the others.
For engineering and procurement teams, the useful question is therefore not simply whether a product lists overload protection. Ask what the supplier’s statement covers, which revision supports it, who accepts the associated behavior and which downstream decisions remain open. This keeps a component description from becoming an undocumented machine-start instruction.
This article uses power supply overload recovery as an acceptance-record topic. It does not prescribe a wiring arrangement, choose a connected load, calculate operating headroom or instruct a technician to create an overload. Those decisions require evidence for the ordered product and actual equipment.
Use the HDR-100-12 as a bounded documentary example
The retained real sample photographs identify the full model as WEHO HDR-100-12. Its nominal input marking is 100–240VAC 3.0A, 50/60Hz, and its output marking is 12V DC 7.5A. The source also prints Max.7.5A Max.90Watt and the separate adjustment marking 12~13.8V. The latter is not the nominal output, an observed setting or proof that any connected equipment is compatible. Do not apply the series’ 100 W description universally to this 12 V sample.
IL official WEHO HDR-100 product page distinguishes the 12 V, 15 V, 24 V and 48 V full-model variants. Both it and the retained complete sheet describe overload output cut-off with automatic recovery. Their overload percentage ranges differ: the retained sheet states 105–150%, while the current public table states 105–160%. This example preserves that source difference rather than choosing a threshold or prescribing a fault test. A separate overvoltage row’s hiccup description is not evidence of overload’s internal behavior.
The retained complete mechanical drawing establishes 70 mm front width × 90 mm height × 54.5 mm body depth. A separate dimension shows a 58.4 mm maximum including the rear clip. These are distinct mechanical extents, not interchangeable depth values or an installation-clearance guarantee. Keep the sample photograph and full drawing together, then obtain the applicable ordered revision before an actual fit decision.
The actual rear photographs show molded upper hooks and a lower black plastic release engaging a DIN rail. This is a rail-mounted product, not a chassis-only enclosed supply. The six contacts are divided between four upper DC positions and two lower AC positions. A photograph and external drawing do not establish approved conductor access, installation clearance or compliance of a finished machine. The final illustrations retain the real full-model front marking and use the independently photographed left and right sides rather than inventing a mirrored face.
Record the component claim separately
Start the component section of the acceptance record with the exact full model, the applicable supplier document and its revision. “HDR series” alone is not enough when different voltage variants or revisions are being evaluated. Keep the actual photograph, nameplate fields and the complete specification together, with any differences clearly assigned to their sources.
Then state the limited proposition being reviewed: the component documentation describes recovery associated with overload protection. Identify what remains to be confirmed for the ordered revision, including whether the particular protective event and recovery condition fall within the accepted supplier statement. Do not insert an invented reset delay, retry interval or current threshold merely to make the record appear complete.
A useful record has room for uncertainty. If the public page and retained sheet use different protection wording, list both sources and assign reconciliation to the component evidence owner. Mark that item as unresolved until appropriate ordered-revision evidence is supplied. “Unresolved” is more informative than a merged description that neither source actually supports.
The record should also distinguish documents from observations. A supplier statement is documentary evidence. A photograph establishes the visible sample identity and construction. A completed equipment test would be a different evidence item, with its own configuration and acceptance criteria. None should silently substitute for the others.
Put the control-state question in a different record
The control-state owner should describe the required state after the relevant disturbance, including which state information is retained, reinitialized or awaiting a separate decision. These are requirements for the control architecture, not properties inferred from the power-supply model suffix or nameplate voltage.
The control-state record can reference the component evidence without inheriting its conclusion. It should identify the applicable controller configuration, software or logic revision and the source of the required behavior. If those items are not yet established, retain an open item instead of calling the controller’s response automatic.
This separation matters during procurement handover. A buyer may accept that the specified power-supply document contains a recovery statement while still requiring the control team to define an initialization state. Conversely, an accepted control-state requirement does not resolve a disputed component revision. The approvals answer different questions.
This textile-equipment illustration is a dry prewiring review context. The source-exact supply is visible in the left part of the open equipment panel; it is not shown energizing heaters, drives or controls. The surrounding roller arrangement identifies the equipment domain, not a verified power relationship. The illustration therefore cannot be used to infer suitability for the machine’s actual electrical demand.
Reserve restart permission for the equipment owner
The equipment restart-permission owner has a separate decision to document: when, and under whose requirements, the equipment may resume its operation. Component output availability is not itself that permission. The owner’s record should reference the applicable equipment requirements and outstanding dependencies without inventing a universal reset instruction.
For example, a project might still need to accept the intended operator interaction or the relationship between an initialization state and the next permitted operation. This article does not select those behaviors. It explains why they should not be accidentally settled by the phrase “automatic recovery” in a power-supply document.
Avoid a single shared checkbox called “recovery passed.” It can hide disagreement about what was accepted. Three distinct acceptance entries make it possible to identify the open layer, the responsible person or team and the evidence needed to close it. They also prevent a purchasing approval from being interpreted as a completed equipment-level demonstration.
Use different equipment contexts without inventing compatibility
The second application illustration uses a dimensional-metrology bridge, stone table and ruby-tipped probe beside the open review panel. It differs from the textile review in equipment domain, layout, product position and source-supported view: the sample occupies the right side, and the camera uses the genuinely photographed right side from a higher angle. The background screen shows a crosshair rather than numerical measurement results. The visible equipment context does not demonstrate a measurement, a completed supply connection or a recovery test.
Neither illustration establishes an actual input supply, a connected load, an adjustment setting or successful overload recovery. All sample terminals remain unconnected, and no indicator or display is presented as a recorded operating result. These images make the documentary discussion concrete while preserving the difference between an illustrative equipment context and a qualified product application.
The scenes use an actual 35 mm DIN rail as their intended dimensional reference. Compare the enclosure’s 90 mm rear-body height with adjacent rail lips only when both are visibly in the same backplate plane. The nominal relationship is 90:35, approximately 2.571:1; a front-face height at another depth is not a substitute. This is a visual review aid, not a precision measurement certificate. Actual final perspective, edge visibility and mounting contact must be independently accepted; writing dimensions in a prompt does not prove that the image follows them.
Build a handover register that keeps open items visible
A practical handover register separates identity, evidence, required behavior and acceptance status. For the component record, include the full model, the exact retained source and the ordered-revision document still required. For the control-state record, identify the configuration owner and the requirement governing retained or initialized state. For restart permission, identify the equipment owner and the requirement that governs the next permitted operation.
Each entry should name its evidence location and describe the limit of that evidence. A nameplate photograph should not be filed as a restart test. A mechanical drawing should not be filed as proof of electrical compatibility. A purchasing confirmation should not silently replace an engineering acceptance entry. This discipline makes an incomplete handover intelligible instead of superficially complete.
Give unresolved differences their own entries. The retained overload range and public overload range, for example, are distinct documentary facts. Neither authorizes a performed test or settles a particular ordered revision. Likewise, the 54.5 mm body depth and 58.4 mm rear-clip maximum have different mechanical meanings. Keep those meanings clear instead of combining them into an assumed installation envelope or clearance decision.
Reopen the affected acceptance entries after a revision change
A new product revision, controller configuration or equipment requirement should trigger a review of the affected acceptance entries. That does not mean every old record becomes false. A retained photograph still records the sample that was photographed. A previous document still records what its particular edition stated. What changes is whether those records remain applicable to the current order and equipment configuration.
Identify the changed item before deciding the scope of reacceptance. A new dimensional drawing may require the mechanical fit record to be reconsidered. A changed protection description may affect the component recovery entry. A revised controller initialization requirement belongs to the control-state review. An equipment restart-permission change is not resolved merely because the power supply’s model marking is unchanged.
Keeping original records alongside the new evidence avoids retrospective rewriting. Record the old source, the new source, the applicable scope and the owner responsible for the decision. If relevance has not been established, leave the entry pending rather than claiming continuity from a similar photograph or a matching family name.
The engineering map is conceptual. Its three cards are separate records, not a measured time sequence or an instruction to connect terminals. It deliberately contains no invented load values, fault waveforms, reset delays or machine-start commands.
Punti chiave
- Power supply overload recovery is a component-level statement, not automatic equipment restart permission.
- Keep component evidence, controller state and equipment permission under separate acceptance owners.
- Preserve exact sample identity and source-specific revision differences rather than merging them.
- Treat dry application illustrations and dimensional checks as review material, not installation or fault-test evidence.
- Ask for the ordered full-model revision before closing mechanical, electrical or behavior-related open items.
Conclusione
The most useful power supply overload recovery requirement says who accepts which behavior and what evidence supports that acceptance. The retained HDR-100-12 sample makes the distinction visible, but it does not close an unspecified equipment application. Keep component recovery, control state and equipment restart permission separate, preserve unresolved revision differences, and use WEHO's contact channel to request documentation for the exact ordered revision.
Domande frequenti
Does power supply overload recovery mean equipment restarts automatically?
No. A component recovery statement does not establish the controller’s state or authorize equipment to restart. Record and accept those three responsibilities separately.
What does the retained HDR-100-12 sample label show?
The actual sample is marked HDR-100-12, nominal input 100–240 VAC, 3.0 A, 50/60 Hz and output 12 V DC, 7.5 A, with Max.7.5A Max.90Watt. The separate 12~13.8V adjustment marking is not a nominal output or an observed setting. These are identity fields, not a qualified connected-load result.
Which dimensions are used in the illustrations?
The complete retained drawing gives 70 mm front width, 90 mm height and 54.5 mm body depth. The 58.4 mm rear clip maximum is a separate mechanical extent, not a fourth body axis or clearance guarantee. Actual installation requires its applicable ordered drawing.
Are the application images completed installations or recovery tests?
No. They are dry documentary-review contexts with unconnected sample terminals. They do not demonstrate actual input, load compatibility, an adjustment setting, a measured protection waveform or equipment restart behavior.
What should procurement request before accepting a recovery requirement?
Request the exact full-model and ordered-revision evidence, retain source differences as open items, and identify separate owners for component behavior, control state and equipment restart permission.
