SINAMICS Application Examples Library: S120, G120, V90 Reference

Siemens publishes a centrally curated library of SINAMICS application and engineering examples covering the S, G, and V drive families and their integration into SIMATIC S7-300, S7-400, S7-1200, and S7-1500 controllers, as well as third-party platforms such as Allen-Bradley CompactLogix and ControlLogix. Each entry ships with tested function blocks, configuration screenshots, parameter assignments, hardware/software bills of material, and HMI screens. Engineers reuse the blocks for scaling setpoints/actual values, parameter access, and motion primitives instead of writing converters and telegram handlers from scratch.

The library lives at siemens.com/sinamics-applications and is filterable by drive type, PLC family, communication protocol, drive function (speed, position, safety, HVAC), and safety category. A complementary reference is published through the Siemens Industry Online Support entry SINAMICS/SIMATIC - Automation of engineering tasks in machine building.

SINAMICS Drive Families Covered

The application library distinguishes four primary drive families plus the basic V20 and V90. Each family is matched to typical power, control, and safety class.

Function Block Library: DriveLib, SINA_Speed, SINA_Pos, SINA_Para

The DriveLib library is the unified function-block collection used across TIA Portal examples (Siemens support entry 68034568, "SINAMICS blocks for SIMATIC S7-1200/S7-1500"). It contains:

• SINA_Speed - speed control via Siemens telegrams 1, 2, 3, 5, 102, 105, 106, 116, 118, 125, 126, 136, 138, 139, 166, 220, 352, 370, 371, 999 with scaling, ramp, enable, and fault/ack handling.
• SINA_Pos - absolute and relative positioning on top of EPOS (basic positioner) in telegram 111. Inputs include position setpoint, velocity override, mode selection, jog, reference, and traversing block selection.
• SINA_Para - generic parameter read/write over acyclic services (PROFINET/PROFIBUS record data), including the request/response header format used by the SINAMICS parameter channel (DO = 47, parameter number, index, subindex).

For S7-300/400 with STEP 7 V5 (Classic), the legacy FB283 and the supporting FC284/FC285/FC286 blocks ship with the S120 application example collection and implement the EPOS traversing-block mode, direct setpoint input (MDI), reference point approach, and jogging functions against telegram 111.

SIMATIC S7-300 / S7-400 Integration (STEP 7 V5 and TIA Portal)

Two parallel integration paths exist for the older S7-300/400 controllers:

1. STEP 7 V5 (Classic) projects - reference examples use FB283 for EPOS, FC284-286 for scaling, and the SIMATIC/SINAMICS example project archive. The S120 positioning example (PROFINET/PROFIBUS, Safety Integrated via terminals, HMI) is built on this stack.
2. TIA Portal V11+SP2 / V12 projects - the G120 speed control example for S7-300 with PROFINET/PROFIBUS and Safety Integrated is delivered as a TIA Portal V11+SP2 or V12 archive. The G120/G120C/G120D positioning example uses CU250S-2 with firmware V4.6 and ships with PROFIsafe configuration, technology objects (TO) for S7-1500, and a WinCC HMI faceplate.

The S7-300/400 examples typically use the following components in the bill of material:

• CPU 315-2 PN/DP or CPU 317-2 PN/DP (for PROFINET examples) / CPU 314C-2 DP (for PROFIBUS examples)
• ET 200S or ET 200M distributed I/O for the Safety Integrated wiring path
• DriveLib blocks imported into the S7 program; FB283 and FC284-286 for the V5-based EPOS examples

SIMATIC S7-1200 / S7-1500 Integration with Startdrive

For S7-1500 (and S7-1200 in supported motion scopes) the examples use Startdrive for drive device configuration, online commissioning, and the integrated trace. The G120 speed-control example with S7-1500 covers:

• PROFINET IRT or PROFIBUS DP with telegram 1 (speed control) and telegram 700/701 (PROFIsafe)
• S7-1500 Technology Object (TO) axis configuration: TO_SpeedAxis for V90, TO_PositioningAxis for S120 with EPOS
• PLCopen motion blocks MC_Power, MC_MoveVelocity, MC_MoveAbsolute, MC_Stop, MC_Reset for the S7-1500 motion axis
• WinCC Comfort/Advanced faceplate with start/stop, setpoint entry, status, fault buffer, and Safety Integrated status

For V90 with S7-1200, the example uses the pulse/direction interface (control word STW1.0-7 over the SINAMICS V90 PN control word bit assignments) with an S7-1200 PTO (Pulse Train Output) on-board or via signal board, plus an HMI for setpoint and feedback. The V20 example instead uses the USS protocol over RS485 from an S7-1500 CM PtP module or ET 200SP PtP module, with the USS_Port_Scan, USS_Drive_Control, and USS_Read_Drive_Param blocks from the SIMATIC USS library.

Communication Protocols: PROFINET, PROFIBUS, EtherNet/IP, CANopen, USS

Each application example is bound to a specific bus protocol. Mixing protocols requires regenerating the GSD/GSDML import and revisiting the telegram configuration.

The EtherNet/IP example set includes a complete project for Allen-Bradley CompactLogix and ControlLogix, with the drive EDS file imported and explicit messaging ladder logic for parameter access.

Safety Integrated: PROFIsafe, SS1, STO, SLS, SLP

Two safety paths are documented across the application library:

1. Safety Integrated via terminal - the safe inputs (Safe Torque Off, Safe Stop 1) are wired directly to the drive's X130 (CU310-2) or X132/X136 (CU320-2, CU250S-2) terminals. The PLC handles the rest of the safety logic but does not carry the safety signal over the bus. The S120 positioning example with S7-300/400 uses this path.
2. Safety Integrated via PROFIsafe - telegram 30 (16-bit) or telegram 31 (32-bit) for S7-300/400 PROFIsafe, or telegram 700/701 for PROFINET PROFIsafe. The G120 CU250S-2 positioning example with S7-300/400 (STEP 7 V5) and the G120 speed control example with S7-1500 use PROFIsafe, with the F-CPU handling safe logic, F-IO, and F-runtime groups.

Common safety functions exercised in the examples:

• STO (Safe Torque Off) - r9773, r9873, r9881
• SS1 (Safe Stop 1, time-controlled and acceleration-monitored) - p9556, p9560, p9651, p9652
• SLS (Safely-Limited Speed) - p9531, p9546, p9547
• SLP / SP (Safely-Limited Position / Safe Position) - S120 with SLP/SBT extensions
• SOS (Safe Operating Stop) - S120 with extended safety

Cross-check after commissioning: r9773 (S120/CU250S-2 Safety Integrated status) must report enabled; the F-CPU's DB for the F-runtime group must show 0 faults. The Siemens acceptance test (SISTEMA library) is bundled in the example project.

Cross-Platform Integration: Allen-Bradley CompactLogix / ControlLogix via EtherNet/IP

For plants running Rockwell Automation controllers, the library provides two main examples:

• SINAMICS S120 speed control with CompactLogix / ControlLogix via EtherNet/IP - implicit messaging using Output Assembly 1 (4 bytes control, 4 bytes speed ref) and Input Assembly 2 (4 bytes status, 4 bytes speed actual) plus the configuration assembly. RSLogix 5000 / Studio 5000 ladder logic with MSG instructions for explicit parameter access over CIP. The EDS file is included in the example project.
• SINAMICS G120 speed control with CompactLogix / ControlLogix via EtherNet/IP - same pattern, with CU250S-2 supported. The example uses the standard EIP assemblies for speed control and includes MSG blocks for acyclic parameter read/write.

Typical explicit message path for parameter read:

Service 0x4B (Read_Attribute_Single) or 0x4C (Read_Attribute_Service); Class 0xA2 (Parameter Object), Instance = parameter number, Attribute 1 (parameter value), Element = subindex. CIP connection path example: 192.168.1.10,1,2,192.168.1.20,0 (backplane slot, port, IP, port 0).

Drive Control Chart (DCC) Applications: GMC, Camming, Gearing, 1:1 Synchronism

Drive Control Chart is the Siemens IEC 61131-3 style logic editor that runs natively on the SINAMICS Control Unit. The application library ships a DCB library called "GMC" (Generic Motion Control) which provides:

• 1:1 synchronism between a master and a slave (electronic gear with ratio)
• Cam disc synthesis and runtime cam profile (camming)
• Positioning state machine with home, jog, absolute/relative move, stop, fault
• Gearing with phase offset and on-the-fly ratio change

DCC examples run without any PLC round-trip - the axis, encoder, drive, and safety all stay on the Control Unit. This reduces bus jitter for high-speed synchronization, especially in printing, packaging, and converting machines. The DCB library is loaded into the drive with STARTER, Startdrive, or the SCOUT engineering tool (for S120 with DCC option).

Key DCC capabilities exposed by the GMC library:

• Master source selection (encoder 1, encoder 2, virtual master)
• Slave axis reference (speed/position) and ratio block
• Cam profile interpolation (linear, cubic spline, 5th order)
• Trigger inputs for registration mark, print mark, or external event

S120 Web Server: User-Defined Web Pages

The SINAMICS S120 with CU320-2 PN or CU310-2 PN exposes a built-in web server on HTTP port 80. The default web pages show drive diagnostics, alarm history, and parameter lists, but the application example for "S120 web server - creating user-defined web pages" demonstrates how to publish drive parameters in a custom HTML view that is loaded into the CU firmware. The CU acts as a static file server, serving the user pages alongside the integrated diagnostics.

Implementation steps:

1. Build a folder of static HTML, CSS, and JavaScript files following the Siemens naming convention (e.g., index.html, config.json, subfolders for images and icons).
2. Add AWP (Automation Web Pages) variable references to the HTML so values are substituted at request time, e.g. :=$00001:00002.HexValue for parameter r2, or :=$00001:00025.HexValue for r25. The leading 00001 is the SINAMICS parameter object class.
3. Pack the folder using the WinCC Web Loader tool, transfer it to the CU via S7 web server upload or by importing the file into the project with the "Web pages" folder in Startdrive / STARTER.
4. Activate the user pages on the CU (default port 80) and load the page from a browser at http://<cu-ip>/index.html.

This path is used for remote diagnostics cabinets, operator panels with a tablet browser, and machine-builders who want a branded diagnostics view without buying a full SCADA license.

HVAC Application Library: SINAMICS G120P

The G120P drive is the HVAC-specific variant of the G120 family, with a CU230P-2 control unit, integrated PID controller, real-time clock, and a firmware feature set tuned for fans and pumps. Three application examples ship in the library:

1. Closed-loop control of exhaust air fans - PID loop on differential pressure across filters; setpoint derived from room occupancy and duct pressure sensor.
2. Closed-loop control of a tunnel / car park fan - CO / NO2 sensor feedback, ramp-limited setpoint change, fire override (bypass), ECO mode scheduling.
3. Closed-loop control of a staircase fan - smoke exhaust, time-based and event-based setpoint, redundant fan staging.

These examples demonstrate the free function blocks (FFB) inside the CU230P-2 for sequencing fans, the analog input scaling, and the integrated PID controller with auto-tuning. They also use the G120P-specific parameters p2200 (PID enable), p2253 (PID setpoint source), p2261 (PID actual value source), p2271 (PID proportional gain), and p2274 (PID integral time).

XML Parser and LabVIEW Connectivity

Two auxiliary examples round out the library:

• SINAMICS XML Parser - converts the parameter export from STARTER / Startdrive (XML format with class, parameter, subindex, text, value, default) into clear-text listings for documentation or import into a third-party tool. Useful when an EPLAN macro library or PLC data-block generator needs a current parameter list.
• PROFINET connection to LabVIEW - bridges the SINAMICS PROFINET device with NI LabVIEW DSC using either the NI OPC UA Server or a dedicated PROFINET driver. Useful for test stands and laboratory automation.

GSDML File Generation for S120, S150, G130, G150

Cabinet-format drives (S120 chassis, S150, G130, G150) with a CU320-2 typically have their GSDML generated per project, because the number and type of line modules, motor modules, and encoders define the slots. The application example "SINAMICS G/S: Generating GSDML files for S120, S150, G130, G150" walks through the STARTER / Startdrive export of the device description and the integration into TIA Portal with the correct module layout.

Application Matrix: Drive / PLC / Protocol / Function

The complete coverage matrix at the time of this reference is summarized below.

Accessing the Application Library

Entry points to the library:

1. Main portal: siemens.com/sinamics-applications
2. Siemens Industry Online Support overview: Automation of engineering tasks in machine building
3. DriveLib blocks: Siemens support entry 68034568 (SINA_Speed, SINA_Pos, SINA_Para for S7-1200/S7-1500)

Use the filter combination to narrow to your drive (S120, S150, G120, G120C, G120D, G120P, G130, G150, V20, V90), PLC (S7-300, S7-400, S7-1200, S7-1500, ET 200SP, CompactLogix, ControlLogix), bus (PROFINET, PROFIBUS, EtherNet/IP, CANopen, USS, Modbus), and function (speed, position, EPOS, safety, HVAC, DCC, web server).

Field Commissioning Checklist

When bringing a downloaded example to a real cabinet, walk through this list before closing the panel:

1. Open the project and confirm the device versions match your hardware (article numbers) and firmware (e.g., CU240S-2 FW V4.7, CU250S-2 FW V4.6 or later).
2. Update the drive telegram selection (p0922 on the drive) to match the slot in TIA Portal; download the project and look for "drive does not match configured telegram" warnings.
3. For S7-1500 examples, regenerate the technology object axis if the mechanical configuration (load gear, pitch, leadscrew) differs from the example default.
4. Wire the encoder (HTL, TTL, SSI, EnDat 2.1/2.2, DRIVE-CLiQ) and configure p0400 (encoder type) and p0420 (encoder configuration) per the example values, not the factory defaults.
5. For Safety Integrated, perform the acceptance test with SISTEMA and archive the signed PDF report with the project archive.
6. Run the drive under no load: jog forward, jog reverse, verify direction with the encoder sign. Swap two motor phases if the direction is wrong rather than flipping the encoder sign on S120 (keeps DRIVE-CLiQ naming intact).
7. For EtherNet/IP examples with Allen-Bradley, import the EDS, configure the IP, set the DLR (Device Level Ring) topology if used, and verify the implicit connection size in the I/O tree matches the example (e.g., 4 bytes output, 4 bytes input for speed control).
8. Save a backup of the drive parameters with STARTER / Startdrive ("Upload to PG") and the PLC project to the project archive; include the SISTEMA report and the S7 safety acceptance test as part of the as-built documentation.

FAQ