IMDHMIControls LibraryShop main store

Troubleshooting

Connecting STARTER to a PROFIBUS drive through an S7-300

Industrial networks Published 8 min read

Short answer

Being online with the S7-300 does not put STARTER online with the drive. Confirm the drives are on PROFIBUS, make the drive's station address match the one the project expects, select the routed path through the S7-300 in STARTER, and save the new parameters to EEPROM with P0971 = 1.

On this page
  1. Is the purple daisy chain PROFIBUS or Modbus?
  2. Why can I go online with the CPU but not the drive?
  3. Which station address does the drive need, and how do I set it?
  4. How do I point STARTER through the S7-300 to the drive?
  5. What if one drive still will not come online?
  6. How do I keep the new motor parameters after a power loss?
  7. When is the drive ready to run again?
  8. Questions asked

You are online with the S7-300 over Ethernet, STARTER still cannot see the MICROMASTER 440, and the fix is not another cable. Those drives sit on PROFIBUS behind the CPU, so STARTER must reach them on a routed path: from your Ethernet adapter, through the CPU, out of its PROFIBUS master interface. The repair order is fixed — confirm the network is PROFIBUS, make the drive's station address match the one HW Config expects, select that routed path in STARTER, then write the edited motor data to non-volatile memory so it survives the next power cut. The sections below work through those steps in the order you meet them.

Is the purple daisy chain PROFIBUS or Modbus? #

Treat the purple daisy chain as PROFIBUS: RS-485 is the shared electrical layer, Modbus RTU is a different protocol that runs on the same wiring, and drives that appear as DP stations in the STEP 7 project settle the identification.

RS-485 is the TIA/EIA-485 electrical standard, and both PROFIBUS and Modbus RTU run over it, so cable and topology never identify a protocol on their own. Purple sheathed cable in a daisy chain ending in DB9 plugs is classic PROFIBUS practice, but it is a hint, not proof.

PROFIBUS DP is the IEC 61158 type 3 fieldbus: an addressed master-slave bus in which the master's configuration declares every station address. That is why the decisive evidence lives in the project. Open the HW Config view of the STEP 7 project that matches this rack — the MICROMASTER 440 drives and the G120 appear there as DP stations under a PROFIBUS master interface, and that same page gives you each drive's configured station address. A machine on Modbus would instead show a serial interface or a gateway in the project, with the drives polled by register, nothing like a DP master.

Leave the working bus alone. The drives exchange control data with the CPU in production; the task is to borrow a path for STARTER, not to re-cable or re-address anything.

Why can I go online with the CPU but not the drive? #

Going online with the CPU proves only the Ethernet leg; the drive sits on PROFIBUS behind that CPU, and STARTER reaches it only through a routed path the CPU forwards — a successful CPU session contributes nothing to drive parameter access until that route is selected.

Routing is documented S7 behavior: a PG/PC crosses subnetwork boundaries through an S7 station to reach further stations. Your session enters the rack through the Ethernet CP (in this rack, a CP 343-Lean type card), crosses to the CPU over the backplane, and leaves through the CPU's PROFIBUS DP master interface toward the drive bus. The CPU is the router; the Ethernet card is only the door. Three things must line up:

  • A matching project. The STEP 7 project loaded in the tool must contain this CPU with its DP interface configured as PROFIBUS master and the drive stations entered, because the route and the target addresses are read from that configuration.
  • An activated DP interface. The PROFIBUS interface that carries the route must be configured and active on the CPU; a DP port the project never set up forwards nothing.
  • A free connection resource. Every routed engineering session occupies one of the CPU's finite connection resources, so close idle online sessions before connecting STARTER through the same CPU.

STEP 7 succeeding while STARTER fails is therefore the expected symptom when the route was simply never selected — it is not evidence of a broken drive.

Which station address does the drive need, and how do I set it? #

Set the drive's station address to the exact value the STEP 7 project shows in HW Config — if the master expects station 5, the drive must read 5 — because a mismatch or a duplicate leaves the CPU polling a station that is not where the configuration says it is.

Read the expected value from the project, not from guesswork: open the properties of the drive's DP station in HW Config and note its address, then compare it with what is actually set at the drive. The setting mechanism belongs to the fitted communication board: switch banks behind a screwdriver-opened window are common, some boards take the address from a parameter, and the board's manual names its own method.

Worked example. HW Config shows the failing MICROMASTER 440 at station 5, so the drive must be set to 5. Binary switch banks make the arithmetic explicit: with switch weights 1, 2, 4, 8, 16, 32, 64 and 128, station 5 is 1 + 4, so switch 1 ON, switch 2 OFF, switch 4 ON, and every heavier switch OFF. Set nothing else — a wrong address leaves the CPU looking for the station where the configuration says it should be, and a duplicate collides with a neighbor.

Switch settings are read at initialization: after a change, bring the machine to a safe state, remove power from the drive completely, restore it, and let it re-initialize before judging the result. Two decisions follow from your actual fault. The gear motor was replaced, not the drive, so do not touch the working address at all. If a communication board itself was ever replaced, copy the old board's switch positions onto the new one before it goes in.

For a G120 target, the notes on configuring a G120 module address for online access in STARTER V4.5 show the same pairing of configured address and routed session.

How do I point STARTER through the S7-300 to the drive? #

In STARTER, select the laptop's physical Ethernet adapter as the access point and connect through the S7-300 station that owns the PROFIBUS master interface — the tool then lists the drives behind that DP network instead of hunting for a drive on the laptop's own subnet.

Set the tool's access point to the same adapter STEP 7 uses; a stale access-point selection quietly sends STARTER out of a different interface and produces errors that look like drive faults. In the target selection, choose the route via the S7 station — this CPU — rather than a direct drive connection, so the tool resolves the drive objects behind that station's DP network from the loaded project. Where that dialog is the sticking point, the walkthrough of STARTER PG/PC interface configuration for a G120 online connection covers the selection step by step.

Reuse the project that connected successfully in the past if it can be found: it already holds the drive object with the right device type, address, and route. Assembling a fresh direct-to-drive connection is how a healthy bus gets broken, and the vendor's routing guidance explicitly supports going online through the CPU without first downloading any new hardware configuration into it — read the project, do not re-download the rack just to gain a route.

One safety note: keep the machine stopped and the drive inhibited while you write motor data, because a parameter change that leaves the drive enabled can produce unexpected shaft movement.

What if one drive still will not come online? #

A drive that stays unreachable while its neighbors connect is a local problem — station address, drop wiring, or a project target that does not match the fitted board — and the split is simple: one drive means look at that station, no drives means look at the route.

Work the symptom down this list:

  • No drives reachable, CPU online: the route or the access point is wrong. Fix the tool side; the bus is innocent.
  • One drive unreachable, neighbors fine: check that station alone — switch positions against HW Config, drop connector seated, terminating-resistor switch ON at both ends of the segment.
  • CPU diagnostics report the station missing: verify station power, connector lock, and termination first; a missing station is a wiring or power fact before it is a software fact.
  • Station present but flagged as a configuration mismatch: the message frame configured in HW Config does not match the fitted board, so correct the project entry to the board's documented profile.
  • Drive online but parameter writes rejected: read the rejection text; it usually names the drive's operating state, which is a drive-side condition rather than a route fault.

These presence-and-match checks are the same discipline as the remote I/O commissioning checklist for a modular station, applied to drive stations instead of I/O islands.

Commit the split: neighbors connecting means the fault is inside that one station; nothing connecting means the fault is the route through the CPU, and no amount of drive-side switching will fix it.

How do I keep the new motor parameters after a power loss? #

On a MICROMASTER 440 the save step is P0971 = 1: setting that parameter copies the drive's active RAM parameter set into EEPROM, and without it a freshly entered motor data set survives only until the next power removal.

Live parameters sit in RAM; EEPROM is where they survive. Enter the motor nameplate data, then run the save and let it finish before touching anything else. Other drive families label the same operation copy RAM to ROM or save to non-volatile memory — use the fitted drive's documented command rather than assuming the MICROMASTER 440's parameter carries across models.

Prove the save worked: remove power cleanly, restore it, and read the motor data back from the drive before anyone presses start. A read-back after a real power cycle is the only receipt that matters.

When is the drive ready to run again? #

The drive is ready when the station shows present and matched in CPU diagnostics, STARTER holds its online connection through the routed path, the new motor data reads back after a full power cycle, and a reduced-speed test run gives the expected rotation and current.

Decisions for each case on this machine:

  • Gear motor replaced, drive retained: enter the new motor's nameplate data, save to non-volatile memory, power-cycle, read back, then run the reduced-speed test and compare rotation direction and current against the motor's rated current. All four checks good — return the machine to service.
  • Parameter writes still rejected after the operating-state checks: stop fighting the route and use the drive's documented service connection; the parameters matter more than the elegance of the path.
  • Station never appears in CPU diagnostics after an address and termination review: the fault is physical — power, connector, or cable — and the machine stays down until that station is present.

Questions asked

Can I change the motor data from the drive keypad instead of the laptop?

Only if the drive's access level allows it. Keypad editing depends on the level currently set in the drive, and machine builders often lock that level deliberately so production cannot alter motor or control data. The documented unlock is the drive's own access-level parameter or the authorized level entry in the engineering tool — no other route is legitimate.

What station addresses can a drive's PROFIBUS board take?

Typical drive PROFIBUS option boards take station addresses 1 to 125, set in binary on switch banks: seven switches give 2^7 - 1 = 127 usable combinations, which covers that span. Whatever the board's range, the only correct value is the one HW Config shows for that station, and it must be unique on the segment.

Can I reach the drive directly if the routed path stays dead?

Many G-series drives carry a service USB port on the front, and a direct laptop connection reaches the parameters without the PROFIBUS route at all. Check the drive manual for the supported cable and driver, treat it as the recovery path, and go back to the routed connection as the normal route once the bus is healthy.

How do I make a motor data change reversible?

Before editing anything, upload the drive's complete current parameter set into STARTER and store it as a file. If the new motor data misbehaves, downloading that stored set back to the drive — and saving it again to non-volatile memory — returns the machine to its pre-fault behavior in minutes instead of re-deriving every value under production pressure.

Keep reading

  • Troubleshooting

    Why a Kinetix 5500 needs a motion-capable Logix controller

    A Kinetix 5500 servo drive used as a Logix integrated motion axis requires a motion-capable CompactLogix controller such as the 5069-L306ERM. A non-motion 5069-L306ER cannot add the drive to the module tree and is reported to read only some drive parameters over explicit messaging. Confirm the controller catalog number and the required axis count before troubleshooting anything else.

    Drives and motion

  • Explainer

    What STEP 7 is in a PLC project, and which one you need

    STEP 7 is the engineering software you use to program, configure, diagnose and download to SIMATIC PLCs — a workstation tool, not a part of the PLC itself. SIMATIC Manager, also called STEP 7 Classic, configures S7-300 and S7-400 CPUs; STEP 7 inside TIA Portal configures S7-1200 and S7-1500. Read the CPU family from the module label or the existing project, open the matching environment, and confirm the project's hardware configuration matches the installed CPU before you edit or download.

    PLC programming

  • Troubleshooting

    Why Modbus RTU drive polling on one serial port is slow

    Modbus RTU carries one request-response transaction at a time, and at 19.2 kbit/s each drive transaction costs 40-60 ms, so 18 drives polled with a read and a write each need about 1.5-2.5 s per cycle no matter how the messages are chained. Cut the transaction count, schedule command writes ahead of status reads, set each drive's communication-loss timeout above the finished cycle, and change networks when the arithmetic cannot meet the update rate.

    Industrial networks