Fix a PLC-499 0x021C error code on the panel

Read the code in two parts

PLC-499 is the panel reporting that the number after it came from the PLC. The panel is the messenger; the condition lives in the CPU. That split decides where you start. A panel-side fault sends you into the panel's setup screens. A PLC-side code sends you to the controller and to the manual that governs the CPU model you actually have.

0x021C is a hexadecimal value. The code documentation behind the panel maps it, as decimal 540, to CPU Locked and attaches a qualifier: DL440 only. The qualifier travels with the label. Before the label becomes your diagnosis, match it against the family of the CPU in the rack and read the same condition in that family's own documentation.

The same split, a panel relaying a controller-side code, is what PLC-011 invalid function code on an Ethernet HMI link covers for Ethernet; the reading habit is identical even when the transport changes.

Why it ran in the shop and failed at first power-up in the field

A DL205 CPU with a password configured holds its communication ports locked until a connection supplies that password. A PC running the PLC's programming software clears this at every connect: the software asks for the password, someone types it, and the ports carry traffic for that session. An operator panel has nobody to type anything. It polls on its own, meets locked ports, and the CPU answers with its own error code, which the screen prints as PLC-499 0x021C.

That is also why freight changed nothing. If the bench checkout ran while the programming PC was still attached, that session carried the password and the system looked healthy. The first field power-up runs with the panel alone, the ports are locked, and the message appears. The password was in the CPU before the crate was sealed; the bench never exercised the panel's own access path.

Symptoms and what each points to

• PLC-499 0x021C at the first power-up in the field: the CPU sent its own code. Start at the controller and keep the panel out of the diagnosis until the CPU side is settled.
• The programming software asks for a password at connect: a password is configured on the CPU, and the locked-CPU reading of 540 has its confirming fact.
• The programming software connects straight away with no password asked: that CPU carries no password. Skip the password path and work the link itself; HMI PLC timeout and invalid checksum errors gives the order to check cable, protocol and station settings.
• The system ran with a PC attached and fails with the panel alone: the bench session carried the password, and the panel never had display access configured for a locked CPU.
• No panel values update and the code stays on screen: the CPU is denying display access while a password is configured. The AUX 8 operation is the documented route back.

Worked example: PLC-499 0x021C on a DL205 with a D260 CPU

Inputs:

• Panel: a 12-inch operator panel, firmware 2.73, polling the PLC unaided. Values come from the case as it presented in the field.
• Displayed string: PLC-499 0x021C, read off the screen at power-up.
• Installed CPU: a D260, read from the module; the D260 belongs to the DL205 family.
• Code-list entry: decimal 540, labeled CPU Locked, qualified DL440 only, from the panel's code documentation.
• Documented procedure: DL205 User Manual, Appendix A, AUX 8 Password Operations, starting at page A-14 of the 4th edition appendix.

Rule, in words: PLC-499 marks the number that follows as a PLC-side code. Hexadecimal converts to decimal by place value, each digit worth 16 to the power of its position counting from the right. A DL205 CPU with a password configured keeps its ports locked until the password arrives on a connection, and display access from a locked CPU uses the documented format: the letter A followed by exactly 7 numeric characters, 8 characters in all.

Arithmetic: in 0x21C the left digit 2 sits in the 256s place, the 1 sits in the 16s place, and C is 12 in the 1s place. 2 x 256 = 512. 1 x 16 = 16. 12 x 1 = 12. 512 + 16 + 12 = 540. The display-access password length: 1 letter + 7 digits = 8 characters.

Result: 540 decimal, CPU Locked per the code list with the DL440 qualifier attached, reported against an installation whose CPU is a D260. The number points at a password lock on the CPU; the qualifier sends the confirmation to the DL205 manual.

Decision and threshold: the qualifier's CPU family must be the family installed for the label to close the case on its own. DL440 wording over a D260 opens the case. The deciding check is the programming software's connect: a password prompt confirms the lock and sends you to AUX 8 with the A + 7 digits display-access format; no prompt means the CPU has no password and the fault moves to the link and the panel's PLC setup.

Checks, in this order

1. Read the CPU model off the module, here a D260 in a DL205 system. The model selects the manual, so take it from the hardware, never from the job paperwork.
2. Connect the programming software at the CPU's port and note what happens at connect: a password prompt, or an immediate link.
3. Write down the exact string on the screen, the panel firmware (2.73 here) and the CPU model while you are standing in front of the machine.
4. Open the DL205 User Manual and read the family's own description of password behavior before any setting changes.

The fix: AUX 8, run by the password's owner

The procedure lives in Appendix A of the DL205 User Manual, AUX 8 Password Operations, from page A-14 in the 4th edition appendix. AUX 8 is the manual's block of password operations for the CPU. For a locked CPU that has to serve an operator panel, the display-access password takes the documented format: the letter A followed by exactly 7 numeric characters, A1234567 as the shape of it. The password's owner makes the change, and if the CPU's configured password sits in some other format, AUX 8 is how the owner sets it right. The panel keeps polling through it; the code clears once the CPU holds a display-access password in the format it accepts.

The manual's wording here is terse. Read the whole AUX 8 block before keying anything, and make the change with the machine at a safe point, the person who owns the password doing the keying. Guessing passwords at the panel is not a recovery path and just burns link time.

One safety rule: never clear CPU memory or force a reset to make the message disappear. A memory clear can stop a machine that was otherwise healthy and take the program with it. Access, configured correctly, is the whole fix.

Verify, then write the handoff

Power the CPU down and up, leave the programming PC out of the link, and let the panel poll on its own. The code should stay gone and the values on the screen should track the machine. Push one write the application authorizes from a maintenance screen and watch it land in the PLC. A clean programming session and a clean panel connection are two different results; test both, and treat the panel's pass with the PC out of the link as the one that matters.

Handoff sheet: CPU model, panel firmware, exact code string, the fact that the CPU carries a password, and the display-access format of A plus 7 digits. The password itself stays off the sheet; it lives with the person authorized to change it.

Recommendation: When PLC-499 0x021C appears, read the installed CPU model first, confirm the lock with the programming software's password prompt, and have the password's owner run AUX 8 from Appendix A of the DL205 User Manual so the CPU carries a display-access password in the A + 7 digits format. If the software connects with no prompt, leave the password untouched and work the link checks in order.

Questions