Understanding Profibus and Its Components

Profibus (Process Field Bus) is a fieldbus standard for industrial automation that enables high-speed, deterministic communication between controllers, sensors, actuators, and other devices. It is defined by the IEC 61158 and IEC 61784 standards, with two primary variants: Profibus DP (Decentralized Peripherals) for fast factory automation and Profibus PA (Process Automation) for intrinsic safety and power over the bus. The protocol operates on a master-slave architecture, where one or more masters coordinate data exchange with multiple slaves.

Key hardware components include:

  • Profibus Master: Typically a PLC, DCS, or dedicated communication processor that initiates all data exchanges. Masters can be Class 1 (central controller) or Class 2 (engineering/configuration tool).
  • Profibus Slaves: Devices such as I/O modules, drives, valves, and transmitters that respond only to master requests.
  • Profibus Cable: A shielded twisted-pair cable with characteristic impedance of 150 Ω, commonly using 9-pin D-sub connectors or M12 connectors. Proper termination resistors (220 Ω) are required at both ends of the segment.
  • Repeaters/ Segment Couplers: Used to extend cable length, add branches, or connect DP and PA segments.

Understanding bus topology (daisy-chain, star with repeaters, or tree) and maximum segment lengths (typically 100–1200 m depending on baud rate) is critical before starting configuration.

Prerequisites for Configuration

Before launching engineering software, gather the following:

  • Engineering Software: Common options include Siemens STEP 7 (for S7‑300/400/1200/1500), Siemens PCS 7 (for process control), or vendor-specific tools like ABB Automation Builder, Rockwell Studio 5000 with ProSoft modules, or CODESYS. Ensure the software version supports Profibus DP/PA.
  • Hardware Interface: A Profibus communication processor (CP) or a USB/PCI adapter (e.g., Siemens CP 5711, Hilscher cifX, or Softing PBpro). Install the corresponding drivers and ensure the interface is recognized by Windows or the engineering environment.
  • GSD Files: Each slave device requires a General Station Description (GSD) file that defines its capabilities, parameters, and communication settings. Obtain GSD files from the device manufacturer (often in .GSD, .GSE, or .XDD format).
  • Device Documentation: Know the station address (set via DIP switches or software), baud rate compatibility, input/output data sizes, and any special parameter requirements.
  • Network Topology Map: A drawing showing all nodes, cable lengths, termination points, and repeater positions helps avoid address conflicts and signal reflection.
  • Test Equipment: A bus monitor or oscilloscope may be needed for troubleshooting physical layer issues.

Step-by-Step Configuration Process

1. Launch the Engineering Software and Set Up a Project

Open your engineering software and create a new project. Name it according to the machine or line. In Siemens STEP 7, navigate to the hardware configurator (HW Config). Ensure the software detects your Profibus interface—usually shown as a CP or built-in Profibus port. If using a USB adapter, check that the COM port assignment matches in the device manager. Configure the interface’s master parameters: select the correct Profibus profile (DP, PA, or DPV1), set the master’s station address (typically 1 for the first master), and define the bus parameters like baud rate (e.g., 1.5 Mbps or 12 Mbps) and highest station address (HSA).

2. Add a Profibus Network and Import Slave GSD Files

Insert a Profibus network into your project workspace (e.g., drag a DP master system from the hardware catalog). Add the master device (e.g., an IM 153‑2 interface module for ET 200M). Then add slave devices by browsing the hardware catalog or importing GSD files. To import a GSD file: go to Options > Install GSD File (in STEP 7) or use the appropriate tool in your software. After installation, the device appears in the catalog under “Additional Field Devices.” Drag the device onto the Profibus line. Repeat for each slave. Assign each slave a unique station address (must match the physical address set on the device). Typically addresses range from 3 to 125 (addresses 0, 1, 2 are reserved for masters or special functions).

3. Configure Device Parameters and I/O Data

Double-click each slave to open its properties. Configure parameters such as:

  • Station Address: Confirm it matches the physical setting.
  • Baud Rate: This is set on the master and must be supported by all slaves. Common rates: 93.75 kbps, 187.5 kbps, 500 kbps, 1.5 Mbps, 3 Mbps, 6 Mbps, 12 Mbps. Use the highest rate supported by all devices for best performance.
  • Input/Output Data Length: Define the number of input and output bytes. The GSD file lists possible configurations (e.g., 2 bytes analog, 4 bytes digital). Select the appropriate module configuration—some devices allow you to choose between different I/O maps.
  • Watchdog (WD): Enable a watchdog timeout so the slave goes to a safe state if communication fails. Typical timeout is 1–2 seconds.
  • Diagnostic Reporting: Enable diagnostic interrupts if the slave supports them.
  • Parameters for Specific Devices: For example, drive parameters like ramp time, or analog module measurement range. These are often written as “parameter data” during startup.

For Profibus PA devices, you must also configure the PA bus parameters (e.g., internal resistance, power supply settings) and map them through a segment coupler or link device.

4. Assign Profibus Addresses

Address assignment in software should match each device’s physical address. Most slaves have DIP switches to set the address (0‑126). For devices without switches (e.g., some PA instruments), address assignment is done via the master using a dedicated “Set slave address” command during commissioning. In the engineering tool, verify address uniqueness: no two devices on the same bus segment can share the same station number. If using repeaters, note that each segment reuses addresses; ensure the master’s HSA is higher than the highest slave address.

5. Validate the Configuration

Run the software’s consistency check or compilation. Common checks include:

  • Address Conflicts: The tool warns if two slaves share the same address.
  • Bus Parameter Calculation: Software computes timing parameters like Tslot, Tset, Tqui, and watchdog intervals based on selected baud rate and segment length. Some tools allow manual adjustment; accept calculated defaults unless you have a specific reason to override.
  • Missing GSD Files: Unknown device types will cause errors—download the correct GSD.
  • I/O Data Overlap: Check that total I/O data does not exceed the master’s capacity (e.g., maximum 244 bytes per slave in Profibus DP).

Correct any errors. If warnings about bus cycle time appear (e.g., too long for time‑critical applications), consider reducing baud rate or removing unnecessary slaves.

6. Download Configuration to Devices

Transfer the configuration to the master and slaves. In STEP 7, use “Download” from the hardware configurator. The master downloads its configuration and then begins setting parameters to each slave via the bus. Steps:

  • Ensure the master is in STOP mode (for PLCs) to avoid accidental process actions.
  • Select the correct target device (PG/PC interface).
  • Click “Download” (or “Load” in TIA Portal). The software will prompt to overwrite the existing configuration.
  • After download, the master starts the parameterization phase: it sends parameter data to each slave according to the GSD. Slaves that receive correct parameters respond with diagnostics “Parameterization done” and then wait for configuration data (I/O mapping). If a slave does not respond, check its physical connection, termination, and address.
  • For devices requiring a “Set slave address” command, some engineering tools allow this as a separate step under “Accessible devices” or “Online diagnostics.”

After all slaves are configured, the master performs a “Data_Exchange” phase. The bus becomes operational.

7. Test Network Communication

Verify correct communication using the software’s online diagnostics:

  • Bus Status: Check that the master shows “RUN” or “Data Exchange” state.
  • Slave Diagnostics: In STEP 7, go to “PLC > Monitor/Modify Variables” or use the “Diagnostics” view. Each slave should have green status (no errors). Common error LEDs on devices: Bus Fault (red) means no communication; BF (bus fault) flashing indicates wrong baud rate or address.
  • Data Exchange: Write a test value to an output and read back from an input. Use the engineering tool’s variable table or a simple ladder logic snippet.
  • Bus Monitor: Use a tool like ProfiTrace or ibaAnalyzer to capture telegram traffic. Check for retries, CRC errors, or voltage levels. Typical waveform should be a clean differential signal with ~5 V amplitude. If not, check cable termination (must have 220 Ω between A and B lines at both ends) and shield grounding (single‑point grounded at master side).

If communication fails, systematically check:

  • Physical connections: D‑sub connector pinout (Pin 3 = B line, Pin 8 = A line, Pin 5 = GND).
  • Baud rate match between master and all slaves.
  • Station addresses: no duplicates and within range.
  • Termination: both ends must have termination resistors enabled. Do not terminate a repeater port that connects to another segment without its own termination.
  • Supply voltage: some slaves require external 24 VDC; ensure power is on.

Common Pitfalls and How to Avoid Them

  • Incorrect GSD File: Always use the exact GSD file matching the device firmware version; a mismatch can cause parameterization errors.
  • Baud Rate Mismatch: Many devices default to 1.5 Mbps. If your master is set to 12 Mbps, older devices may not sync. Start at a low common rate and increase after confirming all devices support higher speeds.
  • Missing Termination: Every Profibus segment must have termination resistors at both physical ends of the cable. Incorrect termination causes reflections, data corruption, and intermittent faults.
  • Over‑complicated Topology: Keep the bus simple; avoid stubs longer than 0.3 m for high baud rates. Use repeaters for star or tree structures.
  • Forgetting to Download: Configuration changes in the engineering tool don’t take effect until downloaded. Always perform a download after any parameter change.

Conclusion

Configuring Profibus devices requires careful planning, correct hardware setup, and methodical software steps. By understanding the network components, gathering proper GSD files, and following the 7‑step process—from project creation to online testing—engineers can achieve reliable, deterministic communication. Always refer to device manuals and the Profibus & Profinet International website for updated specifications and best practices. Additional support can be found through Siemens Industry Online Support and GSD file repositories. Keep a documented record of all addresses and parameter settings to simplify future maintenance and troubleshooting.