The PLC has detected a Fault condition and has set the SV_STOP system variable, which causes the job to be cancelled with the "327" message, but the PLC has neglected to trigger display of an appropriate additional message to explain the Fault condition.
The block in the PLC program that is likely to have set SV_STOP reads:
Code: Select all
IF !EStopOk || PLCFault_M || SV_STALL_ERROR || SpindleFault_M || SkinResetSet_M ||
LubeFault_M || AxisFault_M || ProbeFault_M || OtherFault_M || DoorShutDownStop_M
THEN SET SV_STOP
Code: Select all
DoorShutDownStop_M IS MEM25
;...
;--DoorShutdown Mode
;IF in Shutdown mode and door is open, STOP and send error
IF (DoorInterlockShutdown_M && !SafetyDoorSwitchClosed_I)
THEN SET DoorShutDownStop_M, ErrorMsg_W = WAITING_FOR_DOOR_CLOSED
In your case, since Parameter 985 = 0, we can probably assume that DoorInterlockShutdown_M is false, so it is unlikely that the door interlock logic is the issue. But you could follow similar paths to check out PLCFault_M, SpindleFault_M, SkinResetSet_M, LubeFault_M, etc..
You could also use the Source view in PLC Detective to see what tokens in the catch-all SV_STOP line are highlighted when your 327 fault occurs.