How-to
Editing a Delta DOP HMI project without breaking PLC comms
Short answer
Downloading a revised project to a Delta DOP panel replaces only the panel's project; the PLC program and its port configuration are untouched. The link survives because the driver and serial parameters are stored separately in each device and a revision leaves them matching. Record both sides first, then prove read and write after the download.
On this page
You do not program the two devices together, and you never merge the files. The panel and the PLC each hold their own project, built by their own tool, and downloading a revised project to a Delta DOP panel replaces only what is in the panel — nothing is written to the PLC. The link between them is an agreement held in stored settings: the driver and serial parameters saved in the HMI project must match the port configuration saved in the PLC. Revising the existing project leaves that agreement exactly as it was. Only three things break it: a factory reset on either device, a PLC download that rewrites the PLC's port configuration, or an edit to the communication settings themselves. Record both sides before you start, keep the settings untouched, and prove the link with a read-and-write test after the download.
Two projects, one link #
What the operator sees are tags. Each tag is bound to a device address in the PLC, and the panel reads and writes that address through a chosen driver over a chosen port. Two tools own the two sides: the PLC software owns the logic and the PLC's port configuration, while DOPSoft, Delta's editor for the DOP series, owns the screens, the tags and the driver settings, all reached in DOPSoft under Options > Communication Setting. Neither tool copies its settings to the other device. The link is simply the agreement that both stored sets match, and maintaining that agreement is your job.
| Setting | Stored in | Symptom when wrong |
|---|---|---|
| Controller/driver selection | HMI project | Tags read nothing; the PLC does not understand the frames |
| Baud rate, data bits, parity, stop bits | HMI project and the PLC's port configuration | Timeouts and frame errors on every object at once |
| Station address | HMI project and the PLC's port configuration | The PLC ignores the panel's requests |
| Tag-to-address bindings | HMI project; the addresses must exist in the PLC program | Link is up but one value reads wrong or zero |
What to verify before you edit #
- Find the HMI project file. Search the workshop PC, USB sticks and backup shares first: the previous maintainer's file is the only complete copy of the screens, alarms, recipes and tag bindings. Open it and confirm the panel model set in the project matches the nameplate on the unit.
- If there is no file, try upload. DOPSoft's upload function (its manual lists Upload All Data) works only when upload was permitted at the last download; an upload-disable setting or a password set at that download blocks it, and there is no legitimate route around it. When upload is blocked the screens must be rebuilt — photograph every screen before anything else, because a download replaces the running project, and take the device addresses and comments from the PLC program. The wider paths are covered in recovering an HMI program when the source file is lost. What survives the trip between engineering tool and device is its own question on every platform; what survives a LOGO! Soft Comfort upload/download round trip is the same audit applied to another controller.
- Read both nameplates. The PLC model decides which controller driver belongs in the HMI project; the panel model decides the screen size and resolution the project is built for. A project built for the wrong panel is refused at download or comes up with the wrong layout.
- Record the PLC's port parameters. In the PLC software, open the port the panel cable lands on and write down the protocol, baud rate, data bits, parity, stop bits, station address and which physical port it is. Then open Options > Communication Setting in the HMI project and compare every field against that list. These recorded values are the reference for every comparison that follows.
- Test the live link with the old project still loaded. Put the PLC in RUN and open a screen that shows a live value — a counter, a timer, an output state. Three outcomes tell you where you stand:
- Values track the PLC: driver, port and addresses agree, so revise the screens and leave the communication settings alone.
- A communication error, or every value frozen: the fault is in the link layer — cable, port type, driver, baud, parity or station address.
- One object wrong while the rest track: that tag's address, data type or format is the fault; the port settings are fine.
Edit, compile, download #
- Back up the PLC program and the HMI project file to separate folders before any edit.
- If the PLC program changed, download it first. Then re-read the PLC's port configuration and compare it against your recorded values: depending on the PLC family and what the project contains, a PLC download can rewrite the port configuration.
- Open the HMI project, confirm the panel model and the controller type, and make the screen edits. Leave the communication settings untouched — a revision keeps them exactly as they were.
- Compile, then download to the panel over whatever route you use. That transfer route is a separate decision from the PLC driver, and separating HMI transfer method from PLC driver selection keeps the two from being confused.
- Go straight to the round-trip proof.
Prove the round trip #
- Read: change a live value from the PLC side and watch the panel follow it.
- Write: enter a value in a panel input object, then open the PLC software's online monitor at that same device address and confirm the value arrived.
- Reverse: change that address from the PLC side and watch the panel update.
One safety rule for step 2: run the write test against a spare, unused address, or with the machine in a state where a test value cannot start motion or energize an output.
A link can run in one direction and still look healthy — the panel displays values while its writes never arrive, or the reverse. The three steps cover both directions, and together with the download they are the whole proof that the revision changed nothing it should not have.
Wire time for one 9600 baud poll of two registers #
Inputs, each with its origin:
- 9600 baud, taken from the recorded port table of this example link. 115200 baud is the rate such links move to when 9600 runs out, so it is computed here as well.
- 8 data bits, no parity, 1 stop bit — the recorded format, so one character on the wire is 1 start + 8 data + 1 stop = 10 bits.
- A Modbus RTU read of two holding registers: an 8-byte request and a 9-byte reply. Whatever protocol your driver list names, count its request and reply bytes the same way.
- The Modbus interframe rule: at least 3.5 character times of silence between frames, fixed at 1.75 ms per interval above 19200 baud.
- An assumed load of 20 such polls per screen refresh at a 1 s refresh, for the decision.
The rule in words: character time is bits per character divided by baud rate; a frame takes its byte count times the character time; one poll cycle is request plus reply plus two silent intervals; and the polling ceiling is 1000 ms divided by the cycle time.
The arithmetic:
- Character time: 10 bits ÷ 9600 bit/s = 1.0417 ms.
- Request: 8 bytes × 1.0417 ms = 8.33 ms.
- Reply: 9 bytes × 1.0417 ms = 9.38 ms.
- Silence: 3.5 × 1.0417 ms = 3.65 ms per gap, two gaps = 7.29 ms.
- Cycle: 8.33 + 9.38 + 7.29 = 25.0 ms per poll.
- Ceiling: 1000 ms ÷ 25.0 ms = 40 polls per second. The assumed screen needs 20 × 25.0 ms = 500 ms of wire time inside its 1000 ms refresh.
Decision: keep 9600 baud while the screen polls no more than 40 two-register tags at a 1 s refresh — this one polls 20, so it fits with the PLC's response time still to spare. Move both ends to 115200 in one session the moment the poll count passes 40 or the refresh must be faster than the wire total: there, 10 bits ÷ 115200 bit/s = 0.0868 ms per character, frames of 0.69 ms and 0.78 ms, two fixed gaps of 1.75 ms, so a cycle is 0.69 + 0.78 + 3.50 = 4.97 ms and the same 20 polls take 100 ms.
This 25.0 ms is the wire minimum only. The PLC's measured response time, the driver's polling schedule, retries and the panel's refresh all add on top of it.
When the link breaks after a download #
Every object faulting at the same moment is the port layer disagreeing: compare cable, port type, driver, baud, parity and station address against your recorded list. One object wrong while the rest keep tracking is a tag fault — fix that binding's address, data type or format and leave the ports alone.
The port type includes the configured mode matching where the cable physically lands. Delta's own FAQ records the failure mode: a DOP series panel set to communicate via CPU port fails when the PLC side uses a CNET card, so the mode in the communication settings must match the port the cable actually uses.
A PLC download that carries port settings, or a factory reset on either device, is how the link breaks even though your own HMI edit was clean. Compare the PLC's current port values against the HMI project field by field. If other equipment shares that PLC port, restore the PLC side to the recorded values; otherwise change the HMI project to match the PLC, because the HMI edit is the smaller change, then download and run the proof again. On an Ethernet pair the same failure arrives as HMI comms errors after a PLC IP address change, and the cure is the same: the address lives in both devices, and both must agree.
Revise, download, prove both directions — that is the entire discipline.
Questions asked
Does the machine have to stop while I download the HMI project?
The PLC keeps running, because a project download is panel-side only. But the panel reloads its project during the transfer, so its screen is unavailable for that time. Schedule the download for a moment when the operator can lose the display, and do the write test only with the machine in a state where a test value cannot start anything.
Can I change the baud rate from the HMI project alone?
No. The baud rate is stored on both ends: in the HMI project's communication settings and in the PLC's port configuration. Set both to the new value in one session, download the PLC side first, then the panel, and re-run the read-and-write proof afterwards. Changing one end alone guarantees the every-object communication fault.
The panel refuses upload and there is no project file. What now?
Upload works only when it was permitted at the last download, and a password or upload-disable set at that download cannot be legitimately bypassed. Photograph every screen before downloading anything, take the device addresses and comments from the PLC program, rebuild the screens in the editor, and reuse the recorded port settings when you rebuild.
Why does the panel fault on every object after a PLC download?
The download can rewrite the PLC's communication port configuration, so the two ends stop agreeing, and the signature is every object faulting at the same moment. Read the PLC's current port values, compare them field by field with the HMI project, and change the HMI side to match unless other devices share that PLC port, in which case restore the PLC side instead.