IMDTouchKnowledge BaseShop main store

How-to

Connect a TSX Premium PLC to WinCC or Vijeo Designer

HMI and touchscreens Published 7 min read

Short answer

Pick WinCC or Vijeo Designer as the single supervisory endpoint, then choose the TSX Premium Ethernet module by the driver it can serve, not by its connector. Both packages speak Modbus TCP to the module's server, so the chain is controller, module, protocol, driver. Enter the module's IP and port 502, prove the map with one animated test word, then import the rest of the tag list.

On this page
  1. Pick one supervisory endpoint, not two
  2. Match the Ethernet module to the driver
  3. Set the network addresses from one plan
  4. Configure the driver step by step
  5. Worked example: animating %MW100 in WinCC over Modbus TCP
  6. Map the rest of the PLC addresses to tags
  7. Prove the path before loading the tag list
  8. Questions asked

A TSX Premium programmed in PL7 Pro reaches WinCC or Vijeo Designer one documented way: through the Ethernet module's Modbus TCP server, driven by the matching driver in whichever package you picked. The module's connector never animates a variable — the chain controller to module, module to protocol, protocol to supervisory driver does. So pick one supervisory endpoint first, confirm the rack and the PL7 Pro hardware configuration accept the module you fit, point the driver at the module's IP address, and prove the address map with one animated test word before importing the tag list. This article works that chain for a machine that already runs: the control program exists, the supervision view is drawn, and only the path from view to PLC is missing.

Pick one supervisory endpoint, not two #

WinCC and Vijeo Designer are alternatives in this installation, not layers on top of each other. The package you pick owns the driver, the tag list and the animation, and it initiates every exchange: the runtime asks, the Premium answers from the requested addresses. Decide by what the plant already runs — a site standardized on WinCC keeps WinCC, a site with Magelis terminals already built in Vijeo Designer keeps Vijeo Designer. Whichever you pick runs as a PC runtime at the machine, and shop-floor operator stations built for that role are industrial panel PCs.

Either choice lands on the same protocol, because the Premium's Ethernet module serves Modbus TCP and both packages speak it; the module decision below follows from that, not from the connector. PL7 Pro itself publishes nothing to supervision: it edits and diagnoses the controller application, and the supervisory package reads PLC addresses. Your Unity Pro background transfers to this job untouched — the runtime side never sees the editor. Other clients ride the same server the same way; the walkthrough on connecting a TSX Premium to a Visual Basic HMI starts from that identical principle.

Match the Ethernet module to the driver #

Read the deciding chain left to right: the CPU must accept the module in that rack, the module must expose the protocol the driver speaks, and the driver must document that interface. A module fitted for its Ethernet connector alone fails quietly at the third link — the link lights go green and the session still carries no data.

Three checks before anything is fitted:

  • Open the existing PL7 Pro project's hardware configuration and confirm it supports the module you intend to fit for that CPU and rack. A mismatch can keep the PLC configuration from validating or leave the module unavailable.
  • Confirm the chosen package documents a Modbus TCP/IP client for this controller: Siemens' support forum carries a documented WinCC 7 case against a MODICON TSX Premium over Modbus TCP/IP, and Schneider Electric's own driver-selection FAQ for Vijeo Designer makes the target device — not the cable — decide the driver entry.
  • If the driver list offers no entry the module's documentation supports, stop there; what to do when the HMI software has no driver for your PLC is the honest next read.

Set the network addresses from one plan #

Assign both ends from the machine network plan before any driver work, then prove the plan with a ping.

Setting PLC side Supervisory side What proves it
IP address the Ethernet module's unique address the station's own unique address no duplicate-address complaint at either end
Subnet mask per the plan per the plan the station pings the module
Default gateway only where traffic crosses a router the same routing plan a round trip through the router
Service port 502 on the module's Modbus TCP server 502 in the driver the session opens

A lit link LED at both ends proves electrical link and negotiation and nothing more — it says nothing about IP reachability. Ping the module from the supervisory computer before building a single tag. If that ping drops intermittently, fix the wire, the switch port or the addressing first; the walkthrough on diagnosing intermittent HMI to PLC Ethernet comms hangs follows that hunt step by step.

Configure the driver step by step #

  1. Create one communication connection in the supervisory project for the Premium.
  2. Select the Modbus TCP/IP driver — the Modbus TCP/IP channel in WinCC, the Modbus TCP entry in Vijeo Designer's driver catalog.
  3. Enter the Ethernet module's IP address from the network plan — the module's address, never the programming PC's.
  4. Leave the service port at 502 unless the network plan explicitly remaps it.
  5. Fill any station, unit or route fields the driver shows with values taken from the module's configuration in the PL7 Pro project; a default that looks right is not a match.
  6. Set the connection timeout for the network you actually have and leave retries alone — retries mask a broken path, they do not repair it.
  7. Open the connection and watch the driver's own status diagnostic until it holds steady with no retry cycle before any tag work.

Worked example: animating %MW100 in WinCC over Modbus TCP #

The inputs, each with its source: the endpoint is WinCC 7 with its Modbus TCP/IP channel, documented in a Siemens support-forum case against a MODICON TSX Premium; the transport is Modbus TCP on TCP port 502, the registered Modbus TCP port; the test word is %MW100 — illustrative here, so use a word your own program actually writes, read from the PL7 Pro listing; the sizes come from the two standards involved, one %MW word equals 16 bits and one Modbus holding register equals 16 bits.

The rule in words: the module's Modbus TCP server serves the controller's internal words as holding registers, so the %MW index is the register offset, and a client address field in the 5-digit 4x convention writes that offset as 40001 plus the offset, while a field expecting a plain decimal offset takes the offset itself.

The arithmetic: offset = 100, so the 4x reference = 40001 + 100 = 40101.

The result: configure one WinCC tag as holding register 40101 — or 100 if the field is 0-based decimal — with the PLC address set to the module's IP and the port at 502, then force %MW100 to a known value in PL7 Pro or drive it with the process.

The decision: quality good and the tag value tracking the live word proves the mapping base, so import the remaining tags. A bad tag while the ping and the driver status are clean makes the offset convention the first knob — flip once between 100 and 40101 and re-check. Values still scrambled after that point to the data-type row of the mapping table below, not to the connection.

Map the rest of the PLC addresses to tags #

Build an address map from the PL7 Pro application and bind every tag to the address and type the control program actually uses — the supervisory package reads PLC memory addresses, not symbol names, unless your exact workflow provides a verified import path. For example, the illustrative 32-bit value at %MW100 occupies the pair %MW100 and %MW101 and is read as 2 registers from offset 100 in one request. For the bit-level side of that mapping on the Vijeo Designer endpoint, the TSX Premium to Vijeo Designer input bit mapping walkthrough works through input bits one register at a time.

Field to verify What to check Symptom when wrong
PLC address the exact address the control program writes a plausible but wrong value, or a frozen one
Data type bit, 16-bit word or 32-bit pair matching at both ends scaling garbage or huge plausible numbers
Access direction commands writable, statuses read-only the display works but operator commands fail
Update cycle poll rate suited to the signal and the network sluggish animation or bandwidth spent for nothing
Alarm source the intended bit and its polarity alarms never fire, or fire inverted

If a large list starts animating slowly once it is loaded, the poll rates and the link are the suspects, not the driver — the piece on why HMI point updates run slow on an Ethernet PLC link breaks that arithmetic down.

Prove the path before loading the tag list #

  • The PLC is in its intended operating state and the Ethernet module reports no fault.
  • The PL7 Pro programming session is closed: Schneider Electric's FAQ documents an unclosed PL7 Pro connection making the next connection impossible, so close it before commissioning.
  • Link lights are up at the module, the station and any switch in between.
  • A ping to the module runs clean, not intermittently.
  • The driver status holds a session with no retry cycle.
  • The one test word from the worked example animates with good quality.
  • One writable test point is written once and observed — and only where the PLC logic already interlocks that command; never prove a write on a machine running product.

When that list is green, load the full tag list. The endpoint, module, protocol and driver now describe one working path, and every remaining tag is an address-mapping job, not a communications one.

Questions asked

Can WinCC and Vijeo Designer both stay connected to the same TSX Premium?

Yes. The Ethernet module's Modbus TCP server is built to serve several client stations at once, so each package gets its own connection entry pointing at the same module IP address and service port. Keep them as two independent stations with their own timeouts and their own tag lists, and commission the first one alone — one driver to tune, one list to keep consistent. Add the second only when a second operator role really needs it.

Does it matter that I know Unity Pro but have never used PL7 Pro?

Not for the supervisory link. The Premium serves Modbus TCP from its Ethernet module no matter which programming package wrote the application, and the driver chain on the PC side is identical. PL7 Pro matters for exactly two jobs: confirming its hardware configuration accepts the Ethernet module you fit, and reading the addresses your program uses so every tag maps to the right word. Both jobs are done in the existing project without touching the control logic.

A value in the PLC is 32-bit but Modbus registers are 16-bit — how do I map it?

Read it as two consecutive registers in one request. A 32-bit value stored at %MW100 occupies %MW100 and %MW101, so the client asks for 2 registers from offset 100 and the driver assembles them. The driver then offers a word-order or swap setting; pick the order that reproduces the PL7 Pro value and prove it by writing a known pattern to one word first. A wrong word order shows a huge plausible-looking number, not bad quality.

Does anything besides the two endpoints need to allow the traffic?

Yes. A switch is transparent, but a router or firewall between the supervisory PC and the cabinet is not: Modbus TCP runs on TCP port 502, so a firewall must pass that port in both directions, and anything doing address translation must keep the driver's port field equal to the port the server answers on. On one flat machine subnet with a switch in between none of this appears, and a ping through every hop is the quick proof.

Keep reading

  • Troubleshooting

    Why Vijeo Designer cannot connect to an M580 PLC

    The HMI fails to reach an M580 because one leap hides which layer broke. Match the project target to the HMIGTO, prove the computer-to-panel transfer path and the panel-to-PLC runtime path as two separate tests, add the Modbus TCP equipment the controller actually serves, then prove communication with one forced read and one approved write before any faceplate. Each layer gives a pass or a named fault.

    HMI and touchscreens

  • How-to

    Connecting an HMI to a GE Fanuc PLC Over Ethernet SRTP

    Yes. GE controllers speak SRTP, their native Ethernet protocol, on TCP port 18245, and the HMI editor's built-in GE Fanuc SRTP driver needs no Modbus TCP and no purchased add-on. VersaMax CPUs with integrated Ethernet serve SRTP only, and a Series 90-30 needs CPU firmware 8.xx before its IC693CMM321 Ethernet module will cooperate.

    HMI and touchscreens

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens