Connecting Siemens S5-95U Profibus Devices to GE Fanuc 90-30

David Krause16 min read
ProfibusSiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

Replacing a legacy Siemens S5-95U master with a GE Fanuc 90-30 PLC, or adding a 90-30 as a secondary master on an existing PROFIBUS segment, requires careful hardware identification. The S5-95U family is not a single product; it shipped with three electrically and logically distinct PROFIBUS interfaces that share the same DB-9 connector but are not mutually compatible on the wire. Selecting the wrong variant leads to bus errors, token-retries, and the mistaken conclusion that "PROFIBUS does not work" between the controllers.

This reference covers the three S5-95U PROFIBUS variants (MLFB suffixes 8MB0x, 8MD0x, 8ME0x), the protocol layer each implements (SINEC L2 FDL vs. PROFIBUS FDL vs. PROFIBUS DP), and the integration paths available on a GE Fanuc 90-30 rack. Field-proven wiring rules, GSD integration steps, and a DP/DP coupler workaround for SINEC L2 islands are included.

Critical: SINEC L2 is not PROFIBUS DP. A 6ES5095-8MB02 will never appear as a DP slave on a DP master, regardless of master brand. Verify the MLFB suffix on the device label before ordering any replacement hardware.

S5-95U Hardware Identification: Three Profibus Variants

The order number (MLFB) printed on the front of every S5-95U determines the protocol implemented by the on-board PROFIBUS port. The first six characters 6ES5095 identify the S5-95U compact unit; the suffix after the dash identifies the interface type.

MLFB Suffix Example Protocol Layer Role on Bus DP Compatible?
8MB0x 6ES5095-8MB02 SINEC L2 (FDL) only Active FDL station No
8MD0x 6ES5095-8MD02 PROFIBUS DP slave DP slave (passive) Yes
8ME0x 6ES5095-8ME02 PROFIBUS DP master DP class 1 master Master only

All three variants share the same 9-pin Sub-D female connector on the front panel and the same RS-485 physical layer. Differentiation must be performed by reading the order label, not by visual inspection of the connector.

Refer to the official entry for the S5-95U with PROFIBUS interface (6ES5095-8MB02) in the Siemens Product Support database for the full datasheet, manuals, and firmware history.

Variant 8MB02 - SINEC L2 FDL Station

The 6ES5095-8MB02 implements SINEC L2, which is the Siemens-internal name for FDL-based peer-to-peer communication as defined in the original PROFIBUS FDL specification (DIN 19245 Part 1, predecessor of EN 50170). It does not implement DP-V0 state machine, does not exchange GSD-derived parameterization telegrams, and cannot be addressed by a DP class 1 master. It exchanges data via SDN and SRD services only. The companion manual SINEC L2 Interface of the S5-95U Programmable Controller documents the bus parameters, station address range, and the AG-SEND / AG-RECEIVE FB-call interface inside STEP 5.

Variant 8MD02 - PROFIBUS DP Slave

The 6ES5095-8MD02 is a standard PROFIBUS DP-V0 slave. It loads a GSD file (Siemens-provided, file name format SIEM_8MD0.GSD or similar, version-keyed) into the configurator of any DP class 1 master and exposes up to 32 bytes of input and 32 bytes of output through the standard DP slot model. Any brand of DP master can poll it.

Variant 8ME02 - PROFIBUS DP Master

The 6ES5095-8ME02 is a PROFIBUS DP class 1 master. It cannot operate as a DP slave. It is used to couple downstream DP slaves (distributed I/O, drives, third-party controllers) back to the S5-95U CPU. If a third-party PLC is to read the devices on this segment, the 90-30 cannot take over as a slave to the 8ME02 without a DP/DP coupler.

SINEC L2, PROFIBUS FDL, and PROFIBUS DP: Protocol Distinctions

Confusion between these three protocol layers is the single most common cause of failed S5-95U integrations. The naming convention predates the formal PROFIBUS standard and persists in legacy STEP 5 documentation.

Layer Standard Basis Service Used Configuration Mechanism Master Required?
SINEC L2 Pre-standard (Siemens), FDL subset SDN, SRD (FDL) STEP 5 FB AG-SEND/AG-RECEIVE, COM 95U configurator None; peer-to-peer
PROFIBUS FDL EN 50170 / IEC 61158 SDN, SRD, SDA FDL connection table in master configurator Yes (active station)
PROFIBUS DP EN 50170 / IEC 61158-3 DP-V0/V1 cyclic I/O exchange GSD file, slot/index mapping Class 1 master required
Engineer note: The original "SINEC L2" label is a Siemens trademark, not a protocol. As Siemens itself notes, "SINEC L2 is not fully compatible with PROFIBUS" - it lacks the DP state machine, the watchdog, and the diagnostic channel that a DP master expects from a slave.

GE Fanuc 90-30 PROFIBUS Master Module Selection

The GE Fanuc (now Emerson Automation) Series 90-30 supports PROFIBUS DP master operation only through the IC693BEM331 Genius/PROFIBUS module (later IC693PBM200 for higher-density applications). Verify availability of these modules for new builds; production of legacy 90-30 PROFIBUS masters was discontinued by Emerson, with field replacement units sourced from aftermarket channels.

Catalog Number Function DP Version Max Slaves Notes
IC693BEM331 Genius/PROFIBUS master DP-V0 32 Slot occupies one slot in 90-30 baseplate; 12 Mbps max
IC693PBM200 PROFIBUS master module DP-V0/V1 125 Later Emerson designation; replacement for BEM331

The 90-30 PROFIBUS master accepts standard GSD files (GSD Rev. 3 or later recommended) and imports them through the PROFIBUS configurator plug-in for VersaPro or CIMPLICITY Machine Edition Logic Developer. The configurator produces an I/O map file consumed by the ladder logic, with each slave's slots mapped to discrete %I / %Q addresses and words to %AI / %AQ.

Connection Strategy Decision Matrix

Use the matrix below to choose the integration path based on the S5-95U MLFB suffix discovered in the field.

S5-95U Variant Goal Recommended Path Hardware Required
8MB0x (SINEC L2) Replace S5-95U with 90-30, keep downstream devices running Bridge via CP342-5 on S7-300 with FDL connection, OR add DP/DP coupler + 90-30 DP master reading DP side S7-300 + CP 342-5, or DP/DP coupler (Siemens 6ES7158-0AD01-0XA0)
8MD0x (DP slave) Replace S5-95U with 90-30 as new DP master Direct - load GSD into 90-30 PROFIBUS configurator IC693BEM331 or IC693PBM200
8ME0x (DP master) Replace S5-95U, take over downstream DP slaves Direct - 90-30 PROFIBUS master with GSD files of all downstream slaves IC693BEM331 + GSD for each downstream slave

Wiring and Physical Layer Requirements

All three S5-95U PROFIBUS variants and the GE Fanuc IC693BEM331 use the IEC 61158-2 physical layer on a 9-pin Sub-D connector with the standard PROFIBUS pinout (pin 3 = data B, pin 8 = data A, pin 6 = +5 V termination power, pin 5 = ground, pins 1, 2, 4, 7, 9 reserved/unused). Cable is two-wire shielded twisted pair with characteristic impedance 150 ohms (PROFIBUS cable type A, e.g., Siemens 6XV1830-0EH10).

Parameter Spec Notes
Cable type PROFIBUS type A, 150 ohm Do not substitute RS-485 generic cable
Max segment length @ 1.5 Mbps 200 m Drop cables limited to 0.3 m at 12 Mbps
Max segment length @ 12 Mbps 100 m 9.6 kbps allows 1200 m
Termination 220 ohm / 390 ohm divider, +5 V Active at both ends only; never in middle
Shield Bonded at both ends, low-impedance Use PROFIBUS connector with switchable termination (6ES7972-0BA12)

When mixing the S5-95U with a 90-30 in the same segment, verify that no two stations share the same PROFIBUS address. The S5-95U uses COM 95U or the DIP switches on the front panel to set the address; the 90-30 sets its master address in the PROFIBUS configurator (default 1, change to avoid conflict if the S5-95U is still present).

Configuring S7-300 with CP 342-5 Communications Processor

If a third-party PLC must integrate with an S5-95U 8MB0x over FDL, the field-proven approach is to insert a Siemens S7-300 station with a CP 342-5 communications processor as an FDL gateway. This is the configuration that the original Siemens "experts" referenced in the field discussion arrived at after the on-board S7-300 DP port proved insufficient.

  1. Insert the CP 342-5 (6GK7342-5DA02-0XE0 or later -0XE3 for FW V5.x with DP-V1) into the S7-300 rack. Use STEP 7 V5.5 (or TIA Portal V13+ with GSD import for CP 342-5) to configure.
  2. In HW Config, set the CP operating mode to "PROFIBUS FDL" (not DP master, not DP slave).
  3. Define an FDL connection to the S5-95U 8MB02: connection name (8 chars), local station address, remote station address (must match the S5-95U COM 95U setting), and the LSAP / service access point numbers (default 0 / 1 for one FDL partner, increment for multiple).
  4. Choose SRD service with send and receive buffer lengths. The S5-95U expects 240-byte max payload per FDL frame, configured inside the STEP 5 AG-SEND / AG-RECEIVE FB calls.
  5. Insert FC AG_SEND / FC AG_RECV into the S7-300 OB1 cycle. Parameter ID = connection ID from HW Config; LADDR = I/O start address of the CP 342-5; SEND / RECV = any DB; LEN = byte count.
  6. Compile and download the HW Config. Bring up the CP - the SF LED on the CP must extinguish within ~5 s of bus activity from the S5-95U.

Refer to the Siemens Industry Online Support FAQ for CP 342-5 FDL configuration, including example STEP 7 projects and the OPC server bridge pattern documented for the 6ES5095-8MB02 integration with CP5611 / SIMATIC NET OPC server.

Configuring GE Fanuc 90-30 as PROFIBUS DP Master

  1. Verify that the target slot in the 90-30 baseplate is empty and that the rack power budget can supply the IC693BEM331 / IC693PBM200 (typical 410 mA at +5 V).
  2. Open CIMPLICITY Machine Edition Logic Developer or VersaPro. Insert the PROFIBUS master module into the configured hardware tree.
  3. Set master PROFIBUS address (1-126, default 1). Set the baud rate to Auto-Detect up to 12 Mbps (or hard-code if a non-compliant slave is present).
  4. Right-click the master node and select "Add Slave". Browse to the GSD file of the target device. For an S5-95U 8MD02 slave, the GSD identifies the device as SIEMENS S5-95U/DPSlave with module definitions matching its I/O slot map.
  5. Configure each slot to the correct I/O length (typically 4-byte or 8-byte boundaries). Map the inputs to %I and %AI, outputs to %Q and %AQ in the slot-to-address table.
  6. Save the configuration to the 90-30 CPU. The master will cycle the bus at the configured watchdog time (default 10 s). If the slave fails to enter Data_Exchange within watchdog, the master flags the slave with a diagnostic entry.

GSD File Integration and I/O Mapping

The GSD file (General Station Description) is the standardized text file in which a PROFIBUS slave vendor declares its identity, supported baud rates, slot count, I/O lengths, and diagnostic structure. The 90-30 PROFIBUS configurator parses the GSD during slave import. Common pitfalls encountered when importing older Siemens GSDs (e.g., the S5-95U 8MD02 GSD dated circa 1996):

  • GSD revision mismatch: GSD Rev. 1 files predate several keywords and may import as generic "unknown device" in modern configurators. Manually patch the GSD_Revision field to 2 or higher; verify no DP-V1-only keywords are used.
  • Slot length zero: Some legacy GSDs declare empty slots. The 90-30 configurator may refuse them. Add a 1-byte "diagnostic" slot to satisfy the slot-count validation.
  • MaxTsdr value: If a slave declares a maximum Min_Slave_Intermessage_Gap larger than the master's allowed value, the configurator silently downscopes baud rate. Confirm the calculated Tsd at 12 Mbps is <= 100 bit-times for all slaves in the segment.
Slave Sample GSD Line Effect on Configurator
S5-95U 8MD02 Module = "8 Bytes In/Out" 0x10,0x11 Maps to %I and %Q 8-byte block
Generic 16DI/16DO slave Module = "16 DI" 0x00 Maps to %I 16-bit
Third-party controller Fail_Safe = 0 Standard DP-V0 only; no DP-V1 / F-Slave negotiation

Bridging SINEC L2 FDL via OPC Server (CP5611)

When the only path into the S5-95U 8MB02 is its SINEC L2 FDL interface, and the replacement controller is a non-Siemens master without native FDL support (GE Fanuc 90-30 has no FDL stack), an OPC server running on a PC with a CP5611 (or CP5612 / CP5613 / CP5621 PCI Express) can act as a transparent data bridge.

  1. Install SIMATIC NET PC software on the gateway PC (version matched to the CP5611 driver set; current version SIMATIC NET V16 supports CP5611 on Windows 10 LTSC).
  2. Configure the CP5611 as a PROFIBUS station in the SIMATIC NET Configuration Console. Set its station address to one not used by the S5-95U 8MB02.
  3. Define an FDL connection to the S5-95U 8MB02 station with the SIMATIC NET OPC Server configured to expose the FDL connection tags.
  4. The 90-30 exchanges data with the gateway PC via Ethernet (Modbus TCP from an OPC-DA-to-Modbus bridge, or OPC-UA in newer Emerson configurations). The PC thus appears to the 90-30 as a TCP/RTU gateway rather than a PROFIBUS peer.
  5. This pattern is explicitly documented by Siemens for the 6ES5095-8MB02: "a CP5611 is used to establish the FDL connection with a SIMATIC S5 95-U on the PROFIBUS via the OPC server".
Latency consideration: An OPC-DA round trip plus Ethernet between the 90-30 and the gateway PC adds 20-100 ms to the FDL transaction cycle. Acceptable for monitoring and slow control (e.g., 100 ms closed-loop); unsuitable for high-speed motion.

DP/DP Coupler Alternative

Siemens DP/DP coupler (6GK1571-0BA00-0AA00 or successor 6ES7158-0AD01-0XA0) bridges two physically independent PROFIBUS DP segments, copying the input image of one segment to the output image of the other and vice versa. It is the field-preferred workaround when the S5-95U 8MB02 cannot be reconfigured for DP but the downstream devices on its bus are DP slaves rather than pure SINEC L2 peers.

  1. Segment A: legacy S5-95U 8MB02 with its SINEC L2 FDL peer devices.
  2. Segment B: GE Fanuc 90-30 (IC693BEM331) as DP master of a new DP segment.
  3. Insert the DP/DP coupler as a slave on Segment B. The 90-30 PROFIBUS configurator imports the coupler's GSD (SIEM8040.GSD for the 6ES7158 variant) and allocates up to 244 bytes input + 244 bytes output to the coupler slot.
  4. On Segment A, the coupler appears as a DP slave to the S5-95U 8MB02 only if the 8MB02 firmware supports DP slave mode - which it does not. Therefore Segment A must remain an FDL peer-to-peer network; the DP/DP coupler is useful only when the S5-95U is itself a DP master (8ME0x) and a parallel DP master (90-30) must co-exist on a parallel segment.

For the 8MB02 case, the coupler adds little value over the OPC server bridge. Reserve it for the 8ME02-to-90-30 master handover scenario, where the new 90-30 master and the legacy 8ME02 must temporarily share slaves during cutover.

Troubleshooting Matrix

Symptom Likely Cause Diagnostic Remediation
90-30 PROFIBUS master reports "Slave not found" for S5-95U S5-95U is 8MB0x (SINEC L2, not DP) Read MLFB label; check for FDL-only AG-SEND FB in S5-95U program Use OPC bridge or replace S5-95U with 8MD0x variant if firmware allows
Bus LED flickers, no slave enters Data_Exchange Duplicate PROFIBUS address Use PROFIBUS tester (e.g., Softing PROFIbus Tester 5) to enumerate stations Re-address conflicting station
Intermittent slave dropouts under vibration Missing or incorrect termination Measure 220/390 divider resistance at bus ends with power off Enable termination only at physical ends
Master cycles but slave reports diagnostic "PRM-ERROR" GSD parameter mismatch (slot length, consistency) Read slave diagnostic buffer via PROFIBUS live-list Re-import GSD, verify slot lengths match firmware
CP 342-5 SF LED stays lit after bus attach FDL connection table mismatch (LSAP / address) STEP 7 "Go Online" -> CP diagnostics Verify LSAP numbers; ensure S5-95U COM 95U DB matches
OPC server cannot browse FDL tags CP5611 driver mismatch or station address collision SIMATIC NET Configuration Console -> Station state Re-install matching SIMATIC NET version; reassign station address
Baud rate auto-detect fails to reach 1.5 Mbps One slave declares MaxTsdr greater than master tolerance Parse GSD; compute Tsd budget Hard-set baud rate below the limiting slave's min

Verification and Commissioning

Commissioning checklist before handover:

  1. Bus physical layer: With all stations disconnected, measure DC resistance between pins 3 and 8 at each end. Reading 110 ohms (220 || 220) confirms termination. Reading 220 ohms indicates only one end is terminated.
  2. Station enumeration: Run a PROFIBUS live-list (Siemens "Set PG/PC Interface" diagnostic, or Emerson PROFIBus Diagnostics tool) and verify every expected station appears exactly once with the correct address.
  3. Cyclic I/O test: Force a known pattern from the 90-30 master and verify the slave's mapped %I / %AI values match. Reverse direction for outputs.
  4. Diagnostic test: Disconnect the slave mid-run and confirm the 90-30 PROFIBUS master logs a "station failure" diagnostic within one watchdog interval (default 10 s).
  5. Bus cycle time: Use the master's bus statistics page to record the actual cycle time at full load. Confirm it is <= 80% of the application's cycle budget.
  6. FDL round-trip (if applicable): On the S7-300 + CP 342-5 path, instrument the FC AG_RECV "STATUS" output and verify the DONE bit toggles each OB1 cycle.
  7. Long-term soak: Run the bus for 24-72 hours under full I/O load. PROFIBUS DP is sensitive to connector oxidation; a single loose pin surfaces as intermittent retries.

Field-Proven Notes

  • Devices originally programmed with late-1980s SINEC L2 firmware typically have no DP fallback path. Budget for a CP 5611 + OPC gateway or a full controller replacement rather than hoping for a DP re-flash.
  • The CP 342-5 ("-0DA02-0XE0") and the CP 342-5 FO ("-5DA02-0XF0") both support FDL and DP simultaneously; selecting the wrong firmware mode in HW Config renders the FDL path silent. Re-confirm the mode after every firmware update.
  • For Emerson IC693PBM200 replacement of obsolete IC693BEM331, check that the spare module's firmware is at Rev. 2.10 or later. Earlier revisions had a known issue enumerating slaves with modular GSDs (multi-slot GSDs declared with the "Modular_Station" keyword).
  • When sourcing replacement S5-95U modules from surplus channels, verify that the COM 95U EPROM (6ES5 895-0BS11 or later) matches the CPU firmware. Mismatched COM 95U and CPU FW cause silent FDL handshake failures with no LED indication.

Can a GE Fanuc 90-30 with IC693BEM331 talk to a Siemens S5-95U 8MB02 directly?

No. The 6ES5095-8MB02 implements SINEC L2 (FDL peer-to-peer), not PROFIBUS DP. The 90-30 PROFIBUS master only speaks DP. Add a CP5611-based OPC server bridge or an S7-300 + CP 342-5 gateway that translates FDL to a protocol the 90-30 can read (Modbus TCP, Ethernet/IP, or PROFIBUS DP).

How do I identify whether an S5-95U is a SINEC L2 or a PROFIBUS DP device?

Read the MLFB on the front label. Suffix 8MB0x = SINEC L2 FDL only; 8MD0x = PROFIBUS DP slave; 8ME0x = PROFIBUS DP master. The connector and cable type are identical across all three, so visual inspection will not differentiate them.

What is the difference between PROFIBUS FDL and PROFIBUS DP?

FDL is the layer-2 data-link service used for peer-to-peer or routed transfers via SEND/RECEIVE. DP is an application-layer profile built on top of FDL that defines cyclic I/O exchange, parameterization, and diagnostics using a master-slave model with a GSD file. A DP master cannot read an FDL-only station, and an FDL peer cannot be polled as a DP slave.

Can a DP/DP coupler let my 90-30 master and an S5-95U 8ME02 share slaves?

Yes, during cutover the DP/DP coupler (e.g., 6ES7158-0AD01-0XA0) can bridge two independent DP segments so both masters see the same I/O image. This is useful when the legacy 8ME02 and the new 90-30 must run in parallel briefly. Note that this does not help with a 6ES5095-8MB02, which is FDL-only and cannot act as a DP slave.

What GSD file do I need for an S5-95U 8MD02 slave on a non-Siemens master?

Use the Siemens-provided GSD for the 8MD0x family (commonly SIEM_8MD0.GSD or the GSD keyed to the specific CPU firmware version). Import it into the 90-30 PROFIBUS configurator (CIMPLICITY Machine Edition or VersaPro), assign slot lengths, and map to %I / %Q / %AI / %AQ. If the GSD is older than Rev. 2, patch the GSD_Revision keyword before import.

Back to blog