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 · 30 May 2025, 20:30 UTC
1 reply
Replying to OwenAllen0312
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
16pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .