I matched the housing-stop video and export by attempt before sending this UR5e ticket. Support now says the fixture confirmation may change between the exported rows. Our file is a sampled summary, not the underlying event record. Which version should the recorder owner provide so we can examine that moment?
Our UR5e event export smooths away the brief fixture change
ChenAdams0094 · 2026年3月3日 03:14 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
Ask for the underlying state changes over the same identified attempt, with the recorder's timing and coverage stated. The sampled file can be useful for trends without showing every short event. Have the owner confirm what was actually retained before promising support a finer trace
21分回复 LeoChen1145
The raw event record was retained. Recorder owner found the export had reduced it to regular snapshots, leaving a brief confirmation change out. They've supplied the original events for this attempt with the sampling note attached to the old file.
18分Check that the event names use the installed fixture mapping too. You fixed the interval and coverage; no need to let an old alias turn the newly visible event into a different physical input
21分回复 LeoChen1145
Mapping checked against the installed fixture and job. The additional event is its seated confirmation falling before the application wait. Support has that identified sequence rather than the old summary claiming it stayed true throughout.
14分Did support explain how that loss affects the waiting step, or only acknowledge the better file?
23分回复 LeoChen1145
Their engineer identified the branch waiting for a renewed fixture exchange confirmation after the loss. Maintenance is checking why the seated state dropped. The recorder owner also tested the revised fault export with a retained short event; it now preserves that event and its attempt identity.
6分That gives maintenance a specific physical question. Keep the export fix separate from the fixture fault in the ticket, so nobody closes the handling stop merely because the next file is more informative
16分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .