When a returned membrane switch does not reproduce the reported fault, purchasing should first match the part identity, its condition before and after removal, and the supplier's test conditions. Agree what further evidence and action are needed. A fault not reproduced describes this test only. It does not establish that the equipment is ready for use, that the original fault never occurred, or that responsibility has been determined.
In its Torso NXT manufacturer announcement dated 19 October 2026, EchoNous describes a portable ultrasound probe with a cable that clinical or biomedical engineering teams can replace on site following routine wear. This is the manufacturer's stated service-unit arrangement. It is not an assessment of diagnostic performance, evidence that the probe uses a membrane switch, or a supply relationship with Baoshengda.
If your own equipment also has replaceable controls, restored operation after replacement and the supplier's ability to reproduce a fault in the returned part are separate pieces of evidence. Removing an enclosure constraint, disconnecting an interface, or cleaning a surface can change the original condition. Record those actions when returning a membrane switch instead of sending only a note saying "the key failed." The following suggestions concern ordinary controls without a safety function. Equipment maintenance documents govern removal and release for use.
Connect the field observation to the condition on receipt
Record the affected key, the conditions in which the fault occurred, and the original symptom. Then list what happened before return: disconnection, reinsertion, cleaning, adhesive removal, or replacement of mating parts, and whether the symptom changed afterward. Keep unknown information unknown. Do not infer damage in a particular layer simply to complete an explanation.
TI's failure-analysis guidance asks for device history, application conditions, failure characteristics, and findings made before return. It also calls for removal and handling that avoid additional damage and preserve testability. The guidance concerns TI semiconductor products. This article borrows the evidence principle of connecting the reported fault to the return conditions, not chip-analysis equipment, processes, or service commitments.
The returned part, packaging, and accompanying records should identify one another. The recipient records the appearance, connection end, and packaging on arrival and compares them with photographs taken before dispatch. Clearly identify a sample that has already been delaminated or had traces cut. Results obtained in that state cannot automatically represent an intact installed component.
Ask the supplier to state what this test covered
A "normal test result" needs supporting records. The table below combines the evidence approach in the TI guidance with Baoshengda's project testing and inspection guide (Chinese). It is a handoff suggestion, not a universal returns standard or a promise that every order includes the same analysis.
| Evidence to compare | Field team or sender provides | Recipient and test team records |
|---|---|---|
| Same part and revision | Part number, drawing revision, batch, sample identifier, and matching photographs | Received identifiers, completeness, and information that cannot yet be matched |
| Reported symptom | Affected key, response, operating sequence, and available original records | The symptom the team attempted to reproduce, what it observed, and what it did not observe |
| Removal and handling changes | Actual reinsertion, cleaning, delamination, or securing steps before transport | Condition on receipt, preparation before testing, and any further state changes |
| Test conditions | Known information about the original PCB, connector, enclosure constraints, and use conditions | Standalone or installed state, fixture or instrument, method, conditions, count or duration, and criteria |
| Conclusion and exclusions | The question to resolve and information still missing | Results, references to original records, differences from the field setup, and open next steps |
Shenzhen Baoshengda Technology Co., Ltd.'s testing guide requires equipment, methods, samples, conditions, criteria, and original records to correspond to the project. The page describes a project review method. A photograph of equipment does not prove that a particular returned part underwent a specified failure analysis. Confirm the tests available, any mating parts required, and how records can be provided.
Choose the evidence gap to address next
If the supplier tested only an uninstalled part but the field fault appeared after closing the enclosure, record the missing original assembly condition as a difference. If reinsertion restored operation before return, preserve that sequence. The project owner decides whether to review the part with mating hardware, retain it for observation, or obtain further field records, considering what can safely be done. This does not call for repeatedly provoking a fault on equipment.
For example, suppose the field record says that one key intermittently fails to respond after the enclosure is secured. The returned part is no longer in the enclosure, and the supplier does not observe that symptom using the agreed fixture method. The report can identify the object and conditions tested, the actual result, and the assembly state not covered, then list the enclosure or interface information still needed. This is a hypothetical reporting example, not a Baoshengda customer case. It proves neither that the part conforms nor that the enclosure caused the fault.
Before delamination, trace cutting, or another check that changes the sample, agree its purpose, permitted extent, records, and whether the sample will remain usable for review under the original conditions. TI places non-destructive inspection before analysis that alters the device. Select membrane-switch methods for the actual construction; do not copy semiconductor decapsulation processes.
Record temporary replacement and cause closure separately
A replacement supplied to restore production can be recorded as a separate supply arrangement, identifying the part, quantity, revision, and remaining actions. Confirm replacement delivery, the original returned part's test conclusion, whether the cause has been established, and the handling of costs separately. Restored operation after one replacement does not automatically close the original-part investigation or determine responsibility.
Baoshengda's batch and revision traceability guide (Chinese) calls for queryable links among orders, drawings, BOMs, approved samples, inspection, material batches, and shipment records. Applied to a return, these links can connect the original shipment, field record, returned sample, test report, and replacement without losing their relationship when a new identifier is assigned. This is the article's handoff suggestion, not a claim that such a chain has already been established for an order.
For product scope, see custom membrane switches and the Chinese source product guide. A separate graphic overlay or keypad overlay without a switch circuit should not be expected to support a complete electrical conclusion. An overlay with metal domes used on the customer's PCB requires the customer's PCB, support, and installed conditions to be identified. Even a complete switch assembly cannot replace confirmation by the PCB, software, and equipment owners.
For interface troubleshooting, see staged checks for intermittent tail connections (Chinese). For report-to-batch links, see inspection-report delivery checks (Chinese). This article addresses evidence gaps and disposition records after a returned fault is not reproduced, rather than repeating connector diagnostics or a general report format.
Use the project contact page to share the fault timeline, current drawings, and sample identifiers, and state what happened before return. Ask the recipient to confirm what should be sent and what can be tested. Do not send a PCB, equipment, or other customer information before agreeing the receiving scope. First establish the specific question this handling record should resolve.