IMDHMIControls LibraryShop main store

Troubleshooting

Resolve a ladder logic mismatch in Concept on a 984

PLC programming Published 5 min read

Short answer

The not-equal notice in Concept 2.6 means the working file and the program in the 984 processor differ; the PLC is not faulted. Upload the processor program into a saved copy of the project to preserve the reported online input change, and download only a verified offline project, never as a test.

On this page
  1. What the not-equal notice is comparing
  2. Pick the transfer direction before you connect
  3. Prepare the file and the controller
  4. Upload and adopt the result
  5. If the decision is download
  6. A worked example of what a download reverts
  7. Where these mismatches come from
  8. Confirm the mismatch is actually gone
  9. Questions asked

The mismatch means what you suspected: the ladder logic in the Concept 2.6 working file and the program executing in the Modicon 984 are different, and the not-equal indicator is Concept reporting that compare. It is a notice about two copies of one program, not a processor fault, and the machine keeps running the controller's own logic. The easy fix is a single upload — read the processor into a saved copy of the project — because the reported cause is a minor input change made online that never made it back into the offline file. A download would erase that change, so it is the wrong direction until the offline project is proven to be the approved program.

What the not-equal notice is comparing #

Concept keeps a working project on the engineering station and compares it against the user program in the connected 984. The mismatch notice is the result: the two copies differ. That is everything it says. It does not identify which copy is correct, and it does not stop the controller — the 984 executes the logic in its own memory regardless of what the workstation holds.

Is it a major problem? For the machine this minute, no. For your program management, yes: the working file no longer represents the running program, and the next download from that file silently reverts the change that exists only in the processor.

Pick the transfer direction before you connect #

Two operations clear the notice, and they do opposite things.

Operation Writes Choose when Costs you
Upload, read from the PLC Processor program into the working file The online change is intended, or you have not verified it, or the process runs correctly on current logic Offline edits that exist only in the working file
Download, write to the PLC Working file into the processor The offline project is verified as the approved program and the online change is deliberately rejected Everything that exists only in the processor, permanently

The rule that decides it: upload whenever the processor's content is intended or unverified. An upload is recoverable, because the previous working file still exists as a saved copy; a download is not. Your reported case is a deliberate input edit made online, so the direction is upload.

Prepare the file and the controller #

  • Save the current working file under a new, dated name so both copies survive whatever happens next.
  • Confirm Concept is online with the intended 984, not another controller reachable on the same network.
  • Record who chose the direction and on what basis. If any of this logic performs a safety function, IEC 61511-1 requires a modification to be authorized and assessed for impact before it is made and verified afterwards — that discipline applies to the undocumented online edit and to your download alike.

Upload and adopt the result #

  1. Open the working project and save it under the new name; leave the original untouched.
  2. Run the Concept upload procedure, which reads the processor program into the project.
  3. Find the change before adopting the file: discrete inputs live in the 1xxxx reference range in 984 addressing, so check the contact reference on the rung the edit touched, against the person who made it or the change record.
  4. Save the uploaded project as the controlled baseline. The not-equal indicator clears once the working file and the processor hold the same program.

If the decision is download #

A download replaces the processor program; it is never a test of whether the notice clears. Proceed only when all three hold:

  • The offline project is verified to contain every approved change.
  • The online-only input change is confirmed unwanted, not merely unrecorded.
  • The process is in a state that tolerates the logic swap, and you hold the authority to write to the controller.

Then download, watch the transfer report completion, and verify machine behavior against the approved sequence. If the transfer fails or is interrupted, do not assume the copies now match — re-establish the connection and check status before any further move. A download that goes wrong is its own incident; one pattern from another platform is an SLC 5/03 left in Default/Faulted after a bad download.

A worked example of what a download reverts #

Illustrative numbers, same decision shape as your case. Suppose the online edit raised the debounce timer on a pump-start rung from 2.0 s to 3.5 s to stop input chatter. LL984 offers separate timer block types per time base, including 0.1 s and 1.0 s bases, so the preset is a count, not a time.

  • Processor, with the online edit: 3.5 s ÷ 0.1 s per count = 35 counts.
  • Stale working file: 20 counts × 0.1 s per count = 2.0 s.
  • What a download writes back: 35 − 20 = 15 counts, or 15 × 0.1 s = 1.5 s of debounce removed.

The upload preserves 35 counts; the download forces 20. That 1.5 s is the chatter suppression the edit added, so the choice of direction has a measurable process effect — upload.

Where these mismatches come from #

  • An edit made in the controller and never read back into the project — your case.
  • A working file restored from an old backup after the PLC had moved on.
  • A transfer interrupted partway, leaving both copies mid-state.
  • A project carried between tools or dialects: LL984 logic is edited outside Concept as well, in ProWorx NxT and ProWorx 32, and Concept hosts IEC languages alongside the LL984 dialect, so conversions and carry-overs drop or shift details.

Carrying a project across software generations carries the same risk, and whether a move counts as a revision or a full migration decides what survives — how PLC software revisions and migrations differ works through that distinction.

Prevention is one habit: after every online edit, upload into the project and save it, so the file and the processor never stay apart overnight.

Confirm the mismatch is actually gone #

  • Concept reports the working file and the processor equal.
  • The saved, uploaded project opens and shows the input change you went looking for.
  • The pre-upload file still exists under its dated name.
  • If the notice survives a clean upload, stop cycling transfers: verify the connection targets the right 984, reopen the correct project, and compare again rather than transferring a third time.

Questions asked

Does the not-equal notice mean the 984 is faulted?

No. It is Concept's compare result between the working file and the processor program, not a controller fault. The 984 keeps scanning the logic in its own memory, which is why the machine can run normally while the notice is up. Treat an actual processor fault as a separate problem with its own symptoms.

Can I leave the mismatch unresolved for now?

You can, and nothing on the machine changes. The exposure is administrative: the working file no longer represents the running program, so the next person who downloads it — during a restore, a processor swap, or routine maintenance — silently erases the online input change. Upload into a saved copy the first chance you get and the exposure closes.

Will an upload destroy my offline edits?

It replaces the working file's content with the processor program, so any edits that exist only in that file are gone from the live copy — which is exactly why you save the file under a new name first. With both files kept, you can compare them rung by rung and merge deliberately instead of losing either side.

Does it matter that the change was to an input rather than a register?

Not to the notice. The compare trips on any difference — a discrete input reference in the 1xxxx range, a holding register in the 4xxxx range, a timer preset — and shows the same not-equal either way. What matters is where the change lives and whether it is intended; search the uploaded project for the reference number you were told changed.

Was the online edit itself a violation?

If it was made without authorization and a record, it is an undocumented modification, and if the logic performs any safety function, the IEC 61511-1 modification requirements apply to it: impact assessment and authorization beforehand, verification afterwards. Document it as part of resolving the mismatch, so the baseline you adopt is also defensible.

Keep reading

  • Troubleshooting

    Why Modbus cannot transfer a PLC ladder program over TCP

    No Modbus address reaches ladder memory: the application protocol defines four data tables — coils, discrete inputs, input registers, holding registers — and program storage is not in any of them. Swapping RTU for TCP changes transport, not protocol. On DirectLogic PLCs the program moves only over K-Sequence or DirectNET through the vendor's programming tools; Modbus stays for mapped user data.

    PLC programming

  • How-to

    Write an S7-1200 heartbeat in ladder logic in TIA Portal

    Tie the light to a detector, not to the heartbeat level: time the on half with one TON and the off half with a second TON, both at three times the measured state time, and OR the two done bits into one communication-fault coil. With a PC heartbeat that changes once per second, PT is 3 s and the fault trips 3 s after the last change; add TCON and TDIAG supervision when the PLC owns the TCP connection.

    PLC programming

  • Troubleshooting

    Recovering alarm data from an undocumented SLC 5/04

    An upload from an SLC 5/04 returns the running logic and data files but no symbols or descriptions, because the processor never stores them. Recover alarm meaning from the operator interface tag database, any older backup and the electrical drawings, trace each alarm backward through the logic, then map only explained addresses into the gateway.

    PLC programming