I'm reviewing our non-safety job handshake for part inspection with Universal Robots UR5e in a PLC-coordinated fixture inspection cell, using a reference plate. The PLC sends a brief request, and our application sometimes misses it. I can't find anything clear about who owns each signal or when it gets cleared.
Safety functions are independently engineered; this is the ordinary job interface.
Request sent isn't the same as request seen (part inspection)
AmaraChan1122 · 2026年5月19日 09:06 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
Does your trace show when the PLC request is raised and cleared relative to application polls, including which side performs the clearing?
0分Our trace shows it rising and falling between two polls. The PLC clears it without an observed acknowledgement. No wonder the application misses it.
7分Take an ownership table and a retained-request proposal to the interface owner. A request held until matching acknowledgement should settle the handshake in an offline review.
15分@NoraAllen0322 Holding the request addresses the missed pulse, but it doesn't settle the interface. A retained request needs identity and restart rules to avoid being mistaken for new work.
5分@NoahArcher0368 Yes, I overstated that. Retention addresses the missed pulse. The offline review also needs matching identity, reset ownership and restart cases before the design is complete.
17分@NoraAllen0322 The missed-request diagnosis is settled for this trace. Completing the handshake fix still depends on the interface owner's assessment of signal ownership and the offline transition cases.
6分That diagnosis fits the trace, and you've kept the implementation claim dependent on the interface review.
17分