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

Both suppliers ticked ready while describing different events

AdamBlair · 2025年10月17日 07:29 UTC

已关闭
AD
AdamBlair
I put our proposed UR5e bush-loading sequence in a shared table. Both suppliers ticked the ready column, which looked promising until one explained it meant request received and the other meant the loading area was available. We have agreed on a word and almost nothing behind it.

19 条回复

MA
MayaBarnes0562
回复 AdamBlair

What does each team expect the other side to do when ready turns on?

11
RE
RebeccaBarnes0604
回复 AdamBlair

Can you draw the sequence with event names instead of signal names? I would take ready off the first draft altogether.

-2
SA
SamBaker0507
回复 AdamBlair

Who clears it?

24
YA
YasminAdams0093

Rebecca's approach helped us untangle a similar table, though we still needed the eventual signal names alongside it for maintenance to follow the screen.

8
AD
AdamBlair

Maya, one team expects us to wait after ready and the other expects the sequence to proceed. Sam, they also disagree about who clears it. Rebecca's event-only version may save us another meeting about the spelling.

22
MA
MayaBarnes0562

Yasmin, yes, event wording first and screen wording beside it once the meanings agree.

16
RE
RebeccaBarnes0604
回复 AdamBlair

Adam, what happens to an accepted request when communication drops? That is where our tidy drawing fell apart.

21
SA
SamBaker0507

Was yours forgotten, Rebecca, or repeated?

1
RE
RebeccaBarnes0604

Repeated in the software test. The receiver remembered accepting it, but the sender restarted as though nothing had happened. We needed the controls people to sort that out, not another label.

16
AD
AdamBlair

Rebecca, ours has a blank box for communication loss. I had treated that as a later detail. Your example is useful; I have added it to the supplier discussion alongside the normal loading sequence.

13
YA
YasminAdams0093
回复 AdamBlair

A blank box is easy to overlook when the normal path fills a page, and the operator will meet that box without the two suppliers beside them.

13
MA
MayaBarnes0562
回复 AdamBlair

Also, request received must not be treated as permission to enter the machine area.

23
AD
AdamBlair

Agreed, Maya. We are calling it request accepted in the discussion copy and keeping the access conditions separate. Neither team has signed the revised sequence, so these are proposed meanings, not a commissioned interface.

15
RE
RebeccaBarnes0604

Maya, would you put the access conditions on the same drawing? Ours became hard to read once every dependency was squeezed in.

24
MA
MayaBarnes0562

Linked detail is fine, Rebecca, as long as the sequence points to it unambiguously.

4
SA
SamBaker0507
回复 AdamBlair

Adam, is there a request identifier in the proposal?

17
YA
YasminAdams0093

Sam, I would let their controls teams choose the mechanism, but I do want them to explain how a delayed answer is matched to the request it belongs to.

-2
AD
AdamBlair

Sam and Yasmin, nothing has been chosen for matching requests yet. I have asked for a worked example with a delayed answer after reconnect. Thanks Rebecca for the restart story; it made the missing case much easier to explain.

8
RE
RebeccaBarnes0604
回复 AdamBlair

Good. Ask them to walk it from both ends. We each thought the other application was retaining the bit that mattered.

25

讨论已关闭

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