Replacing SIMOTION E510 with S7-300 I/O on S7-319 Profibus

System Overview: SIMOTION E510 on S7-319 with PROFIBUS DP

The SIMOTION E510 periphery module is a Siemens compact, motion-oriented distributed I/O station designed for SIMATIC S7-300/400 CPUs and SIMOTION controllers. On a typical blow-molding machine, an S7-319 PN/DP CPU (a SIMATIC S7-300 high-end CPU) acts as DP master and exchanges cyclic I/O with the E510 over PROFIBUS DP. From the S7 program point of view the E510 looks like a standard DP slave: the channels are mapped into the S7 process image, accessed as bytes/bits (digital) or words (analog), and the standard SIMATIC analog scaling blocks FC105 (SCALE) and FC106 (UNSCALE) operate on the raw I/O words exactly as they would for an ET 200 station.

The E510 was engineered specifically for the high I/O density typical of plastics machinery: hydraulic clamp position, parison wall thickness, mold temperature zones, ejector position, carriage position, and dozens of digital interlocks and valve outputs. The E510 Interface Module (IM) carries the PROFIBUS interface and the internal backplane for the integrated channels. It exposes four operator-relevant indicators: SF (red, system fault within the slave), BF (red, bus fault on PROFIBUS DP), ON (green, power OK) and DC 5V (green, internal 5 V supply OK). When both SF and BF are lit, two fault classes compete: a slave-internal fault (configuration mismatch or degraded IM electronics) and a physical-layer fault (cable, termination, baud rate, or slave address conflict). In production cells with thermal cycling, vibration, and contamination, the root cause is frequently the IM electronics itself, with the BF LED reflecting the slave's withdrawal from the token ring after watchdog timeout.

Document Reference and Affected Hardware

Before any replacement work, retrieve the E510 manual from Siemens Industry Online Support (SIOS): SIMOTION E510 Periphery Module - SIOS entry 20146178. The manual documents the original wiring diagram, the channel-to-address mapping, the supported PROFIBUS baud rates (9.6 kbps to 12 Mbps), and the diagnostic buffer layout. Print the manual for the panel; it is the only authoritative reference for the legacy part and should be archived with the machine documentation.

If the machine is also controlled by a SIMOTION controller (separate from the S7-319) and the E510 was visible in the SIMOTION project as an I/O device, the SIMOTION side must be updated as well. In most plastic-machinery rebuilds the E510 is owned by the S7-319 only; the SIMOTION controller talks to its own drives and encoders, not the E510. Verify this in the project before scoping the migration. The relevant SIMOTION SCOUT reference is the V4.2 axis / cam / path technology manual: SIMOTION SCOUT V4.2 - Axis / Cam / Path Technology Functions (PDF).

Reference Part Numbers

Choose module density to match the original E510 channel count per type (DI, DO, AI, AO). The exact channel count must be taken from the customer's I/O list (the "cabinet drawing" or the bill of materials in the original STEP 7 project), not assumed. If the E510 was, for example, 24 DI / 16 DO / 8 AI / 4 AO, the closest S7-300 split is one SM 321 DI 32 + one SM 322 DO 16 + one SM 331 AI 8 + one SM 332 AO 4, occupying slots 4-7 in the ET 200M.

SF and BF LED Diagnostics on the E510 IM

Both LEDs being red on a Siemens DP slave is the most common failure presentation. Distinguishing the layer of the fault is the first step before any hardware swap.

LED Behavior and What It Means

Reading the DP Slave Diagnostic Buffer

From STEP 7, open the S7-300 station, right-click the E510 in the PROFIBUS DP master system, and select "DP Slave Diagnostics". The diagnostic buffer contains the standardized DP-V0 diagnostic frame:

• Byte 0: station_status_1 - common codes 0x00 (OK), 0x3C (slave not in ring or no parameterization), 0x44 (configuration mismatch)
• Byte 1: station_status_2 - bit 3 set = "no parameterization"
• Byte 2-3: DP master PROFIBUS address
• Byte 4-5: vendor ID (Siemens = 0x002A)
• Byte 6: header byte - bit 0 = parameter fault, bit 1 = configuration fault, bit 2 = watchdog
• Byte 7+: device-specific diagnostic (E510 channel and module status)

A persistent watchdog flag (bit 2 of byte 6) means the master is no longer talking to the slave, which on a still-terminated, still-powered bus points to a slave hardware failure rather than a cable issue. This is the cleanest evidence to justify a migration rather than continued troubleshooting of the E510.

Replacement Architecture: ET 200M vs Central Rack

Two replacement topologies are supported. Pick based on cabinet layout, free slots in the central rack, and cable re-routing cost.

Option A: ET 200M as Drop-In Slave

Replace the E510 in place on the PROFIBUS segment with an ET 200M station. The IM 153-1 is the new DP slave head; S7-300 SM modules (SM 321/322/331/332) are inserted into slots 4-11.

Pros:

• PROFIBUS topology, baud rate, and slave PROFIBUS address preserved
• No rack-space impact on the CPU
• Hot-swap friendly (with active backplane)
• Channel-by-channel mapping; no field rewiring beyond the connector swap

Cons:

• PROFIBUS DP cycle time still applies (typically 5-10 ms at 1.5 Mbps)
• One extra component (IM 153-1) to maintain

Option B: Central Rack SM Modules

Move the channels into the S7-319's central rack using standard SM modules, possibly with an IM 360/IM 361 expansion if the central rack is full.

Pros:

• No DP cycle time; faster channel access
• Fewer components; the PROFIBUS segment can be simplified or removed

Cons:

• Requires free slots in the central rack or a new expansion rack
• Field wiring at the E510's old location must be re-pulled to the CPU cabinet - significant rework
• The existing PROFIBUS segment still needs termination even if the E510 is gone (replace with a passive terminator plug)

Recommendation: For a service call where the customer wants minimum downtime, Option A (ET 200M drop-in) is almost always the right choice. The field wiring stays at the E510's old location; the SM modules are mounted on a DIN rail next to it or in a sub-cabinet. Option B is a redesign, not a repair.

Address Mapping from E510 to S7-300 SM Modules

This is the most error-prone step. The E510 occupies a contiguous I/O address range in the S7 process image; the replacement ET 200M can be configured to occupy a different range. Every PLC access to the old addresses must be rewritten.

Step 1: Extract the E510 Address Map

1. Open the STEP 7 project (or TIA Portal project) containing the original S7-319 station.
2. Open HW Config (or Device view in TIA).
3. Right-click the E510 DP slave, select "Object Properties" and open the "Addresses" tab. Note the input and output start addresses and the slot-by-slot allocation.
4. Cross-reference these addresses in the S7 program: use "Cross-References" (STEP 7) or "Go to > Usage" (TIA) to find every FC, FB, OB, and DB that reads or writes an I/Q/P bit/byte/word/double-word in that range.
5. Print the cross-reference list. This is your migration map.

Step 2: Build the New Address Map

For the ET 200M with the channel split above, STEP 7 will suggest default addresses in the next free area. You can accept those, or you can force them to a clean block. The pattern below assumes the E510 was at input bytes 256-287 and output bytes 256-295 (placeholder - verify in your project):

Exact addresses depend on how STEP 7 lays out the new station. Use this table as a template, not as a verbatim map for every project. The crucial rule: every channel must land at the same physical terminal after migration, but the byte address in the S7 program is allowed to change.

Step 3: Rewrite the S7 Program

1. In SIMATIC Manager, use "Edit > Find and Replace" or "Options > Cross-References" to do a controlled find/replace on the old address operands (e.g., IB 256 to IB 0, IW 256 to IW 0, Q 256.0 to Q 0.0, IW 272 to IW 4). Replace only the I/Q/P operands in the old range; be careful not to touch DB addresses, timers, counters, or markers that happen to share the same byte number.
2. For analog inputs, find every FC105 (SCALE) call and update the IN parameter to the new IW. For analog outputs, update the OUT parameter on every FC106 (UNSCALE) call to the new QW.
3. Compile all blocks; resolve any compiler warnings about overlapping or invalid addresses.
4. Download blocks to the CPU.

Hardware Configuration in STEP 7 V5.5 and TIA Portal

STEP 7 V5.5 (S7-300 Classic)

1. Open SIMATIC Manager, then the S7-300 station, then HW Config.
2. In the catalog, navigate to PROFIBUS DP > ET 200M > IM 153-1.
3. Drag the IM 153-1 onto the PROFIBUS master system at the same PROFIBUS address the E510 used.
4. In the ET 200M rack view (slot 3 = power supply, slots 4-11 = I/O), drag the appropriate SM modules into slots 4 onward. The slot number, not the catalog order, determines the address range; STEP 7 increments the input/output addresses automatically based on slot.
5. Right-click each SM, select Object Properties, open the Addresses tab, and override the auto-assigned start address only if you have a documented reason (otherwise leave STEP 7 to assign).
6. Save and compile. If the GSD for the IM 153-1 is not already installed, install it under Options > Install GSD before adding the IM 153-1 to the catalog.
7. Download HW Config to the CPU. The CPU will perform a restart; OB 100 / OB 101 / OB 102 will run if present.

TIA Portal (V16 or later)

1. Open the TIA Portal project, then Devices & Networks.
2. In the network view, locate the S7-319 device and its PROFIBUS subnet.
3. Delete the E510 node.
4. From the catalog, expand "Distributed I/O > ET 200M > Interface modules > IM 153-1" and drag it onto the subnet.
5. Open the ET 200M device view; insert SM modules in the rack view.
6. In the Properties > Addresses tab of each SM, set the I/O start address. TIA Portal will also auto-assign; override only for clean migration.
7. Compile (rebuild all) and download to the device.

SIMOTION SCOUT Cross-Reference for Axis Bindings

If the machine is also controlled by a SIMOTION controller (separate from the S7-319) and the E510 was visible in the SIMOTION project, the migration must include the SIMOTION side. Two cases apply.

1. Case 1: SIMOTION controller only references drives and encoders (not the E510). No action needed on the SIMOTION side. The S7-319 owns the E510 I/O and exchanges data with SIMOTION via a different mechanism (e.g., DP/DP coupler, PROFINET, or shared I/O via a PN/PN coupler). Verify by opening SIMOTION SCOUT and checking the I/O symbols of the SIMOTION project: the E510 address range should be empty.
2. Case 2: SIMOTION controller references the E510 I/O directly (e.g., cam tracks, axis position feedback on a SIMOTION I/O device, hydraulic axis setpoints). The symbol bindings must be re-mapped to the new SM module addresses. The process is documented in the SIMOTION SCOUT V4.2 axis technology manual: SIMOTION SCOUT V4.2 - Axis / Cam / Path Technology Functions (PDF). The relevant chapter is "Configuring I/O for axes and external encoders"; the binding is done in the SIMOTION SCOUT symbol browser or in the axis configuration dialog under "Encoder / Actuator interface".

Field Wiring, Shielding, and Bus Termination

Even on a drop-in replacement, the field wiring and bus termination are the most common reasons for a post-migration BF LED on the new IM 153-1.

PROFIBUS Segment Termination

• Insert a 6ES7 972-0BA12-0XA0 (or equivalent) PROFIBUS connector at the IM 153-1.
• Set the terminating resistor switch ON at the first and last station on the segment; OFF on every station in between.
• Verify the bus is terminated at exactly two points. An over-terminated or under-terminated segment will cause intermittent BF faults that are very hard to chase.

Shielding and Grounding

• The PROFIBUS cable shield must be bonded to ground at one end only - typically at the cabinet entry, via the PROFIBUS connector's shield clamp.
• Do not bond both ends; this creates a ground loop that injects noise into the bus and can corrupt DP telegrams.
• The shield continuity must run continuously from the IM 153-1 to the master. Splicing shields with pigtails degrades high-frequency performance.

Analog Wiring Practices

• Use shielded, twisted-pair cable for all analog channels (SM 331 AI and SM 332 AO). Ground the shield at the cabinet end only.
• For 4-wire sensors, wire the sensor supply in the same cable as the signal pair to avoid ground loops through the sensor body.
• For 0-10 V outputs, use a 100 ohm series resistor at the SM 332 output if the receiving device has a low-impedance input - this prevents capacitive loading from distorting the signal.

Commissioning and Channel Verification

After HW Config download, the IM 153-1 should report: SF off, BF off, ON green, DC 5V green. If so, proceed with the channel-level verification.

1. Digital inputs: From STEP 7, open the S7 program in Monitor mode. Force each input sensor (or use a screwdriver to bridge a 24 V signal) and verify the bit toggles in the process image at the new address.
2. Digital outputs: From STEP 7 Monitor/Modify, force each output bit to 1. Verify with a multimeter at the field terminal that the contact goes to 24 V. Force to 0 and verify the voltage drops. Return all outputs to 0 before leaving the cell.
3. Analog inputs: Apply a known reference signal (e.g., a calibrator or a precision decade box) to each AI channel. Verify the raw word in the process image and the scaled engineering value after FC 105 matches the applied input within tolerance.
4. Analog outputs: From STEP 7, write a known engineering value via FC 106 to each AO channel. Measure the voltage (or current, depending on the configured range) at the field terminal. Verify linearity at 0%, 25%, 50%, 75%, and 100% of range.
5. Diagnostic buffer: Open the S7-300 > Diagnostic Buffer. There should be no DP diagnostic entries for the new IM 153-1.
6. Cycle time: Open HW Config > DP Master System > Bus Parameters. Verify the DP cycle time is within the expected range (typically 5-10 ms for 1.5 Mbps with a handful of slaves).

Verification Checklist

Troubleshooting Matrix for Post-Migration Faults

Performance and Cycle Time Considerations

The E510 was a single-slave PROFIBUS device, so its DP cycle time cost was essentially the slave's per-cycle acknowledge time. An ET 200M station with N SM modules has a per-cycle cost proportional to the total I/O word count. For a typical 1.5 Mbps PROFIBUS segment and 64 bytes of I/O, the per-cycle cost is in the 1-2 ms range - usually negligible compared to the 5-10 ms DP master cycle.

If the application is a fast blow-molding cycle (e.g., 200 ms parison profile, 50 Hz wall-thickness update), check whether the original E510 was on a separate PROFIBUS sub-master with a faster cycle. The S7-319 supports multiple DP master systems; in that case, mirror the architecture with a second IM 153-1 on the same sub-master, rather than putting everything on the standard DP master system.

For the S7-319 PN/DP specifically, the PROFINET side is independent of the PROFIBUS side. If the machine is being modernized, the long-term recommendation is to migrate the entire I/O layer to PROFINET with IM 153-4 PN or ET 200SP, removing PROFIBUS entirely. This is out of scope for the immediate E510 replacement but worth raising with the customer as a follow-up project.

FAQ