FANUC oversize tool management PS5360: why an edit can be rejected even when adjacent pockets are empty
The 30i-A oversize-tool supplement separates shape definitions, tool associations and magazine registration. An empty-pocket counterexample shows that PS5360 does not always mean physical interference has already occurred.
Contents
PS5360 during an oversize-tool data change cannot immediately be attributed to adjacent pockets being too close. It may also mean that a shape definition referenced by a tool registered in the magazine cannot be edited while that association remains.
Identify which data layer is being changed
Based on the FANUC 30i-MODEL A supplementary specification A-79346E, edition dated 2004-1-6, page 18/22 (public mirror of the original manual), this article concerns data-entry rules with oversize-tool support configured. Separate three layers to identify where rejection occurs:
| Data layer | Meaning | Distinction to retain |
|---|---|---|
| Tool shape definition | Geometric data associated with a shape number | A shape number is not a physical tool number |
| Tool management | The shape number used by a particular tool | Changing an association differs from editing the shape itself |
| Magazine registration | The magazine position in which a tool is registered | Recorded occupancy and a visibly empty pocket are different evidence |
Three rejection conditions in this edition
The same page lists: registering or modifying shape data in tool-management data for a registered tool causes interference with another tool; registering or modifying the magazine-management table causes interference; and editing shape data while a tool referencing that shape number remains registered in the magazine. All three issue PS5360 and reject that data input. The third condition does not itself require proof of interference between adjacent tools.
Why empty pockets do not rule out the alarm
Original relationship example: tool 31 references shape 7; tool 31 is registered in position 6 of magazine A; positions 5 and 7 are empty. The edit changes “the definition of shape 7,” not tool 31's associated shape number. Although neighboring pockets are empty, shape 7 is still referenced by a registered tool, satisfying the third rejection condition.
Editing the shape number associated with tool 31 instead invokes a different class of data check; editing a magazine-position record invokes another. These operations may appear on nearby screens but change different objects. Recording only “alarm while editing a tool” loses the most important diagnostic detail.
Distinguish input rejection from a geometric relationship problem
Link the field being edited, its previous shape number, the tools referencing it and their magazine registrations, then compare the three conditions. For the third, focus on whether the reference remains. For the first two, check registered tool geometry and neighboring occupancy rather than relying on an empty-pocket photograph.
After the alarm, reread the target record to establish whether the requested data were accepted. “File transfer completed” does not mean every record became effective. Nor does this article infer automatic rollback of an entire import batch.
The example explains data-consistency restrictions and supplies no method for bypassing checks by deleting magazine registrations. Physical magazine state and management data must correspond; adjustment order should follow the machine builder's tool-management process. Further function resources are in the OPTION section.