When a DOP-B03S211 accepts addresses in the screen editor but never shows or writes live values in the CJ1M, the fault sits in one of three places: the serial link, the controller driver, or the address syntax. Check them in that order. An address-format fix cannot help while the link is down, and a correct link still fails if the driver belongs to the wrong Omron family.
Check 1: Link Status Between the HMI and the CJ1M Serial Port
Prerequisite:
- In CX-Programmer, open PLC Setup and read the serial settings for the port the HMI uses. Record the mode, baud rate, data bits, parity, stop bits, and Host Link unit number.
- Confirm the mode is Host Link. NT Link and Toolbus are Omron-to-Omron protocols, and a third-party HMI driver will not answer on them.
- Check the CPU front DIP switch. One pin forces default port settings and overrides PLC Setup. Its state must match the settings you intend to use.
- In the Delta editor communication settings, set the same baud, data bits, parity, and stop bits. Set the PLC station or unit number equal to the Host Link unit number.
- Build the cable from the Omron wiring diagram in Delta's HMI communication manual. Do not reuse a cable made for a drive.
Reading that gates the next check: put a single numeric display on a DM word that the ladder is actively changing.
- If the HMI shows a communication error or the display stays blank, fix the link first. Recheck the parity and stop bits, the unit number, the TX/RX crossover, and the signal ground.
- If the value updates, the link is good. Go to Check 2 only if some areas or addresses still fail.
Check 2: Delta Driver Family Matched to the CJ1M Memory Map
Omron serial Host Link has two command sets:
- C-mode commands date from the C-series. They reach only the legacy areas: CIO/IR, HR, AR, LR, DM, and timer/counter.
- FINS commands carried over Host Link reach the CS/CJ memory map, including the W (work) area and the CS/CJ-style H area.
If the Delta project uses a driver written for older C-series PLCs, DM words may work while W or H addresses fail or return the wrong data.
- Open the controller selection in the Delta project. Select the Omron driver listed for the CS/CJ family, not a C200H/CQM1-era driver.
- Look up the supported area table for that driver in Delta's communication manual. Confirm every area your screens use (CIO, W, H, D, A, T, C) appears there, and note its allowed range.
- Download the project again. Retest one address from each area used.
Outcome: if every area now reads, go to verification. If some addresses in a supported area still map to the wrong location, go to Check 3.
Check 3: Address Syntax, Word/Bit Notation, and Hex Entry
The Delta editor keeps whatever string you type, but the driver parses it by its own rules. A wrong format can point to a different word or bit without raising any error. Test these cases one at a time:
| Symptom on the HMI | Likely cause | Check / correction |
|---|---|---|
| Word address shows data from a different word | Missing or wrong area prefix, so the driver falls back to a default area | Pick the area from the driver's dropdown (for example DM or W) instead of typing a bare number |
| Bits 00–07 work, bits 08–15 fail or hit the wrong bit | Bit field entered in a different radix than the driver expects | Omron bits run 00–15 within a word (word.bit). Check whether the Delta driver wants the bit number in decimal or as a hex digit 0–F, and try the other form |
| Word address correct in decimal but reads the wrong location | Driver expects hex word entry for that area | Enter the same address in hex and compare it against the manual's address format column |
| Bit object on a DM word does nothing | Driver does not support bit access in that area | Use a word object with bit masking, or move the flag to CIO/W/H |
| Address rejected or goes to error when high | Outside the driver's supported range | Compare with the range in the Delta area table and the CJ1M memory map in CX-Programmer |
Confirm each correction by watching the same address in the CX-Programmer Watch window. Write a value from one side and check that it appears on the other before moving on.
Check 4: Why the Modbus Driver Route Does Not Apply to the CJ1M
Setting the HMI to a Delta Modbus RTU or ASCII controller works on drives from other brands because those drives are Modbus slaves. The CJ1M built-in serial ports do not answer as a Modbus slave. They support Omron protocols, and the serial gateway function acts as a master toward other devices, not as a slave to an HMI.
If a Modbus driver on the DOP-B03S211 polls the CJ1M directly, you get timeouts regardless of how the addresses are entered. Making the CJ1M a Modbus slave requires an added serial communications unit with a protocol program, or a no-protocol port with ladder that decodes the frames. Both add engineering work and scan-time cost that the native Omron driver avoids.
Decision:
- Use the native Omron CS/CJ Host Link driver in all cases.
- Consider Modbus only when the same HMI port must also talk to Modbus drives on a shared bus. In that case, give the PLC its own port instead.
Driver and Address Correction Procedure with Live Verification
Prerequisites:
- Check 1 passed (link is live).
- The CS/CJ driver is selected.
- The Delta area table for that driver is at hand.
- Freeze the port settings. Record the final PLC Setup values and the DIP switch state. Confirm the HMI settings match them field for field.
- Build a test screen. Add one word display per area in use, one set/reset bit on a CIO or W bit above 07, and one numeric entry writing to a spare DM word.
- Set the entry format. Enter every address using the area prefix and radix from the Delta table. Confirm the editor accepts each one without warning before downloading.
- Test word reads. Download and watch each word display. In CX-Programmer Watch, change the same words and confirm the HMI tracks every change.
-
Test bit writes. Press the HMI bit button. Confirm the matching
word.bittoggles in the Watch window and no neighbouring bit changes. - Test word writes. Enter a distinctive value (for example 1234) on the HMI. Confirm the spare DM word reads that value in CX-Programmer and holds it through one PLC scan cycle in RUN.
- Apply to the full project. Convert the production screens to the same address format, download again, and repeat steps 4–6 on a sample of real tags from each area.
- Run the final verification. Cycle power on the HMI only and confirm it reconnects on its own. Then cycle the PLC and confirm the displays recover without a manual reset on the HMI.
FAQ
Why does my Delta HMI read Omron DM words but not W or H addresses?
The selected driver is almost certainly using C-mode Host Link commands, which reach only the legacy areas such as DM, CIO, HR, AR, and LR. Select the Omron CS/CJ family driver in the Delta project so the HMI uses FINS over Host Link and can reach the CJ1M W and H areas.
Why does the DOP-B03S211 time out when set to Modbus RTU with a CJ1M?
The CJ1M built-in serial ports do not respond as a Modbus slave, so a Modbus master HMI gets no reply. Set the CJ1M port to Host Link in PLC Setup and use Delta's native Omron driver instead.
Why do Omron bit addresses above 07 go to the wrong bit on a Delta HMI?
Omron bits run 00–15 within each word, and the driver may expect the bit field in a different radix than the one you typed. Check the address format column in Delta's communication manual for that driver, re-enter the bit in the expected form, and confirm the toggle in the CX-Programmer Watch window.