IMDTouchKnowledge BaseShop main store

How-to

Connecting an Omron CV1000 PLC to WinCC over an OPC server

HMI and touchscreens Published 7 min read

Short answer

Classic WinCC has no Omron CV-series channel, so the working route is an OPC server that speaks Host Link to the CV1000 and OPC DA to WinCC. Configure the server against the PLC first, prove one read, then build WinCC tags from the server's item addresses. Use the documented CV1000-CPU01-EV1 Host Link reference values: ASCII, 7 data bits, even parity, 2 stop bits, unit 00, 9600 or 19200 bps.

On this page
  1. What talks to what
  2. Host Link settings on the CV1000 side
  3. How many characters per second the line carries
  4. The procedure from PLC port to WinCC tags
  5. Get the data interpretation right
  6. The decision for each case
  7. Questions asked

Classic WinCC has no Omron CV-series channel, and Siemens support guidance is blunt about recent versions: in WinCC V7.5 there is no Omron driver in the software at all, and Host Link through the WinCC OPC client is the route. So build the connection in three pieces: the CV1000 on Host Link serial, an OPC server on a Windows PC that owns the Omron protocol, and WinCC as the OPC DA client reading that server. WinCC never speaks Host Link itself. That is the standard fix whenever the HMI software has no driver for your PLC: put a server in the middle and let each side use the interface it already has. This article gives the architecture, the serial settings documented for the CV1000-CPU01-EV1, the arithmetic for choosing 9600 or 19200 bps, and the procedure from PLC port to live WinCC tags.

What talks to what #

OPC Data Access (OPC DA) is the classic Windows COM/DCOM interface for moving process values. In plain terms, it requires a server program that exposes each process value as an item at an address the server itself defines, and a client that reads and writes those items. The server owns the device protocol; the client never sees it. When server and client run on different computers, Windows DCOM security has to let the client's identity reach the server before any item moves.

WinCC takes the client role. Nothing in a CV-series rack serves OPC, so the server is a separate Windows program, and for this PLC the documented pairing is CX-OPC Server from Omron: the WinCC-as-OPC-client procedure is documented for WinCC V6.2 SP2, and the classic WinCC V7.3 communication manual documents the OPC DA client connection. Any third-party server is equally valid the day its device list names your exact CV CPU and Host Link, and not before.

When a real driver exists you skip the server entirely and configure the channel directly, as in connecting a TSX Premium PLC to WinCC. The CV1000 has no such channel, which is why the server is not optional here.

Identify your WinCC product before configuring anything. The procedure in this article is classic WinCC; WinCC Unified and the TIA runtime are different products with their own communications options, and the V7.3 OPC DA documentation does not carry over word for word.

The NS-Series Host Link Operation Manual V098-E1-05 covers the CV1000-CPU01-EV1 directly, and its Host Link connection values are the verified reference for this CPU's port:

Setting Documented value What it must match
CPU CV1000-CPU01-EV1 The full designation, suffix included, against the server driver's device list
Character format ASCII, 7 data bits Serial framing in the OPC server driver
Parity Even Both endpoints
Stop bits 2 Both endpoints
Unit number 00 The server driver's destination station
Transmission speed 9600 or 19200 bps Both endpoints

These are that manual's settings for an NS terminal talking to this CPU, so treat them as a verified reference for the port, not as a universal server configuration. The rule that matters: the server driver must use the same character format, parity, stop bits, unit number and speed as the PLC port, and any change must be made at both ends together.

Get the cable pinout and the electrical interface from the manuals for your exact port hardware. Connector shape proves nothing about signaling, and a passive cable cannot convert one electrical interface into another.

A parity or format mismatch does not fail cleanly: you get garbage characters and timeouts instead of an obvious error, the same failure mode seen when Modbus RTU devices disagree on even or odd parity.

How many characters per second the line carries #

Size the link with the documented framing. One character on the wire is 1 start bit + 7 data bits + 1 even-parity bit + 2 stop bits = 11 bits. At 9600 bps the line moves 9600 bps ÷ 11 bits per character = 872.7, so about 873 characters per second. At 19200 bps it moves 19200 ÷ 11 = 1745.4, about 1745 characters per second, exactly double, because the framing is unchanged and only the bit rate doubles. Host Link request and response share the same wire, so every poll spends characters from that budget in both directions, and the turn-around gap between frames keeps the real transaction rate below these numbers. Treat them as line capacity, not as polls per second.

Decision: commission at 19200 bps with both ends set identically. Drop both ends to 9600 bps only if the link shows framing or overrun errors at the higher speed. Never split the speed between the two ends; a speed mismatch produces no traffic at all, which is harder to diagnose than garbage.

The procedure from PLC port to WinCC tags #

  1. Read the full CPU designation from the nameplate, here CV1000-CPU01-EV1, and identify the actual port or communications unit the cable will use. The bare family name CV1000 selects neither wiring nor driver settings.
  2. Choose the OPC server against a device list that names that CPU and Host Link. CX-OPC Server is the documented Omron-side pairing for the WinCC OPC client. Confirm operating-system compatibility, the OPC DA interface, and licensing with the manufacturer or its authorized distributor before you build on it.
  3. Wire to the pinout in the manuals for your exact port hardware, then set the framing from the table above identically at the PLC port and in the server driver.
  4. Close every other program holding that serial port, including the PLC programming tool. Two applications cannot share one COM port, and each will blame the other.
  5. In the server, configure the device for the CV CPU, the port, and destination unit 00, then read one known, noncritical PLC value with the server's own test client. A successful read proves the link; you do not need a write.
  6. Change that value through normal machine operation, never by forcing an output, and confirm the server tracks it with no repeating communication errors. Port or setting changes on a running machine belong under its approved maintenance procedure, because a port change drops every existing Host Link session.
  7. Bring in WinCC with the server running on the WinCC computer. Add the OPC DA client connection and browse the server's items from WinCC.
  8. Create a pilot set of about five WinCC tags from the server's item browser. Do not carry address syntax over from another driver; the item syntax belongs to the server.
  9. Compare every pilot tag against the same PLC address in the programming tool: raw value, sign, data type, and bit state must all agree before you import the full tag list.

Get the data interpretation right #

A working connection and correct data are two different proofs. A good transaction can still read the wrong address or interpret the right bits as the wrong type: signed against unsigned, or a two-word value with the words in the wrong order, both put plausible numbers on the screen.

Keep each engineering-unit conversion in exactly one place. If the server scales a raw count and WinCC scales it again, the display is wrong with no communication fault to chase. Leave write access disabled on every tag the HMI only displays.

If the OPC server must end up on a different computer, that move adds DCOM configuration, meaning client identity plus access and launch permissions, to the job. Do it after the single-computer proof above, never as the first step, so a failure is either the PLC link or the DCOM layer, never both at once.

The decision for each case #

  • Classic WinCC to a CV1000: take the OPC DA server route, with CX-OPC Server as first choice because the pairing is documented; a third-party server only when its device list names your exact CV CPU and Host Link.
  • WinCC version unknown: identify the product first. This procedure is classic WinCC; Unified and TIA runtimes are different products.
  • Serial speed: 19200 bps at both ends, 9600 bps at both ends as the fallback on framing errors.
  • Server placement: same PC as WinCC through commissioning; move it to its own computer with DCOM only when the architecture requires it.

Questions asked

Can I reach the CV1000 with WinCC sockets instead of an OPC server?

Not for the CPU port documented here. Sockets give WinCC raw TCP or UDP on Ethernet, and the CV1000-CPU01-EV1 link in this setup is Host Link on serial, so nothing at the PLC end is listening on a socket. If your rack carries a supported Ethernet communications unit, the route is still an OPC server whose device list names that unit; sockets would mean hand-writing the Omron protocol yourself.

Will an OPC UA server work with this WinCC connection?

Not directly, and not with the procedure in this article. OPC DA is the classic COM/DCOM Data Access interface that classic WinCC V7.3 documents, while OPC UA is a different, platform-independent interface. A server exposing only OPC UA cannot serve the DA client connection described here. Choose a server that exposes OPC DA alongside UA, and the interface question is closed before the PLC is even connected.

The server's test client reads the PLC, but WinCC cannot read the server. Why?

Because the failure has moved from the PLC link to the PC layer. With both programs on one computer, suspect DA registration or name resolution between client and server. With the server on a different computer, suspect DCOM security blocking the client identity. Running the proof on a single computer first tells you which half is broken before you touch DCOM permissions.

Is there any way to write a native WinCC channel for the CV1000?

Siemens offers a channel development kit for writing your own communications channel, and that is the only native route left for this CPU. Treat it as a software project with long-term maintenance, not a configuration task: you own the protocol implementation, the testing, and every Windows migration afterward. For one CV1000 on Host Link, the OPC server route reaches the same tags for a fraction of the engineering.

Where does the unit number 00 come from?

It is the Host Link station number the PLC answers on that port, and 00 is the value the documented NS connection for the CV1000-CPU01-EV1 uses. It must equal the destination station configured in the OPC server driver. Keep one master on the port: the server polls it, and anything else addressing unit 00 at the same time contends for the same link.

Keep reading

  • Explainer

    HMI OPC UA Server vs Client: Which Direction Works

    OPC UA support on an HMI spec sheet almost always means the panel runs a server that serves its tags to external clients. Reading PLC symbols by name needs an OPC UA client driver, a separate capability you verify in the driver list for your exact software release, target and license.

    HMI and touchscreens

  • How-to

    Connecting an HMISTO735 to an M241 PLC with Vijeo XD

    Commission the HMISTO735 to M241 link in three layers: a driver and endpoint both Vijeo XD and the SoMachine project support, a proven Ethernet path with addresses and a ping, then one exposed test variable passed read and write end to end. Build screens only after that loop closes, and fix each fault at the first layer that fails.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens