C-more 0x0010 Error: Find and Correct PLC Addresses

The C-more panel stopped reporting error 0x0010 after the MicroLogix 1500 integer data file was resized to include addresses used by numeric-entry objects. Timer and counter displays continued to work, so the useful fix was to locate the rejected read and make the requested integer addresses valid in the PLC—not to treat the message as a C-more-generated error or assume the whole link was down.

Keep the working communication path intact

In this installation, the C-more communicated with an Allen-Bradley MicroLogix 1500 over the AB-PIC driver and DH485. Existing timer and counter displays updated, while the panel flashed Error code 0x0010 returned from PLC. Those observations distinguish a request-level problem from a complete communication failure: a working display proves that some reads succeed, but it does not prove that every address referenced by every screen exists in the controller.

The PLC returned the error in response to a C-more read request. The hexadecimal code alone is not enough to identify the offending tag; interpret the request in the context of the selected driver and the panel's diagnostic information.

Observation	What it indicates	Next check
Timer and counter values display, but the error appears	Some communication is working; one or more other reads may be rejected	Find the address named in the C-more error information
The error is absent on the startup screen	The startup screen may not use the offending address	Compare the screens where the message appears and inspect their objects
The error appears on every screen	A bad address may be referenced by multiple screens, a shared object, or the event manager	Check shared tags and event-manager references as well as screen objects

Before changing the driver, cable, or protocol, confirm that valid displays still update and move on to identify the rejected address.

Use screen changes to narrow the failing read

The panel's startup page in this case was a screen selector, and the error did not appear there. The application then opened one of 13 nearly identical screens. That pattern points the investigation toward objects or tags used on those screens rather than the selector page, while still leaving shared or event-triggered references in scope.

1. Open a screen where the error occurs and record whether it appears immediately or after a particular object is used.
2. Navigate to another screen. Note whether the error disappears, persists, or returns when the original screen is reopened.
3. Compare the screen-specific tags and numeric-entry objects on affected and unaffected screens.
4. If all screens show the error, include common tags and any event-manager references in the search; a tag used everywhere can make one bad address look like a global fault.

Use this as a localization test, not proof that the screen itself is defective. A screen can trigger a read for a PLC address that has never been created or allocated.

Check: identify at least one screen transition that reliably makes the error appear or disappear, or establish that it is global. This directs the next address search.

Read the rejected address in C-more diagnostics

Use the C-more setup screen's information button and open its error tab. The installation report indicated that this view should list the problematic address and may show a PLC-499 error. Treat the listed address as the lead for investigation; there may be more than one invalid request.

1. Open the setup information and error tab while the fault is present or after reproducing it.
2. Record each listed PLC address and any associated error entry, including PLC-499 if shown.
3. Match each address to the HMI object that reads or writes it, including numeric-entry objects and tags used by events.
4. Repeat after correcting one address, because a remaining invalid address can continue to generate a PLC response.

Do not guess the register from the hexadecimal code or change the communication selection just to make the message disappear. The original setup used AB-PIC over DH485; a suggested DF1 driver change was not the fix in this case. Confirm a protocol or driver mismatch from the actual panel and PLC configuration before altering it.

Check: you can name the HMI object and PLC address associated with each reported error. If the diagnostic view gives no address, use the screen-isolation results to inspect the objects on the affected page and consult the product's official documentation or support for the diagnostic procedure.

Compare each HMI address with the PLC data file

A numeric-entry object can reference an integer address that the application designer has added to the HMI but not yet made available in the PLC's data files. In the reported case, integer-value tags in numeric-entry objects referred to integer locations that were not present in the controller data file. The PLC rejected those reads even though other data types displayed normally.

For every diagnostic address, compare the complete address and data type in the HMI object with the corresponding file and element in the MicroLogix project. Confirm that the referenced integer data file exists and has a size that includes the requested element. Check all numeric-entry objects rather than only the first one found; similarly named screens can contain different tag references.

Separate an address that does not exist from other possible mismatches. Check for a wrong file, an element outside the configured file size, or an HMI tag using a different data type or address than intended. Correct the mismatch at its source rather than replacing the object with a seemingly valid but unrelated address.

Check: for every address in the C-more error list, identify the matching PLC data file and show that the requested element is within its configured range. Do not proceed on the assumption that a successful timer read validates the integer file.

Resize the integer data file to cover the requested tags

The production-restoring change in this case was to resize the PLC integer data file so it included the new tag addresses referenced by the C-more numeric-entry objects. Apply that correction to the actual MicroLogix project, using the required file size for the highest intended element. The evidence does not provide a specific file number, address, or size, so read those values from the HMI tag list and controller project rather than copying a guessed range.

1. Back up the current controller project and confirm the intended integer addresses from the HMI configuration.
2. In the PLC project, locate the relevant integer data file and set its size to include all intended elements.
3. Check that the new range does not conflict with another application convention or unintended tag use.
4. Apply the project change using the site's approved controller procedure, then confirm the running controller has the updated data-file configuration.
5. Return to the C-more error tab and check whether the corresponding rejected-address entries have cleared.

Do not enlarge a data file blindly to silence an error. If the HMI address is a typo or refers to the wrong file, correct the HMI tag instead. File sizing and HMI addressing must agree.

Check: verify that the PLC's live data-file size includes each intended numeric address and that the matching error entries no longer recur before releasing the screen for normal use.

Verify numeric entry and all affected screens

A cleared message is necessary but not sufficient: numeric-entry objects also need to read and write the intended integer locations. Test the repaired addresses from the panel and confirm the values against the controller project or an approved PLC monitor view.

1. Open each affected screen, including the nearly identical screens that share or repeat numeric-entry objects.
2. Confirm displayed integer values update without the PLC-returned error.
3. Test numeric entry only with an approved test value and confirm the intended PLC element changes; then restore the operational value if needed.
4. Revisit the startup selector and any screens or events that use shared tags.
5. Recheck the C-more error tab after exercising the application. Resolve any remaining listed addresses individually.

Keep the temporary production restoration distinct from the permanent correction: if operations must continue before every screen and event reference has been audited, document which screens and tags remain unverified and restrict their use according to site procedure. The permanent repair is complete only when all intended addresses exist, numeric entry reaches the correct elements, and the diagnostic error does not return during normal screen navigation.

FAQ: Diagnose C-more error 0x0010