Executing V90 PN RAM-to-ROM Save via SINA_PARA Block

SINAMICS V90 PN servo drives do not expose the legacy Copy RAM to ROM command at the same parameter index used by SINAMICS S120 or G120. Where an S120 accepts a non-volatile save request through p0971, the V90 PN firmware accepts the equivalent command through parameter p0977. When a SIMATIC S7-1500 / ET 200SP CPU 1512 writes drive parameters through the SINA_PARA function block from the SINAMICS DriveLib, the values land in volatile RAM and are lost on the next 24 V power cycle unless an explicit RAM-to-ROM save is triggered. This article consolidates the canonical procedure, the block wiring details, the correct AxisNo for V90 PN, and the field-proven diagnostics for the most common faults.

1. When to Use SINA_PARA for Save vs. Other Paths

The SINAMICS V90 PN exposes three different ways to commit RAM contents to non-volatile storage:

All three paths execute the same firmware routine and accept or reject the request using the same error codes. For a controller-driven architecture the SINA_PARA path is the only deterministic, repeatable option.

2. Prerequisites

• TIA Portal: V15.1 or later (V16, V17, V18, V19 confirmed working). V15.0 lacks the SINAMICS DriveLib revision that ships with the current S7-1500 HSP.
• SIMATIC controller: S7-1500 CPU or ET 200SP CPU 1512 with a PROFINET interface configured and the V90 PN assigned as a PROFINET IO device. CPU firmware 2.6 or later recommended for the DriveLib block generation.
• SINAMICS V90 PN firmware version 1.04 or later. The p0977 RAM-to-ROM mechanism is documented in the SINAMICS V90 Operating Instructions (01/2015 edition, PDF attachment 108586837) and is verified on field revisions V1.05 and V1.06.
• GSDML for the V90 PN installed in TIA Portal. The file pattern is GSDML-V2.xx-Siemens-Sinamics_V90_PN-xxxxx.xml. Current GSDML-V2.42 builds support the Standard Telegrams 1, 2, 3, 102, 105, and 106.
• SINAMICS DriveLib library installed. The library is delivered with the SINAMICS S120 HSP and as a standalone package on the Siemens Industry Online Support portal. The relevant blocks are SINA_PARA, SINA_SPEED, SINA_POS, SINA_BRAKE.
• PROFINET IO AR established between the controller and the V90 PN; standard diagnostics must show green before any acyclic access is attempted.

3. Why V90 PN Uses p0977 Instead of p0971

The "Save parameter set in non-volatile memory" function is mapped to different parameter numbers across the SINAMICS family. S120 and G120 use p0971; the V90 PN intentionally omits p0971 and routes the same internal routine through p0977 because the V90 PN parameter model is intentionally compressed.

Attempting to write p0971 on a V90 PN with SINA_PARA returns parameter access error code 0x1002 ("parameter does not exist") and the request is rejected without state change. The V90 PN parameter list, available as Siemens entry 109748475, contains p0977 but not p0971.

4. SINA_PARA Function Block Reference

The SINA_PARA block is a universal Siemens library block that performs a single acyclic read or write against one drive parameter over PROFINET. Internally it uses the PROFIdrive parameter channel (record data) defined by IEC 61784-2 and the PROFIdrive profile V4.2.

4.1 Block Inputs

4.2 Block Outputs

5. Determining the Correct Axis Number

The AxisNo input is the most common source of SINA_PARA errors. V90 PN on PROFINET uses a fixed axis number independent of the assigned PROFINET device number or the IP address. For every standard telegram, every SINA block, and every acyclic access, the V90 PN always reports AxisNo = 2.

If AxisNo is left at the default value of 1 (the S120 commissioning default), SINA_PARA returns error 0x1001 ("axis / DO does not exist") and no write is performed. This single misconfiguration accounts for the majority of "SINA_PARA does nothing" field calls.

6. Step-by-Step Procedure

Step 1 — Install DriveLib and Place SINA_PARA

1. In TIA Portal, navigate to Options → Manage Library → Global libraries.
2. Open the supplied SINAMICS DriveLib package, e.g. SINAMICS_DriveLib_Vxx.zip.
3. Drag SINA_PARA from the library into a cyclic OB (typically OB1) or a dedicated OB for acyclic parameter handling.
4. Create a global data block (e.g. dbSinaParaV90) with optimised access and instantiate SINA_PARA inside it.

Step 2 — Declare the Instance

DATA_BLOCK "dbSinaParaV90"
{ S7_Optimized_Access := 'TRUE' }
VERSION : 0.1
NON_RETAIN
   VAR
      iSinaPara : "SINA_PARA";
   END_VAR
END_DATA_BLOCK

Step 3 — Wire the Save Request

Trigger the save on a rising edge of a user flag. Never hold Execute continuously; the drive takes 1–8 seconds to commit the parameter set and over-triggering generates acyclic traffic noise and may collide with other acyclic consumers such as V-ASSIST.

// One-shot rising-edge detector for the user "save now" signal
IF "bSaveV90RamToRom" AND NOT "bSaveV90RamToRom_old" THEN
    "dbSinaParaV90".iSinaPara.Execute  := TRUE;
    "dbSinaParaV90".iSinaPara.Mode     := 1;     // 1 = write
    "dbSinaParaV90".iSinaPara.AxisNo   := 2;     // V90 PN axis number
    "dbSinaParaV90".iSinaPara.ParamNr  := 977;
    "dbSinaParaV90".iSinaPara.SubIndex := 0;
    "dbSinaParaV90".iSinaPara.Value    := 1;     // 1 = save RAM to ROM
END_IF;

"bSaveV90RamToRom_old" := "bSaveV90RamToRom";

// Reset Execute after one cycle to prevent retriggering
"dbSinaParaV90".iSinaPara.Execute := FALSE;

IF "dbSinaParaV90".iSinaPara.Done THEN
    "bSaveV90Complete" := TRUE;
END_IF;

IF "dbSinaParaV90".iSinaPara.Error THEN
    "wSaveV90ErrorId" := "dbSinaParaV90".iSinaPara.ErrorId;
    "bSaveV90Fault"   := TRUE;
END_IF;

Step 4 — Wait for Completion

The V90 PN commits the parameter image within 1–8 seconds, depending on the number of parameters modified since the last save. During the commit:

• The PROFINET connection stays online; standard telegrams continue to exchange data.
• Subsequent SINA_PARA requests on other parameters are queued and return Busy = TRUE until p0977 returns to 0 internally.
• The drive remains in normal run mode and follows active setpoints.

Step 5 — Poll p0977 to Confirm Save Finished

Read p0977 in mode 0. A returned value of 0 confirms that the firmware has finished the commit and that the parameter image is now in ROM. A returned value of 1 indicates the drive is still processing and the PLC should wait and re-poll after 500 ms.

7. Verification

Three independent verification paths exist after triggering p0977 = 1. Any one of them is sufficient; running all three is the standard commissioning test sequence.

7.1 Read-back via SINA_PARA

Configure a second SINA_PARA instance (or toggle the same instance to read mode after the write completes). Trigger a read of p0977. Expect Value = 0 once the save has finished.

7.2 Power-Cycle Test

1. Note the current value of a parameter that was just written by the PLC (e.g. p2647 mechanical system ratio, or p2572 maximum velocity).
2. Cycle 24 V to the V90 PN (full power-down, not just PROFINET stop).
3. On reboot, read the same parameter again from the PLC or V-ASSIST. The value must match the last PLC write.

7.3 V-ASSIST Confirmation

1. Open V-ASSIST and connect online to the V90 PN.
2. Open Online → Parameter list; if prompted, choose All parameters.
3. Confirm that the values displayed match the most recent PLC writes.
4. If the values revert to factory defaults, the save was never executed.

8. Troubleshooting Matrix

9. Edge Cases and Field Notes

• Active faults block save: A V90 PN cannot commit a RAM image to ROM while a fault is active. Clear all F-codes and the relevant warnings (e.g. F30002 overvoltage, F7452 safety configuration incomplete, F01105 commissioning parameter active) before triggering p0977.
• Commissioning mode blocks save: Save requests issued while p0010 ≠ 0 are accepted by the firmware but may not persist beyond the next mode change. Always return p0010 to 0 after commissioning.
• V-ASSIST hides p0977 by default: The standard filter in V-ASSIST excludes p0977. Switch the filter to All parameters to confirm presence; the parameter is still accessible through SINA_PARA regardless of the local filter.
• Concurrent access collisions: If V-ASSIST and the PLC attempt to save at the same instant, both writes are accepted but only the latest image is retained. For deterministic behavior, lock the V-ASSIST online connection during PLC-driven commissioning or coordinate through a PLC-held semaphore bit.
• Third-party controllers: If the controller is a non-Siemens PROFINET IO controller without the DriveLib, the same operation can be issued using the raw PROFINET record-data read/write services (record indices 0xBF02, 0xBF03, 0xBF0A). Refer to the SINAMICS V90 Operating Instructions for the parameter channel mapping.
• Save cycle time: Allow up to 8 seconds for a full save in production programs. Buffer acyclic traffic by gating other SINA_PARA calls on the completion of the save.

10. Compatibility with Other SINAMICS Blocks

SINA_PARA is normally used alongside other blocks of the SINAMICS DriveLib. The most common combinations on a V90 PN:

SINA_PARA can write any writable V90 PN parameter including p2647 (mechanical system ratio), p2572 (maximum velocity), p2573 (maximum acceleration), p1220 (ramp-up time), and the safety-related p9601 if the safety expansion is enabled.

11. Safety Considerations

A RAM-to-ROM save initiated through SINA_PARA must not be used as a substitute for the certified parameter save in safety applications. For SINUMERIK Safety Integrated (STO, SS1, SBC) on a V90 PN with the safety expansion module, parameter commit must follow the procedure defined in the V90 Safety Integrated Function Manual, which includes additional checksum verification steps. Saving safety parameters through SINA_PARA is technically possible but does not satisfy the safety acceptance test; the safety commissioning log must record the V-ASSIST or BOP-initiated save explicitly.

12. Frequently Asked Questions