Our 56-day ticket has a captured seated-state loss now. Static checks did not reproduce it. Who should investigate next?
FR10 connector stop with a trace nobody has explained
HanaBell0622 · 2026年3月4日 09:05 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
11 条回复
回复 HanaBell0622
Ask the installer to compare the captured loss with the physical confirmation arrangement on the identified tray. Does the trace show the condition never arriving, or arriving and then dropping?
22分Arrives, then drops before the wait. Tray-present stays on. Installer has the same occurrence and tray identity.
8分回复 HanaBell0622
Has the installer inspected the seating and confirmation target, or only reviewed the exported states? The distinction would help you ask for the next actual task.
22分Inspected target and mounting. No fault found there. Tray support comparison is still outstanding.
9分回复 HanaBell0622
Does it happen with one tray or several?
13分Known occurrence is one identified tray. Earlier reports don't identify theirs, so I can't claim it follows this tray.
5分回复 HanaBell0622
Keep that tray available. Otherwise the next visit starts with everyone's favourite theory again
12分And compare it with a correctly identified normal tray on the intended contacts. Retaining the suspect one is useful, but the installer needs to know which differences are intended before calling one a defect.
10分Comparison found a cracked support strip on the captured tray. Tooling says the loose end can obstruct seating. Tray withdrawn; replacement being checked.
-1分回复 HanaBell0622
Did the identified replacement complete the agreed seating and transfer checks? That would move the account beyond a plausible cause for the captured loss.
23分回复 HanaBell0622
And has stores got the cracked-strip example? It needs to stop circulating, not just miss this shift
13分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .