Configuring SIMOTION D445 as a PROFIBUS DP Slave Station

A GSD file defines how a PROFIBUS DP master represents a slave in its hardware configuration. The term GSD here means General Station Description. It supplies the device identity and selectable cyclic I/O structure; it does not contain the SIMOTION application or configure the D445 itself.

Configuration boundary

The CPU319 project and the SIMOTION D445 project have separate responsibilities. STEP 7 HW Config uses the GSD to place the D445 in the CPU319 PROFIBUS DP master system and map its cyclic I/O. SIMOTION SCOUT configures and programs the D445 side.

This boundary explains why importing Si0180ab.gsd cannot replace SCOUT. A valid master configuration can define exchanged bytes, but the D445 must still be configured to operate as the intended DP slave with a matching data layout.

Check 1: Engineering-station software

Check 1: inspect the installed software. The reported engineering station contains STEP7_V54_SP3 and STEP7_HSPs_201002, but no SIMOTION SCOUT. Expect the requested SIMOTION GSD to be absent unless it was installed separately.

SIMOTION SCOUT normally installs the SIMOTION GSD files on the engineering computer. Install SCOUT when the same computer must configure or program the D445. If another authorized engineering computer already has the correct SIMOTION installation, obtain the GSD through the controlled engineering-software workflow and import it into STEP 7. Keep the file with the project records so another workstation can reproduce the hardware catalog.

A hardware support package and a GSD serve related but different catalog functions. The presence of STEP7_HSPs_201002 does not by itself demonstrate that Si0180ab.gsd is installed. Search the local Siemens engineering-software directories by the exact filename rather than assuming that a visible D445-like catalog object is the requested device description.

Check 2: GSD identity and catalog import

Check 2: locate Si0180ab.gsd and import it using the GSD installation function in STEP 7 HW Config. Expect the import to complete without a parsing or duplicate-file error and the corresponding SIMOTION slave entry to become available in the hardware catalog.

Use the exact file supplied by the SIMOTION installation. Do not rename a different GSD to match the requested filename. A filename match alone is also insufficient: after import, inspect the displayed device identity and available module structure. Those catalog properties must describe the slave configuration being engineered.

If a downloaded archive asks for a password or login, first distinguish the transfer tool from the archive. Download-manager interception can present an authentication window even when the file itself is not protected. Disable or bypass that manager and retrieve the file through the normal authorized channel. Do not treat an authentication prompt as proof that the GSD is encrypted.

If the import succeeds, proceed to Check 3. If it fails, stop and obtain a clean copy from the installed SIMOTION software or an official Siemens software channel; repeated imports of an incomplete archive will not repair the catalog.

Check 3: CPU319 master configuration

Check 3: create or open the CPU319 PROFIBUS DP master system in HW Config, then attach the imported D445 slave entry. Expect the graphical network to show the CPU319 as master and the D445 as a slave on the same DP segment.

1. Assign the D445 a PROFIBUS station address that is unique on the segment.
2. Select the cyclic input and output modules required by the application. Read their byte lengths from the imported catalog; no fixed length is implied by the filename.
3. Record the CPU319 input and output start addresses and total lengths.
4. Check the data direction from each controller's viewpoint. Data sent by the D445 becomes input data at the CPU319; data sent by the CPU319 becomes input data at the D445.
5. Compile the hardware configuration. Expect no configuration error involving the selected slave modules or address ranges.

Do not resolve an address conflict by changing only one project. The station address used by the physical D445 must equal the slave address configured under the CPU319 master. Likewise, cyclic data lengths and ordering must match on both sides.

Check 4: D445 slave configuration

Check 4: open the D445 project in SIMOTION SCOUT and configure the required PROFIBUS interface for slave operation. Expect its station address, cyclic data direction, byte lengths, and ordering to match the CPU319 hardware configuration.

The GSD cannot perform this step. It describes the slave to HW Config, while SCOUT establishes how the D445 interface and application exchange those bytes. Installing only the GSD is sufficient for building the CPU319-side representation, but it is not sufficient for programming or configuring the SIMOTION device.

Map the exchanged data into the D445 application deliberately. Confirm that every field has the same width, order, and interpretation in both controllers. A bus can enter cyclic data exchange while the application still reads incorrect values if byte order, signedness, scaling, or field boundaries differ.

Compile the SIMOTION configuration and load it through the approved commissioning connection. Then load the compiled CPU319 hardware configuration. If either controller reports a configuration mismatch, compare module selection and total byte counts before investigating application logic.

Resolving procedure

1. Install SIMOTION SCOUT on the engineering computer that will configure the D445.
2. Locate the installed Si0180ab.gsd file and import it into STEP 7 HW Config.
3. Add the D445 slave to the CPU319 PROFIBUS DP master system.
4. Assign a unique station address and select the required cyclic I/O modules.
5. Record the module order, data direction, start addresses, and byte lengths.
6. Configure the matching slave address and cyclic data layout in SIMOTION SCOUT.
7. Compile both projects and correct all configuration errors.
8. Load the D445 configuration and the CPU319 hardware configuration.
9. Place the network in operation and use online diagnostics to identify any remaining address, configuration, or physical-layer fault.

Recurring wrong practice is treating catalog visibility as proof of device readiness. Catalog visibility proves only that HW Config can interpret the GSD. It does not prove that the D445 is configured, that the physical address matches, or that cyclic data has reached the application.

Numbered verification readings

1. Check 1: inspect the STEP 7 hardware catalog. Expect the imported SIMOTION slave entry and its selectable I/O structure to be present.
2. Check 2: compile the CPU319 hardware configuration. Expect zero configuration errors for the DP master system, slave modules, and address ranges.
3. Check 3: compare the configured slave address with the address active at the D445. Expect an exact match and no duplicate address on the segment.
4. Check 4: compare cyclic module order and byte counts in HW Config and SCOUT. Expect the output length of each sender to equal the input length of its receiver.
5. Check 5: read online PROFIBUS diagnostics after both configurations are loaded. Expect the D445 to participate in cyclic data exchange without a station-not-available or configuration-mismatch indication.
6. Check 6: change a controlled test value at each sender and observe the mapped receiver value. Expect the correct value at the correct address in both directions, with the agreed data type and scaling.

FAQ