The reported fault occurs in a PROFINET I-Device connection after one PLC is powered down before the other.User data failure of hardware component - Labeler / Labeler.Transfer area_1. The evidence does not identify a firmware-specific defect or an explicit manual reset command.
Identify the shutdown-related fault
The transfer works after downloading the project and continues working after the fault appears. This separates the observed diagnostic indication from a persistent loss of cyclic communication.
| Observation | Engineering significance |
|---|---|
| One PLC is powered down while its partner remains powered | The transfer area becomes unavailable during the shutdown interval. |
| Error names Labeler.Transfer area_1 | Investigate the configured I-Device transfer area and its diagnostic handling. |
| Communication works after power-up | Verify current data exchange separately from the retained diagnostic indication. |
| Diagnostic buffer was not saved | The exact event sequence and interrupt details remain unknown. |
Capture the diagnostic evidence first
Upload and save the main PLC diagnostic buffer before attempting to clear the indication. Correlate its entries with the power-down and power-up sequence, noting whether the controller or I-Device lost power first. Without that buffer, the evidence cannot establish whether the blinking red indication represents an active transfer-area fault or a recorded event.
Handle the diagnostic interrupt
Configure the appropriate diagnostic-error interrupt organization block so the CPU can handle this class of I/O event instead of halting.I/O_FLT OB83prevented that stop behavior.
Verify the corrective configuration
- Save the diagnostic buffer with the fault present.
- Review the I-Device transfer-area configuration and any options governing behavior when the partner is unavailable.
- Configure the diagnostic-error interrupt handling supported by the installed CPU and project.
- Repeat the normal shutdown sequence, then confirm CPU operating state, status indication, diagnostic-buffer entries, and transferred output data after both PLCs restart.
The available evidence supports interrupt handling and configuration review as avoidance measures. It does not document a specific reset instruction, so do not substitute an assumed reset procedure for diagnosing whether the event remains active.
FAQ
Why does Labeler.Transfer area_1 fail when one PLC is powered off?
The reported event follows loss of power to one partner in a PROFINET I-Device connection. Capture the diagnostic buffer to confirm the event sequence and determine whether the transfer-area failure is still active.
Yes, in the reported case the data exchange worked after power-up even though the main PLC showed a blinking red indication. Verify live transfer data and inspect the diagnostic buffer instead of judging communication solely from the LED.
Does OB83 prevent an I-Device shutdown from stopping the PLC?
I/O_FLT OB83