Monitoring SINUMERIK 840D Motor Current and Power via Profibus

Overview

Extracting live motor current and power data from a SINUMERIK 840D controller over Profibus requires direct access to NCK (Numerical Control Kernel) system variables. Unlike PLC-side data exposed through the DP slave image, drive-side current and torque values are mapped to NC variables such as $AA_CURR, $AA_TORQUE, $AA_POWER, and the corresponding axis-specific load data blocks. This article describes the variable set, the NCK version constraints, the Profibus DP coupling, and a LabVIEW acquisition workflow that reads these values from a connected server PC.

SINUMERIK 840D System Architecture Relevant to Drive Data

The 840D controller consists of three logical units that determine how drive data becomes accessible:

• NCK – the numerical control kernel. Holds axis-specific state, setpoints, and actual value variables prefixed with $AA_ (axis actual) and $VA_ (VO actual).
• PLC – a SIMATIC S7-300 subsystem. Exchanges process data with the NCK through the NC/PLC interface (DP1 / DP2 / DP3 internal couplings).
• Drive bus (Profibus) – the external DP master line to which a server PC can be attached as a DP slave or via a Profibus-to-Ethernet gateway.

Motor current and torque are drive-side signals. The NCK mirrors them into its variable pool at each IPO cycle so user programs (compile cycles, HMI, OA applications, and external readers) can address them symbolically rather than parsing raw telegram slots.

NCK System Variables for Current and Power Monitoring

The following NCK variables are the primary access path for drive load data. Indices map to the logical axis (1 = X, 2 = Y, 3 = Z, 4 = A, 5 = B, 6 = C, and so on for spindle and additional axes up to the configured maximum).

For the spindle, the same prefix pattern applies but with the spindle index reserved in the machine data. Typical access is $AA_CURR[$SN_SPIND_ASSIGN_TAB[0]] or direct read of $AA_CURR[31] when the spindle is the highest-indexed axis, as commonly documented in NCK version 6 projects.

NCK Version Compatibility Matrix

Variable availability and unit scaling depend on the NCK software version. The 840D and 840D-sl line shipped through several major releases with different default units (metric/imperial) and additional variables for power monitoring introduced incrementally.

Profibus Communication Setup

Two architectural patterns are deployed in the field:

1. Direct DP slave coupling – the server PC hosts a Profibus DP slave card (e.g., Siemens CP5611, CP5621, or compatible Hilscher / Siemens PC cards). The 840D is the DP master; the PC is the slave. Telegrams 370 (drive actual values) or custom PPO types carry the desired signals.
2. Profibus-to-Ethernet bridge – a DP/DP coupler or Profinet gateway translates the bus to TCP/IP. The server PC reads data over Ethernet using OPC or a vendor SDK.

DP Slave Telegram Configuration

For direct drive data extraction, configure the slave with a PPO type that includes PZD (Process Data) words. A typical configuration for axis actual values:

• PPO type 5: 2 PKW (parameter) words + 6 PZD (process data) words
• PPO type 4: 2 PKW + 4 PZD

PZD slot 1 / 2 generally carry status word and actual speed; the additional PZD slots are mapped to actual current, actual torque, and DC-link voltage as configured in SINUMERIK Commissioning tool under Drive > Telegram configuration.

GSD File and Node Address

Install the Siemens siem80d5.gsd (or version-appropriate) GSD into the PC's Profibus configurator (COM PROFIBUS / STEP 7 HW Config). Assign a free node address (e.g., 6) that does not conflict with the NCK's own DP master (default 1) or HMI (default 2). The PLC's Profibus is address 3 in default 840D layouts.

Data Acquisition with LabVIEW

LabVIEW supports two practical approaches for SINUMERIK 840D data extraction:

1. Profibus raw read via LabVIEW DSC – using a National Instruments Profibus master interface (e.g., NI PXI-8531) with the NI-Profibus driver. Telegrams are decoded in LabVIEW Real-Time and scaled according to SINAMICS drive scaling rules.
2. OPC / S7 variable bridge – the server PC runs an OPC DA/UA server (e.g., Softing S7 OPC, Kepware SIEMENS TCP/IP Ethernet Driver) that exposes NCK variables. LabVIEW's DSC Module binds OPC tags to shared variables. This is the most common production path because it does not require additional Profibus hardware on the PC.

Reading NCK Variables via OPC

The NCK exports a subset of its variables through the /Nck/ path when an OPC server is bound to the 840D's CMI (Configuration Management Interface) or via the SINUMERIK Integrate server. A sample tag address for current:

For the spindle on a machine with spindle at axis index 31:

For active power on the same spindle:

LabVIEW Block Diagram Outline

1. Place an OPC Read or DSC Tag node for each variable of interest.
2. Bundle tags into a cluster and convert from Variant to double-precision (DBL).
3. Apply engineering-unit scaling: raw counts are typically 4000 hex = 100% for current on SINAMICS S120. Convert with:
   I_actual [A] = (raw / 16384) * MD1107 (motor rated current)
4. Write to a TDMS file at 100 ms intervals for trend recording.

Variable Address Mapping Reference

The following table summarizes the read access points used in production deployments. The Item ID column shows the symbolic path exposed by the SINUMERIK Integrate OPC server; the native column shows the NCK variable name.

Configuration Procedure

1. Confirm the controller generation. Open the HMI menu Commissioning > Version and note the NCK software version and the controller type (840D vs 840D sl). This determines the variable set.
2. Enable monitoring access. The system variable access rights are controlled by MD51074 $MN_ACTIVATE_SL_BOX and access level settings in the user interface. In default configurations, $AA_* and $VA_* are read-accessible at user level.
3. Set up the OPC bridge. Install SINUMERIK Integrate / Access MyMachine / OPC UA server on the PC or on a separate node. Configure the CMI connection to the 840D's internal OPC DA server (port 7001 / 7002) or use the OPC UA server on sl controllers.
4. Browse the NCK namespace. In your OPC client (e.g., Matrikon, Kepware, or LabVIEW DSC), connect and browse to /NCK/. Verify that AA_CURR, AA_POWER, and AA_TORQUE items are present for each axis.
5. Read at the IPO cycle. Configure subscription update rate to 10–100 ms to match the IPO cycle (typical 4–20 ms on 840D sl; up to 40 ms on 840D legacy).
6. Scale to engineering units. Apply the formula above using the motor's rated current from MD1107 and rated torque from MD1113 / MD1114.
7. Log to disk. Stream to a TDMS or CSV store for offline analysis.

Verification and Diagnostics

After the data path is live, perform the following checks to confirm signal integrity:

1. Static check: With the machine idle, $AA_CURR values should be within ±2% of zero (offset). Persistent offsets indicate scaling errors or noise pickup on the drive bus.
2. Step response check: Issue a controlled axis move (e.g., 1 mm at 1 mm/s) on axis X. The X current trace should rise briefly while the move executes and return to zero after completion. Y/Z currents should remain near zero.
3. Cross-check with HMI: Open Diagnostics > Axis Diagnostics > Service on the HMI and compare the displayed current and torque to the values read by LabVIEW. Deviation beyond the scaling tolerance (typically 1–2% of rated) indicates MD-side scaling mismatch.
4. Power sanity check: Verify that $AA_POWER ≈ $AA_TORQUE * $AA_VACT[ax] * 2π / 60 / 1000 for a rotating axis. Discrepancy indicates that scaling machine data (MD10240, MD10220) is set differently between variables.

Troubleshooting Matrix

Safety and Operational Considerations

• Drive current data is informational; it must not be used in safety chains (EN ISO 13849-1 / EN 61508). Use SINAMICS Safety Integrated signals for safety paths.
• The server PC must be on a separately protected network segment. Profibus media is not routable; if crossing subnet boundaries, use a certified Profibus-to-Ethernet gateway (e.g., Scalance, Helmholz).
• Personnel accessing drive current data should be qualified per the warning at the head of the monitoring/compensating manual. Drive-level information is not a substitute for the HMI's safety-critical diagnostics.

Extending the Approach Beyond 840D sl

The same NCK variable philosophy applies to SINUMERIK 828D and SINUMERIK ONE controllers. On 828D, the OPC server is built-in and exposes /NCK/ names directly. On SINUMERIK ONE (driven by SINAMICS S120 with Create MyVirtual Machine), the OPC UA server uses the same root namespace and adds per-axis telemetry at higher sample rates (1 kHz native).

For legacy environments with the original 840D (NCK v4–v6) where $AA_CURR is the only available current variable, the recommended approach is to read the variable at IPO cycle and use the scaling formula:

where I_max is the motor's maximum current from MD1108 (current limit).