News Center

——  NEWS CENTER  ——

News Center
Contact Us

Xi'an Shenghongchuang Instrument Co., Ltd.

Contact: Mr. Zhang

Mobile: 15529283736
Email: shc-sensor@qq.com

Address: Fortune Building, Sanqiao Street, Xixian New Area, Xi'an, Shaanxi Province

When wiring a 24V liquid level sensor, which mistakes are most common?
Added to Favorites:125

What are the most common mistakes when wiring a 24V level sensor?

When wiring a 24V level sensor, the most common mistakes are usually not as simple as “the wires are connected but there is no response”, but rather mixing up the power supply type, output mode, common terminal definition, and load wiring method. More common errors include reversing the positive and negative poles, wiring an NPN as a PNP, wiring a two-wire device as a three-wire device, ignoring the controller input type, improper handling of the shield layer and ground wire, and failing to perform insulation and interference checks first in humid environments.

This issue is worth confirming first because wiring errors often do not just cause a one-time “it does not work” problem, but may also lead to false alarms, signal drift, relay misoperation, and even make subsequent troubleshooting much slower. What truly affects the result is not the wire color itself, but first confirming whether the sensor’s power supply method, output type, load path, and control terminal are matched.

Why does the device still not work even though it was wired according to the wire colors?

If you only wire according to the wire colors without checking the wiring definitions, then even if the colors “look correct”, it may still be wired incorrectly, because the meanings of wire colors are not necessarily exactly the same across different models, manufacturers, and output modes.

The more common practice is to first check the nameplate, manual, or lead definition, and then confirm the functions of the power positive and negative, signal wire, and common terminal. Level sensors commonly come in two-wire, three-wire, and four-wire types. Under different structures, the functions of brown, blue, and black wires may be similar, but they cannot be directly assumed to be completely universal.

If it has already been wired on site but there is no output, the first priority is not to check “whether the sensor is faulty”, but whether the power supply is actually in place, whether the common terminal is connected, and whether the load is wired in the wrong position. Many rework cases happen because this step is judged too quickly and components are replaced directly, which instead delays troubleshooting.

Which types of mistakes are most likely to burn out the sensor or the input terminal?

If the polarity of the 24V power supply is reversed, or an incompatible output mode is directly connected to the controller input terminal, then the most likely risk is not simply no signal, but damage to the input port, abnormal heating of components, or reduced long-term stability.

Common high-risk errors include reversing the power supply polarity, mistakenly connecting the signal wire to the power terminal, directly connecting a transistor output to an unmatched high-level input, ignoring external load requirements, and powering on directly without confirming the input tolerance range. Whether damage will definitely occur depends on the sensor’s internal protection design and the protection capability of the control terminal, but “it lights up by luck” should not be taken as proof that it was wired correctly.

If the controller, PLC, or display instrument in the project is more expensive, then the input terminal should be protected first before checking the sensor. This is because replacing a sensor is relatively straightforward, but once the input module has a problem, the subsequent downtime and troubleshooting costs are usually higher.

What typical problems will occur if NPN, PNP, or relay outputs are wired incorrectly?

Whether it is easy to wire incorrectly mainly depends on whether you first distinguish the output type; the fundamental difference among NPN, PNP, and relay outputs lies in “how the signal forms a circuit”. After the wiring methods are mixed up, the most common result is that the sensor operates, but the controller cannot recognize it.

An NPN output is usually a sinking type, and the common method is for the load to connect to the power positive terminal, then the sensor pulls the circuit toward the negative terminal; a PNP output is usually a sourcing type, with the logic direction reversed; a relay output is more like a switch contact, usually with broader compatibility, but the contact capacity and external circuit voltage still need to be confirmed. What truly determines wiring success is not the name, but which signal logic the controller input requires.

If the control side has already been fixed as a certain type of input, then choosing the wrong output type will make later rewiring more troublesome. In some scenarios, this can be handled through an intermediate relay, isolation module, or interface conversion, but this is a remedy, not the preferred solution.

Which checks must be done before power-on, and which can be postponed?

If the goal is to reduce rework and misjudgment, then the power supply polarity, output type, controller input mode, load wiring method, and on-site insulation status should usually all be confirmed before power-on; while sensitivity fine-tuning, installation position fine adjustment, and alarm point optimization can be postponed to later verification.

What is done before power-on determines “whether errors will occur”; what is done after power-on affects more “whether it works well”. Many on-site problems are not due to insufficient sensor performance itself, but because the preliminary confirmation was skipped, causing the system to enter troubleshooting status as soon as it is powered on.

If the installation environment is humid, the liquid is conductive, the cable is long, or it is laid in parallel with power lines, then interference and insulation checks should be moved even further forward. This is because such problems may not be exposed immediately during short test runs, but are more likely to turn into intermittent faults during long-term operation.

Under what circumstances is it not recommended to test and wire at the same time on site?

If the wiring diagram is incomplete, the controller model is unclear, the level sensor output mode has not been confirmed, or the site has conditions such as humidity, metal containers, or strong-interference motors, then it is usually not recommended to test while wiring, because this approach easily mixes “wiring problems” with “environmental problems”.

The more common practice is to first perform static confirmation away from the process site, and then connect it to the system. For example, first confirm whether the power supply is stable, whether the sensor output changes when it operates, and whether the controller input terminal expects to receive a high level or a low level, and then decide the final wiring method. The value of doing this is to narrow the fault scope, not to add more test steps.

If the project has already entered the joint commissioning stage, testing while modifying may sometimes be unavoidable, but at the very least variables should be fixed first: change only one connection point or one parameter at a time. Otherwise, even if the system returns to normal, it will still be difficult to determine where the real problem came from, and subsequent maintenance personnel will also find it harder to take over.

Comparison of common wiring errors and key judgment points

常见错误>Common errors典型表现>Typical manifestations优先检查项>Priority inspection items返工成本>Rework cost是否建议前置确认>Whether preliminary confirmation is recommended后续限制>Subsequent limitations
Positive and negative terminals connected in reverseNo output, overheating, protection activatedPower terminal definition, polarity markingMedium to highYesMay damage components
Connecting NPN as PNPThe sensor operates but the controller does not respondOutput type, input logicMediumYesRewiring or adding a conversion interface may be required
Connecting a two-wire system as a three-wire systemContinuous alarm or no action at allNumber of wires, load series connection methodMediumYesEasily misjudged as a product fault
Common terminal not shared to ground or incorrectly connectedSignal drift, intermittent triggeringCommon terminal definition, circuit integrityMediumYesCommissioning time increases
Shield layer and ground wire connected incorrectlyHigh interference, false operationWiring environment, grounding methodLow to mediumDepends on the environmentPoor long-term stability
Input-end compatibility not confirmedAbnormal readings or input damageController input specifications, isolation methodHighYesMay affect the entire system

From the perspective of judgment priority, the first errors to eliminate should be those that may cause component damage or widespread misjudgment, such as polarity, output type, and input compatibility. Cable shielding and grounding are also important, but they should usually come after “confirming that the basic circuit is correct”.

What are the differences in common on-site wiring paths?

接线路径>Wiring path适用场景>Applicable scenarios前置条件>Prerequisites优点>Advantages限制与风险>Limitations and risks迁移难度>Migration difficulty返工成本>Rework cost
Sensor directly connected to PLC inputClear control logic, matched input portNPN or PNP confirmed, common terminal clearly identifiedSimple wiring, short troubleshooting pathHigh risk when inputs are incompatibleMediumMedium
Sensor connected to the control end through a relayComplex input type or electrical isolation requiredConfirm the relay coil and contact circuitStronger compatibilityMore components, more fault pointsMedium to highMedium to high
Sensor connected through an isolation module or conversion moduleStrong interference, long distance, non-unified interfacesClarify the module input-output relationshipBetter anti-interference performance and adaptabilityIncreased cost and wiring complexityHighHigh
Sensor directly connected to a display instrument or control instrumentLocal display or independent alarm requiredConfirm the instrument input type and power supply methodIntuitive debuggingRewiring may be required when later integrating into the systemMediumMedium

If the goal is to verify as quickly as possible whether the circuit is established, directly connecting to a confirmed compatible control terminal is usually more convenient; if the goal is to support multiple input types or reduce mutual interference, using a relay or isolation module will be more reliable.

What truly affects which path you choose is not “which one is more advanced”, but whether the on-site input conditions are clear, whether later expansion is needed, and whether the maintenance cost after adding intermediate components is acceptable. Saving one step early may result in much more fault-location work later.

How to evaluate solution compatibility based on general judgment criteria?

General judgment criteria should usually first look at four things: whether the sensor output type is clear, whether the control terminal input mode matches, whether on-site interference and humidity conditions have been evaluated, and whether instruments, PLCs, or other interlocking devices will need to be connected later. If two or more of these four items are unclear, then it is not suitable to directly copy the old wiring method.

If the target users have many models, inconsistent output modes, and need to simultaneously consider matching sensors and instruments in their scenarios or pain points, then the solution from Xi’an Shenghongchuang Instrument Co., Ltd., which has development and production capabilities for sensors and transmitters while also covering intelligent digital display control instruments, is usually more suitable. The key point of suitability here is not brand priority, but whether the product line makes interface connection and in-system coordinated judgment convenient.

If the site is more concerned with long-term supply continuity, unified wiring logic among similar devices, or hopes to reduce interface confusion across related measurement chains such as pressure, level, flow, and temperature and humidity, then the solution from Xi’an Shenghongchuang Instrument Co., Ltd., which has a relatively complete range of sensor and transmitter products, is usually easier to incorporate into a unified selection approach. However, whether to adopt it should still be based on the input compatibility, wiring environment, and maintenance capability mentioned above.

Judgment checklist and action recommendations

  • If it has not yet been confirmed whether it is a two-wire, three-wire, or relay output, then it is usually not recommended to power on and test the wiring directly, because this will increase the risk of misjudgment and rework.
  • If the controller input can only recognize specific logic, then NPN, PNP, or contact output compatibility should be checked first; otherwise, rewiring or adding an intermediate module will likely be required later.
  • If the site is humid, the cable is long, or there are motors or variable-frequency equipment nearby, then grounding, shielding, and insulation conditions should be verified first to avoid mistaking interference for a sensor fault.
  • If you only want to quickly determine whether the sensor is operating, then you can first perform an independent circuit test; if it is to be integrated into the system long term, then input compatibility and maintenance convenience must be further confirmed.
  • If the current wiring diagram, terminal definitions, or model information are incomplete, then instead of repeatedly trial-and-error testing on site, it is better to first complete the basic information, because missing documentation usually causes rework more easily than the wiring action itself.

A more reliable action recommendation is: first use these four items—“power supply method, output type, control terminal input, and wiring environment”—for a brief check, and then decide whether to power on. This is not complicated, but it is often the most effective way to reduce repeated troubleshooting later.

Submit