Our planned FR5 lathe interface uses ready for request received in the machine notes and loading area available in the integrator's notes. Both teams say their definition is obvious. I need a state table someone can implement and support. How would you get that discussion onto separate, testable meanings?
Can we stop calling two different things ready?
OwenAllen0312 · 2025年5月30日 20:30 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
Give those meanings separate names first. For each ordinary job signal, write who owns it, what makes it change and what the receiver does. Then walk a request and an interrupted request through together. Keep the separately engineered safety permissions explicit; a general ready bit can't stand in for them
16分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .