An auxiliary contact with a large maximum-current rating is not automatically suitable for a low-current PLC input. The purchasing review must establish the contact's applicable minimum-load conditions and the controller circuit's actual burden, then confirm that the complete interface works within both manufacturers' documented boundaries.
A feedback signal can appear satisfactory on a new sample while the quotation still leaves important conditions undefined. The interface may use a different contact option, a lower-current input variant, an intermittent sensing method or an unrecorded previous switching duty. Those differences need to be resolved before they become production substitutions.
This guide provides an RFQ and evidence-review method for a DC contactor's auxiliary feedback circuit. It does not design a safety function, prescribe a wetting resistor, authorize energized testing or prove the state of the main power contacts. Qualified engineering personnel must approve the actual circuit and any evaluation procedure. Purchasing's role is to make the required evidence complete and traceable.
Separate low-load compatibility from mechanical feedback meaning
Start with two questions on different approval lines. First, what physical state does the auxiliary contact represent? Second, can that contact provide the required electrical signal to the selected controller interface? A satisfactory answer to either question does not automatically answer the other.
The DC contactor weld-detection guide addresses auxiliary and mirror-contact meaning and diagnostic limitations. This article focuses on the separate low-current electrical interface. A reliable electrical transition cannot create a mechanical relationship that the contactor manufacturer has not specified.
Likewise, the industrial connector pilot-contact sequencing guide concerns the order and purpose of connection events. Sequencing information does not establish that a particular input circuit provides the load required by a particular auxiliary contact.
Write the intended feedback function in a short requirement statement. Name the contactor, the auxiliary contact identifiers, the controller input and the operating states to be interpreted. Then assign separate owners to the mechanical-state claim, the electrical interface and the system-level interpretation.
Identify every part in the sensing loop
Freeze the full contactor ordering code and the auxiliary option. An optional normally open contact, a normally closed contact and a different auxiliary module may have different documentation. The product-family name is insufficient when the option code determines which contact is actually delivered.
Identify the input hardware by complete article number and revision where relevant. Include the input channel configuration, supply arrangement, interposing devices, wiring reference and any components that influence the sensing path. A label such as "24 V PLC" does not describe the input-current requirement.
Use a loop identifier, for example AF-01, across the circuit drawing, RFQ, supplier response and acceptance record. If an alternative input module is proposed, give that alternative its own controlled configuration. Do not let an equipment-level description hide a component change inside the feedback circuit.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Interface element | Information to freeze | Evidence to request |
|---|---|---|
| Contactor auxiliary | Full code, contact identifiers, NO/NC option | Applicable contact load specifications and instructions |
| Controller input | Exact module, channel and configuration | Input current behavior, thresholds and timing data |
| Control supply | Defined operating range and state | Engineering-approved worst-case interface assessment |
| Wiring and intermediates | Circuit drawing and component references | Voltage-drop, leakage and signal-path assumptions |
| Operating mode | Continuous or sampled sensing | Applicable current amplitude, duration and repetition |
| Contact history | New or previously used, with duty recorded | Traceable sample history and manufacturer limitations |
| Required function | What the receiving controller must recognize | Defined acceptance criteria and responsible reviewer |
The table is a documentation boundary. It does not prescribe a circuit topology or imply that every listed element must be added to the design. Use the elements present in the approved project and keep unknown fields visible.
Distinguish maximum switching, carrying and minimum-load information
A maximum switching rating describes an upper permitted duty under its stated conditions. A carrying-current rating describes another condition. A minimum-load statement addresses a different part of the application range. Record these fields separately, including whether a published minimum is described as a reference value, recommendation or specified operating requirement.
For a concrete DC-contactor example, the Sensata GIGAVAC GX14 datasheet, note 1 on page 4, lists the auxiliary contact at 2 A and 24 VDC resistive load for the stated cycle rating, while its minimum-current entry pairs 0.1 mA with 5 V. These are statements for the specified GX14 auxiliary, not for every GIGAVAC product or every auxiliary contact.
Keep the voltage and current conditions together when extracting that note. The current figure is not a license to use any sensing voltage, nor should the voltage be confused with the small voltage drop across a closed contact. Ask the manufacturer to clarify any ambiguity in how its minimum-load statement applies to the proposed circuit.
As a separate manufacturer example, the Schneider Electric LC1D126B7 datasheet specifies 5 mA minimum switching current and 17 V minimum switching voltage for its signalling circuit. That document describes a different contactor product; it is included to show that minimum-load values are product-specific, not to propose it as a substitute for a battery DC contactor.
Understand wetting current without turning it into a universal setting
Wetting current concerns current used to support reliable behavior of a mechanical switch contact at low signal levels. It is not a synonym for coil pickup current, contactor main current or the maximum current an auxiliary can interrupt. Keep these terms distinct in supplier discussions.
Texas Instruments' SLLA606 application brief discusses switch-input circuits and the role of wetting current in limiting excessive contact resistance associated with surface films. It also distinguishes continuous and polling operation in its interface discussion. This is useful background for asking the right questions; its example circuits and typical values are not settings for an arbitrary contactor auxiliary.
OMRON's minimum-load contact-resistance FAQ explains that film-related resistance can matter at minimum loads and that suitability depends on the circuit consequence. It treats the minimum applicable load and failure-rate reference in context rather than making all contacts interchangeable. Use that guidance to request the offered product's conditions and evidence.
Do not add a resistor, capacitor or pulse source merely because an internet example mentions wetting. Such changes can affect dissipation, open-state behavior, switching duty and diagnostic interpretation. Any proposed solution belongs in an engineering-reviewed circuit revision with manufacturer support and defined acceptance evidence.
Read the PLC input burden from the correct field
A controller module's total power consumption is not necessarily the current through one auxiliary contact. Obtain the input-channel current characteristic and relevant tolerances or limits for the intended voltage range. Distinguish a typical figure from a guaranteed minimum when checking the contact's low-load boundary.
The Beckhoff EL1008 product page provides a clear example of separate fields: it lists a typical input current of 3 mA, a typical input filter of 3 ms, and separate consumption entries for the module's supply domains. Its input-voltage states are also specified independently. These values describe that module, not all PLC inputs.
A typical 3 mA value cannot be promoted into a guaranteed worst-case minimum without additional evidence. Nor should the module's aggregate consumption be used to claim that an auxiliary contact sees a larger burden. Ask the controller supplier or design authority for the relevant channel behavior at the actual operating extremes.
Keep the input's recognized high and low states separate from the contact's switching-load conditions. One side of the review asks whether the contact is being used appropriately; the other asks whether the controller will correctly interpret the resulting signal. Approval needs both, including any defined open-state leakage and voltage-drop assumptions.
Request a two-sided interface assessment
Have engineering define the supply extremes and relevant environmental conditions for AF-01. Ask for the minimum and maximum current through the auxiliary under those conditions, along with the basis for each value. A single nominal operating point leaves the qualification incomplete.
The assessment should also address the input signal levels in the commanded or expected open and closed states. Identify any wiring or intermediate components that affect those levels. Purchasing should request the documented result rather than calculate a safety-related threshold from a catalog thumbnail.
Preserve tolerances in the evidence. A calculation using typical component values is a different deliverable from one that establishes coverage of specified limits. If the only available value is typical, record the missing bound as an open item and ask who will supply or justify it.
For sampled sensing, include when current is applied and when the controller evaluates the input. A reported peak current without its duration and schedule may not answer the contact supplier's low-load question. The reviewer should identify the applicable operating mode, not average a pulse train into an assumed equivalent continuous load.
Treat contact history as part of the sample identity
Record whether the auxiliary is new and what loads it has previously switched. A sample used for one evaluation should not silently become a representative sample for a different duty. Keep the contact identifiers and serial or lot references connected to its operating history.
If the vendor proposes a particular contact material or construction for low-level switching, request the exact product documentation. Do not infer suitability from a generic claim such as "gold contacts." The actual contact design, permitted duty and manufacturer instructions remain relevant to the specified part.
Ask whether any prior high-load operation changes the permitted low-load use for the offered contact. The answer must come from applicable manufacturer documentation or a project-specific technical response. An unused terminal on a previously exercised device is not necessarily evidence that the corresponding contact has an untouched history.
The purchase specification can require traceable new samples for an agreed low-load evaluation without inventing a universal service-life rule. Define which changes or prior uses require review, who makes that decision and what information must accompany a replacement device.
Compare hypothetical bids against one low-current loop
The following circuit requirements, component labels, figures and supplier responses are hypothetical procurement examples. They are not a proposed circuit or test result for any real product. Assume the design authority defines AF-01 as a nominal 24 VDC sensing loop and provides an approved assessment showing 2.0 to 2.8 mA through the closed auxiliary across its specified operating range.
The RFQ requests applicable low-load support for that entire range, plus separate approval of voltage conditions, input states and feedback meaning. It does not ask the buyer to conclude compatibility from the maximum contact rating.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Hypothetical offer | Submitted evidence | RFQ disposition |
|---|---|---|
| A | Auxiliary maximum rating of 3 A; no minimum-load statement | Hold: a high maximum does not establish low-current suitability |
| B | Minimum stated as 5 mA at the required switching-voltage condition | Hold: AF-01's documented current range is below the stated minimum |
| C | Applicable statement covering 1 mA at the stated voltage and AF-01's operating conditions | Advance the low-load review, subject to all other interface gates |
| D | Claim that an added interface will provide sufficient current | Hold pending a controlled circuit revision and supporting evidence |
The comparison does not make C an unconditional product approval. The supplier must still identify the exact auxiliary option, contact history assumptions and any duty or environmental restrictions. Mechanical feedback meaning, controller interpretation and system safety assessment remain separate.
Preserve a filled exception record when a revision changes the load
Suppose the controller team changes the hypothetical input module from IM-A to IM-B to reduce control power. The revised AF-02 assessment shows 0.7 to 1.1 mA instead of 2.0 to 2.8 mA. Offer C's 1 mA minimum statement no longer covers the full range, even though the nominal voltage and contactor remain unchanged.
Record exception EX-AF-04 as "minimum current 0.7 mA below the supported 1 mA condition; evidence pending for AF-02." Retain the AF-01 approval, its drawing and its limits. Do not overwrite the old range or present the earlier acceptance as valid for the replacement module.
The useful next action is a reviewed alternative input, an applicable manufacturer statement or an approved interface redesign. The buyer should not round 0.7 mA up to 1 mA, use the 1.1 mA upper value, or average the range to erase the uncovered condition.
Review sensing behavior and timing without claiming fault coverage
Ask for a clear definition of what the input record represents: raw electrical state, filtered state or an interpreted controller status. A filter can change how a short transition appears to software. Its existence does not prove contact reliability or correct mechanical-state inference.
Keep the component response, input filtering and application-level timing assumptions separate. Request engineering's approved criteria for the complete function rather than deriving a permissible diagnostic delay from one product's typical filter entry. Typical timing data should remain identified as typical.
If the project uses diagnostic pulses or polling, identify the actual current waveform and sampling schedule in the interface documentation. Ask both relevant suppliers to state whether their evidence covers that mode. A statement about continuous operation may not settle an intermittently energized interface.
Avoid using an apparently stable signal as proof that every fault is detected. A wiring error, input fault or unsupported mechanical assumption may still require consideration by the system designer. Procurement can require the assessment record without inventing a diagnostic coverage percentage or claiming a safety certification.
Specify evidence for a professional sample evaluation
Where catalog information leaves a gap, agree the evaluation question first. Define the exact parts, circuit revision, operating conditions and required signal behavior. Identify the manufacturer or competent laboratory responsible for the work and the design authority responsible for accepting its scope.
Request sample identities, preparation and previous duty, the applicable procedure revision, observation records and deviations. Ensure the evaluation represents the actual low-current loop rather than a higher-current continuity check that changes the condition being examined. The method and equipment choices belong to the qualified evaluation team.
A successful new-sample observation is one piece of evidence. Ask how the agreed plan addresses relevant operating history, environmental exposure and intended duty where required by the project. Do not attach an invented cycle count or reliability percentage simply to make the report look quantitative.
If a result is intermittent, preserve the individual events and investigation. Repeating an operation until a favorable result appears is not a substitute for explaining the original observation. Record any replacement, adjustment or circuit change and determine whether the revised sample still represents the agreed configuration.
Send your auxiliary-contact code, controller input data and sensing-loop drawing for an RFQ review. Include the missing minimum-load or current-bound evidence so the supplier can respond to a defined question.
Compare alternatives without concealing added responsibilities
An alternative auxiliary option, dedicated signal interface or different input module may be reasonable, but each changes the evidence package. Request a controlled drawing and bill of materials for every proposed solution. State who approves the new component selection and its effect on the required function.
An interposing device adds another interface to review. Its input and output sides, power requirements, state behavior and relevant failure assumptions cannot be treated as automatically solved because it is sold as an interface module. The procurement decision should include the necessary supporting documents.
Ask the bidder to quote documentation, samples and any agreed evaluation separately from production hardware where useful. A lower hardware price may create additional engineering or qualification work. Comparing the same scope makes that cost visible without assuming that the cheapest component is the least expensive approved solution.
The OEM/ODM service page is an entry point for discussing an assembly project. Availability of a particular component, supported engineering work, test capability, minimum quantity, pricing and delivery still require written project-specific confirmation. None is established by this guide.
Carry the approved interface into purchasing and replacement control
The released purchasing record should reference the contactor code, auxiliary option, controller input, loop drawing and accepted evidence. A substitution process should identify changes to any of those elements, including firmware or configuration changes that affect sensing behavior.
Receiving checks should confirm identifiers and required documentation against that record. They should not replace the engineering assessment with an improvised energized check. Define any sample or production acceptance activity through the approved quality plan, with responsible personnel and methods identified.
Keep an exception list with owners and closure evidence. Useful entries include missing input-current bounds, unsupported polling mode, ambiguous minimum-load wording, unknown contact history and a proposed input-module substitute. Each item should close through an identified document or approved change, not a general sales assurance.
Retain the original release and later revisions so a service replacement can be matched to the supported configuration. The knowledge center provides related guides on contactor duty and wiring evidence, but the released project documents remain the controlling reference for the actual assembly.
Distinguish a closed document gap from a redesigned interface
Use separate closure categories in the exception list. A missing datasheet page can close by receiving the applicable document. An inadequate current range may require a changed component or circuit. Those outcomes have different effects on drawings, purchasing codes and later replacement decisions, even if both eventually receive an approval signature.
For the hypothetical AF-02 example, record whether the accepted solution restores a supported input-current range, changes the auxiliary option, or introduces a new interface. Reference the actual approved revision and identify which earlier conclusions remain applicable. Do not close EX-AF-04 with only "supplier confirmed" when the supplier's response assumes a different module.
Give the commercial team a clear release status for each configuration: approved within documented scope, awaiting evidence, or superseded by an approved alternative. That prevents an obsolete but inexpensive quotation from being ordered accidentally after engineering has moved to another solution. Retain the earlier price and technical response for traceability without presenting them as current release authority.
A final handoff should also name the owner who maintains the controller configuration. Purchasing may control hardware part numbers but cannot by itself prevent a later sensing-mode change. Connecting these responsibilities makes the low-load review maintainable after the first order.
FAQ
Why is a high-current auxiliary contact not automatically better for a PLC input?
Its maximum rating answers an upper-duty question. Low-current suitability depends on the applicable minimum-load conditions and the real sensing circuit. Request both sides of the interface evidence before treating a larger maximum-current figure as an advantage.
Is wetting current the same as contactor coil current?
No. Coil current operates the contactor mechanism; wetting current concerns the mechanical contact's sensing or switching interface. Main-contact load current is another quantity. Use separate labels and documents so information from one circuit is not applied to another.
Can a typical PLC input-current value prove compliance with a contact minimum?
A typical value alone does not establish the minimum across the operating range. Obtain the required bounds or an applicable manufacturer-supported assessment. Also confirm the voltage conditions and operating mode; nominal current is only part of the compatibility question.
Should I add a resistor when the input current is too low?
Do not make that change as a purchasing shortcut. Engineering must assess any proposed interface modification, including dissipation, switching conditions and recognized input states. Require a revised circuit and applicable evidence rather than copying a generic wetting-current example.
Does a successful continuity check establish long-term low-load reliability?
No. The check has its own electrical conditions and observes a particular sample state. Ask for an evaluation that represents the specified interface and relevant duty. Keep its scope and limitations visible rather than turning one favorable observation into a service-life claim.
Does suitable low-load behavior prove welded-main-contact detection?
No. Electrical interface compatibility and the auxiliary's documented mechanical relationship are different approvals. The system designer must establish the required diagnostic interpretation and limitations. A clean input signal alone does not prove that the main power path is safely open.
What information is needed for a useful quotation?
Provide full contactor and auxiliary codes, input-module details, loop drawing, supply range, current evidence, sensing mode, environmental conditions and required documentation. Add quantity and destination for commercial review. Price, delivery and any evaluation capability need specific written confirmation.
Send a low-load auxiliary-contact RFQ
Make the qualification question explicit: the offered auxiliary must be supported for the actual sensing loop, including its lowest relevant current and its documented voltage and operating conditions. Keep that electrical decision linked to, but distinct from, the mechanical feedback and system-function approvals.
Send your contactor auxiliary and PLC input evidence package. A complete interface record helps suppliers explain what is supported, identify genuine gaps and quote the work needed to resolve them before production release.