C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Configuring SINAMICS G120 Inverters in PCS 7 with APL FbDrive and MotSpdCL Blocks

Configuring SINAMICS G120 Inverters in PCS 7 with APL FbDrive and MotSpdCL Blocks

In SIMATIC PCS 7, the recommended standard approach for integrating SINAMICS G120 variable frequency drives without proprietary vendor blocks is utilizing the Advanced Process Library (APL) channel driver block FbDrive (FB1784) paired with the technological control block MotSpdCL (FB1854). FbDrive communicates with the inverter via standard PROFIdrive telegrams (Telegram 1 or Siemens Telegram 352), passing unpacked process data directly to MotSpdCL for visualization via standard APL faceplates and block icons.

Table of Contents

APL Drive Integration Architecture: FbDrive vs. Dedicated Vendor Blocks

In modern process engineering running SIMATIC PCS 7, variable frequency drives (VFDs) such as the SINAMICS G120 modular drive series (comprising Power Module PM240/PM250 and Control Unit CU240E-2 / CU250S-2) require seamless integration into both automation logic and operator graphics. Historically, projects deployed specialized blocks such as SINAG120 or legacy Drive ES SIMO_MM4. However, proprietary blocks create version migration friction and non-standard faceplate interfaces.

In the PCS 7 Advanced Process Library (APL), Siemens introduced a decoupled, standardized drive integration model:
1. Channel Driver Block FbDrive (FB1784): Interfaces directly with the physical peripheral hardware over PROFIBUS-DP or PROFINET IO using standard cyclic process data (PZD) telegrams. It handles status word unpacking, control word packing, driver diagnostic buffering, and acyclic dataset reading (e.g., retrieving exact drive trip fault codes via DPV1 / RDREC).
2. Technological Control Block MotSpdCL (FB1854): Implements speed-controlled motor functionality, interlock evaluation (Permit, Protect, Interlock), operating modes (Auto, Manual, Local, Out of Service), setpoint ramping, and alarm logging.
3. Standard APL Visualization: Connects natively to @MotSpdCL/1 block icons and @pg_MotSpdCL.pdl faceplates, eliminating the need to design custom graphic objects.

PROFIdrive Telegram Selection and Mapping Table

Select the appropriate standard or manufacturer-specific telegram for SINAMICS G120 integration:

Telegram TypeLength (PZD In / Out)Words Transmitted (Controller to Drive)Words Transmitted (Drive to Controller)Recommended Application in PCS 7Standard Telegram 12 / 2 PZDSTW1 (Control Word), NSOLL_A (Speed Setpoint)ZSW1 (Status Word), NIST_A (Actual Speed)Basic speed control without current or torque feedbackStandard Telegram 202 / 6 PZDSTW1, NSOLL_AZSW1, NIST_A, IAIST (Current), MIST (Torque), PIST (Power)Speed control with complete energy/electrical telemetrySiemens Telegram 352 (Recommended)6 / 6 PZDSTW1, NSOLL_A, Control Words 3-6ZSW1, NIST_A, IAIST, MIST, WARN_CODE, FAULT_CODEStandard PCS 7 Choice: Direct drive fault/warning code reportingSiemens Telegram 3504 / 4 PZDSTW1, NSOLL_A, Control WordsZSW1, NIST_A, IAIST, WARN_CODECompact drive telemetry with current monitoring

Procurement notice: Always verify Control Unit MLFBs (e.g., CU240E-2 DP 6SL3244-0BB12-1PA1 or CU240E-2 PN 6SL3244-0BB12-1FA0) against official Siemens equipment schedules.

Configuring Telegram 352 in HW Config and Parameterizing FbDrive

Follow this procedure to configure hardware and parameterize the channel driver:

  1. Configure Inverter in HW Config:
    * Open HW Config in STEP 7.
    * From the PROFIBUS-DP or PROFINET IO catalog, locate the SINAMICS G120 station (or insert using GSD/GSDML file).
    * In the slot configuration table, assign Siemens Telegram 352 (PZD 6/6).
    * Note the starting peripheral I/O addresses (e.g., Input PIW 512, Output PQW 512).
    * Save and compile HW Config.
  2. Instantiate FbDrive in CFC:
    * Open the target technological CFC chart.
    * From the APL library (PCS 7 AP Library > Channel), insert FbDrive (FB1784).
    * Parameterize input LAddr with the starting peripheral address configured in HW Config (512).
    * Set parameter Telegram to 352.
    * Configure PZDIn1 through PZDIn6 to receive the peripheral input words, or let the PCS 7 Generate Module Drivers wizard wire the driver automatically.

Connecting FbDrive to MotSpdCL and Driving Standard APL Faceplates

Wire the technological logic to provide complete operator control:
1. From the APL library (PCS 7 AP Library > Control), drag MotSpdCL (FB1854) into the chart.
2. Interconnect driver outputs to technological inputs:
* Connect FbDrive.PZD_In structure to MotSpdCL.PZD_In.
* Connect MotSpdCL.PZD_Out structure to FbDrive.PZD_Out.
3. Interconnect status and fault reporting:
* Connect FbDrive.Fault to MotSpdCL.Trip.
* Connect FbDrive.Warn to MotSpdCL.WarnAct.
* Connect FbDrive.ActSpd to MotSpdCL.Rbk (Readback actual speed).
4. Run Compile OS:
* The compiler detects MotSpdCL, automatically places @MotSpdCL/1 in the designated process picture, and maps all structure tags to @pg_MotSpdCL.pdl.

Verification

Verify drive operation from the OS faceplate:
1. Power up the SINAMICS G120 drive and verify zero active hardware faults (solid green RDY LED on Control Unit).
2. Open WinCC Runtime and locate the motor block icon: Confirm it displays grey (Stopped) with zero active alarms.
3. Open the MotSpdCL faceplate: Switch to Manual Mode, enter a speed setpoint of 50.0%, and click Start.
4. Confirm that the drive accelerates to 50% speed: The block icon turns solid green (Running) and actual speed readback displays 50.0%.
5. Trigger a drive safety trip or disconnect motor cable: Verify that the faceplate immediately reports Fault, the icon flashes red, and the active Siemens fault code (e.g., F07900) is displayed.

Limitations and Operational Precautions

  • Never connect the inverter's Safe Torque Off (STO) safety inputs to standard software outputs on FbDrive or MotSpdCL; functional safety interlocks require a fail-safe controller (S7-400F / S7-410F) and PROFIsafe telegrams (e.g., Telegram 30 / 900).
  • Ensure drive ramp times in drive parameters P1120/P1121 are shorter than or coordinated with MotSpdCL ramp rates (SP_UpRmp / SP_DnRmp) to avoid velocity readback tracking errors.
  • When using Telegram 352, ensure drive parameter P2000 (reference frequency) in the G120 inverter matches the scaling factor configured on FbDrive (typically 50.0 Hz = 16#4000 = 100%).

Engineer FAQ

What is the difference between FbDrive and Drive ES MotSpdCL?

FbDrive is the standard, native APL channel driver included with standard PCS 7 licenses, requiring no optional packages. Drive ES MotSpdCL is part of the Drive ES PCS 7 APL optional package, providing extended parameter uploading and graphic commissioning views.

Can FbDrive read actual motor current from the G120?

Yes. When configured with Telegram 352 or Telegram 20, word PZD3 contains actual current (IAIST), which FbDrive scales and outputs as a REAL process variable.

What block should be used if I am running classic STEP 7 and WinCC instead of PCS 7?

For standard STEP 7 and WinCC (TIA or classic), use the SIMATIC Industry Library (IL) block S7MotSpdC or the Drive ES Basic function blocks.

Technical References

Related Articles

Related Tags

  • SINAMICS G120
  • FbDrive
  • MotSpdCL
  • APL
  • Telegram 352
  • PROFIdrive
  • PCS 7 Drives
6 respuestas