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?
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
16 points