Electrical Measurement & Monitoring · Technical Explainer
Wireless Temperature Sensors in Metal Switchgear: Receiver Checks
Identify the complete receiving system first
Write down the ordered sensor version, receiver version, antenna arrangement, firmware and supervisory interface before planning tests. The LSMT3/M wireless switchgear temperature sensor page describes a battery-powered strap-mounted sensor and explicitly requires a matched receiver. It does not establish an open protocol, universal access-point compatibility or a guaranteed reception distance for the proposed cabinet arrangement (RITOKS, n.d.). Where each sensor should sit is a separate decision; see planning switchgear contact temperature sensor locations.
Ask the supplier which receiver is supported for the exact order and which commissioning instructions govern that combination. Obtain the identification format, pairing procedure, measurement-update behavior and any available radio diagnostics. If those documents are missing, mark the receiving system incomplete rather than filling gaps from a visually similar product.
Other manufacturers demonstrate why this distinction matters. Schneider Electric's TH110 manual requires pairing with a ZigBee Green Power access point and explains that receiver or antenna position and intervening metallic barriers affect received signal strength. That is evidence for the TH110 system, not proof that LSMT3/M uses the same protocol, power source or acceptance limits (Schneider Electric, 2021).
Separate the radio receiver from the onward connection to the monitoring platform. A value might arrive at the receiver but fail to appear in the supervisory system. Recording both interfaces makes that failure distinguishable from a sensor radio problem and avoids replacing hardware before identifying the broken link.
Build a sensor identity and ownership map
Start with a map that a different engineer could use without remembering the commissioning sequence. Assign a cabinet location, measurement-point description, sensor identifier and intended receiver to every point. Preserve the supplier's original identifier alongside the customer-facing tag. A friendly label alone may become ambiguous after a sensor is replaced or moved.
| Record field | What it establishes | What it does not establish |
|---|---|---|
| Sensor identifier and ordered version | Which physical unit is being evaluated | Compatibility with every receiver |
| Cabinet and measurement-point tag | Where the unit belongs in the project | Adequacy of the thermal measurement point |
| Receiver identifier and supported version | The intended collecting device | Reception in the completed enclosure |
| Antenna location and mounting arrangement | The arrangement tested during the survey | Permission to move or modify the antenna |
| Platform point name | Where the received measurement is displayed | Correct treatment of stale values |
Reconcile this map with the receiver's actual device list using the documented procedure. Record duplicate tags, unmatched identifiers and unexpected devices as discrepancies. Do not assume that a plausible temperature reading proves correct identity; two nearby points can display similar values.
Where the equipment permits a safe documented identification check, use it to connect the physical unit to the receiving record. Do not improvise heating, open an energized enclosure or move a mounted sensor to make identification easier. Installation and test access must remain within the site's approved electrical safety arrangements.
Survey reception in the intended cabinet state
The receiver survey should reflect the final installation, including closed doors, installed partitions, cable routing and the approved antenna location. An open-door check can help explain a difference, but it should be labeled a diagnostic condition rather than silently becoming the acceptance condition. Record any unfinished enclosure work that could change the radio path later.
Create the test-state list before collecting data. Include the relevant normal operating arrangement and any permitted changes that the customer expects in service. The project engineer must decide which states are appropriate and safely observable. This article does not specify universal test duration, signal threshold or packet-loss limit; those belong to the supported system documents and the customer's monitoring requirement.
For each state, record the sensor identifier, receiver, observation start and end, available signal metric, received-update behavior and unresolved gaps. If the receiver provides received signal strength, preserve its units and interpretation from the exact manual. Do not compare numbers from dissimilar systems as though they had a common acceptance scale.
A useful survey keeps configuration changes separate from observations. First capture a baseline with the intended arrangement. If an authorized antenna relocation or receiver change is needed, record the change and collect a new observation set. Merging both sets into one result hides which arrangement actually worked.
Do not promise that a short successful observation proves indefinite reliability. It establishes performance during the documented conditions and interval. The customer can then decide whether further observation is needed for an operating state that was absent, a cabinet modification or a monitoring requirement that was not tested.
Distinguish missing updates from normal temperatures
An unchanged displayed value may mean a stable temperature, a defined transmission behavior, a stalled receiver-to-platform link or a stale reading. These possibilities should not be collapsed into a single green status. Request the system's documented update rules and its method for identifying the age of the latest valid measurement.
The receiver record should show when a measurement was last received if that function is supported. The platform should preserve the distinction between measurement time, collection time and display time where those fields are available. Do not invent timestamps in an export when the interface supplies only a value.
Agree how missing data will be presented before handover. A stale temperature should not become a new zero-temperature reading, and communication loss should not be described as a verified overtemperature condition. Those are different events with different meanings. If the system cannot expose data freshness, record the limitation explicitly for the customer.
Schneider Electric's TH110 troubleshooting section asks whether a sensor remains paired and whether its identifier appears in receiver backup files. It also directs attention to the access point's reception level. These are useful examples of separate identity and reception checks, but the manual's numerical limits must not be transferred to another sensor family (Schneider Electric, 2021).
Define the loss-of-communication handover
The customer needs an actionable description of what happens when the communication chain is unavailable. Define who receives the indication, where it appears and what maintenance record is created. If the proposed receiver does not support a requested alarm, identify that gap before describing the system as complete.
| Handover question | 提出を求める証拠 | Unresolved outcome to record |
|---|---|---|
| Can the receiver identify an absent sensor? | Supported device-status behavior | Sensor absence is not exposed |
| Can the platform distinguish stale data? | Point-status and freshness documentation | Displayed values may lack age information |
| What triggers the notification? | Documented rule and project setting | Timeout or rule not approved |
| What happens after reception returns? | Recovery behavior and event handling | Acknowledgment or reset behavior unknown |
| What survives a configuration replacement? | Backup and restoration instructions | Identity map may need rebuilding |
Use the manufacturer's supported test method and the site's approved procedure to demonstrate the requested indication. Do not disconnect a safety function, bypass an interlock or open live switchgear solely to simulate a missing sensor. If a safe demonstration cannot be performed, distinguish a documented function from a function witnessed on the installation.
Temperature monitoring does not automatically constitute a protective trip function. Keep any alarm-to-action integration within the separately engineered control and protection design. Neither successful pairing nor a communication-loss notification proves that a breaker will operate correctly or that the installation meets a particular safety performance level.
Turn survey findings into a purchasing decision
The purchasing decision should identify a supported combination and its remaining evidence needs. A receiver quantity selected only from a claimed maximum distance can miss the actual cabinet arrangement. Conversely, adding receivers without a recorded survey may conceal identification or platform-mapping problems rather than solving them.
Request an offer that names the sensor and receiver versions, permitted antenna arrangement, required accessories and commissioning documentation. Attach the cabinet layout and the proposed identity map. Ask the supplier to identify assumptions that need an on-site survey rather than presenting them as already verified operating capability.
After evaluation, classify each point as demonstrated in the recorded state, awaiting a configuration change or not yet observed. This is more useful than one undifferentiated pass label. Include the responsible person and next action for incomplete points, especially where the final cabinet arrangement was unavailable during the survey.
For broader family discovery, the existing electrical measurement and monitoring category provides related measurement products. It is not a compatibility list for the selected wireless receiver. Keep the quotation anchored to the exact sensor-receiver combination and its supporting documents.
Common receiver-survey questions
Does successful pairing prove reception through closed doors?
No. Pairing establishes an association under the conditions used for commissioning. The receiver survey must separately record reception in the intended closed-door cabinet arrangement and other agreed operating states. A workbench or open-door result should retain that description rather than becoming evidence for an untested condition.
Can a TH110 reception limit be used for LSMT3/M?
No. TH110 documentation describes its own sensor, access-point arrangement and radio system. The LSMT3/M combination requires its own matched-receiver instructions and project acceptance criteria. Similar application language does not establish equivalent protocols, power requirements, antenna behavior or supported reception thresholds.
Should every communication gap cause a temperature alarm?
Not automatically. A communication gap indicates missing information, not a measured temperature excursion. Specify the separate status or notification required by the customer and confirm whether the receiving system can provide it. Any protective response needs its own engineered justification and approved integration.
What should be retained after commissioning?
Keep the identity map, supported-version record, receiver configuration backup where available, observed test states, measured diagnostic fields and unresolved actions. Preserve the distinction between documented features and witnessed behavior. That record makes a later replacement, cabinet modification or reception complaint easier to investigate without reconstructing the installation from memory.
Conclusion
Specify wireless temperature monitoring as a complete sensor-to-receiver-to-platform chain. Prove identity first, survey the final cabinet arrangement, record actual update behavior and define how missing information will be presented. Keep untested range claims, borrowed radio thresholds and protective-function assumptions out of the acceptance record. The result is a traceable receiving-system decision rather than a collection of successfully paired devices.
参考文献
- RITOKS. (n.d.). 電気的測定および監視. https://ritoks.com/product-category/electrical-measurement-monitoring/
- RITOKS. (n.d.). LSMT3/M wireless switchgear temperature sensors. https://ritoks.com/products/lsmt3-m-wireless-switchgear-temperature-sensors/
- Schneider Electric. (2021). TH110 installation and operation manual (NVE6274001-03; download record NVE62740 dated April 7, 2022). https://download.schneider-electric.com/files?p_Doc_Ref=NVE62740