Configuring Parker AC30 Profibus on S7-300 CPU314C-2DP

1. Migration Overview: ABB Drive to Parker AC30 on S7-300 Profibus

Field retrofits that swap an ABB ACS/ACQ-class Profibus drive for a Parker AC30 variable speed drive on an existing Siemens SIMATIC S7-300 CPU314C-2DP are not a drop-in replacement. The Parker AC30 family (0.75 kW to 450 kW) is a modular platform with a different Profibus DP slave implementation than ABB drives. Two technical consequences follow directly:

1. The Parker AC30 does not natively emulate the ABB PPO type (e.g., PPO2 with 4 PKW + 6 PZD) when using its own GSD file. The Parker Profibus option module builds its process data from a configurable pool of parameter words.
2. The S7-300 hardware configuration in TIA Portal V13 (or the legacy STEP 7 HW Config) must be re-built around the new Parker's GSD file. Simply re-mapping the old I/O addresses to the new drive will not work because the cyclic data layout is different.

This reference covers the end-to-end migration path: GSD installation, hardware configuration, parameter mapping (especially Parker's 0044 Comms Required), logic-block porting, configuration-state exit, and field verification.

2. Prerequisites

3. Why the ABB GSD Cannot Be Reused

ABB drives commonly used in S7-300 applications (ACS550, ACS800, ACS350 with Profibus adapter RPBA-01) implement the Profidrive profile and present a fixed PPO type to the master. The PPO type is a packaging of parameter channel (PKW) and process data (PZD) words that is selectable in HW Config:

The Parker AC30 with the 7003-PB-00 Profibus option module does not natively use PPO1–PPO5 telegrams. It builds its cyclic data exchange from a free-form selection of parameter words that the user maps inside the drive's configuration tree. This is documented in the Parker AC30 Profibus product manual (HA501837U001) and is the most common point of confusion when porting an existing S7-300 program.

4. Installing the Parker GSD File

1. Download the current Parker AC30 Profibus GSD file from the Parker EMEA literature portal. The bundle typically includes:
   • PARKER*.GSD – device description
   • PARKER*.BMP / *.DIB – device bitmap for HW Config
   • Type 2 GSD extension file (*.GSE) if DP-V1 diagnostics are required
2. Close TIA Portal V13 / STEP 7 before installation to avoid a file-lock on the GSD directory.
3. Extract the files into the Siemens GSD root: C:\Program Files\Siemens\Automation\Portal V13\Data\Hmi\Transfer\14.0\GSD (TIA Portal) or ...\Siemens\Automation\SIMATIC Manager\S7DATA\GSD (STEP 7 V5.x).
4. Restart the engineering tool and choose Options → Manage General Station Description Files (GSD). The Parker AC30 device should appear under PROFIBUS DP → Drives → Parker Hannifin → AC30.

5. Rebuilding the Hardware Configuration

5.1 Remove the ABB slave

In the device view of the CPU314C-2DP, right-click the old ABB Profibus slave and select Delete. Do not delete the DP master (the CPU's integrated Profibus interface X2). Removing the slave clears the PPO slot reservation from the S7-300 I/O address map.

5.2 Insert the Parker AC30 slave

1. From the hardware catalog, drag Parker Hannifin → AC30 onto the Profibus DP subnet.
2. Assign a unique Profibus node address. If the ABB drives used addresses 3 and 4, the Parker drives can reuse the same physical addresses — but the GSD slot configuration will be new, so verify the addressing does not collide with any other DP slaves on the segment.
3. Open the device's Properties → Slot Configuration. Unlike a PPO type, the Parker AC30 presents one or more parameter-word modules (each module = N input words / N output words, with N typically 1, 2, or 4). Build the cyclic frame by inserting the modules that map to the drive parameters the S7-300 program actually needs.

5.3 Suggested cyclic mapping for a 1:1 ABB PPO2 replacement

If the existing ABB logic was using PPO2 (4 PKW + 6 PZD), the equivalent cyclic data for the Parker AC30 is typically mapped as follows (consult the Parker AC30 Profibus manual HA501837U001 Section 4 for the master configuration tables):

Note: Parker's word orientation is big-endian, while Siemens S7-300 byte ordering is little-endian within a word. The S7-300 will swap the high/low bytes inside the input/output words automatically because the Profibus chip handles byte ordering, but if you are using the SFC14 / SFC15 consistency blocks, ensure the byte order in the destination DB matches the parameter scaling documented in the Parker manual.

6. AC30 Parameter Configuration (Drive Keypad / Parker DSEL)

After the Profibus option is physically installed in the AC30 control module, the drive must be told that fieldbus is the active control source. The following parameters are mandatory:

7. Porting the S7-300 Logic

The S7-300 program is usually divided into two parts: the cyclic I/O driver (SFC14 / SFC15 or direct I/O access) and the application logic (DBs, FBs, FCs).

7.1 Cyclic I/O driver

For PPO2 with ABB, the S7 program typically read/wrote a contiguous block of 10 words per drive starting at the I/O address shown in HW Config. With the Parker AC30, the I/O footprint is shorter (1–4 words in, 1–4 words out by default) and the assignment is per-slot. The driver must be re-built to:

• Read the new input words (status, speed feedback, motor current) into the same DBs the application logic uses, OR re-map the application to the new DB offsets.
• Write the new control word, speed reference, and any user-defined output words using SFC15 (DPWR_DAT) for consistency, or direct PQW writes for non-consistent access.

7.2 Handling manufacturer-protected blocks

If the original S7 program contains know-how-protected FBs (e.g., ABB drive-specific function blocks) the contents are not editable. Two options exist:

1. Replace with Parker-provided FBs: Parker ships sample S7 blocks (FB200-series in some HA501837U001 manual revisions) that decode/encode the Parker control and status words. Substitute the ABB FB call with the Parker FB and re-wire the DB interfaces.
2. Bypass the protected FB: Cut the I/O driver upstream of the protected FB and re-implement the ABB-specific control-word bit mapping as a pure STL/SCL function. This is preferred when the protected FB implemented motor control state-machine logic that the new drive handles differently.

7.3 Control-word mapping (ABB → Parker AC30)

8. TIA Portal V13 Specific Notes

TIA Portal V13 ships with a limited Profibus device library. The Parker GSD may not appear in the device catalog until it is manually imported. If the project was originally created in STEP 7 V5.x and migrated to TIA Portal V13:

• Use Project → Migrate Project to bring the S7-300 station across.
• TIA Portal V13 with HSP (Hardware Support Package) supports the CPU314C-2DP family; confirm the HSP for the specific CPU order number is installed before re-compiling.
• If protected blocks were carried across the migration, you may need to re-import the original ABB FB sources. If unavailable, treat them as black boxes and replace per Section 7.2.

9. Commissioning Procedure

1. Power up the S7-300 with the Parker drives offline (no main contactor).
2. Confirm in TIA Portal online view that both Parker AC30 slaves report Station OK and the diagnostic buffer is clean.
3. Open the AC30 keypad and navigate to Menu 9 (Communications) → Profibus Status. The drive should report the Profibus state machine is Data Exchange.
4. Send a single control word from the S7-300 forcing table: W#16#047E (Parker's standard CW for "ready, no run command"). Verify the drive status word echoes back the expected bits.
5. Send W#16#047F to command Run. Verify the drive's Drive Healthy relay closes and the motor is enabled (no rotation yet).
6. Apply a small positive speed reference (e.g., 5 % of max) and confirm the motor ramps correctly.
7. Send W#16#047E again to stop, then W#16#04FF to clear faults. Verify the cycle is repeatable.

10. Verification Checklist

11. Troubleshooting Matrix

12. Field-Proven Caveats

• The Parker AC30 Profibus option module is a field-replaceable sub-board. If the drive is ordered as a complete unit with Profibus, the GSD version in the documentation bundle may be older than what is on the physical device. Always cross-check the slave's Profibus firmware revision in the device's Diagnostics page.
• The Profibus cable shield must be bonded at both the cabinet entry and at every drive terminal. The 7003-PB-00 module has a dedicated SHIELD terminal; do not rely on the backplane earth.
• When both Parker drives are on the same Profibus segment as other DP slaves, verify the bus cycle time budget. Each parameter-word module adds latency; the CPU314C-2DP's DP cycle should be re-computed in HW Config → Profibus Properties → Network Settings.
• Save a copy of the original ABB project before any porting work. If a customer ever re-commissions a spare ABB drive, the original PPO2 configuration must be reproducible.

13. Standards and References

Verify the following standards against your local revision; they are not a guarantee of compliance for any specific installation:

• IEC 61158 / IEC 61784 – Profibus DP profile
• PROFIdrive Profile (PNO order No. 3.072) – for the ABB PPO type definitions that the Parker drive replaces
• Parker AC30 Profibus product manual HA501837U001 (parameter mapping, control-word definitions, configuration-state exit procedure)
• Parker AC30 product listing on the PROFIBUS & PROFINET International product finder (certified Profibus device identifier)
• Siemens S7-300 CPU314C-2DP manual – integrated Profibus DP master interface specifications

FAQ