IMDHMIControls LibraryShop main store

How-to

Replacing a WAGO 750 Profibus coupler without reconfiguring

Controllers and I/O Published 6 min read

Short answer

For a WAGO 750-3xx Profibus coupler such as the 750-343, the replacement needs no software configuration on the remote node: set the DIP-switch address to the same value, match the termination switch, power-cycle, and the coupler rebuilds its fixed 32-byte input and 32-byte output image from the modules on the backplane. Only 750-8xx couplers must be reconfigured with WAGO IO Check.

On this page
  1. What the replacement depends on
  2. Record four things before you power down
  3. Swap procedure for a 750-3xx coupler
  4. Worked example: setting address 42 on a replacement 750-343
  5. If the node carries an 8xx coupler
  6. Reading the LEDs after power-up
  7. Prove the swap before you hand the machine back
  8. Questions asked

No software configuration lives in a 750-3xx Profibus coupler. For a node such as the 750-343, the swap is a switch-matching job: set the DIP switches to the same Profibus address, return the termination switch to the same state, power-cycle, and the coupler rebuilds its process image from the modules physically present on the backplane. The master keeps reading 32 bytes of input and writing 32 bytes of output exactly as before, so the PLC program and its GSD-based hardware configuration stay untouched. Only 750-8xx couplers hold their configuration inside the coupler, and those must be rewritten with WAGO IO Check through the service socket under the front flap. What you have to get right is the switch pattern, the terminator and the module order.

What the replacement depends on #

The WAGO I/O System 750 and 753 puts the fieldbus logic in the coupler and the I/O in the modules behind it, so a coupler swap leaves the field wiring alone. On a Profibus DP segment the coupler is the slave. The two coupler families differ in the one thing that matters here:

Coupler family Examples Where the I/O image comes from What a replacement needs
750-3xx 750-303, 750-333, 750-343 Built from the modules on the backplane at power-up, fixed at 32 bytes in and 32 bytes out Address and termination switches matched; no software step
750-8xx 750-833, 750-843 Parameter set stored in the coupler, edited in WAGO IO Check Physical swap plus the saved IO Check project written to the new unit

The 750-343 documentation adds two facts that explain why the master never notices a 3xx swap: I/O modules with a bit width smaller than eight bits are grouped into one byte, and the master's configuration needs the coupler's GSD file. That fixed image is also what you count when the same node is served over EtherNet/IP instead, as in sizing a Generic Ethernet Module connection for WAGO 750 I/O.

Record four things before you power down #

  • The catalog number on the side label of the faulty coupler, for example 750-343. The replacement must carry the same number, because the GSD the master was configured against belongs to that type.
  • A close photograph of the DIP switch block, with the decimal address written next to it.
  • The position of the termination switch, ON or OFF.
  • The module order from the coupler to the end module, also photographed.

On a Profibus segment, stations hold addresses from 0 through 125 and the master usually sits at address 1. The coupler's switches cover only 1 through 99, so a recorded slave address above 99 cannot belong to this node: re-check the record before you copy anything.

Swap procedure for a 750-3xx coupler #

  1. Take the master out of run, or the segment out of data exchange, so nothing writes outputs to a half-built node.
  2. De-energize the 24 V DC supply to the node. The Profibus cable is signal level, but the backplane and the output circuits carry field energy, so nothing is unseated while powered.
  3. Photograph the switch block, the termination switch and the module order, and write the decimal address next to the photo.
  4. Unscrew the Profibus D-Sub on the front of the coupler and lay the cable aside.
  5. Pull the orange release tab and unseat the coupler from the backplane.
  6. On the replacement, set switches 1 through 7 to the recorded address, set switch 8 OFF so the address comes from the switches, and set the termination switch to the recorded state.
  7. Re-sum the ON switch weights and confirm they equal the recorded address before any power goes on.
  8. Seat the coupler until the release tab clicks, refit the D-Sub and lock its screws.
  9. Re-apply 24 V DC, give the coupler its two to three seconds of boot time, then return the master to run and confirm data exchange.

Worked example: setting address 42 on a replacement 750-343 #

Inputs: the recorded slave address is 42, read from the photograph of the removed coupler's switch block. The switch weights come from the coupler's front panel: switches 1 through 7 are worth 1, 2, 4, 8, 16, 32 and 64 when ON, and switch 8 OFF makes the switch block the address source.

Rule in words: the node's address is the sum of the weights of its ON switches, so the job is finding which weights add up to 42.

Arithmetic, largest weight first: 42 − 32 = 10; 10 − 8 = 2; 2 − 2 = 0. Switch 6 (32), switch 4 (8) and switch 2 (2) go ON; switches 1, 3, 5 and 7 stay OFF. Check the sum: 32 + 8 + 2 = 42. Cross-check: the OFF weights total 64 + 16 + 4 + 1 = 85, and 42 + 85 = 127, the sum of all seven weights, so no bit is left ambiguous.

Decision: with switch 8 OFF and the ON weights summing to 42, the coupler answers at station 42 and the swap needs nothing further. If the sum reads anything but the recorded address, stop and re-set before applying power: one wrong bit moves the address by that bit's weight, so a flipped switch 6 turns 42 into 10 or 74, and the segment gains a missing station and a duplicate in one move.

If the node carries an 8xx coupler #

Work through the same physical steps, then add the configuration pass before the node is trusted: connect the WAGO service cable to the service socket under the lift-up flap on the front, open the node's saved IO Check project, write it to the coupler, and cycle power once more. That service connection is also how coupler firmware is upgraded or the I/O image reshaped, which is exactly the flexibility a straight 3xx replacement does not need. If the saved project is gone, rebuild it: IO Check reads the modules on the live backplane, and the slave configuration in the master tells you the image the program expects.

Reading the LEDs after power-up #

LED State Meaning Action
Power Off No 24 V DC at the power contacts Check the supply and its polarity
Bus Solid green Node is in data exchange with the master None
Bus Flashing green Link up, master has not taken the node into exchange Wait a few seconds; confirm the master's config carries the GSD
Bus Red Segment fault: address, termination or cable Re-sum the switches, check terminator placement, reseat the D-Sub
I/O Red Coupler or backplane hardware fault, the red light that started this job Replace the coupler; on an 8xx, reload the configuration

The terminator belongs on the first and last physical devices of a segment and nowhere between them. A 750-303 segment runs at up to 12 Mbaud, and at that rate a misplaced terminator is enough to hold the bus LED red. Reading a switch-set address against an end-of-segment terminator is the same discipline as the DIP-switch and termination setup of a PLC-5 remote I/O adapter. When the symptom is intermittent dropouts rather than a steady red, suspect the segment before the coupler; the steps in troubleshooting intermittent Profibus dropouts on an S7-400 network apply to any DP master.

Prove the swap before you hand the machine back #

With the node in data exchange, work one point end to end in each direction: toggle a known field input and watch it move in the master's input table at the byte you expect, then command one output and measure it at the terminal. That catches a module-order slip the LED states cannot see, because the image size never changes when the order does. For the full pass, follow the remote I/O commissioning checklist for a modular station.

Questions asked

Does anything change in the PLC program after the swap?

Nothing, as long as the slave address, the module types and their order match. The 32-byte input and 32-byte output image is fixed by coupler family, but the data inside it is mapped in physical module order, with channels narrower than eight bits packed into shared bytes. Reorder or substitute modules and your channels move inside the same image, so the program reads them in the wrong place.

The new coupler powers up but the bus LED stays red. What should I check?

A red bus LED points at the segment, not at the coupler's health. Sum the ON switch weights again and compare with the recorded address, confirm the node is not sitting on the master's address, since masters commonly use address 1, and check that exactly the two end devices on the segment carry the terminator. Also confirm the D-Sub connector is fully seated with its screws locked.

Can I do the replacement with the node still powered?

No. The Profibus cable is signal level and can be unplugged live, but the backplane and the output circuits are not: de-energize the 24 V DC supply to the node before unseating the coupler or any module.

I lost the IO Check project for our 8xx node. Is the old configuration recoverable?

Not from a coupler that no longer boots, but the node can be rebuilt. Connect to the service socket under the front flap, let WAGO IO Check read the modules on the live backplane, and rebuild the parameter set from that physical module list together with the slave configuration the master already holds. Write it to the replacement, then cycle power once more.

Do the other stations on the segment need re-addressing?

No. Each station's Profibus address is set on its own switches and nothing else inherits it. Keep the replacement at the recorded address and leave every other node alone. Addresses only have to stay unique across the segment and clear of the master's own address, which is why you copy the old value instead of picking a fresh one.

Keep reading

  • Troubleshooting

    Sizing a Generic Ethernet Module connection for WAGO 750 I/O

    Enter the Generic Ethernet Module connection from the coupler's process image: input assembly instance 107 sized to input-image bytes plus one, output assembly instance 101 sized to the output-image bytes exactly, configuration assembly instance 1 at size 0, Comm Format SINT, and the remaining settings at their defaults. The 750-352 orders analog data before digital, so build both byte maps from the coupler's image view and round the totals once, never slot by slot.

    Controllers and I/O

  • How-to

    Driving a WAGO 750-653 Modbus RTU module from CODESYS

    On a CODESYS Control Win V3 soft PLC, WagoAppPlcModbus cannot reach a 750-653 behind a 750-354 EtherCAT coupler, because those blocks need WAGO controller firmware. Drive the module's raw process image yourself: set the serial parameters, move each fragment with the control/status byte toggle handshake, and frame the Modbus RTU request and response in your task. Each fragment costs at least two task cycles, so a full transaction takes ten cycles or more.

    Industrial networks

  • How-to

    Using a PLC as a Modbus RTU to Profibus gateway

    Keep the regulator and let one PLC carry both buses. Poll the regulator over Modbus RTU on a fixed cyclic interval, map every register to a defined PROFIBUS DP location with documented scaling, and hand the BMS a data-valid flag instead of stale values. Terminate each bus at its own two ends; never join RS-485 and PROFIBUS into one network.

    Industrial networks