简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

our sleeve video shows the pause we made for filming

AmaraBell0687 · 2025年12月15日 12:30 UTC

已关闭
AM
AmaraBell0687
We paused the UR5e sleeve job to film its position after an intermittent stop. Support thinks that pause is the fault. How do I untangle this?

18 条回复

MI
MinaArcher0424

Tell support directly which part was a later reconstruction and retain the original occurrence's message, history and operator account separately. The staged pause may explain the position, but it cannot establish the cause or timing of the original stop.

18
AM
AmaraBell0687

I've corrected the description. Embarrassing, but yes, we filmed the position later. Original message wasn't saved.

11
MA
MayaChen1171

Is any original event history still available? Check that before arranging more filming. The useful next evidence may be in a retained record rather than another view of the arm.

20
TH
ThomasAbbott0016

I've sent a reconstruction too, but labelled it separately. Useful for showing a cramped contact; useless for proving which signal changed during the real occurrence.

4
AM
AmaraBell0687

Controller history retained. PLC lead-in isn't. Technician is checking what the original controller entries actually identify.

17
TH
TheoAllen0323

Did the operator stop it deliberately at the same point as the earlier event, or just somewhere nearby? Even the position explanation could be misleading if support assumes a precise match you didn't intend.

14
MI
MinaArcher0424

Keep that uncertainty with the reconstructed clip, Amara. It may remain useful context, but do not let a carefully chosen camera angle turn it into a substitute occurrence.

17
AM
AmaraBell0687

Nearby, not exact. I've said that too. The real stop and the later filming now have separate entries.

7
MA
MayaChen1171

Who can preserve the next real occurrence before its history rolls over? The current reconstruction problem should not leave both shifts without a usable capture method.

8
TH
ThomasAbbott0016

Maya's right. A short capture list is cheaper than another afternoon arguing about what a video was meant to show.

24
TH
TheoAllen0323

Thomas, did support still use your labelled reconstruction? I'm asking because ours sometimes asks for a clearer picture when it really needs an earlier event, and people end up filming the wrong thing very clearly.

3
TH
ThomasAbbott0016

Yes, to understand the physical access. The actual diagnostic answer used the captured event history. We kept both, with different jobs to do.

9
AM
AmaraBell0687

Both shift technicians now have support's capture list. Thanks Maya. Original controller entries don't identify the missing receiving condition.

16
MI
MinaArcher0424

Then leave that old condition unknown and capture the required source states around a new occurrence, with its exact message, job version and sleeve fixture identity. The reconstruction can remain clearly marked background.

16
MA
MayaChen1171

Has support stated which source states it needs, rather than only asking for a longer video?

4
AM
AmaraBell0687

Yes. Controls and support agreed the specific export. No new occurrence captured yet.

15
TH
TheoAllen0323

That's a clearer next step. I'd put the reconstruction label on the clip itself as well as the ticket description, because attachments have a habit of travelling without the sentence that explains them.

18
MI
MinaArcher0424

Keep the exact original and the labelled teaching copy distinguishable if you do that. The aim is to prevent misreading, not overwrite the material explaining how the ticket became confused.

22

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .